Carbon reporting handover: documenting assumptions and limitations
Admin · 22 October 2026
Illustrative image. Photo by Cherrydeck on Unsplash. Unsplash License.
A carbon assessment result is difficult to interpret without knowing its scope, method and inputs. The headline number may be retained in a project report while the assumptions and supporting files remain with an individual consultant. A useful handover preserves the context needed to understand what the assessment represents and how future changes or comparisons should be considered.
For clients and project managers, the task is to agree the information required from the responsible assessor and organise its transfer. Competent specialists must determine the method, technical content and interpretation. This article concerns that management process. It does not provide an assessment methodology, establish targets or certify that a particular carbon claim meets a standard.
Identify the assessment purpose
Record the decision or reporting need the assessment supports. An option comparison, a design-stage estimate and a later project account may have different information maturity and purposes. The recipient needs to know which one it has received. Avoid allowing a result produced for one question to be reused for another without appropriate review.
State the relevant project and stage, including the accepted information basis. Where the assessment covers only part of the works, make that boundary visible in the summary as well as the detailed report. A scope limitation should not disappear when the result is copied into a presentation or asset record.
Record the method and version
The assessor should identify the method, relevant standards and version used, including departures or limitations as required. RICS’s whole-life carbon assessment hub provides authoritative context for its professional standard. The appropriate method and requirements for the actual assignment must be established by the responsible advisers.
Keep the method reference with the result. A future reader should not have to infer it from a software name or an old proposal. If the approach changes between assessments, ask the assessor to explain the implication for comparison. Differences in reported totals should not automatically be attributed to design improvement when the assessment basis has also changed.
Describe boundaries in usable language
Ask the assessor to explain the included scope, period and relevant categories at a level the client can understand, supported by the required technical detail. Identify exclusions and why they were made. The purpose is not to simplify away the method but to help decision makers interpret the result without mistaking a partial account for a complete one.
Connect the boundaries to the project scope. Client-provided equipment or separately procured work may require particular consideration under the agreed method. The assessor should establish the treatment. The project manager helps by providing a complete account of what the project includes and identifying information that sits outside the main contractor’s records.
Preserve consequential assumptions
Identify assumptions that materially influence interpretation, as determined by the assessor. Record their source, date and status. A forecast scenario should remain distinguishable from a verified project input. The recipient needs to understand which parts of the assessment reflect available evidence and which rely on an accepted modelling basis.
Ask how unresolved inputs were treated and what information would support a later update. This makes the limitation actionable. A broad statement that estimates were used may leave the client unable to prioritise further evidence. The responsible assessor should identify the significance and appropriate next steps without the project team inventing technical conclusions.
Link quantities and product data
Agree what supporting information the assignment requires and how its provenance will be recorded. The technical assessor determines suitability and treatment. The project can support that work by retaining clear product identities, relevant quantities and the accepted source documents. Inconsistent references can make a later review unnecessarily difficult.
Consider a hypothetical assessment prepared from an early material schedule. Several products change before installation. The final handover should explain whether and how those changes were reflected, according to the agreed scope. The client should not receive a design result labelled as delivered performance without the appropriate basis and review.
Reconcile accepted changes
Identify the route for feeding consequential project changes to the assessor. A substitution, scope amendment or revised quantity may need consideration under the method used. The responsible specialists should determine the effect. Do not assume that every minor change requires the same treatment, or that a similar product name means no review is necessary.
Record the current assessment and preserve relevant earlier versions with clear status. The handover should make it easy to identify the accepted result and understand why it differs from previous reports. A folder of several files labelled final can obscure both progress and limitations.
Explain comparisons carefully
If the report compares options, stages or a baseline, retain the basis of that comparison. Ask the assessor to identify scope and method consistency and any qualifications. A percentage reduction should remain connected to the reference case and conditions that produced it. Removing that context can turn a useful finding into a misleading general claim.
Keep forecast outcomes separate from measured or otherwise verified project information. The final narrative should reflect the evidence actually available. Where the assignment does not establish a particular result, avoid filling the gap with an unsupported number. The recipient can make better decisions from a clear limitation than from false precision.
Provide a reviewable information set
Agree the report, supporting records and formats to be transferred under the actual appointment. Consider what the client needs for retrieval and any later reassessment. Appropriate advice should establish rights, access and any restrictions. A software output alone may not explain the assessment, while an extensive archive may be difficult to use without an index.
Assign technical review to competent people and distinguish it from administrative completeness. A project coordinator can check that listed files are present without verifying the model or conclusions. Record what each reviewer assessed and the accepted response to comments. This gives the handover an understandable basis without expanding anyone’s role implicitly.
Test recipient understanding
Ask a suitable client representative to locate the current result, explain its purpose and find the main assumptions. The exercise checks clarity and retrieval, not the technical validity of the assessment. Record questions and obtain answers from the assessor while the assignment remains active.
Where the result will be used in wider reporting, identify the approved summary and its conditions. The communication should preserve consequential scope and uncertainty. The client’s relevant advisers should assess claims under the applicable arrangements. The handover process should not treat a concise headline as permission to remove the context that makes it accurate.
Define the update trigger
Ask the responsible assessor and client what future events would justify reconsidering the information under the intended use. The answer depends on the assignment and asset, rather than a universal review interval. Record ownership and where new information should be retained. This helps the operator avoid treating the original result as permanently current after significant changes.
Distinguish a new assessment from an administrative correction or clarification. The appropriate professional scope and review are needed for technical updates. Keep the history traceable so a future reader can identify the change in basis and the person responsible for the revised conclusion.
Close with an honest account
Summarise what was assessed, the accepted result, consequential assumptions and unresolved limitations. Assign any remaining information actions and identify the relevant decision route. A handover can be clear about incomplete evidence without disguising it as a verified outcome.
Carbon-reporting handover works when the client receives a usable explanation alongside the result. Preserving the method, boundaries and source information allows the assessment to support future decisions with its meaning intact, rather than leaving a headline number disconnected from the evidence and assumptions that produced it.
