Ask What Decision the Report Must Support
A reporting schedule should connect an actual information need with the right evidence and timing. Frequent reports can still arrive too late for a decision or ask for data the recipient cannot responsibly collect. Start with the purpose, risk and existing records, then agree the schedule through the actual grant terms.
This is an original fictional design case, not permission to change a current duty. A 60,000-unit, 12-month community-service grant pays half initially and half after an accepted midyear progress note. The recipient maintains a monthly cost ledger and activity register. No other mandatory reporting or incident deadline is supplied.
Compare Three Schedules for the Same Grant
| Proposed Schedule | What It Could Tell the Funder | Burden and Gap |
|---|---|---|
| Monthly narrative, cost report and full receipt copies | Frequent detail and earlier indications of difficulty | Much repeated narrative; twelve full submissions even when no decision uses them; raw records may expose unnecessary personal information |
| Midyear progress/cost note plus end report, with agreed exception notices | Supports the second-payment decision and learning at closeout | Needs clear dates, definition of acceptance and escalation for material problems between reports |
| End report only | Summarizes completed work and costs | Cannot support the specified midyear payment condition; may miss an emerging problem until too late |
For this supplied case, the second proposal better matches the stated decision points, provided the parties agree appropriate risk notices and reviewers can act. This is a reasoned design choice, not a universal recommendation for every grant of this amount. Greater risk, different work or an external duty may require another approach.
Design the Product Before Setting the Date
Name what the midyear reviewer needs: work completed against the agreed plan; spending and commitments on the agreed basis; explanation of material deviations; current risks; decisions or support requested. Use existing cost and activity records where their definitions and coverage fit. Do not demand participant names to demonstrate aggregate activity by default.
Then define the reporting period, submission date, reviewer role, response/clarification window and what acceptance means. In the fictional agreement packet, January-June information is due July 10, with review planned July 15. The parties must test whether the recipient can close its records and the funder can review in that window. An acceptance-dependent payment needs a credible review process; a deadline imposed on the recipient alone does not ensure cash arrives on time.
Estimate the Burden and Test Necessity
Suppose the monthly design requires four staff-hours of narrative and three of compilation each month: 12 × 7 = 84 hours. The two scheduled reports require ten hours each, plus four two-hour internal checks: 20 + 8 = 28 hours. These fictional estimates exclude investigation and exceptional notices. A 56-hour difference identifies a question, not proof the lighter design is adequate. If the omitted information manages a consequential risk, redesign the collection rather than discard it because it takes time.
For every requested field, ask who will use it, which decision it changes, whether the recipient already holds it and whether an alternative provides adequate evidence. Drop unused detail before asking a small partner to build a new system. Keep independent finance and safeguarding duties with their own qualified owners; a general progress schedule does not replace them.
Agree Exceptions Without Inventing Deadlines
Define which material changes or incidents require notification under the actual applicable terms, how sensitive details travel, who receives them and who decides what follows. Do not publish a universal number of hours or assume a routine report can wait when a separate duty requires action. If a current grant already demands monthly reports, seek an authorized amendment or clarification before adopting the lighter proposal.
Record the approved schedule, review responsibility and change trigger in the agreement worksheet. Revisit when risk, scope, payment conditions or recipient capacity changes. Use reporting-capacity negotiation when an intermediary faces a different upstream timetable.
Source and Scope
Grantmaking guidance, June 3, 2026, Monitor Your Charity's Grants, addresses risk-related monitoring in England and Wales. The schedules, hours and decision above are fictional; actual terms govern.