Sustainability Reporting Grant: define the group and first-report boundary

A Sustainability Reporting Grant application needs a clear answer to two related questions: which legal entity applies, and what group or reporting boundary the first ISSB-based report will cover. If those boundaries are left implicit, revenue eligibility, reporting history, consultant scope, data collection and final deliverables can point to different populations.

Fix the applicant and group eligibility facts

Record the applying entity, ownership, listing status, latest financial year, revenue basis and relevant related entities. Identify whether the route sits with Enterprise Singapore or EDB under the current programme. Use the current SRG page and the official SRG FAQ for current eligibility, support and application conditions.

Preserve financial statements and the ownership chart used. Do not substitute group revenue, Singapore revenue or a management estimate without confirming the stated basis. Record any restructuring expected before the report so the adviser can assess its effect rather than silently changing scope later.

Test the first-report condition

Create a register of sustainability reports previously issued by the applicant and relevant group entities, with period, framework, publication status and boundary. Distinguish a marketing update, voluntary ESG report and ISSB-based sustainability report. The conclusion should be specific to the current official condition and facts.

If another group entity has reported, explain whether that report covered the applicant and why the proposed report remains within the programme purpose. Obtain professional or authority guidance where the position is not clear. Do not hide a prior publication because its title differs.

Write one reporting-boundary statement

List included entities, sites and operations, consolidation approach, reporting period, material topics, data owners and planned assurance. Record exclusions and the reason for each. Make the consultant proposal, project plan and data request follow the same statement.

Before claim closeout, reconcile the Letter of Offer, adviser scope, published report, assurance work, invoices and payment. Preserve boundary changes and their effect on comparability. Record who approved each boundary judgment and the source used. The grant project may end after the first report, but management still owns the ongoing reporting process and public claims.

Turn the decision into a controlled file

Use a dated decision record that identifies the applicant, business need, current official source, chosen route, responsible owner, costs, milestones and evidence. Separate facts already verified from forecasts and assumptions. A catalogue listing, supplier statement, consultant recommendation or portal acknowledgement does not establish approval. The company remains responsible for its declarations and commercial decision.

Give each quotation, contract, invoice, payment and deliverable a stable reference. Preserve earlier versions and explain material changes instead of silently replacing them. Where the authority, tax adviser, auditor or another professional must decide a point, record the open question and obtain the required view. Do not convert uncertainty into a confident eligibility statement.

Review before commitment and again before closeout

Run four reviews: suitability, authority, implementation and closeout. At suitability, test the entity, activity and business outcome. Before commitment, freeze the proposed scope, vendor and financial assumptions. During implementation, compare actual work with approved terms. At closeout, reconcile deliverables, accepted results, invoices, full payment, operating evidence and obligations that continue.

Name the person who may approve each stage and the records that person must see. Procurement should not treat a draft application as permission to contract. A project team should not treat supplier completion as company acceptance. Finance should not treat a submitted claim as cash received. Clear status words prevent accidental commitments and weak reporting.

Handle exceptions without rewriting history

Maintain an exception log for changed facts, delayed milestones, supplier variations, cost movements, missing records and failed tests. State the effect on scope, eligibility, timing and expected value. If an authority decision or formal variation is required, use the published route before relying on the change. Silence and helpdesk receipt are not approval.

If a material defect appears, pause the affected acceptance, filing or claim item. Keep original evidence, assign corrective action and set a review date. Do not backdate records, move costs between categories or adjust a baseline after seeing the result. A candid exception with an owned resolution is more credible than a clean-looking file that cannot explain what happened.

Plan handovers before the original project team disperses. The handover should identify the current version, source locations, system access owner, next review date, open exceptions and any condition that continues after payment or filing. Restrict personal, financial and commercially sensitive records to authorised users, while giving each responsible owner enough information to perform the assigned control. Record the external event that should trigger an earlier review, such as a changed programme page, revised authority letter, supplier failure or material business change.

Verify the final outcome independently

Ask someone who did not prepare the final pack to compare the decision, current official source, approved terms, deliverables, payments and operating evidence. Recalculate totals and sample source records. The reviewer should be able to reproduce the conclusion without relying on the preparer’s memory. Record unresolved points with named owners and dates.

Use the SRG first-report fit guide for the wider decision and keep this article as the narrower operating guide. After submission, preserve the receipt and reconcile questions, adjustments and the final registered or paid outcome. Continue any reporting, retention, asset-use or other condition that survives closeout.

Practical review checklist

• Applicant fixed
• Group revenue basis retained
• Prior reports checked
• Boundary statement approved
• Final report reconciled

The boundary is controlled when the eligible applicant, group facts, prior reporting history and final ISSB-based report all describe a consistent and reviewable scope.