How to plan a recurring reporting period on a Gantt chart
Plan one grant or programme reporting period as a reusable Gantt chart: partner data coming in, finance and narrative in parallel, sign-off, the funder's response wait and queries, then copy the plan for the next period.
A report cycle repeats, and so do its waits: partners send their data late and the funder takes time to respond. This guide shows how to plan one reporting period on a Gantt chart so you can reuse it every period and see which wait sets the closing date.
The short version
- Plan one period as a full chart and reuse it, copying the plan for each period.
- Put the partner data behind one milestone and link only the work that needs it to that gate.
- Start the chasing task part way into the partner wait with a start-to-start link.
- Give the funder's response and the queries a duration each, and allow for a second round in the query task.
- Fix the first start and the due date, then compare the finish the chart gives with the date you need.
Plan one period, then reuse it
A reporting period is limited by two things the team does not control. The first is the data that partners send in. The second is the funder's response after you submit. The report can be written, checked and polished, and the period still cannot be closed until both have happened. A timeline helps because it shows how much of the period is waiting and how much is work you can do while you wait.
Plan one period as a complete chart and treat it as the pattern. The tasks that do not need partner data, such as closing the ledgers, gathering evidence and drafting the narrative, start as soon as the calendar is agreed. The tasks that do need it, such as reconciling spend and adding partner figures to the draft, wait for a single milestone, "Partner data received". That milestone is the gate. Everything that depends on it is linked to it, not to the task before it, so a late return moves exactly the work that needs the data.
The wait for the partners should not be passive. Give the follow-up its own task and start it part way into the wait with a start-to-start link, so that early returns are read and missing ones chased while the rest are still being prepared. After submission the funder's side is also a task: a wait with a duration, followed by a task for answering queries. A Gantt chart cannot draw a loop, so if a round of questions usually comes back with a second round, give the query task a duration that allows for it rather than adding the loop.
The example below is the grant reporting template: 20 tasks in five groups. After it, the financial reporting process shows the loops a Gantt chart leaves out, such as incomplete inputs going back to the consolidation step. All durations are illustrative working days. Replace them with the time your partners say they need and with what the funder tells you about its own review. A timeline schedules the work. It does not make a report accepted, compliant or approved, and it does not replace the funder's rules about what must be reported and when.
For the next period, copy the whole chart, change the fixed dates and resize the waits from what you learned. For how a gate and its dependencies work see /guides/gantt-chart-dependencies, and for reading a late return through the plan see /guides/gantt-chart-delays. For planning around a fixed submission date, see /guides/grant-deadline-gantt-chart, and for the funded project itself, /guides/work-packages-and-deliverables-gantt-chart.
One grant reporting period, built in stages
Twenty tasks in five groups, 38 working days in total. Durations and lags are illustrative. Open the spreadsheet panel to see the rows behind each stage.
Partner data is the first gate
"Agree the reporting calendar and templates" (2 working days) leads to "Send data requests to partners" (1), then "Partners prepare and return their data" (8). "Chase and check partner returns" (5) starts 3 working days into that task, so early returns are read while the rest are still being prepared. "Partner data received" waits for both.
Finance starts before the data arrives
"Close the period ledgers" (3) starts as soon as the calendar is agreed, beside the partner tasks. "Reconcile spend with partner returns" (4) needs the closed ledgers and "Partner data received". "Prepare the financial statement" (3) follows, and "Finance figures agreed" is the milestone.
The narrative overlaps the evidence
"Gather activity and outcome evidence" (4) starts after the calendar is agreed, and "Draft the progress narrative" (5) starts 2 working days into it. "Add partner figures to the draft" (2) needs the draft and "Partner data received", so a late return holds this task and what follows it, not the draft.
Review comes before sign-off
"Partner review of the draft" (4) and "Revise after partner comments" (3) come before "Internal sign-off" (3), because a change after sign-off means signing again. "Internal sign-off" also waits for "Finance figures agreed", which is ready 2 working days earlier, so that is the slack if the reconciliation turns up a problem. "Report approved for submission" is the milestone.
The funder decides when the period closes
"Submit through the funder's portal" (1) leads to "Wait for the funder's response" (10) and "Answer the funder's queries" (4), then "Period closed". The longest chain adds up to 38 working days. Give "Agree the reporting calendar and templates" and the submission task fixed starts, then read the conflict flag if the submission cannot be met.
The loops inside a reporting cycle
The financial reporting process as a flowchart. A Gantt chart gives each of these loops a duration, because it cannot draw them.
Inputs must be complete before analysis
"Closed trial balance and operational data available" leads to "Map, consolidate and validate reporting inputs" and then "Inputs reconciled and complete?". When the answer is No, "Investigate data gap or reconciliation" sends the work back to the consolidation step. On the Gantt chart this is the partner data wait and its chasing.
A second loop for the explanation
"Analyse variance and performance drivers" leads to "Variance explanation **supported**?". A No goes to "Obtain commentary and correct analysis" and back to the analysis. On the Gantt chart the narrative tasks need a duration that allows for this correction.
Review and release
"Controller reviews management pack" leads to "Ready for management release?". A Yes goes to "Issue approved financial report", and a No goes to "Return pack for controlled rework", which sends the pack back to the consolidation step. A rework after approval sends the pack back through the earlier steps.
The report is issued
"Issue approved financial report" leads to "Financial reporting pack issued", the end of the flow. A reporting period on a Gantt chart ends differently, with a wait for the funder's response and a task for the queries, which a flowchart of one organisation's process does not show.
How it works
Plan one period as a full chart
Start from the grant reporting template, or list the steps of your own period in a table: data from partners, finance, narrative, review and sign-off, submission, the funder's response. Put each in a group of its own.
Put partner data behind one milestone
Add a milestone such as "Partner data received" and link every task that needs the returns to it. Start a chasing task part way into the wait with a start-to-start link, for example 4SS+3.
Start the independent work early
Link the ledgers, the evidence and the first draft to the agreed calendar, not to the partner data, so they run while the returns come in.
Give the funder's side a duration
Add a wait task for the funder's response and a task for the queries, and set both from what you have been told. If queries usually come back more than once, make the query task longer.
Fix the dates that are real
Give the first task a fixed Start and the submission task a fixed Start on the due date. The chart schedules forward from the earliest fixed Start. If the earliest date its dependencies allow is later than the due date, the submission task shows a conflict.
Copy the plan for the next period
Duplicate the chart, change the fixed dates and resize the waits from what the last period taught you. Put the person responsible for each task in People and share the chart as a link.
Mistakes to avoid
Linking everything to the partner data
If the ledgers, evidence and draft wait for the returns, the whole period stretches by the length of the wait. Link only the work that needs the data to the gate.
Treating the funder's response as zero
A report is not closed when it is submitted. If the response wait and the queries are missing, the chart shows the period ending days before it can.
Sizing queries for the best case
A chart cannot draw a loop. If a second round of questions is likely, give the query task a duration that allows for it.
Expecting dates to follow progress
Progress does not move dates. When a task is running long, change its duration and read the new finish, then compare it with the date you need.
Open the grant reporting Gantt chart
Open the template, set your partner and funder waits, fix the due date and see which wait sets the closing date.
Related guides
Frequently asked questions
Can I reuse the same plan every reporting period?
Yes. Duplicate the chart, change the fixed dates and resize the waits. Keep what you learned in the durations, for example how long partners really take.
Can the chart tell me when the funder will respond?
No. It shows the duration you enter for the wait and moves the dates after it. When you are told how long the review takes, change that task.
What if a partner returns data late?
Lengthen the partner preparation task and see which dates move. Only the tasks linked to the gate move; the ledgers, evidence and first draft do not.
Does the plan make my report compliant?
No. It schedules the work. It does not check the report against the funder's requirements and does not replace its rules. Keep any requirement as a task or a note with an owner.
Can I see planned against actual dates?
No. The chart shows one schedule from your dates and durations. To compare periods, keep a copy of each period's chart and compare their finish dates yourself.