Communication Between Client and Contractor: How to Run a Renovation Without Conflict

The client-contractor relationship on a renovation project is one of the most unusual in commercial life. The contractor is working in the client's home or future home, often for months, in a relationship of mutual dependence: the client needs the contractor to deliver; the contractor needs the client to make decisions, provide access, and pay on time. When the relationship works well, it is genuinely collaborative. When it fails, both parties suffer.

The majority of renovation disputes that escalate to formal proceedings — adjudication, mediation, litigation — arose from communication failures: things that were not written down, decisions that were not confirmed, changes that were assumed to be included. This guide covers the communication practices that prevent disputes from developing.

Establish a single point of contact on each side

The most common source of confusion on a renovation project is multiple people on the client side issuing instructions to the contractor. A spouse who changes the tile specification, a parent who asks a subcontractor to move a socket, a friend who suggests a different approach to the contractor's foreman — all of these generate confusion, rework, and cost that is impossible to attribute clearly.

Establish, at the outset, a single point of contact on the client side through whom all decisions and instructions are communicated. The contractor's site manager or foreman is the appropriate counterpart. This does not prevent the client from visiting the site or discussing the works with the contractor's team — it simply means that any instruction that changes the scope, sequence, or specification goes through one channel and is confirmed in writing.

All changes in writing, before they are implemented

Every variation to the contracted scope — whether requested by the client or identified as necessary by the contractor — should be confirmed in writing before it is implemented. This means:

• —The client requests or the contractor identifies a change
• —The contractor provides a written change order with a description of the change and the cost
• —The client approves (in writing) before the work proceeds

This process does not slow a project down. It takes 15 minutes to send an email and receive a reply. What it prevents is the accumulation of uncosted variations that surprise the client at the final account stage. Verbal agreements about variations are the single largest source of final account disputes.

The change order does not need to be a formal document. An email chain works perfectly well for a domestic project: "We've agreed to extend the run of units to include the alcove — please confirm the additional cost" followed by "Confirmed, additional cost is £1,200 + VAT, to be included in the next interim valuation" is an adequate change record.

Weekly site meetings with written minutes

A weekly site meeting — client (or client representative), contractor's site manager, and where appointed the architect or project manager — keeps all parties informed of progress, upcoming decisions, and emerging issues. The meeting should cover:

• —Progress against programme (what was planned this week, what was achieved)
• —Upcoming decisions required from the client (specification choices, approval of samples, access arrangements)
• —Any issues or risks that may affect the programme or cost
• —Outstanding change orders — agreed, pending approval, or disputed

The minutes of this meeting should be issued by the contract administrator (architect, PM) or by the client immediately after the meeting. Minutes do not need to be elaborate — a bullet-point record of decisions taken and actions agreed is sufficient. The discipline of written minutes creates a running record that prevents "he said/she said" disputes about what was agreed.

Respond to information requests promptly

Renovation programmes are constrained by information: if the contractor needs to know the tile specification before they can order and the order has an 8-week lead time, a decision that is delayed by two weeks pushes the programme by two weeks. Contractors are not always good at flagging information requirements clearly in advance; clients are not always good at prioritising decisions over other demands on their time. The result is programme delays that both parties then dispute the cause of.

A good project manager will maintain a Requests for Information (RFI) log — a live schedule of open information requests, when each was raised, and when a response is needed to maintain the programme. Even without a formal PM, the contractor's site manager should flag information requirements at weekly meetings with the latest response date needed to maintain programme.

When a response is needed to keep the programme moving, treat it as urgent.

Managing expectations about programme

Programme delays are nearly universal on London renovation projects. The causes — late information, bad weather affecting external works, subcontractor availability, hidden structural problems — are almost always outside anyone's complete control. The question is whether delays are managed transparently or discovered late.

A contractor who manages the programme honestly — flagging early when a delay is developing, identifying the cause clearly, and proposing mitigation — is worth more than one who consistently reports "on track" until the completion date has passed. Ask your contractor at every weekly meeting: are we on track for the agreed completion? If not, what is the projected completion, and what is causing the delay?

Liquidated damages (a contractually agreed rate of delay damages per day of overrun) are a standard JCT contract provision. They are rarely invoked in domestic projects — the relationship between client and contractor on a residential renovation is too personal for the adversarial language of damages to sit comfortably. But the existence of a LD provision focuses the contractor's attention on programme and provides the client a remedy if delays become egregious.

Payment discipline

Pay on time. A contractor who is not paid on time is a contractor who is not paying their subcontractors on time — and subcontractors who are not paid stop coming to site. Cash flow problems cascade through the supply chain faster than most clients realise.

The flip side: do not pay ahead of the works. A front-loaded payment schedule — paying 40% at the start when 10% of the work is complete — gives the contractor working capital at the client's risk. Standard JCT payment terms provide for monthly interim valuations of work done, with a percentage retention held by the client. This structure protects both parties.

If a monthly payment is disputed — if the client believes the contractor's valuation is higher than the value of work completed — raise the dispute clearly and specifically. Do not simply withhold payment without explanation; do not pay an amount you believe is incorrect without noting the disagreement. A specific, written dispute of a valuation item preserves the client's position without creating a payment default.

When things go wrong

Problems on a renovation project are inevitable. The question is how they are handled. A contractor who identifies a problem, brings it to the client's attention, proposes a solution, and agrees a cost for resolving it is handling the problem professionally. A contractor who conceals problems, or who raises them only when the client discovers them, is not.

If a significant problem arises — structural discovery, failure of installed work, a dispute about scope — address it directly and in writing. Set out your understanding of the issue, what you expect to happen, and by when. A written record of the issue and the proposed resolution prevents it from becoming a dispute by establishing shared understanding.

ASAAN operates a dedicated client communication protocol on every project — weekly written site reports, a live variation log, and a named project contact who responds to queries within one working day. This level of transparency is, we believe, the minimum a client should expect on any renovation project of significance.