Skip to content

Commit 9d093d1

Browse files
practices: rename and update reports page
1 parent 39195cb commit 9d093d1

File tree

1 file changed

+7
-5
lines changed

1 file changed

+7
-5
lines changed
Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,24 +1,26 @@
1-
# TPS Reports
1+
# Reports
2+
3+
When a report it required then the person creating that report should know what its value is and who is the audience.
4+
5+
26

37

48
## Identify reports
59

6-
If repeating reports are required to be delivered, they should be identified as early as possilble.
10+
If repeating reports are required to be delivered, they should be identified as early as possible.
711

812
Capture the value the report provides and the stakeholders that will consume the report.
913

10-
Ask those consuming each report what they really want to see and how often.
14+
Ask those consuming each report what they really want to see and how often.
1115

1216
Also consult as to the presentation of the information to ensure that the information can be consumed effectively.
1317

14-
1518
## Identify source data
1619

1720
What information is used to generate the report.
1821

1922
Identify related information that could be useful to the stakeholders and provide examples to stakeholders for feedback.
2023

21-
2224
## Optomise Creation
2325

2426
Ensure that data capture and transformation for the report is as automated as possible, minimising the time it takes to generate each report.

0 commit comments

Comments
 (0)