Alyssa Castillo
Morta.com helps property developers bring budgets, project information and reporting into one place, making it easier to see how a development’s commercial position is changing. One useful tool for that is a CVR report. Short for cost value reconciliation, it compares project value with cost and helps reveal whether the expected financial position is holding up as work progresses.
For a property developer, a CVR report should make it easier to answer practical questions: What has the project cost so far? What work has been completed or valued? What costs are committed but not yet paid? What changes could affect the final forecast? Morta supports this reporting process, but a useful CVR still depends on reliable data, clear assumptions and regular review by the people responsible for the project.
Try Morta for FreeCVR stands for cost value reconciliation. In construction, it usually refers to a periodic commercial report comparing the value of work completed with the cost of delivering it. It is commonly used by contractors to monitor project performance and forecast the expected final position.
From a property developer’s perspective, the report can help assess whether the project’s costs, commitments and changes remain consistent with the approved budget and development assumptions. The exact format will depend on the organisation, contract, procurement route and purpose of the report. A contractor’s CVR may focus on its own earned value and margin, while a developer’s cost report may focus on the project’s anticipated outturn cost against the approved budget.
These reports are related, but they are not interchangeable. Developers should be clear about whose value and whose costs the report describes. A report can be accurate for a contractor’s commercial position and still omit information the developer needs to assess total project cost, funding requirements or expected return.
There is no single universal CVR template that every property developer must use. Report requirements vary with the project and contract. However, a CVR should give its intended readers a dependable view of cost, value, forecast and risk, and it should explain how those figures have been prepared.
For UK projects, the RICS Cost Reporting guidance is a relevant professional reference. It sets out principles for reporting to the client during construction, including the purpose of cost reports, factors affecting outturn cost and different reporting formats. RICS explains that a cost report should inform the client of the likely outturn cost and that regular, frequent reporting helps the client and team control it.
That guidance does not make one CVR layout compulsory for every project. Instead, developers can use it alongside the contract, their cost management procedures and the reporting needs of their project. Where a RICS professional is producing a cost prediction report, the RICS Cost Prediction professional standard sets out requirements for RICS professionals and RICS-regulated firms. Its scope concerns cost prediction, so it should not be presented as a universal CVR template.
The practical standard, then, is that the report should be consistent, traceable and suitable for the decisions it supports. Readers should be able to understand what each figure means, what period it covers and what assumptions sit behind the forecast.
A useful CVR report joins the current project position to a credible forecast. It should show how the project is performing at the reporting date, what has changed since the previous report and what the team expects at completion. The information below is a strong basis for that report, though the level of detail will vary between a small refurbishment and a multi-package development.
Every report should identify the project, reporting period, cut-off date, preparer and intended audience. It should also state the contract or procurement basis being used, the relevant budget baseline and whether figures include or exclude VAT, inflation, contingency, fees or other cost categories.
This context matters because a number without a basis can be misleading. For example, one report may compare construction costs only, while another includes professional fees, enabling works and authority charges. Similarly, the approved budget may have changed since the original appraisal. The report should state which baseline is used and show any approved revisions rather than quietly replacing the original figure.
A developer needs to see the approved budget beside the latest forecast. The report should make clear the original or approved allowance, any formally authorised changes, the current budget and the forecast final cost. Where relevant, the budget should be broken down by cost headings or work packages so that material movements are visible.
The forecast should not be limited to expenditure already recorded in the accounting system. It should include costs incurred, committed costs, estimated cost to complete and reasonable allowances for foreseeable risks. RICS guidance describes cost reporting as capturing known and estimated costs, foreseeable future costs and necessary risk allowances.
For a developer, this is the section that connects the report to the investment case. If the forecast has increased, the team needs to understand whether the rise is due to a scope change, an estimate correction, a market movement, a risk event or another cause. The variance should have a clear explanation, not just a revised number.
The value side should explain what value has been earned, certified, claimed or otherwise recognised by the reporting party, in line with the report’s purpose and contract. A contractor’s CVR often compares the value of work completed with the cost of producing it. A developer’s reporting may also need to show contract sums, certified applications, approved variations, pending changes and the remaining value of work.
These figures should not be casually combined. For instance, an application submitted by a contractor is not necessarily equivalent to a certified amount or a payment made. The report should distinguish the status of each figure, so decision-makers can see what is agreed, what is under assessment and what remains uncertain.
Where sales receipts, rental income or development value are relevant to the project’s wider financial position, those should be presented consistently with the development appraisal and cash flow forecast. Construction CVR and development feasibility are connected, but they answer different questions. The former helps track cost and value during delivery; the latter considers the overall commercial viability of the scheme.
A strong report separates costs already incurred from costs that are committed and those still to be forecast. Actual costs may include invoices or certified amounts recorded up to the cut-off date. Committed costs may include awarded contracts, purchase orders or other obligations that have not yet been fully invoiced. Forecast cost to complete represents the expected cost of the remaining work, based on the latest scope, programme and procurement information.
This separation helps prevent a common reporting problem: showing low spend to date as though it means the project is within budget. A project can have substantial unpaid commitments or unpriced work ahead. If the report only reflects paid invoices, the apparent position may be materially better than the likely final result.
Accruals and liabilities should also be considered where work has been completed but the corresponding invoice has not yet arrived. The aim is not to make an unsupported adjustment, but to avoid understating the cost position simply because of invoice timing. The report should explain any significant estimate or accrual and identify who has reviewed it.
Changes to scope, variations, claims, provisional sums and other unresolved commercial matters can materially affect the forecast. The report should show their status and likely cost impact, distinguishing approved changes from submitted, anticipated or disputed items.
A single total for “variations” is rarely enough for effective oversight. The developer should be able to identify which changes have been approved, which are awaiting a decision and which may create additional cost or delay. Where a change is significant, the report should connect it to the relevant approval, instruction or contract record.
Risk allowances should also be visible and explained. A contingency figure without a clear link to identified risks can hide uncertainty rather than communicate it. The report should make clear what the allowance covers, whether any of it has been used and whether newly identified risks have changed the expected outturn.
The report should state the current and forecast position in terms relevant to its audience. For a contractor’s CVR, that often includes forecast final value, forecast final cost and forecast margin. For a developer’s project report, the key comparison is commonly the latest forecast outturn against the approved budget, with commentary on the effect on project viability, funding or expected return where appropriate.
The commentary is essential. It should explain the main movements since the previous period, identify the cause of material variances and state what action is being taken. A report that presents figures without explaining them leaves senior decision-makers to guess whether the change is temporary, approved, recoverable or likely to continue.
The RICS Cost Reporting guidance can help teams establish a suitable reporting approach, while RICS New Rules of Measurement provides measurement rules and guidance for construction cost management. Neither replaces the need to agree a project-specific reporting basis and use it consistently.
If a CVR report is incomplete, late or difficult to reconcile, decision-makers may act on an inaccurate view of the project. Costs may be understated, a likely overrun may emerge too late to respond, or an unapproved change may be treated as though it is already part of the budget. In turn, the developer may make weaker decisions about procurement, funding, scope or the timing of other projects.
A poor report can also reduce confidence among internal stakeholders, lenders, investors and project partners. If figures cannot be traced to their source or the forecast keeps changing without explanation, it becomes harder to distinguish normal project movement from a deeper control problem. The report itself does not cause those issues, but it can delay the point at which they become visible.
A CVR is most useful when it is produced on a regular cycle, uses a consistent cut-off date and draws on current information from the project team. The quantity surveyor or commercial lead should review the forecast with people who understand design, procurement, construction progress and changes. That way, the expected cost to complete reflects what is happening on site and in the supply chain, rather than only what has been recorded financially.
The process should also make it easy to trace figures back to supporting records. A developer needs to understand why the forecast changed, who approved the change and what evidence supports the new position. Storing budgets, approvals, contract information, variations and reporting data in disconnected files makes that review slower and increases the chance that teams use different versions.
Property development software can support a consistent reporting process by bringing project information together and reducing manual compilation. It cannot replace professional judgement or contract administration, but it can make information easier to access and keep the reporting workflow more structured.
Morta gives property developers a central place to manage project budgets, costs and reporting, helping teams build a clearer view of the commercial position as projects progress. The Morta CVR process can be generated at the click of a button, turning work that one customer says used to take the commercial team days into a faster reporting process.
If your CVR process relies on manual consolidation, disconnected spreadsheets, or repeated PDF preparation, see how Morta property development software can support your reporting workflow. Book a discovery call today to explore how Morta can help your team produce and review CVR reports with greater visibility.
