Skip to content
Review.Live

Difficult conversations

Preventing conflict with clear expectations at the pre-construction meeting

By Review.LivePublished 3 min readHow we write

On your last job with this owner, their facilities manager emailed trades directly, approved a colour change nobody had priced and expected an answer to every message within the hour. The next project with the same owner starts in three weeks. The pre-construction meeting is on Thursday, and the agenda is still a blank page.

Two people in an office review a large drawing on a sloped table, one pointing to a detail.
Photo: ThisisEngineering on Unsplash

A lot of conflict on a job starts as two sets of expectations nobody said out loud: how fast questions get answered, who may give an instruction, when the site is open, what counts as a change. The pre-construction meeting is the cheapest place to find those gaps, because nothing has gone wrong yet and nobody is defending a position. Run it as a working session that ends in written agreements, not only as introductions.

  1. Name who speaks for whom: one contact each for the owner, the consultant and your company, and who may give an instruction or approve a change.
  2. Agree the communication rhythm: the weekly meeting, the report, the channel for urgent problems, and response times for requests for information and submittals, using the contract's times where it sets them — see a client communication plan.
  3. Settle access and site rules: working hours, deliveries, parking, occupied areas, noise and keys.
  4. Map the approvals: submittals, samples, mock-ups and inspections, with who approves each and how long it takes.
  5. Walk through how changes work under your contract: request, price, written approval, then work — and what happens when something urgent cannot wait.
  6. Agree how problems go up when the site level cannot solve them, and who talks to whom at each step.
  7. Put it all in the minutes and ask every party to confirm them within a week.

Common mistakes

  • Spending the meeting on introductions and leaving the hard topics for later.
  • Agreeing response times your team cannot keep.
  • Leaving the change process to "the contract" without walking through it.
  • Not recording the agreements, so each party remembers its own version.

Checklist

Put these on the agenda

  • Contacts, and who may instruct or approve
  • Meeting and report rhythm, and response times
  • Hours, deliveries, access and site rules
  • Submittals, samples, mock-ups and inspections
  • The change process, step by step
  • The escalation path
  • Minutes confirmed by every party

Check your understanding

The owner says the contract already covers all of this. Why spend meeting time on it?

Show the answer
The contract says what each party must do; it rarely says how the people in the room will work together day to day — who calls whom, how fast, and what happens on a Friday afternoon. Walking through it turns the contract's rules into habits both sides have agreed to, and it shows where the owner's expectations differ from the contract before that difference costs anything.

Related articles