Reporting disclosure gap register
A reporting gap can remain even when the requested evidence is already available. The figure may appear in the draft while its period, coverage or method explanation is missing. This register connects each disclosure question to the evidence examined and the exact draft passage, so the owner can distinguish a collection task from a writing task.
The nine-page pack contains instructions, four reusable blank sheets and a four-page completed fictional case. It is an editable Word register with repeatable requirement and gap records, plus a matching static PDF. It does not calculate a compliance percentage, determine legal applicability or grant permission to release a report.
Download the editable reporting disclosure gap register (DOCX).
Download the print reporting disclosure gap register (PDF).
Define the requirement set before rating the draft
Record why the report is being prepared, who will receive it, which entity and period it concerns and who can decide questions about its reporting basis. List the source documents and editions that govern the agreed review. Keep an unresolved applicability question visible instead of assigning a convenient green status.
An official source can carry an important date without settling applicability. SEBI’s listing identifies its listed-entity master circular as dated 30 January 2026. That listing is a source-identification example, not a rule assessment.
For an actual assessment, obtain and review the relevant provisions, amendments and adoption decisions. A search result or document title does not supply the requirements inside it. The pack leaves the source locator and edition fields editable because the appropriate basis depends on the organisation and intended use. The fictional case uses an invented internal brief, not a real regulatory checklist.
Break a compound requirement into separately testable components while retaining its parent reference. If a question asks for an amount, period, sites and method, a matching amount alone does not answer it. Give each component a stable identifier and describe the expected information in plain language. Check the decomposition with the reporting-basis owner so an important condition is not lost.
Maintain two observations for each component
First record what the available evidence supports, including its version, precise location and limitations. Then record what the actual draft says and where it says it. The two observations need separate fields. Evidence can be adequate for the agreed narrow check while the disclosure is incomplete, or polished disclosure can lack support.
Use the issue record to describe the smallest observable difference. “The selected draft names no included sites” tells a writer what is missing. “Not compliant” claims much more and does not explain the work needed. If the review examined only specified pages, preserve that limit rather than claiming the information is absent from every possible document.
The blank register separates applicability, evidence and disclosure states. It also records a remediation owner, target date, dependency and repeat-check condition. These are working conventions, not a standard’s prescribed categories. Decide whether a gap requires new evidence, interpretation, revised wording or a cross-reference repair before requesting more files from every department.
Follow one invented brief through the register
All entities, documents, quantities and decisions in the case are fictional. Alder Components prepares a quarterly internal resource note for its management team. Brief RQ1 asks for a purchased-water amount with its unit, period, included sites and compilation method. It separately asks whether a proposed reuse assessment occurred. A warehouse item is conditional on that location being inside the agreed note boundary.
The supplied source schedule E1 contains 840 kilolitres for Sites North and South, covering 1 April to 30 June 2026. It states that the amount was compiled from supplier invoices for the selected sites and period. The example accepts this schedule as supplied evidence for a document-to-draft check; it does not independently test invoices or establish actual water use.
Draft D1 reproduces the amount, unit and quarter. It omits the site names and compilation explanation. Two component records therefore match the supplied schedule, while two disclosure gaps remain. Asking finance to collect the same schedule again would not repair either gap. The writer needs a precise instruction to bring the existing supported context into the note.
A different issue concerns the reuse assessment. E2 is only a meeting proposal, and D1 says the assessment is complete. The proposal does not establish whether the assessment occurred or what it concluded. This is an evidence question as well as an unsupported draft statement. The register asks the responsible owner for confirmation and removes the unsupported completion wording from the next candidate.
The warehouse item follows another route. The invented brief makes that question conditional, and the supplied boundary decision places Warehouse West outside this internal note. The owner records the condition as not met for this brief. That disposition does not say the warehouse has no water use or would fall outside any other reporting requirement.
Close the writing gap on a named revision
Draft D2 adds the two site names and compilation explanation. The checker compares the exact paragraph against E1 and records closure of the two writing gaps for D2 only. Receiving E1, assigning the writer or reaching the due date would not have been enough. Closure refers to the observed corrected output, not merely a promise to make the change.
D2 also describes the reuse-assessment status as unresolved. That removes an unsupported statement but does not provide the yes-or-no answer requested by the brief. The evidence gap remains open with its owner and a specific request. A more careful sentence can improve a draft without completing the underlying reporting task.
Keep the original observation and every response alongside the final disposition. Do not overwrite “site names absent in D1” with “complete” and lose the reason the issue existed. The worked record retains both versions, the changed locator and the reviewer’s repeat check, making the narrow closure understandable to a replacement team member.
Use the register to plan the next decision
A useful summary lists the decisions still blocking the agreed review. It should identify the affected requirement, consequence, responsible role and next evidence date. Counting closed rows is a workload measure at most; it does not establish the quality, significance or completeness of the report. Six small checks cannot stand in for a full reporting framework assessment.
Reopen a record when the requirement, applicability decision, evidence or draft changes in a way that affects its conclusion. A layout revision may need only a locator check, while deleted qualifications need substantive review. Preserve the prior closure and record what was rechecked. Do not let an old page reference make corrected content appear missing or a stale version appear current.
The source document register maintains source versions and permissions. The management review checklist records decisions about release. This gap register sits between them: it connects a reporting requirement to supported information, actual wording and a testable correction. Keep these different decisions linked without merging their approvals.
For framework-specific context, use the GRI content-index guide or the IFRS S2 gap-assessment guide alongside the current requirements relevant to your report. Neither a general guide nor this blank register is a substitute for a complete assessment of the selected reporting basis.
Source checked 15 October 2026: SEBI official listing for the 30 January 2026 listed-entity master circular. Only its identity and date are used.
Version 1.0. Original Nitium Advisory register and fictional case. No source format, regulatory checklist, actual client result, independent assurance or certification is supplied. No source organisation endorses this resource. Specialist interpretation and release approval remain with the authorised people for the actual engagement.
Comments