Confirm the actual reporting requirement
Start with the current agreement and programme instructions. Record the deadline, reporting period, required format and submission route. Where the agreement uses a relative date, such as a period after an anniversary, confirm how that date is calculated before entering a fixed date.
Keep the funder deadline separate from an internal target. Do not move the external date merely because an internal review slips. If the date or route is unclear, assign a person to seek clarification and retain the answer.
Work backwards from submission
Identify who supplies the financial position, delivery narrative and evidence. Ask those people how much time they need, then reserve time for reconciliation and sign-off. The right lead time depends on the report and team; there is no universal number of preparation days.
Record dependencies explicitly. A report writer may need an approved finance schedule before finishing the narrative. A senior approver may be unavailable on the final day. The calendar should reveal these constraints while there is still time to act.
Give every milestone an owner
An illustrative sequence is: finance cut-off, evidence check, first draft, joint review, approval and submission. Name one owner for each milestone and a deputy where absence would stop the process. Add a route for escalating a missed internal milestone.
Use a shared calendar to show dates, but keep links to the underlying obligations and evidence register. The calendar tells the team when to act; the register explains what the action must achieve.
Close the reporting cycle
After submission, save the version actually sent and the receipt or confirmation. Record any follow-up questions and their owners. A report that has been drafted or approved should not be labelled submitted before the submission has occurred.
Review the preparation sequence after the deadline. If an input repeatedly arrives late, change ownership, lead time or the underlying process rather than adding more reminders to the same broken dependency.
A worked example
Fictional illustration. These dates, amounts and requirements are examples, not a rule for every funder or a client result.
| Illustrative milestone | Illustrative date | Owner | Completion evidence |
|---|---|---|---|
| Finance and evidence inputs ready | 17 January | Finance and delivery leads | Dated source schedules |
| Joint review and reconciliation | 21 January | Report owner | Differences resolved or logged |
| Approval | 24 January | Authorised approver | Approval of the final version |
| Funder submission | 31 January | Named submitter | Submitted copy and receipt |
Check your working version
- The reporting period is recorded.
- The funder deadline has a source.
- Inputs, review, approval and submission have owners.
- The calendar allows for staff availability.
- Submission evidence is retained.
Use the free branded workbook (.xlsx) to record your own case. The workbook includes Obligations, Evidence and Exceptions tabs.
Sources and scope
The steps and example above are suggested operating practices. Confirm the actual requirements against your award agreement and current programme instructions. They are not a compliance opinion.
- Charity Commission: internal financial controls (CC8). General context for charities in England and Wales; different jurisdictions and organisations need the relevant guidance.
- National Lottery Community Fund: managing your funding. An example of funder-specific guidance, not a universal rule.
Published for Antony Draper Advisory with AI-assisted drafting. Examples are fictional and have not been presented as client evidence.
Choose a practical next step.
Use the free plan yourself, or talk to Antony about the grant that needs attention. The free call ends with one agreed priority, a suggested owner and the next action.
Get my free grant control plan