Ben Goodman
A property development can remain commercially viable while its reporting gradually becomes less reliable. Morta.com connects the information generated from land acquisition through to completion, helping developers retain a current view of costs, programme, risk and projected returns as a scheme progresses. This continuity matters because development margin is often weakened through decisions made between formal reporting points, when information has moved faster than the systems intended to record it.
When a board member asks for the current margin on a live development, the answer should be readily available. In many businesses, however, the response arrives with qualifications. The latest cost report may exclude a recent variation, the sales forecast may be held elsewhere, or the programme may not reflect a planning delay that has already affected the delivery team.
These qualifications rarely indicate a lack of expertise. They reflect the way property development information is commonly divided between specialist teams, individual files and software designed for separate stages of the project.
Every stage can appear well managed when reviewed independently. The exposure emerges during the transition from one stage to another, when assumptions are copied, reports are rebuilt and decisions lose their original commercial context.
Try Morta for FreeA property development begins with a relatively concentrated set of information. The acquisition team assesses the site, the initial appraisal establishes the commercial case and senior decision-makers agree the conditions under which the opportunity should proceed.
As the project advances, the volume of information increases. Planning consultants produce new reports, designs develop, contractors submit tenders, funding conditions are introduced and the sales or leasing strategy becomes more detailed. Responsibility also expands across a larger group of internal and external stakeholders.
The original appraisal remains an important reference point, but it is soon surrounded by operational information held in other places. Unless the business maintains a reliable connection between the approved assumptions and subsequent project activity, management visibility becomes increasingly dependent on manual reconciliation.
This is how a development can accumulate extensive documentation while producing less certainty about its commercial position. The information exists, but obtaining a dependable answer requires several people to locate, compare and interpret it.
The acquisition appraisal establishes the price the developer can afford to pay for land and the return the scheme may generate. It brings together assumptions about construction cost, programme, professional fees, finance, revenue and risk.
These assumptions are made with limited information, which is normal at this stage. The commercial weakness appears when the original appraisal is preserved as a static approval document rather than maintained as the baseline against which the development is measured.
The RICS guidance on the valuation of development property recognises the role of variables such as build costs, sales values and timing within development appraisals. It also discusses sensitivity analysis as a means of understanding how movements in key inputs affect the outcome. These principles remain relevant throughout delivery because the assumptions that supported the land decision continue to influence the developer’s exposure.
If the acquisition appraisal is stored separately from the live project budget, subsequent changes become difficult to trace back to their commercial origin. A higher construction estimate may be visible in the cost plan, but management may not immediately see how it has altered the land value, funding requirement or expected return.
A feasibility appraisal provides more value when it develops with the project. This does not mean rewriting the original investment case or obscuring the assumptions approved at acquisition. The original position should remain preserved so that movements can be understood.
The live appraisal should then incorporate current information as design, planning and procurement progress. Management can compare the approved case with the current forecast and identify which assumptions have improved, weakened or remained stable.
Without this connection, teams may discuss whether a project remains “on budget” without agreeing which budget is being referenced. The initial feasibility, pre-contract cost plan and live construction forecast can all contain valid figures, yet represent different moments in the development.
A connected baseline allows the developer to explain the movement between those moments. This produces a more useful commercial narrative than a collection of reports that each present a different figure without showing how it changed.
Planning is often managed through applications, conditions, consultant correspondence and design revisions. The commercial impact of this activity may not become apparent until a planning requirement alters the unit mix, net saleable area, specification or delivery programme.
When planning information and appraisal data are maintained separately, these changes can take time to reach the financial model. The design team may already be working from a revised scheme while senior reporting continues to use the previous areas or revenue assumptions.
Timing changes can be equally significant. A planning delay can extend option costs, professional appointments and finance exposure before construction begins. If the programme is updated without a corresponding change to the cash flow forecast, the project’s funding requirements and anticipated return may be overstated.
Good development management requires planning decisions to be interpreted commercially when they occur. The developer needs to understand what has changed, why it changed and which assumptions are affected. Recording the planning event without updating the development forecast preserves the history but misses the financial consequence.
Funding introduces another reporting layer. Lenders and investors require information about costs, programme, equity, drawdowns, sales or leasing assumptions and forecast returns. Much of this information already exists within the development business, but it is frequently repackaged for each submission.
Manual repackaging can create subtle differences between the internal project position and the version presented externally. A cost heading may be classified differently, a programme date may come from an earlier report, or a revised revenue assumption may reach one model but not another.
These differences become more difficult to control when reports are prepared under deadline pressure. The person compiling the funding pack may spend much of the available time locating and formatting information, leaving less time to examine whether the numbers present a coherent position.
A connected property development system gives the funding report a dependable source. Information can still be presented in the format required by the lender, but the underlying costs, dates and assumptions remain aligned with the live project record.
The flow of information should also travel back into the project. Loan covenants, drawdown conditions and approved facility limits can affect procurement decisions, payment timing and the use of contingency.
If these obligations remain confined to funding documentation, delivery teams may not see how a proposed commitment affects the facility. Finance teams may then discover the consequence after an order has been placed or a payment has become due.
Commercial visibility therefore depends on more than presenting accurate information to funders. The conditions attached to that funding should remain visible to the people making decisions throughout delivery.
Procurement is one of the points at which early assumptions are tested against the market. Tender returns provide firmer evidence about package costs, contractor availability, exclusions and delivery risk.
The commercial value of this evidence is reduced when tender comparisons are managed separately from the development appraisal. A procurement decision may be approved because it represents the strongest tender response, while the effect on the overall development return remains unclear.
The selected value should update the live commitment and forecast position while retaining the earlier allowance for comparison. This enables the developer to see whether procurement has released contingency or created additional exposure.
Exclusions and qualifications also require visibility. A lower tender may appear favourable until omitted items are included elsewhere in the budget. Preserving the relationship between the tender assessment, approval and project cost plan makes the decision easier to understand during later reporting.
Once work begins, the pace of decision-making increases. The delivery team manages programme, site conditions, design coordination and contractor performance, while the commercial team assesses commitments, applications, variations and forecast cost.
These activities are closely related, but they are often recorded through different processes. A site decision can affect cost before the commercial team has received a quotation, and a programme delay can affect finance before the next appraisal update is prepared.
During this reporting delay, the project can appear healthier than it is. The approved budget may remain unchanged even though the delivery team is already aware of additional work or a revised completion date.
The risk becomes greater when several developments are being managed at once. Small delays in updating individual projects can combine into a material distortion of portfolio cash flow, committed expenditure and projected profit.
A credible margin forecast must account for information that is known but not yet finalised. Pending variations, emerging risks and anticipated programme effects should be visible without being presented as approved facts.
This requires clear statuses and ownership. Management should be able to distinguish an agreed cost from an estimate under review, while still understanding the likely exposure associated with both.
When this information is connected to the appraisal, budget and programme, the developer can evaluate its impact before the next formal reporting cycle. Corrective action can then take place while options remain available.
Completion brings another transfer of responsibility. The construction team may hand the development to a completions, sales, leasing or asset management function. Contractors submit final accounts, outstanding defects are recorded and project documents are assembled.
Information that was weakly documented earlier becomes particularly expensive at this stage. An unresolved instruction can delay final-account agreement, while an incomplete record of specification changes can affect handover, customer queries or future asset management.
The receiving team needs more than a folder of files. It needs to understand which decisions were made, which obligations remain open and how the final asset differs from the position originally approved.
The UK BIM Framework explains that the ISO 19650 series applies across the whole lifecycle of built-environment assets. Its emphasis on managing information throughout an asset’s life supports a broader principle for developers: information should remain usable as responsibility moves between project stages and teams.
A connected handover preserves commercial and operational meaning. The asset team can trace relevant approvals, warranties, defects and project decisions without reconstructing the development’s history after the people most familiar with it have moved on.
Visibility problems become more consequential as a developer grows. Senior management needs to understand performance across multiple schemes, phases and special purpose vehicles without relying on a separate reporting exercise for each one.
If every project structures budgets, risks and forecasts differently, portfolio reporting requires interpretation before comparison can begin. Figures may be technically correct while using inconsistent definitions or reporting dates.
This limits the business’s ability to identify patterns. Repeated planning delays, tender movements or cost overruns may remain hidden within individual project reports rather than informing future acquisitions and delivery strategies.
Consistent property development data gives completed projects continuing commercial value. Actual performance can be compared with acquisition assumptions, allowing future appraisals to reflect the developer’s own delivery history rather than depending entirely on generic benchmarks.
Connected property development management does not require every department to work in exactly the same way. Acquisition, planning, finance, commercial and delivery teams have different responsibilities and require different levels of detail.
The underlying project information should nevertheless tell one coherent commercial story. An approved change to cost, programme or revenue should be reflected wherever that decision affects the development position.
Morta supports this continuity by connecting appraisals, budgets, procurement, delivery information, cash flow and reporting within one platform. Teams can work within their areas of responsibility while management retains visibility across the full property development lifecycle.
This also creates a clearer audit trail. Decision-makers can see how the current forecast developed from the original acquisition case, which movements have been approved and where unresolved exposure remains.
Property developers do not lose visibility because their projects lack information. Visibility declines when information is repeatedly transferred without retaining its context, authority and relationship to the original commercial case.
Every disconnected handover adds time to reporting and increases the possibility that decisions will be made using a partial view. The financial effect may appear through a missed cost, a delayed intervention or an appraisal assumption that remained unchanged for too long.
Maintaining a connected development record allows the business to respond earlier and report with greater confidence. It also gives senior management a defensible answer when asked where a project’s margin stands today.
To see how Morta connects development information from land acquisition through to completion, book a discovery call.
