A Lender-Side Report Review Process That Works

A report can contain sound valuation judgement and still create an avoidable lender query. The usual cause is not a weak opinion of value. It is a figure that does not reconcile, a lease term stated differently in two places, or an instruction point that has been addressed in the body but omitted from the conclusion. A disciplined lender-side report review process is designed to find those issues before the report reaches credit.

For lender-side teams and panel managers, the task is not to revalue every property. It is to establish whether the report answers the instruction, supports its conclusions and reads as one coherent document. The review needs to be proportionate, but it also needs to be repeatable when volumes rise.

What a lender-side review is really testing

The first question is whether the report can be relied on for the lending decision intended. That involves more than checking the market value against the loan request. A reviewer is testing the relationship between the instruction, inspection evidence, comparable evidence, assumptions, calculations and final figures.

A report may state a market value of £2,500,000 on the executive summary, but show £2,550,000 in the valuation section after a late amendment. Either figure may be defensible. The mismatch is still material because it leaves the lender unclear which conclusion the valuer intends to provide.

The same principle applies to market rent, net initial yield, floor area and unexpired term. These are not isolated data points. They drive the valuation narrative and can alter a lender's view of security, covenant strength or asset liquidity.

A good review therefore asks two related questions: has the valuer exercised and explained appropriate professional judgement, and does every relevant part of the report support that judgement? The first requires an experienced reviewer. The second can be checked more systematically.

Build the lender-side report review process around the instruction

Start with the instruction, not the valuation figure

Reviewers should have the lender's requirements alongside the report from the outset. The most efficient process is to turn these requirements into a clear review schedule. This does not need to be a long checklist for every instruction. It should focus attention on the points that affect lending reliance.

For example, the schedule might require a stated marketing period, commentary on tenant covenant, a minimum number of comparable transactions, an EWS1 disclosure where relevant, or explicit treatment of vacant space. The report should be tested against the actual instruction rather than a generic template.

This matters because an omission can be difficult to spot once a reviewer is drawn into the valuation rationale. A report may include good comparable evidence and a sensible yield, yet still fail to confirm the required exposure period. That is an instruction issue, not necessarily a valuation issue, but it can still hold up the lending decision.

Reconcile the report as one document

Many review findings sit at the joins between sections. A valuer may correctly amend an area following inspection, then update the comparable analysis but not the valuation table. Or a lease event may be described accurately in the tenancy section but the unexpired term in the summary remains based on an earlier date.

The review should compare repeated facts across the document, including:

• market value, market rent and special assumptions;
• net internal area, gross internal area and adopted floor areas;
• yields, capital values and rental tones;
• lease start and expiry dates, break dates and rent review dates; and
• comparable addresses, transaction dates and analysis figures.

These checks are straightforward in principle but demanding at volume. A 90-page report may repeat a market value six times, an area ten times and a key date across several sections. Reading carefully remains essential, but a reviewer should not have to rely on memory to identify every repeated reference.

Test the calculation trail

Not every figure needs recalculating from first principles. The review should focus on calculations that are material to the conclusion or appear inconsistent with the narrative.

Consider an investment valuation based on £180,000 passing rent capitalised at 6.00%. Before deductions, that indicates £3,000,000. If the reported figure is £3,180,000, the reviewer needs to understand whether the difference reflects a rent-free adjustment, a purchaser's costs treatment, a reversionary element or a simple formula error. The objective is not to prescribe methodology. It is to ensure the calculation and explanation lead to the same conclusion.

The same discipline applies to price per square metre. If a comparable is stated as 1,200 sq m at £4,800,000, the analysed rate should be £4,000 per sq m. A rate of £4,400 per sq m could be a transcription error, an incorrect adopted area or an explanation that has not made it into the report. Each possibility warrants a question before sign-off.

Read comparable evidence for relevance, not just quantity

A lender-side reviewer should be wary of a report that has sufficient comparable entries but weak links between the evidence and the adopted figure. Comparable evidence should be identifiable, dated appropriately and analysed consistently. Differences in tenure, condition, location, lease length and transaction circumstances should be addressed where they materially affect the comparison.

There is no universal answer to how much evidence is enough. A prime, transparent market may support a conclusion with a relatively narrow evidence set. A specialist asset, thinly traded location or unusual lot size may require more explanation even where transactions are limited. The key is whether the report makes the valuer's reasoning intelligible and whether the lender's minimum evidence requirements have been met.

Treat exceptions by risk and clarity

A useful review process does not generate queries for their own sake. It separates points that require clarification from points that are clearly immaterial.

A £50,000 mismatch between a £5,000,000 market value in the conclusion and £5,050,000 in a table should be returned. So should a missing EWS1 disclosure where the instruction requires one, or a tenant covenant statement that names the wrong entity after a report amendment. These are clear issues with a direct effect on reliance.

By contrast, a formatting inconsistency with no bearing on the instruction or valuation may be recorded but need not delay the report. The reviewer needs a consistent materiality threshold, particularly when reviewing high volumes. Otherwise, the process becomes slow without making the lending decision safer.

Queries should be precise. Instead of asking a valuer to "review the valuation", identify the page, figure and discrepancy: "The executive summary states £2,500,000, while the valuation conclusion on page 42 states £2,550,000. Please confirm the final market value and amend the report where required." Specific queries reduce unnecessary correspondence and provide a clear audit trail.

Make review repeatable without making it mechanical

The strongest processes combine defined controls with professional judgement. A first-pass audit can check instruction requirements, repeated values, dates, units and calculations. An experienced reviewer can then concentrate on the parts that need context: the choice of comparables, the adopted yield, unusual assumptions and the adequacy of narrative explanation.

Version control is equally important. The report reviewed must be the report issued. If a valuer makes a substantive amendment following a query, the amended areas should be checked again and the final file should be clearly identified. Late changes are where previously resolved figures can reappear in the wrong form.

Review teams also benefit from recording recurring findings. If several reports omit a required marketing-period statement, the answer may be a clearer instruction note or a template change. If calculations repeatedly differ between analysis tables and conclusions, the team may need a more focused reconciliation step. The purpose is not to score valuers. It is to improve the system around them.

Where automated checking earns its place

Document-level checking is well suited to the repetitive part of the task. It can compare figures across a report, identify contradictory dates, flag missing instruction items and test whether calculations reconcile. It does not decide whether 6.25% is the right yield for an asset. That remains a matter of valuation judgement.

WriteUp applies this approach to RICS valuation reports, reviewing draft documents against Red Book requirements, lender instructions and client-specific criteria. Findings should be treated as prompts for the surveyor or reviewer to assess, not as automatic conclusions. Private encrypted processing, with no report storage or model training, also matters where confidential lending and client information is involved.

The practical benefit is not that a tool replaces the review. It gives the reviewer a second pair of eyes for the details most vulnerable to time pressure and report-wide inconsistency. That leaves more time for the judgement a lender-side review actually depends on.

A report that stands up under scrutiny is usually the result of small disciplines applied consistently: start with the instruction, reconcile the evidence, ask clear questions and ensure the final version is the one that was reviewed.