Whole-life carbon assessments: organising project data
Admin · 22 October 2026
Illustrative image. Photo by Jonathan Borba on Unsplash. Unsplash License.
A whole-life carbon assessment depends on a chain of project information: what is being assessed, which quantities describe it, what data represents the relevant products and processes, and which assumptions complete the picture. When that chain is unclear, a result can be difficult to interpret or update. The project team may see a single total without understanding which design decisions it reflects and where uncertainty remains.
For clients and design managers, the priority is to organise the information flow around the assessor’s agreed method and the decisions the assessment supports. This article concerns data management rather than calculating emissions. A suitably competent assessor should define the assessment requirements and interpret the results. Other team members need to provide traceable inputs and communicate changes that could affect them.
Agree the assessment brief
Start by identifying the purpose of the assessment, its scope and the stage of the project. An early options comparison may use different information from an assessment based on developed procurement choices. Ask the assessor to state the method, boundaries and reporting expectations, with reference to the appropriate requirements. Avoid using the phrase whole-life carbon as if it establishes all those choices automatically.
The RICS whole-life carbon assessment standard provides an established professional framework for measurement. The project should identify the applicable edition and any additional client requirements through its assessment brief. Citing a framework does not remove the need to explain the actual scope, information and assumptions used in the project’s work.
Define a common scope reference
Identify the design information and project elements that form the basis of the assessment. Record revisions and the date of the information snapshot. This allows the team to understand what the result represents. If some packages are excluded or not sufficiently defined, state that clearly and explain how the assessor has treated the gap under the agreed approach.
Keep scope descriptions aligned between the carbon assessment, cost plan and design records where comparisons are intended. Differences may be justified, but they need explanation. A change in reported carbon can result from a scope adjustment rather than a different design solution. Without a common reference, the project risks attributing the movement to the wrong cause and making a decision on an incomplete comparison.
Make quantity provenance visible
For significant quantities, record the source, measurement basis and person responsible for the input. A quantity extracted from a model may still need interpretation or checking before it suits the assessment. Ask the relevant specialists and assessor to identify the required basis. Do not assume that a software export is automatically complete or appropriate because it contains detailed numbers.
Distinguish measured quantities from allowances and estimates. All can be useful at the appropriate stage, but their status should remain visible. Where the design develops, identify which quantities need refreshing and who will provide them. The assessment workflow should not depend on the assessor independently discovering that a major package has changed since the previous information issue.
Record product and data assumptions
Ask the assessor to define what supporting information is needed for the proposed products and materials. Track the source and applicability of the data used, including the reason for a substitute where the preferred information is unavailable. The project team should provide accurate product descriptions and avoid treating superficially similar options as identical without the assessor’s review.
Keep procurement status separate from the assessment assumption. A product used in an early calculation may be illustrative rather than selected. Later supplier proposals can change the basis. Record which options are being compared and whether they are technically acceptable, available and incorporated into the current design. Carbon assessment should inform those decisions without implying that it alone establishes suitability.
Assign the missing inputs
Create an input schedule identifying the information, owner and required date. Link requests to decisions or reporting milestones so contributors understand their significance. A broad request for all carbon data is difficult to action. A request tied to a specific package and assessment question gives the owner a clearer route to provide something useful.
Where an input remains unavailable, ask the assessor to state the treatment and its limitation. The project can then decide whether further investigation is proportionate to the decision at hand. Avoid filling gaps with undocumented guesses merely to produce a complete-looking dashboard. An honest limitation with an assigned action is more useful than a precise total whose weak assumptions cannot be traced.
Control updates and comparisons
Use identifiable assessment versions and retain the inputs supporting each reported result. When a result changes, distinguish design changes, updated quantities, revised product information and changes in assumptions or method. This movement analysis helps decision makers understand whether the project has improved the proposed solution or simply improved the quality and coverage of its information.
Consider a hypothetical commercial building where a structural option is revised at the same time as more detailed quantities become available. Comparing only the two totals can confuse the effect of the option with the effect of the new measurement. The assessor should explain the basis of comparison and any limitations, while the project team supplies the information needed to separate meaningful differences where feasible.
Connect findings to design decisions
Ask what decision a reported result supports. A review may identify a package worth investigating, but further technical, programme and commercial assessment can still be necessary. Assign the option study to the appropriate team and define its output. Do not allow an assessment recommendation to bypass the project’s responsibilities for safety, performance or suitability.
For each accepted change, record the relevant assessment evidence and the design information affected. Maintain the link through procurement so that a later substitution is reviewed for its consequence. A benefit identified during concept design can be lost if the purchasing team receives only a product description without understanding the assumption on which the assessment depended.
Report uncertainty in usable language
The client needs enough explanation to interpret the result without becoming a specialist assessor. Identify the major assumptions, missing information and factors capable of changing the conclusion. Avoid relying on a generic caveat at the end of a report. Connect limitations to the actual options or decisions under discussion, with a clear account of the next information needed.
Use consistent units and descriptions established by the assessment approach. If different outputs use different boundaries or normalisation, explain that before comparing them. The project should not select the most favourable presentation without preserving the context. A concise summary is useful when it remains traceable to the detailed assessment and accurately represents its scope.
Prepare a defensible handover record
Agree the assessment and supporting information required at completion. Identify who provides final quantities, accepted product information and relevant construction inputs within the agreed scope. Track outstanding records before the delivery team disperses. The assessor needs a clear basis for updating or qualifying the final output, while the client needs to understand what evidence remains incomplete.
Retain the method, boundaries, input sources and assumptions with the result under the project’s information arrangements. The long-term value lies in traceability as well as the reported number. A later team should be able to understand what was assessed, what evidence supported it and which limitations matter before using the result for another comparison or public claim.
Check access to the supporting record before closing the appointment. The client should know where files are held, who can retrieve them and which formats have been agreed. A result with inaccessible inputs is much harder to review when a later project team needs to understand the earlier assessment.
