A weekly site meeting sounds formal and unnecessary for a house extension. It isn't. It's one of the most effective tools a homeowner has for keeping a project on track, maintaining clear communication with the contractor, and catching problems before they become expensive.
You don't need an agenda template or a formal chairperson. You need a regular, structured conversation that covers the right things, and a brief written record of what was decided. Thirty minutes, once a week, every week. That's it.
Why Formal Meetings Work Better Than Ad Hoc Contact
The alternative to formal site meetings is informal, ad hoc communication: calling the builder when something occurs to you, getting updates when you happen to be on site, relying on the contractor to keep you informed proactively. This approach has two problems.
First, it puts the client in a reactive position. You're responding to what the builder tells you, not systematically checking the things you need to know. Problems that the builder doesn't mention (and they may not mention them because they're hoping to resolve them quietly, or haven't noticed themselves) go undetected until they've compounded.
Second, ad hoc communication doesn't generate a record. Formal meetings, with minutes, create a running document of what was discussed, what was agreed, and who is responsible for what. That document is your protection if anything is later disputed.
Setting Up the Meeting Rhythm
Agree the meeting schedule with your builder before work starts. Same day, same time each week. Monday mornings work well: it reviews the previous week and sets the plan for the coming one. Friday afternoons work for some people: it caps the week and sets up the following Monday.
Attend on site where possible. Site meetings on site are better than phone calls because you can look at things together while discussing them. When you see a question and the builder simultaneously, the response is more precise. A conference call about whether a steel is in the right position is less useful than standing next to the steel.
Keep the meeting short. Thirty minutes is the right target. More than an hour suggests the project has significant problems that need separate, more intensive attention. The meeting should be routine, not dramatic.
What to Cover
A site meeting for a residential project should cover these items in this order:
1. Review of last week. What was planned? What happened? Were there any deviations from programme, and why? This creates accountability without being adversarial. You're not looking to blame; you're looking to understand so you can plan accurately.
2. Plan for next week. What trades are on site? What work will be completed? What decisions or information does the builder need from you to proceed (material selections, approvals, access arrangements)?
3. Current programme review. Is the project on track for the agreed completion date? If not, by how much is it behind, and what's the plan to recover? Never let slippage accumulate silently. Address it the week it first appears.
4. Variations and changes. Any new variations proposed? What's the cost and justification? Any previously agreed variations that haven't yet been priced? Agree how outstanding variations are handled before the meeting ends.
5. Building control and inspections. Any inspections due this week? Has notification been sent? Any information required for an upcoming stage inspection?
6. Materials and orders. Any materials with long lead times that need to be ordered now to avoid delays in three weeks? Any materials delivered that aren't to specification?
7. Any other issues. Problems the builder wants to raise, concerns you want to flag, neighbours, access, skips, welfare. Keep this category contained so it doesn't expand to fill all available time.
Recording the Meeting
At the end of the meeting, spend five minutes writing a brief note of the key decisions and actions. Who is doing what by when. If a variation was agreed, the agreed cost and scope. If a problem was identified, the agreed resolution.
Send this note by email to the builder within 24 hours. Ask them to confirm or correct. Most builders won't correct factually accurate records. Occasionally they'll clarify something that wasn't quite captured correctly. Either way, you now have a contemporaneous written record of what was agreed.
Over a six-month project, those 24 meeting records are enormously valuable if any dispute arises about what was agreed and when. They're also useful for your own reference: it's very easy to forget mid-project that you agreed to a particular variation three months ago.
Don't skip the meeting because things seem to be going well. Regular meetings are not just for problem-solving; they maintain the discipline and communication standard for the whole project. Stopping them because everything is fine means restarting them only when problems arise, which is exactly the wrong time to establish the habit.
Handling Difficult Conversations
The site meeting is the right place to raise concerns. Not by phone when you're frustrated after seeing something on site. Not by a long email written in the evening. In person, at the meeting, in a structured way.
Raise concerns specifically. "I noticed the kitchen ceiling joists looked smaller than the engineer's specification" is better than "I'm not happy with the structural work." Give the builder the opportunity to explain or correct your understanding before escalating. Most apparent problems have an explanation. Some don't, and those need to be addressed. But the site meeting is the professional context in which to do that.
If a builder resists having formal weekly meetings, that's a signal worth examining. Contractors who prefer to operate without formal oversight and records tend to prefer that arrangement for reasons that don't serve the client.