How to Manage Your Contractor — What Homeowners Should Expect and Check
Target Keywords: how to manage a building contractor, what to expect from a contractor, managing a building project, contractor communication tips
Most building disputes do not begin on site. They begin weeks earlier, in a conversation where expectations were left undefined, a price was agreed without a written scope, or a change was made verbally and then remembered differently by two different people.
Managing a contractor well is not about micromanaging tradespeople. It is about understanding your role as a client, maintaining clear communication, and knowing what to look for — and what to push back on — throughout the project lifecycle.
What the Client Is Responsible For
There is a widespread assumption that once a contractor is engaged, the client's job is simply to wait for keys to be handed back. That is not how a successful project works.
As a client, you have specific responsibilities:
A clear brief. The contractor can only price and deliver what has been specified. If your brief changes during the project — a different kitchen layout, additional works to a bathroom that was originally out of scope — that is a variation, and it comes with a cost and a programme impact. The clearer your brief at the outset, the fewer variations you will encounter.
Timely decisions. Building projects involve sequential decisions — tile selections, ironmongery choices, joinery finishes. If you are asked to confirm a specification and you delay, the contractor either waits (and the programme slips) or proceeds on an assumption (and you may not like what they chose). Respond to contractor queries promptly.
Payment on schedule. Cash flow is critical to any contractor. Stage payments agreed in the contract should be made on the due date. Late payment creates tension, disrupts procurement, and can — in extreme cases — result in a contractor demobilising from site. Pay on time.
How to Read a Programme of Works
A professionally run project will be supported by a programme of works — a document showing the sequence and timing of activities from start to practical completion. It may be a simple Gantt chart or a more detailed critical path document. Either way, you should understand its structure.
Key things to look for: What are the dependencies? (Steel can't be installed until the wall is opened; plastering can't begin until first-fix electrics are done.) What are the milestones? (Roof made weathertight, Building Control inspection completed, kitchen installed.) Where are the float points — built-in contingency that absorbs minor delays without pushing the end date?
Review the programme at the start of the project. Ask the contractor to update it if significant changes occur. A contractor who cannot produce or explain a programme is a contractor who has not planned properly.
Communication: Site Visits and Written Updates
Establish communication expectations at the outset. Who is your single point of contact? How often will you receive written updates? When are site visits appropriate?
A responsible principal contractor will provide regular written progress updates — weekly in most cases — and will flag any issues affecting programme or cost as they arise, not retrospectively. You should feel informed without needing to make daily calls.
When visiting site, give notice rather than arriving unannounced. A contractor who is mid-task with materials and operatives in place needs to manage the site safely. Visiting without warning can disrupt coordination and, in some cases, creates a safety issue. Agree a schedule of site visits in advance.
When you raise concerns, do so in writing — email is sufficient. This creates a record and forces a clear response. Verbal concerns raised on site are easily forgotten or contested. Written concerns are not.
Normal Variation vs Red Flags
Not everything that feels wrong in a building project is a red flag. Some things are normal:
- Deliveries that arrive slightly off-schedule.
- A first-fix inspection by Building Control that requires a minor remediation.
- A subcontractor who runs a day or two late.
These are the ordinary friction of construction. They do not indicate a problem contractor.
What does warrant concern:
Escalating extras without explanation. Every variation should come with a written instruction, a price, and your authorisation before work proceeds. If you are being told costs have changed without having been given advance notice and the opportunity to agree, that is a red flag.
Unexplained delays without revised programme. One delay, communicated and explained, is normal. Persistent unexplained delays with no revised timeline and no proactive communication is a pattern that needs addressing directly.
No paperwork. No written scope, no stage payment schedule, no variation notices, no Building Control submissions — these are not acceptable on any substantive project.
Variations and Changes: Always in Writing
This point is worth its own emphasis. If you want to change anything from the agreed scope — anything at all — ask for it in writing and get a price confirmed in writing before the work begins. Verbal agreements about variations are the single most common source of disputes in residential construction.
A written variation instruction should state what is changing, how it affects the scope, what the additional cost is (or saving, if scope is being reduced), and whether there is any programme impact. Sign it off. Keep a copy. Do this every time.
Payment Schedules: Stage, Not Calendar
Stage payments should be linked to the completion of defined project milestones, not to dates on a calendar. A payment schedule that says "payment due on the 1st of each month" is not well-structured — a month may pass with little meaningful progress. A schedule that says "payment due on completion of structural frame and roof made weathertight" is properly constructed and protects you.
Before making any stage payment, confirm that the works associated with that stage have been completed to a satisfactory standard. A site visit tied to each payment milestone is good practice.
Snagging and Practical Completion
As works draw to a close, a snagging list should be prepared — a written schedule of minor defects or incomplete items that need to be addressed before the project is formally closed. Ideally, the snagging list is prepared jointly by you and the contractor (or by an independent project manager or contract administrator where one has been appointed).
Practical completion is the formal milestone at which the works are substantially complete and the building is fit for occupation. At practical completion: the contractor's risk and responsibility for the works transfers back to you; the Defects Liability Period begins (typically 6 to 12 months, as agreed in the contract); and where a retention has been agreed, typically 50% of the retained sum is released.
During the Defects Liability Period, the contractor remains responsible for making good any defects that emerge due to poor workmanship or materials. This is not the same as normal wear and tear — the contractor is not responsible for how you use the building.
How RCB Approaches Client Communication
At RCB Design & Build, we operate to a structured communication model from day one. You will have a single point of contact, regular written updates, a programme from mobilisation, and a defined variation process. We prepare snagging lists in advance of practical completion and manage defects through a documented process. The difference between a professional principal contractor and a loose collection of trades is not just build quality — it is the discipline applied to everything around the build.