Set a reporting cut-off
State the date that the report represents. Registers continue to change, so a report needs a consistent point in time. Explain whether overdue means before that date and how the lookahead window is calculated.
Lead with the items needing attention
Put unanswered queries, approval dependencies and delivery risks ahead of routine completed work. For every item needing attention show the source reference, responsible party and next action. A short decision list is easier to use than a pasted register.
Keep the source within reach
Link back to the controlled record. The report is a view of that information, not a second place to maintain it. If something changes after issue, record the change in the source and flag a material correction through the agreed channel.
Finish with decisions and responsibility
Separate work the administrator will follow up from decisions the PM needs to make. End the report with those decisions, owners and dates. The next reporting cycle should explain which open items were resolved and which still need a decision.
See an example
Explore fictional registers and a downloadable weekly report in the sample Control Centre.
Open sample workspace