Build an ESG reporting timeline around dependencies and review
Before promising a reporting date, check which inputs must arrive first, which tasks can genuinely overlap and when reviewers can respond. A useful timeline lets you explain why a late input changes the finish, or why it does not.
This guide is for coordinators planning a scoped reporting project. The fictional six-package example ends with an approved internal handover. Any separate independent assessment, assurance, filing or publication process needs its own agreed tasks and dates.
Define the calendar and the handover
Record the reporting period separately from the project start, source cut-off and target handover. Have the responsible owner confirm applicable external deadlines. Specify the working calendar, including holidays and reviewer availability, before converting a duration into a date.
GRI 1's Timeliness principle addresses regular, decision-useful reporting while recognising information quality. Verifiability addresses information that can be examined, with sources and decisions documented. These principles support making room for evidence preparation and review; they do not prescribe a project duration. GRI 1 Foundation 2021, section 4
Start from an agreed reporting brief. For each package, name the deliverable, owner, required inputs, duration, reviewer and evidence of completion. Record external response commitments explicitly rather than assuming another party will be available.
Keep duration and effort separate
Duration measures a package’s scheduled time; effort measures labour, such as person-hours. Retrieval may require little work but days of waiting. Summed durations are not labour totals. GAO discusses these distinctions and resource availability alongside dependencies. GAO Schedule Assessment Guide, pages 49–50 and 86–87
Work through six linked packages
All packages, durations and roles below are invented teaching assumptions. Day 1 is the first working day after initial access is available. Everyone uses the same working calendar. Tasks finish at the end of a day; successors start on the next working day. There are no extra lags, interruptions or fixed meeting dates.
The collection team and context writer have separate capacity. C covers only context that can be prepared without B's records or D's figures. E includes checking that context against the figures, management review and agreed corrections, all assumed achievable in its two days. If the actual work needs more time, change the model.
A Confirm scope and owners. Two working days, days 1–2. Initial request and access are available.
B Collect records and resolve collection queries. Five working days, days 3–7. Starts after A.
C Prepare the independent context narrative. Four working days, days 3–6. Starts after A, using the separate writer.
D Reconcile data and draft the figures. Three working days, days 8–10. Starts after B.
E Complete management review and agreed corrections. Two working days, days 11–12. Starts only after both C and D.
F Assemble and check the approved handover. One working day, day 13. Starts after E.
The package durations add to 2 + 5 + 4 + 3 + 2 + 1 = 17 package-days. That label means summed package durations, not 17 person-days of effort. The elapsed project duration is 13 working days: C's four days overlap B.
The sequence A → B → D → E → F takes 2 + 5 + 3 + 2 + 1 = 13 days and controls the finish. The other path, A → C → E → F, takes nine days. In this model, C can finish as late as day 10 without delaying E on day 11. Its four-day allowance is called total float. It is not four extra days reserved for final review.
You can check every row with two rules: finish = start + duration − 1; successor start = latest predecessor finish + 1. For E, the later finish is D's day 10, rather than C's day 6.
Compare delays before choosing a response
Each case below changes the original baseline independently. All other assumptions stay fixed; the delays are not cumulative.
B finishes two working days late. Its usable records arrive at the end of day 9. With the remaining durations unchanged, D moves to days 10–12, E to days 13–14 and F to day 15. Finishing C earlier cannot remove the data dependency. A passive wait can lengthen the schedule without adding the same amount of labour; do not infer extra person-days from this delay.
C finishes two working days late. Its finish moves from day 6 to day 8. D still finishes on day 10, so E and F stay unchanged and handover remains day 13. Two of C's four float days have been used.
C finishes five working days late. It now finishes on day 11, later than D. E moves to days 12–13 and F to day 14. The narrative branch now controls the finish. A task that was initially noncritical can become the limiting one.
Keep the baseline and revised forecast visible. State the late input, affected successors, remaining assumptions and decision needed. If the target is fixed, test a specific resource or sequencing change with its owners. Reducing the review duration on paper does not establish that the work will fit.
Test whether the parallel work has capacity
Return to the original baseline with no delays. Change one assumption: B and C now require the same person full-time for their stated durations, so they cannot overlap. Choose B first, then C on days 8–11. A separate analyst can still perform D on days 8–10. E becomes days 12–13 and F day 14. The six package durations still total 17, but elapsed time is now 14 days. This is one feasible sequence under the new assumptions, not a promise that all resource conflicts can be solved this way.
Before using the original day-13 forecast, confirm the writer's availability and that C really is independent of the figures. If part of the narrative requires D, split that part into a dependent task and recalculate. Record staff commitments across other projects as well as this plan.
Use completion evidence at each handover
B to D: the expected records and coverage are accounted for, with unresolved gaps and agreed treatments visible. A folder marked received is insufficient.
C and D to E: a reviewable narrative and source-linked figures are available together, with questions identified.
E to F: the required decisions and corrections are complete for the named version. An unresolved release condition keeps the affected handover open.
F complete: the approved versions, access and next owner have been checked. The evidence-folder handover guide covers that transfer in detail.
A late source correction can reopen an earlier package. Add its affected calculations and review steps to the forecast rather than hiding the work after the cut-off.
Choose a planning tool with the right limits
The reporting project timeline and dependency planner is a separate, simple calendar-day workbook. It does not calculate working-day calendars, critical paths, total float or resource capacity. Do not enter this example's working-day durations unchanged and treat its calendar dates as equivalent. Use a suitable scheduling tool where those calculations are required.
Discuss a realistic reporting scope
Nitium's sustainability and GRI reporting support includes a report outline, disclosure mapping, draft content and an information-gap list within an agreed scope. Discuss your reporting needs with the intended output, period, target date and a non-confidential outline of available records and review capacity.
Planning and reporting references checked 13 October 2026. The schedule is fictional and provides no statutory deadline, standard delivery time, professional assurance or guarantee of completion.
Comments