Setting up a renovation job the right way: scope, stages, and payments

The four decisions that have to happen before a hammer moves

Most renovation jobs that go wrong do not go wrong on site. They go wrong before the site opens, because one of these four decisions was skipped, left implicit, or decided only in conversation.

1. Scope. Exactly what work is being done, room by room, at what specification.
2. Stages. How the job breaks into discrete, priced, deliverable chunks, and the definition of done for each one.
3. Deadlines. The expected start and end date, with a tolerance.
4. Responsibilities. Who orders what, who coordinates specialists, who supplies materials the client has chosen.

Everything you will later do on the job, the client update, the change order, the final walkthrough, the payment, references one of these four decisions. Made properly, the later event is easy. Skipped, the later event is a fight.

These four decisions are what Renno is built around. You make them once, in the project setup. From there, Renno carries them.

1. Scope: the decision that carries the most weight

Scope is best written room by room, in short, specific lines, with materials named. See our guide on the quote template for the full detail. For the setup, the test is whether someone other than you could read your scope and price the labour and materials to within 10%. If they could, the scope is strong enough to stage. If they could not, you are about to stage a negotiation, not a job.

2. Stages: the structure that does the admin for you

Stages are how the job breaks into discrete, priced, deliverable chunks. A stage is not a stage without its definition of done: the sentence or two that says what has to be true for it to be signed off, paid, and closed.

The shape of the stages depends on the job. Two realistic examples:

The number matters less than the structure. Every stage has a price, a definition of done, and a clean release.

A good definition of done is a list of concrete things that have happened. Three examples, from the jobs above:

• Kitchen, rough-in. Plumbing rough-in for sink and dishwasher complete and pressure-tested. Electrical rough-in for hob, oven, and lighting circuits complete. Any structural changes signed off. Walls plastered and ready for tile and paint.
• Whole house, second fix. Second-fix plumbing, electrics, and joinery installed. Tiling complete to all wet walls. Sanitaryware fitted and commissioned. Decoration complete to quoted rooms. All certificates (Part P, gas where applicable) issued.
• Any job, final stage. Snagging list addressed. Client walkthrough completed. Defect-free sign-off or agreed short-list of remaining items with agreed resolution date. Keys handed back. Handover pack delivered.

Notice what the definitions of done are not: they are not “client is happy.” They are a list of concrete things that happened. “Client is happy” sits on top of concrete things, not in place of them.

3. Deadlines: a date plus a tolerance

An expected end date on a renovation should come with a tolerance. “Expected completion: week 12. A delay of up to 10 working days does not constitute a breach. Delays beyond that trigger a written agreement on a new end date.” That is a complete deadline. “Approximately three months” is not.

The tolerance is not a permission slip to run late. It is an honest acknowledgement that trades, deliveries, and weather all move, and a defined point at which a conversation becomes necessary. Clients prefer the tolerance version almost universally, because it gives them a number they can plan around.

This belongs in your contract, not in a text thread or a verbal aside. The tolerance, the trigger point for renegotiating an end date, and what counts as a breach should all be written down once, alongside the rest of the legal terms.

4. Responsibilities: who does what, written once

Three columns do most of the work here: item, who supplies, who installs. A one-page table for a renovation over £10,000 prevents about 80% of “I thought you were ordering that” conversations.

How Renno turns the setup into a running job

The four decisions above are the spine of every renovation. On Renno, three of them are the setup, the fourth is a single file you upload, and the contract that holds them all together goes on the project once your client has signed off. You put it together once. From that point, the project runs against it.

Here is what that looks like in practice:

• Scope sits at the top of the project, visible to both sides, in one place. Mid-job changes go through a change order with its own price and its own funding step. Never hidden in a text thread.
• Stages, with their definitions of done, become priced release triggers. You submit. Your client has seven days. Approve, or auto-approve at day seven. Funds land in your account instantly.
• Deadlines sit live against each stage on the project. The headline end date and its tolerance live in the signed contract you upload once the setup is agreed, so the live structure and the legal terms sit side by side.
• Responsibilities live on the project as an uploaded PDF for now. A built-in feature is on the way. Until then, the file is the single source of truth, swapped out when something changes.

That is the setup, the project brief, and the running structure. The same thing. You do not write a separate document for the client to follow. The project on Renno is the document.

Setup is the only part you do by hand. Make the four decisions, put them into the project, and the rest of the job runs from them.