Mastering the Real Estate Underwriting Process
By Domus
By Domus
You're probably looking at a site that seems to work. The headline numbers look fine, the agent is pushing for speed, the landowner wants certainty, and the spreadsheet says there's enough margin to keep going. Then the lender starts asking awkward questions. Is planning policy supportive of the scheme you're assuming? Where is the evidence for your GDV? How does the cashflow behave if consent slips? Why does the draw schedule not match the build programme?
That's where many deals stop feeling attractive.
A disciplined real estate underwriting process is what separates a workable project from a site that only looked good in a thin appraisal. In UK development finance, that process is less about proving a deal can work in perfect conditions and more about proving it still holds together when planning, cost, and timing start moving against you.
The expensive mistakes usually don't come from a dramatic market event. They come from small assumptions nobody pinned down early enough.
A developer agrees terms on a site based on a quick residual. Sales values are taken from a broad area average. Build costs come from an old scheme. Planning is treated as straightforward because the site allocation looks encouraging. Months later, after legal fees, consultant fees, and management time have already gone in, underwriting exposes the weak points. Access isn't as clean as assumed. Abnormals were underplayed. The planning path is longer than expected. The finance structure no longer supports the programme.
That isn't bad luck. It's failed underwriting.
Good underwriting forces every major assumption into the open and asks a simple question. Is there enough evidence behind this number, this timeline, and this risk allowance to commit capital?
In practice, that means testing the deal as a linked system:
Underwriting is where optimism meets documentation.
A lot of teams still run this process through disconnected spreadsheets, email chains, old appraisals, and consultant PDFs scattered across folders. That creates friction at exactly the point where clarity matters most. People re key numbers, lose version control, and argue over which appraisal is current.
The danger isn't only that a lender declines the deal. It's that you spend too long chasing a site that should have been screened out in week one.
The strongest operators aren't just good at finding opportunities. They're good at killing weak opportunities early, before internal time and external costs start compounding. Rigorous underwriting protects margin, but it also protects attention. That matters just as much.
Monday morning, a site lands in the inbox with a tight bid deadline, a glossy agent pack, and a price that looks just about workable if everything goes right. That is exactly when poor discipline costs money. Teams rush into a full appraisal, pass files around by email, and spend days arguing over assumptions that should have been screened in the first hour.
Initial screening is a filter for attention. The job is to decide whether the opportunity merits survey costs, consultant input, and management time. A quick screen is fine. A loose screen is expensive.

Start with evidence you can gather fast, and record the basis for each conclusion. If the answer is unclear, mark it as a live risk rather than smoothing it over in the notes.
Plenty of schemes are workable in isolation and still wrong for the buyer. Check location, asset type, likely unit mix, planning complexity, deal size, and whether your team can deliver it. A developer set up for straightforward suburban housing should be cautious about city centre conversion stock with heritage issues and a complicated servicing arrangement.
Is there a credible planning route
Early planning review should be blunt. Look at allocation status, policy position, precedent nearby, access, massing constraints, heritage, trees, flood risk, ecology, and local political sensitivity. If the scheme only works at a density the authority is unlikely to support, that needs to be visible from day one.
Can the headline economics survive a rough cut
Build a simple appraisal with conservative assumptions and enough detail to expose weak points. Land price, build cost, programme, sales pace, and contingency should all be credible at this stage. If you need aggressive values to make a thin margin look acceptable, the problem is already in front of you. For teams who need a quick refresher on value build-up, this guide to gross development value in property appraisals is a useful reference.
Is there a realistic funding route
Finance should be screened early, not bolted on after the land bid. A scheme may look attractive on paper and still fail because the equity requirement is too high, the planning position is too thin for the lender, or the projected timings create pressure on interest cover and exit. If senior debt is likely to be cautious, treat that as a pricing issue immediately.
Some points justify an early no. Others justify a lower land value, a revised structure, or a decision to wait until better evidence is available.
After the desk screen, a short explainer like this can help junior analysts align the process before they go deeper.
Back of envelope judgement still has value. Experienced operators can reject weak sites quickly because they know their patch, their lenders, and their build team. The problem starts when that judgement lives only in one person's head or in a spreadsheet saved across five different folders.
A structured screen gives the team a shared standard. Every deal gets the same core tests, the same evidence prompts, and the same decision trail. That matters when bids move quickly, when multiple analysts are involved, or when an investment committee asks why a site was approved in the first place.
Connected systems are materially superior to scattered spreadsheets and email threads. A platform like Domus does not replace judgement. It records assumptions, keeps supporting evidence tied to the appraisal, and creates an audit trail around the early go or no-go decision. That reduces rework later, especially when planning risk, cost updates, and lender questions start landing at the same time.
Once a site survives screening, the model has to do more than show profit. It has to explain why the project is viable and where that viability is fragile.
That starts with GDV, because every downstream decision depends on it. If your value assumption is loose, your land value, finance requirement, and margin all become unreliable.

A defensible GDV comes from current comparables, product matching, and a clear view of buyer or occupier demand. Broad market averages rarely help. A one bed flat in the wrong micro location can distort the whole appraisal if you use it as a benchmark for family units in a different position.
If you need a practical refresher on the mechanics, this guide on gross development value is a useful starting point.
What matters in live underwriting is the quality of the evidence pack behind the number:
Practical rule: If you can't explain each GDV input line by line to a credit committee, the number isn't ready.
Residual land value often gives false comfort because it converts a stack of assumptions into a single answer. That answer looks precise, but it's only as sound as the inputs feeding it.
In UK development underwriting, residual land value is highly sensitive to planning and construction assumptions because policy risk, abnormal costs, and delayed consent can erode the developer's margin before a site is acquired. Underwriters therefore stress test GDV, build cost, finance cost, and exit values together rather than in isolation, as explained in this overview of real estate underwriting.
A practical example makes the point. Suppose your base appraisal shows enough headroom to bid for the site. If planning takes longer, finance runs for longer. If the programme extends, prelims and overhead move. If values soften while costs stay firm, the residual falls from both sides. None of these shifts happens neatly on its own in real life. They arrive together.
Spreadsheets aren't the issue by themselves. The issue is what happens when several people keep changing them.
Version confusion is common. One file has updated costs but old values. Another has the revised programme but no change to finance timing. Someone copies a tab into a new deal. A formula breaks imperceptibly. The final residual still looks clean, but nobody can audit how it got there.
A sound model should let you trace every assumption back to evidence, test multiple scenarios quickly, and preserve a clear history of changes. If it can't do that, it becomes hard to defend when scrutiny increases.
Projects don't fail only because the total cost is wrong. They fail because the timing of cost and funding is wrong.
A paper profit can still hide a liquidity problem. That's why serious underwriting always moves from static cost totals to timed cashflow.
Junior analysts often focus on the headline construction cost because it's visible and easy to compare. In practice, the full cost stack is what matters.
A proper appraisal usually needs to account for several layers:
The mistake is to treat these as a shopping list. They need to be sequenced against the programme because that affects peak debt and interest carry.
A development rarely spends evenly. Early months may be heavy on planning, pre start design, and legal work. Mid programme tends to carry the main construction burden. Later periods may include fit out, sales costs, and finance tail.
That's why underwriters model monthly cash movement rather than relying on annual or total figures. A rough S curve is often the best way to think about it. Spend ramps up, peaks during the main build period, then tapers.
Here's a simplified view of what you are trying to understand:
| Cashflow question | Why it matters |
|---|---|
| When does the project hit peak cash requirement | This shapes the funding need and the equity timing |
| When are major planning or statutory costs due | Early outflows can pressure liquidity before debt is fully available |
| When do sales or refinance proceeds arrive | Delayed receipts extend interest and working capital pressure |
| Does the draw schedule match actual progress | A mismatch can create a cash gap even in a profitable scheme |
Consider a scheme with healthy headline margin. The developer assumes sales proceeds begin soon after practical completion, so the total finance cost looks manageable. But the lender releases debt in stages based on verified progress, and the contractor payment profile is front loaded. If planning conditions delay mobilisation or utilities drag, the project burns cash before receipts arrive.
The profit may still exist on paper. The problem is that the business can't comfortably fund the path to reach it.
A scheme with decent margin and weak cashflow is not a robust scheme.
The best appraisals tie cost categories to dates, then align funding drawdowns to realistic milestones. When that's done properly, the finance cost becomes something you understand, not a plug figure added at the end.
A deal can show a healthy profit and still fail at credit committee because the debt structure does not fit the lender's rules. That catches junior analysts out all the time. They spend hours refining GDV and margin, then discover the scheme needs more debt financing than the market will support or relies on covenant assumptions the lender will not accept.
Lenders are not pricing your ambition. They are testing whether the loan still looks money-good if the scheme slips, values soften, or costs land higher than expected.
In UK development finance, lender appetite is usually framed by a small set of controls. Loan to value, loan to cost, interest cover or debt service cover where relevant, minimum profit on cost, and clear evidence of sponsor equity. The exact mix changes by lender and asset class, but the principle stays the same. If the structure falls outside the credit box, projected profit does not rescue it.
That is why a messy spreadsheet process causes real problems here. If funding assumptions sit in one file, build costs in another, and equity sources in an email trail, it becomes hard to show how the debt has been sized and why the covenants are defensible. A connected audit trail helps because every ratio can be traced back to an assumption, document, or approval rather than explained away after the fact.
Loan to value measures debt against the lender's view of current or end value, depending on the facility structure. It is the lender's protection against value movement. If the exit value comes under pressure, this is the first cushion they look at.
Loan to cost measures debt against total scheme cost. It shows how much actual risk capital the sponsor has committed. Inflated equity stories do not survive scrutiny for long. Lenders want to see cash equity, deferred land terms properly documented, and any mezzanine piece clearly identified for what it is.
Debt Service Coverage Ratio asks whether the scheme or stabilised asset can service the debt under the proposed terms. On investment deals this sits near the centre of the analysis. On development deals, it may be less prominent during the build and more relevant on refinance, term debt, or income-producing phases.
Here is the practical lens:
| Metric | What the lender is really asking |
|---|---|
| LTV | If value weakens, is there enough headroom left |
| LTC | Is the sponsor putting in real equity and staying exposed |
| DSCR | Can the asset support interest and repayments under realistic assumptions |
A clean, lower-risk scheme may suit straight senior debt. A tighter deal may need more equity, a smaller facility, a different repayment profile, or a phased structure that reflects planning and delivery risk. Seeking the highest possible debt portion in the initial proposal often wastes time. The better approach is to size debt to what the lender can defend internally, then test whether the remaining equity requirement still works for the sponsor.
That is also where junior teams make avoidable errors. They model debt as a single line item instead of a negotiated structure with conditions, covenants, monitoring requirements, and release mechanics. In live transactions, those details decide whether funds arrive when needed.
For a wider view of how facilities are typically set up, see this guide to property development finance in the UK.
Credit teams respond well to deals that are clearly structured before submission, especially when the evidence is easy to follow. That usually means:
The strongest submissions are rarely the most aggressive. They are the ones a lender can understand, verify, and approve without spending two weeks untangling the model.
The base case is only the opening position. Real underwriting starts when you ask what happens if the project doesn't behave as planned.
That matters even more in UK development, where timing risk often outweighs pure borrower risk.

UK underwriters increasingly need scenario based evidence on planning milestones and cost inflation sensitivity. A key challenge for many lenders involves whether the evidence pack can defend the margin when the main threat is schedule slippage from planning delays or cost volatility, not simple borrower default, as discussed in this underwriting perspective.
That changes how you should test a deal.
A weak process tests one variable at a time because it's quick. A better process recognises that delay usually affects several lines together. Programme moves. Finance cost extends. Contractor pricing may change. Exit timing shifts. Sometimes values move as well.
Instead of producing one polished appraisal, build a scenario pack that answers these questions:
A useful reference point is this guide to sensitivity analysis, especially if you're building scenario logic for credit review rather than internal bidding only.
Lenders don't expect certainty. They expect a sponsor to show where the uncertainty sits and how the deal behaves when it shows up.
A credible stress test is not just a revised headline profit figure. It should show:
Connected systems are more useful than disconnected files. Domus is one example of a platform built for UK development teams that need viability, planning, finance, and evidence review in one workflow, with scenario testing and lender ready outputs tied back to a shared project baseline. That matters because re keying assumptions across separate tools is one of the easiest ways to break a risk review.
By the time a deal reaches credit, the numbers alone won't carry it. The lender needs a decision pack that makes the assumptions easy to follow, easy to verify, and hard to challenge.
A messy pack slows credit down. A coherent pack helps the underwriter build the internal case for approval.
Many sponsors treat the evidence pack as admin. It isn't. It is the document set that answers the lender's hidden question. Why should we trust this appraisal enough to advance capital against it?
When the pack is poor, underwriters start reconstructing the scheme themselves. That creates delay, more questions, and often less confidence. When the pack is organised, the reviewer can move from assumption to evidence without friction.
The quality of the pack often shapes the quality of the credit conversation.
| Category | Key Documents & Evidence |
|---|---|
| Site and legal | Title documents, plan, ownership position, rights of way, access information, option or contract terms |
| Planning | Planning history, policy review, consultant advice, application status, draft layouts, design rationale, key constraints |
| Market and value | Comparable sales or lettings evidence, local market commentary, product positioning, valuation support |
| Cost and programme | Cost plan, contractor input, abnormal cost notes, programme, procurement route, phasing assumptions |
| Financial appraisal | GDV build up, residual land value analysis, cashflow, finance assumptions, downside scenarios |
| Sponsorship | Borrower structure, track record, source of equity, team biographies, professional appointments |
| Finance request | Loan amount sought, use of funds, draw schedule, repayment route, covenant assumptions |
| Risk and mitigation | Summary of key risks, planning and delivery dependencies, contingency logic, monitoring proposals |
Three habits make packs materially better.
A junior analyst should aim for a pack that a credit officer can go through without calling for a guided tour. If the reviewer has to chase basic evidence, the pack isn't finished.
The most common underwriting failures are repetitive. Teams overstate GDV, underplay abnormal costs, use a programme that assumes everything goes right, and then submit a pack that leaves the lender doing detective work.
The fix is rarely complicated. It's disciplined.

A practical checklist helps:
The strongest underwriting process isn't the one with the fanciest spreadsheet. It's the one that turns fragmented deal data into a consistent, auditable decision.
If your team is still underwriting through disconnected spreadsheets, consultant PDFs, and email chains, Domus is built for a more structured UK workflow. It brings viability, planning, finance, and lender evidence into one connected process so developers, analysts, and capital teams can assess sites, test scenarios, and prepare investment decisions with a clearer audit trail.
From Domus
Domus gives UK developers a structured platform to run development appraisals, residual land value models, planning viability assessments, and cashflow — all in one place.
Domus