Somewhere on every project there's a moment when a person holding a trowel needs to know which tile goes in the ensuite — and the answer is in a saved quote, a Pinterest board, an email from March, and your head. The finishes schedule is the document that makes that moment boring.
A finishes schedule (you'll also hear "schedule of finishes") is a room-by-room specification of every surface in the project: what product goes where, in what finish and colour, in what size and quantity, supplied by whom, at what status. It's a working document while you design, and an issued document when the pricing and the building start. Contractors price from it. Trades build from it. Clients approve the selections that end up on it.
It is not a budget — money doesn't belong on it, because it's handed to people who shouldn't see your numbers. It's not a mood board — nothing on it is aspirational. And it's not an FF&E schedule, though the two live side by side on every job. Finishes are what gets built in: flooring, wall treatments, tiles, joinery, benchtops, hardware. FF&E — furniture, fixtures and equipment — is what gets placed in the room afterwards. They're separate documents because different people consume them: the finishes schedule goes to the builder; the FF&E schedule drives your own procurement. (Tracking that side of the job well is its own discipline — we've written about what FF&E tracking has to cover separately.)
The structure: rooms first, then surfaces
A schedule that's just a long list of products is a list, not a schedule. The structure that makes it usable on site is two levels deep:
Room by room. Every line belongs to a room — Ensuite, Kitchen, Master Bedroom. The tiler pricing the ensuite should be able to filter to the ensuite and see everything that concerns them, and nothing that doesn't.
Surface by surface within the room. Within each room, lines are sectioned by application: walls, floor, ceiling, joinery, skirting and trim, splashback, benchtop, hardware. This is the sectioning contractors expect, because it's how trades divide the work — the painter reads the wall lines, the flooring contractor reads the floor lines. A schedule sectioned any other way makes every trade read every line.
Keep the vocabulary consistent. If it's "Joinery" in the kitchen, it isn't "Cabinetry" in the laundry. Filters, and people, rely on the words repeating.
The columns that matter
Ask what the person on the other end needs to buy, price, or install the thing without ringing you. That gives you a stable set:
- Code — the reference code (more on this below).
- Room and surface/application — where it goes.
- Product / material — what it is, in words a supplier recognises.
- Manufacturer and supplier — who makes it and who you're buying it from. These are different companies more often than not, and conflating them is how the wrong rep gets called.
- Product code — the manufacturer's SKU, so "the oak one" has an unambiguous identity.
- Finish / colour — matt, honed, brushed brass, Half Strength Natural White. The line most likely to cause a repaint if it's vague.
- Size and quantity + unit — 600×600mm, 43 m². Quantities in units the trade prices in: square metres for tiles, lineal metres for skirting, each for hardware.
- Supplied by — designer, contractor, or client. Arguments about who was buying the tapware are all avoidable, and this column is how.
- Status — draft, specified, issued for approval, approved, ordered, installed. The schedule should answer "where are we with the splashback?" without a meeting.
- Notes — lay direction, grout colour, "template before fabrication". The line-level fine print.
What's deliberately missing: prices. A finishes schedule travels — to the builder, to trades, often to the client. Your trade pricing and margin live in the budget, which travels to nobody.
Reference codes: the part that makes it a schedule
The single feature that separates a professional finishes schedule from a nicely formatted list is the reference code: FL-01, WA-02, JN-03. A short prefix for the application — FL floors, WA walls, CL ceilings, JN joinery, HW hardware — plus a sequence number, one code per distinct product.
The codes exist for exactly one reason: cross-referencing to drawings. "FL-01" written on the floor plan and "FL-01" on the schedule means the drawing shows where and the schedule says what, and neither document has to repeat the other. Without codes, the drawing says "engineered oak" and the schedule has three engineered oaks, and someone on site makes a decision you find out about at handover.
Two rules of code discipline:
- One code per product, not per room. If the same oak runs through the living room and hallway, it's FL-01 in both. The code identifies the product; the room column says where it goes.
- Never renumber mid-job. Codes are only useful because they're stable. If FL-02 gets cut from the project, retire the code — don't shuffle FL-03 up to fill the gap, because a drawing set printed last month still says FL-03 and now means the wrong floor.
Revision discipline: the unglamorous tab that wins arguments
A finishes schedule is issued, not shared. That distinction is the whole game.
A shared document changes under people. An issued document is frozen: Rev A, issued 12 September, to the builder, for approval — and any change after that becomes Rev B, with a note of what changed. The revision register (rev, date, status, issued to, what changed) settles every "that's not the version I have" dispute before it starts, because there's a table that says exactly who was sent what, when.
Three habits make it work:
- Bump the revision every time it leaves you. Even for one changed line. Especially for one changed line — small silent changes are the ones that get built wrong.
- Say what changed. "Rev C — ensuite floor tile changed FL-04 → FL-07; WA-02 grout colour updated." The builder shouldn't have to diff two PDFs to find it.
- Never edit an issued revision. The copy you sent is a historical fact. The working file rolls forward; the issued ones are frozen.
This is also the discipline that most often collapses in a spreadsheet, because a spreadsheet has no concept of "issued" — just Save As, and a folder of files named FINAL-v3-USE-THIS-ONE.
What contractors are looking for
If you want the schedule that stops the phone ringing, build it for its harshest reader. A contractor pricing or building from your schedule needs, in roughly this order: an unambiguous product identity (manufacturer + product code, not a vibe), quantities in the units they price in, who's supplying each item, where each product goes (codes matching the drawing set), which revision is current — and a direct line in the notes for anything that affects labour, because "herringbone" is a different price to "straight lay" for the same FL-01.
Give them that and the questions that remain are the genuinely useful ones.
Build one today
You don't need software to start — you need the structure above in a workbook you'll keep current. We've built a free finishes schedule template the way schedules are issued on real jobs: a revision register, room-by-room surface sectioning, the reference-code legend, and an FF&E schedule tab alongside it. Excel and Google Sheets, print-ready at A4 landscape, no charge.
And an honest note on where the format strains: the schedule is a document, but the decisions on it are live — clients approving selections, statuses moving, prices shifting underneath. That's the gap Mortar was built for: the same room-by-room selections, with client approvals recorded on each item and trade pricing your client never sees, so the document you issue is generated from a project that's current instead of maintained by hand at 11pm.
