How Valuation QA Software Reviews Red Book Reports

A £50,000 discrepancy between the market value in the executive summary and the figure stated in the valuation conclusion is not usually a valuation judgement problem. It is often a drafting, amendment or copy-and-paste problem. Valuation QA software is designed to help find this type of issue before the report reaches a lender, client or panel manager.

That matters because a Red Book report is not read as a series of isolated pages. The market value, market rent, floor areas, tenancy information, comparable evidence, assumptions and calculations all need to make sense together. A careful final review remains essential, but time pressure can make it difficult to re-check every repeated figure and every cross-reference with fresh eyes.

The useful role of software is not to decide whether a property is worth £2.75 million or £2.9 million. That remains the registered valuer's judgement. Its role is to carry out repetitive checks quickly, flag points for review and help the valuer focus attention where professional judgement is needed.

What valuation QA software should review

The starting point is breadth. A useful audit should read the report as one document, rather than checking only spelling, formatting or whether a total has been calculated correctly. It should compare figures and statements wherever they appear, including the instruction, executive summary, property description, valuation rationale, comparable schedule and appendices.

A report may state a net internal area of 1,250 sq m in the property description, but use 1,205 sq m in the valuation calculation. It may refer to a passing rent of £186,000 per annum in the tenancy section, while the investment method uses £168,000. Neither point necessarily means the valuation is wrong. There may be a clear reason. The issue is whether the difference has been identified, explained and reflected consistently throughout the report.

The same applies to dates. A comparable transaction from September 2023 may be described as having occurred "last year" in a report valued in January 2025. A reviewer will usually catch that. At volume, however, stale narrative can survive a revised draft even when the core valuation work has been updated correctly.

Figures that do not reconcile

Capital values, market rents, yields, floor areas, lease terms and valuation dates all tend to recur. Each repetition creates a chance for a number to fall out of step after an amendment.

A document audit can compare the stated market value against the conclusion, summary table, valuation certificate and any sensitivity analysis. It can flag where a yield of 5.25% is stated in the narrative but 5.5% is used in the calculation, or where the valuation date is 31 March in one section and 30 March elsewhere.

The valuer then decides what the flag means. A rounded figure in a narrative paragraph may be reasonable. A different figure in a formal conclusion needs resolving. Software should raise the question, not invent the answer.

Report-wide contradictions

Some of the more difficult issues are not numerical. A report might describe a tenant as having a strong covenant in one section, then refer elsewhere to a recent deterioration in trading performance without explaining the conclusion. It might state that the property is fully let, while the tenancy schedule records a vacant suite. It may describe a lease as having eight years unexpired when the stated expiry date indicates six.

These are the points that can be hard to spot through a linear read. The report may be technically well drafted paragraph by paragraph, but still contain statements that do not sit comfortably together. A good review tool looks for those connections and presents the relevant passages so the surveyor can assess context.

Comparable evidence and valuation rationale

Comparable evidence deserves a different level of checking from basic document consistency. Software can identify where comparable dates, prices, areas, analysed rates or yields do not reconcile between the narrative and schedule. It can also flag a missing analysis field or a comparable referred to in the rationale but absent from the evidence table.

It cannot determine whether a comparable is truly comparable, whether an adjustment is appropriate or whether the evidence supports the adopted figure. Those are professional decisions. What it can do is help ensure that the evidence actually presented supports the method described, and that the report does not rely on a figure which has changed elsewhere in the draft.

Reviewing against Red Book and instruction requirements

A review is not complete merely because the arithmetic works. Lender and client requirements frequently sit alongside Red Book reporting requirements, and they can vary by instruction, asset type and circumstance.

For example, an instruction may require a stated marketing period, a minimum number of comparable transactions, specific commentary on a material uncertainty, or confirmation of an EWS1 position where relevant. A report can be well reasoned but still be returned because one required disclosure is absent or is buried in a section where the reviewer cannot locate it.

The practical value of valuation QA software is that criteria can be applied consistently across drafts. Instead of relying on a reviewer to remember every panel or client requirement each time, the software can check whether the requested points appear and flag apparent omissions. It should not claim to guarantee compliance. Instructions often require interpretation, and the surveyor remains responsible for deciding whether the report addresses them properly.

Where the time saving actually comes from

The benefit is not simply reading a 70-page report faster. It is reducing the time spent on mechanical checking after the valuation work is complete.

A conventional final review often involves searching the document for the market value, then the rent, then the area, then the valuation date, before moving on to the tenancy details and comparable schedule. That is sensible practice, but it is repetitive. It also asks the reviewer to retain many figures and qualifications in their head while reading under deadline.

An automated audit can complete those cross-checks in one to two minutes and return a structured set of findings. The reviewer can then work through the points that merit attention: a £50,000 value mismatch, a missing EWS1 disclosure, an inconsistent lease expiry date or a comparable rate that does not match the calculation.

Not every flag will lead to a change. That is expected. A useful system gives the surveyor the information needed to make a quick, informed decision, rather than creating a new administrative task.

Data security and professional control

Report confidentiality is a reasonable concern. Valuation reports contain client information, transaction evidence, borrower details and professional analysis. Any software used for review should make clear where data is processed, how it is protected and whether report content is retained or used to train models.

For a practice, the questions should be practical: Is processing encrypted? Is uploaded report data stored after the audit? Is it used for model training? Who can access the findings? Can the firm retain its normal document-control process?

WriteUp is built for this use case, with private encrypted processing, no report data storage and no model training on uploaded reports. The audit is a second pair of eyes before the report leaves the desk. The valuer reviews every finding and retains full control of the final document and professional opinion.

Choosing a review process that fits the firm

The right approach depends on report volume and how reviews are currently managed. A sole registered valuer may use a software audit as a disciplined final check before issue. A team may use it to support peer review, particularly during busy periods. A lender-side function may need consistent checks across reports from multiple panel firms, with clear visibility of recurring issues.

The tool should fit the existing review process, not displace it. It should be straightforward to use, relevant to UK valuation reporting and capable of checking the items that genuinely matter in a Red Book report. Generic document software may identify a typo, but it is less likely to understand why a market rent, unexpired term or adopted yield needs to reconcile across the whole report.

A final review is where good valuation work is tested against the document that will be relied upon. The aim is not to make the process automatic. It is to give the surveyor a clearer view of what deserves one more look, before it becomes someone else's query.