Almost every building dispute, examined closely, contains the sentence “but we discussed this”. Discussed where? Confirmed how? The projects that run smoothly aren’t the ones without disagreements — they’re the ones where agreement was captured at the moment it happened. Three habits do it, and none takes ten minutes a day.

Habit 1: one channel, everything confirmed

Agree on day one where decisions live — for most domestic jobs a single WhatsApp thread or email chain with the builder. Conversations can happen anywhere; decisions get confirmed in the channel, in one line, the same day:

“As discussed this morning — sockets in the study go to 6 double, not 4. £180 + VAT agreed, no programme change.”

That sentence is simultaneously a record, a variation order, and the reason your final account holds no surprises. It protects the builder as much as you — which is exactly how to pitch it on day one: “so neither of us has to remember anything.”

Two disciplines keep the channel useful: one topic per message where you can (searchability later), and never let a significant verbal agreement go unconfirmed overnight. If a dispute ever comes, this thread is the first thing everyone reads — write it knowing that.

Habit 2: the weekly walk-round

A standing ten-to-twenty minutes, same time every week (Friday afternoon works), walking the job together with three questions:

  1. What happened this week against the programme?
  2. What happens next week, and is anything blocking it?
  3. What decisions do you need from me, and by when?

That third question is the quiet hero. Client decision-lag — tiles unchosen, socket positions unconfirmed, “we’re still thinking about the door” — is the number one avoidable cause of programme drift, and builders often won’t chase you until the delay has already happened. Ask for a rolling two-week decision look-ahead and put dates on each item like any other deadline. Then hit them: being a good client is mostly being a decisive one.

Confirm the walk-round in the channel afterwards in three lines. If the project has an architect or QS involved, they run this meeting instead — join it anyway.

Habit 3: the site diary

Two lines a day plus photos, kept by you: who was on site, what happened, anything notable (“plasterers finished upstairs; rain stopped roof work pm”). Photograph anything about to be covered up — pipework before boarding, membrane before screed, joist repairs before flooring. Ninety seconds a day.

Its value compounds in every direction: it’s the evidence spine if anything escalates, the fair record that protects a good builder against your own misremembering, the attendance log that turns “you were barely here in March” from impression into fact, and — on the good projects, which is most of them — simply the story of your build.

When communication is the problem

A builder who goes quiet — unanswered messages for days, vague answers to direct questions, no-shows without warning — is giving you data. Address it as its own issue, early and directly: name the pattern, agree the channel and the weekly rhythm, and watch whether behaviour changes. Communication breakdown is almost always the leading indicator of the bigger failures — and the paper trail you’ve built with these three habits is precisely what protects you if it comes to that.