Alyssa Castillo
Property development margins rarely disappear in one dramatic moment. They are usually reduced through dozens of decisions that were understood on site but never documented properly, priced accurately or reflected in the latest forecast. Morta.com helps property developers prevent this disconnect by keeping variation records, approvals, documents and cost information linked to the correct project, giving decision-makers a clearer view of how every change affects the development.
Construction variations are unavoidable. Designs develop, site conditions reveal new constraints, planning requirements change and purchasers request upgrades. The commercial risk is not the existence of change itself. It is allowing work to proceed while the reason, responsibility, value and approval status remain unclear.
For the property developer, poor variation documentation creates three serious problems. It distorts the project’s true financial position, weakens the developer’s ability to challenge costs and delays decisions that could have protected the original return. By the time the full value reaches a cost report, the work may already be complete and the opportunity to respond may have passed.
This article examines those three consequences from the developer’s perspective and explains how disciplined variation management supports construction cost control, reliable forecasting and long-term property development profitability.
Try Morta for FreeA development budget is based on assumptions that become less certain as the project moves from appraisal to construction. Tender returns provide greater clarity, but even an agreed contract sum is only the starting point. Once delivery begins, design revisions, client instructions, material substitutions and unforeseen conditions start changing the commercial position.
When those changes are not recorded immediately, the cost report stops reflecting what is happening on site.
The difference between the reported budget and the likely final cost can grow quietly. An instruction may have been given, but the contractor has not submitted a quotation. A quotation may have arrived, but the quantity surveyor has not finished assessing it. The commercial team may be aware of an emerging cost, but it has not been added to the forecast because the exact value remains uncertain.
From an accounting perspective, the cost is still pending. From a development perspective, the exposure already exists.
This distinction is central to construction cost control. A developer cannot manage only the costs that have been formally agreed. They must also understand the probable effect of instructed, anticipated and disputed changes. Otherwise, the forecast becomes an optimistic version of the project rather than a realistic estimate of the cost to complete.
The Association for Project Management defines cost control as the collection of actual costs in a format that allows them to be compared with the project budget. It explains that cost information helps organisations identify overspend and use actual project data to improve future estimates. That process depends on accurate and current information. If construction variations sit outside the reporting system, the comparison between budget and cost becomes unreliable.
Consider a developer delivering a block of 40 apartments. During construction, the mechanical consultant revises part of the ventilation design. The contractor estimates that the change will cost £45,000, but the quotation has not been formally accepted because the team is still reviewing the breakdown. Work proceeds to avoid delaying the programme.
If the £45,000 remains outside the development forecast until it is formally agreed, the reported contingency is overstated. The developer may approve further upgrades, commit money elsewhere or report an inaccurate expected return to an investment partner. Once the quotation is eventually accepted, the project appears to suffer a sudden cost increase. In reality, the commercial exposure had existed for weeks.
The direct cost of the variation may also represent only part of its financial effect. Revised building services could require new design work, additional preliminaries, testing, regulatory approval or changes to completed areas. If the change delays completion, the development may incur further finance costs and postpone sales or rental income. Variation documentation that records only the contractor’s initial quotation does not provide a complete view of the impact on profitability.
Poor project information has already been associated with substantial financial waste across the construction industry. Research published by Autodesk and FMI found that poor project data and miscommunication were responsible for 48% of rework in the US construction sector, representing an estimated US$31.3 billion in annual rework costs. Respondents also reported spending 35% of their working time on non-productive activities such as searching for project information, resolving conflict and correcting mistakes. The study relates to the US market, so the figures should not be applied directly to an individual UK or UAE development. They do, however, demonstrate how quickly fragmented information can become a commercial cost. The findings are available in the Autodesk and FMI construction report.
Reliable variation tracking closes part of this information gap. Every proposed or instructed change should have a visible status and an estimated financial value, even when the final amount remains under review. A developer should be able to distinguish between potential exposure, submitted quotations, approved variations and certified costs without reconstructing the position from several spreadsheets.
The date of the information matters as much as the figure. A cost report prepared at the end of the month may be technically accurate according to approved expenditure but commercially misleading if it excludes changes already taking place on site. Real-time cost reporting gives the development team an opportunity to act while the outcome can still be influenced.
This issue can be particularly severe in property flipping and smaller residential developments. These projects often have shorter programmes, limited internal commercial resources and margins that are highly sensitive to refurbishment costs. A series of undocumented upgrades, remedial works and specification changes can consume the contingency before the developer realises the financial position has changed.
Large corporate developers face a related problem at portfolio level. Information may be managed differently across each project, consultant team or contractor. Without a consistent variation management process, directors cannot compare exposure accurately or determine which schemes are most at risk of exceeding their approved budgets.
Effective development cost management therefore requires a broader definition of cost. It must include what has been paid, what has been committed and what is reasonably expected to arise from decisions already made. Strong variation documentation makes that position visible.
Construction change orders do not arrive in a commercial vacuum. Each one raises questions about scope, responsibility, entitlement and value. Was the work included in the original contract? Did a consultant revise the design? Was the change requested by the developer? Could the contractor reasonably have anticipated the condition? Has the proposed price been assessed against the contract?
The developer needs evidence to answer those questions. Without it, variation assessment becomes a debate between competing recollections.
A typical change can involve drawings, meeting minutes, requests for information, photographs, contractor notices, consultant comments and cost submissions. If those records are stored separately, the development team may struggle to establish a reliable sequence of events. That gives the contractor’s submission greater influence simply because it is the most complete version available.
The commercial consequence becomes more serious when work has already been completed. The developer may believe that a change was covered by the original scope, while the contractor treats it as additional work. If the instruction was verbal or buried in an email, the quantity surveyor must reconstruct what happened after labour and materials have been used.
At that point, the developer has fewer practical options. Rejecting the cost could lead to a dispute. Accepting it may mean paying for work that was not properly authorised or competitively priced. Negotiation becomes harder because the evidence needed to establish responsibility was not captured when the issue arose.
The Association for Project Management’s guidance on change control defines the process as capturing requests to alter an approved baseline, evaluating their effects and then approving, rejecting or deferring them. The assessment should consider cost, time, quality, scope, risk, resources and the wider business case.
That definition is directly relevant to a developer’s variation approval process. Approval should represent an informed commercial decision. It should not be reduced to a quick instruction issued because the site team needs an immediate answer.
A clear record allows the developer to see what is changing, why it is necessary and what evidence supports the proposed cost. It also identifies the person with authority to approve the expenditure. This prevents informal decisions from being treated as contractual approval before their development-level impact has been considered.
The sequence is especially important under contracts containing formal notification provisions. Under NEC contracts, for example, early warning procedures are designed to identify matters that may affect cost, completion or performance. NEC guidance explains that accurate contemporary records are important when delays and compensation events later need to be assessed retrospectively. Its discussion of good records for retrospective delay assessment reinforces a principle that applies across different contract forms: records created at the time are generally more useful than accounts reconstructed several months later.
This does not mean the developer should turn every variation into an adversarial process. Proper variation documentation can reduce conflict because it gives all parties a common factual record. The contractor can see the status of its submission, the consultant can provide an assessment and the developer can understand the commercial consequence before approving the work.
The problem begins when separate versions circulate. The site team may believe a change has been approved because the contractor was told to proceed. The finance team may believe it remains pending because no signed order has been received. The quantity surveyor may include an estimated value in one report, while the development appraisal continues using the original budget. All three positions can exist at once when there is no shared record.
Public-sector contract guidance offers a useful comparison. The Northern Ireland Department for Communities states that good contract management is critical to achieving value for money and avoiding inappropriate contract variations. It also requires written justification to be retained in circumstances where procurement decisions need to withstand later scrutiny. The rules applying to a private development are different, but the underlying commercial discipline remains relevant. Decisions involving material cost need a traceable rationale. The Department for Communities guidance provides further detail.
A 2024 Southwark Council report shows how substantial the accumulated value of development changes can become. The report sought approval for a £3,961,805.45 variation relating to increased contract costs caused by instructions, changing legislative requirements and unforeseen site conditions. It noted that the wider programme would need to be reprofiled because of the increase. The circumstances differ from a typical private scheme, but the case shows how changes can affect both the contract and the wider capital plan. The full Southwark Council variation report is publicly available.
Property developers should also consider how documentation affects recoverability. A cost caused by a consultant’s error, tenant request, purchaser upgrade or third-party requirement may need to be allocated or recovered elsewhere. If the reason for the change is not recorded, that opportunity can be lost. Months later, the developer may know that an additional cost was incurred but lack enough evidence to establish who should bear it.
A disciplined system should connect each variation with the original scope, the instruction, supporting evidence, commercial assessment and approval decision. The objective is not to create paperwork for its own sake. It is to preserve the developer’s ability to assess entitlement, challenge value and allocate responsibility fairly.
The final effect of poor variation documentation appears in the development appraisal. This is where construction information becomes an investment decision.
A developer must understand whether the expected gross development value, total development cost and financing assumptions still produce an acceptable return. If variation costs enter the appraisal several weeks or months late, the calculated profit may remain artificially high long after the commercial position has changed.
That delay affects more than an internal spreadsheet. Lenders may be monitoring build costs and contingency. Equity partners may expect regular updates on projected returns. Directors may use the reported figures to decide whether to approve specifications, release further funding or pursue another acquisition.
An inaccurate forecast can therefore influence decisions beyond the project where the missing cost originated.
Suppose a scheme has £250,000 of contingency remaining in its latest board report. Several changes are progressing on site, but the contractor has not submitted final quotations. The project team estimates that the combined exposure is between £90,000 and £140,000, yet the costs have not been included because they remain unapproved.
The board sees £250,000 of available protection. The development team may actually have closer to £110,000. Both figures can appear defensible depending on the reporting method, but only one reflects the project’s likely position.
Project budget management must account for uncertainty explicitly. An estimated cost can be identified as an estimate. A disputed submission can be identified as disputed. Neither needs to be presented as an approved commitment. The important point is that decision-makers can see the exposure and understand its status.
The Association for Project Management describes project controls as the coordinated management of scope, time, cost, risk, change, reporting and information. It also states that project controls involve forecasting future outcomes and taking action to correct potential failures. For property developers, this is the difference between reporting a cost overrun and managing one.
If a variation is visible early, the developer still has choices. The design may be revised, the specification may be adjusted or work may be deferred. The contractor’s quotation can be challenged before resources are committed. Contingency can be reserved for the most important risks. The projected return can be reviewed before another commercial decision compounds the problem.
Once the work is complete, most of those options disappear. The remaining discussion usually concerns how much will be paid and where the money will come from.
Late reporting also obscures the connection between construction cost and programme. A variation that extends the build period can increase professional fees, site overheads, interest and other financing costs. It may delay completion proceeds or rental income. If the variation record contains only the direct construction value, the development appraisal can still underestimate the total impact.
This is why property development profitability cannot be protected through cost codes alone. The developer needs to understand the chain of consequence. A change to the works can affect the programme, which affects finance, which affects the return.
The same information has value after completion. Reliable variation data can show where a scheme’s original assumptions proved weak. A developer may discover that late design coordination consistently produces additional mechanical and electrical costs, or that purchaser-led changes consume more management time than the fees recover. Another may identify a contractor whose projects generate an unusually high volume of disputed variations.
Those findings can improve future procurement, consultant appointments, contingencies and appraisals. Poor records remove that opportunity because the final account shows what was spent without explaining how or why the cost developed.
For new property developers, this deserves attention from the first project. Informal processes can appear manageable when the team is small, but memory is not a reliable commercial system. As the number of consultants, packages and decisions grows, undocumented change becomes increasingly difficult to control.
For corporate developers, the challenge is consistency. One project may use a detailed change register while another relies on the contractor’s monthly report. A third may track approved costs but exclude emerging exposure. Portfolio reporting cannot provide a reliable comparison when every project defines variations differently.
Property development software can create a consistent structure without separating commercial information from the rest of delivery. Within Morta, developers can connect variation tracking with project documents, approvals, budgets and reporting. This allows the latest cost position to be understood in context rather than treated as an isolated number copied into a spreadsheet at month-end.
The benefit is practical. Senior leaders receive a clearer picture of exposure across the portfolio. Project teams spend less time searching for supporting information. Commercial decisions are recorded alongside the evidence used to make them. The development appraisal can be updated using information that reflects current site activity.
Construction variations do not automatically make a development unprofitable. Unrecorded, unpriced and poorly governed changes are far more dangerous because they prevent the developer from responding while there is still time.
Strong variation management gives the developer a current view of exposure, preserves the evidence needed to assess contractor claims and allows emerging costs to reach the development appraisal promptly. It also creates useful commercial data for future schemes, helping teams prepare stronger budgets and identify recurring sources of overspend.
The central principle is straightforward. If a change can affect cost, programme, quality or value, it should be recorded when it is identified, not when it appears in the final account.
Morta.com gives property developers one connected place to manage project information, construction variations, approvals and costs throughout the development lifecycle. If your team is still rebuilding the commercial position from separate spreadsheets, emails and contractor reports, book a discovery call today and see how Morta can help you protect the profitability of every project.
