UK Dilapidations Scott Schedule Excel Guide

A UK dilapidations Scott Schedule in Excel is the working spreadsheet that lines up each schedule item with the landlord's claim, the tenant's response, and the agreed figure. To make that file usable, repair items need to stay separate from ancillary heads such as loss of rent, rates, fees, VAT, and any section 18 adjustment, then the negotiated total can be reconciled against the final settlement invoice.

That distinction is what turns a dilapidations Scott Schedule Excel file from a summary sheet into a live negotiation record. The Schedule of Dilapidations gives the item-by-item repair case. The Quantified Demand turns that schedule and the wider heads of claim into a money claim. The Scott Schedule becomes the side-by-side working table where both parties' positions can be compared, updated, and agreed. The later settlement record shows what was actually paid or compromised. Those are related documents, but they should not be collapsed into one undifferentiated total.

In practice, a UK dilapidations quantified demand spreadsheet usually has to hold several numbers at once. The landlord's item-level costings, the tenant's competing figures, the agreed amount on each line, any broader adjustment to reflect likely loss, and the final settlement payment can all differ. If the spreadsheet treats the headline schedule total as the recoverable amount, it stops being a reliable file for negotiation and reconciliation.

Where the Schedule, Quantified Demand, and Scott Schedule sit in the UK protocol

The spreadsheet starts making sense once the document sequence is clear. A dilapidations file will usually move from an interim or terminal Schedule of Dilapidations, to a Quantified Demand, to the tenant's response, then into a Scott Schedule that records both sides' item-by-item positions. After that, practitioners may need to factor in a section 18 valuation, document any compromise in a settlement agreement, and reconcile the outcome to the final settlement invoice.

For spreadsheet design, the important point is not just chronology. It is version control. Practitioners generally work on the basis that the landlord's schedule and quantified demand are issued within 56 days after lease termination, and the tenant's response is usually due within 56 days after the quantified demand. That timing means an effective Pre-Action Protocol dilapidations spreadsheet needs clear date fields, document-version references, and enough structure to show what changed between the landlord's first position, the tenant's answer, and the later negotiated position.

The claim logic matters just as much. As the Justice UK Dilapidations Protocol states, the figures set out in the Quantified Demand should be restricted to the landlord's likely loss, which is not necessarily the same as the cost of works to remedy the breaches. That is why a terminal schedule of dilapidations data extraction workflow should not dump every monetary figure into one amount column. The workbook needs room for the schedule amount, the quantified demand position, the tenant response, and any later settlement movement to coexist without being mistaken for the same number.

Build the item-level Scott Schedule schema before you touch ancillary claims

The core Scott Schedule should stay simple and granular: one row per dilapidations item, with columns for item number, location, alleged breach, lease clause, remedy, landlord cost, tenant position, tenant figure, agreed figure, supersession or note, status, and source-page reference. That schema is detailed enough to support negotiation without forcing the reader to reopen the PDF every time a clause or cost needs checking.

This is the right place to extract Schedule of Dilapidations data into rows. Capture the narrative defect exactly enough that the item still makes sense outside the original report. Keep the clause reference in its own field rather than burying it inside a long note. Preserve the landlord dilapidations costs schedule as the landlord's line-level position, then give the tenant and agreed figures their own columns so the file can evolve into a real Scott Schedule instead of a frozen landlord schedule.

Source-page references matter more than many teams expect. When an item is disputed, the spreadsheet needs to point straight back to the originating page, schedule paragraph, or cost appendix. The same discipline behind extracting UK property completion statements into a consistent spreadsheet schema applies here: a worksheet is most useful when every row preserves enough structure to be checked, filtered, and reused later. Ancillary heads such as loss of rent or fees should not appear in this table at all, because they are not item-level repair entries and they do not negotiate in the same way.

Track section 18, void costs, and settlement invoices in a separate claims ledger

Section 18 diminution is not another repair line. It is a financial interpretation layer that can change what the claim is worth even when the item-level schedule is unchanged. For spreadsheet purposes, that means the headline schedule total, the landlord's likely-loss position, any section 18 diminution valuation, and the negotiated settlement should sit in separate fields or tabs. A section 18 issue may affect the cap on recoverable damages for disrepair, but it should not overwrite the underlying schedule rows that explain what was claimed in the first place.

The same separation applies to ancillary heads of claim. Loss of rent, rates during void, service charge during void, insurance, professional fees, VAT, and any terminal dilapidations invoice belong in a dedicated claims ledger, not inside the item-level Scott Schedule. Those heads may be negotiated globally, partly allowed, or settled on a basis that does not map neatly to individual repair items. Mixing them into the schedule table makes the file harder to read and harder to audit.

This is where cross-document property workflows start to overlap. Teams already dealing with a UK commercial service charge reconciliation workflow built around RICS-style property charges or how to extract UK business rates demand notices into Excel for property liability tracking will recognize the pattern: keep each liability type legible on its own terms, then roll the figures up in a separate reconciliation layer. A strong dilapidations claim reconciliation UK workbook does the same thing. It records the item-by-item repair dispute in one place, then tracks broader void costs, fees, VAT, and settlement payments in a ledger that can be matched back to agreements and invoices.

Extract the dilapidations pack into Excel without replacing specialist review

The operational gain here is not legal automation. It is getting the document pack into a structured file quickly enough that surveyors and solicitors can review it properly. A tool such as an AI extraction tool that turns dilapidations schedules and quantified demands into structured Excel can take PDFs or images, follow a natural-language prompt, and return structured Excel, CSV, or JSON output with source file and page references preserved for checking. That is a useful fit for terminal schedules of dilapidations data extraction because the starting problem is usually document structure, not legal judgment.

For this workflow, the prompt should ask for row-level schedule fields rather than a narrative summary. A practical pattern is: "I'm preparing a dilapidations Scott Schedule. Extract item number, location, alleged breach, lease clause, remedy, landlord cost, and source page. Create one row per schedule item." That stays close to the product's documented prompt style and gives the workbook a usable first pass rather than a block of prose. The same prompt-driven discipline is helpful in the broader commercial lease invoice and CAM review workflow, where document packs also need to become reviewable rows before anyone can reconcile them.

The limits matter. Dilapidations packs are specialized, and section 18 issues, supersession arguments, lease interpretation, and final negotiation positions still need specialist review. The safest recommendation is to test a representative sample of schedules, quantified demands, and settlement paperwork first, confirm that the extracted columns match the team's working schema, then use the tool to accelerate structuring and verification rather than to replace surveyor or legal judgment.

Use the working file to compare positions, mark agreements, and close the claim

Once the workbook is split into an item-level Scott Schedule and a separate claims ledger, it can support the whole negotiation cycle. The Scott Schedule shows the landlord's line, the tenant's answer, and the agreed figure side by side. The ledger shows how broader quantified demand settlement movement affects the total claim. Together, they give the team one file that can be filtered by issue, cost type, status, or stage of negotiation.

Status fields make the file much easier to use in live matters. Simple labels such as open, under review, agreed, removed, settled, invoiced, and paid are usually enough. They help a surveyor or property-finance team see which repair items are still disputed, which ancillary heads have been agreed in principle, and which payments or settlement invoices still need to be matched back to the negotiated position.

The close-out step is to preserve the history instead of overwriting it. Keep the original landlord figures, the tenant response, the agreed item position, the separate section 18 or likely-loss view, and the final payment record visible in the workbook, with document references back to the settlement agreement or invoice where relevant. That creates an auditable trail from initial schedule to compromise payment, which is what makes the spreadsheet useful after the meeting, after the invoice arrives, and after the claim is supposed to be finished.