The most expensive meeting is the one that never happened
Every remodel has a moment, usually three or four weeks into construction, when someone asks a question that should have been answered before demolition day. The tile installer wants to know who owns the layout. The contractor assumed the vanity was owner-furnished; the designer assumed it was in the contractor's bid. The alternate for the range hood was discussed in February and never documented, and now the cabinet shop needs an answer by Friday.
None of these are complicated problems. They are unasked questions, and they are expensive. Each one costs a phone call, a site visit, a revised drawing, or a change order — and the cumulative drag of a dozen such questions over a project is measured in weeks.
The fix is not more documentation. It is one short, disciplined conversation held before work starts: a 30-minute preconstruction alignment meeting with the designer, the contractor, and whoever owns production support. Its only job is to confirm scope, surface assumptions, settle alternates, and log open questions while every answer is still cheap.
In brief
- The most expensive meeting is the one that never happened — most preconstruction friction comes from questions nobody asked before work started.
- Three seats, no more: the designer, the contractor (or the PM who will actually run the job), and the production support lead. Each holds a different piece of the truth.
- Thirty minutes, five blocks: scope confirmation, assumptions review, alternates and allowances, open questions log, next actions.
- A standing cadence — weekly while selections and pricing are moving — beats a one-time kickoff. The output is a single page: every open question with an owner and a date.
Who needs to be in the room
Three seats, no more. The designer (or the designer's project lead), the contractor (or the PM who will actually run the job), and the production support lead — whoever owns the drawing set, finish schedules, and procurement tracking. On small teams, one person may wear two hats. What matters is that each function is represented, because each one holds a different piece of the truth.
The designer holds intent. The contractor holds means, methods, and pricing reality. Production support holds the documentation — what is actually drawn, specified, and ordered. Misalignment almost always lives in the gaps between these three views, and you cannot close a gap you cannot see.
Invite the client only if a specific decision genuinely needs them. This is a working session, not a presentation.
The standing agenda
Thirty minutes, five blocks. Keep it tight enough that nobody dreads it and structured enough that it actually produces decisions.
| Block | Time | What gets decided |
|---|---|---|
| 1. Scope confirmation | 5 min | Walk the scope boundary out loud: what is in, what is explicitly out, and what sits in the gray zone. If the drawings show scope the bid does not include, it surfaces here — not at the first pay application. |
| 2. Assumptions review | 5 min | State every assumption plainly — site conditions, existing dimensions, lead times, who furnishes what — and mark each verified or assumed. A flagged assumption becomes a site verification task with an owner and a date instead of a future change order. |
| 3. Alternates and allowances | 5 min | Confirm every alternate and allowance: what triggers it, what it costs, and who decides. Alternates discussed verbally and never documented are one of the most reliable sources of mid-project disputes. If it is not written down with a price and a decision-maker, it does not exist. |
| 4. Open questions log | 10 min | The heart of the meeting. Collect every unresolved question — selections pending, details uncoordinated, long-lead items unconfirmed — and log each one with an owner and a due date. The goal is not to answer everything in the room; it is that no question leaves the room without an owner. |
| 5. Next actions | 5 min | Read back the owners and dates. Confirm the next check-in. End on time. |
Unasked questions in the documentation layer have the same shape — drawing gaps that generate avoidable RFIs shows what happens when the questions the meeting would have caught instead reach the field.
Why a standing meeting beats a one-time kickoff
A single kickoff meeting decays. Selections change, site conditions reveal themselves, and a dimension verified before design development can be wrong by the time the cabinet shop measures. An allowance set in March may not survive a June price change. A standing alignment meeting — weekly or biweekly through preconstruction, then at key milestones during construction — keeps the three views synchronized as reality evolves.
Pick the cadence by phase: weekly while selections, pricing, and documentation are actively moving; biweekly once the set is stable and the project is waiting on permits or long-lead confirmations. The cadence matters more than the duration. Thirty minutes is short enough to hold regularly and long enough to be useful, but only if the agenda is enforced. The moment the meeting becomes a general status update, it loses its purpose. Protect the format: scope, assumptions, alternates, questions, actions.
Small teams sometimes resist adding a meeting to the calendar. Frame it as a trade: thirty minutes a week against the hours each clarification cycle consumes — a phone call, a site visit, a revised detail — and the objection usually settles itself. Thirty minutes a week is the cheapest insurance on the project.
For teams that want decisions tracked on a tighter loop between meetings, a 24-hour decision log keeps resolutions visible so the same question never gets asked twice.
FAQ
Who should run the meeting?
The production support lead — they own the documents the conversation is built on. On small teams it can be the designer or the contractor's PM. What matters is not the title but the discipline: the agenda is enforced, the open-questions log gets written down, and it happens on the same cadence whether or not anyone feels like it.
Should the client attend?
Only for a specific decision that genuinely needs them. This is a working session, not a presentation. The client gets the one-page open-questions log afterward — every open item with an owner and a date — not the working meeting itself.
Does a small project really need this?
The format scales. A powder-room remodel can run the same five blocks in fifteen minutes. The cost of an unasked question doesn't scale down with project size — a wrong vanity rough-in stalls a small job just as fast as a misordered range hood stalls a large one.
What happens to questions that can't be answered in the meeting?
That's the point of the log. Every unresolved question leaves the room with an owner and a due date, and the next session opens by reviewing the log. A question without an owner is the meeting failing at its one job.
Starting this week
You do not need new software or a new process document. For the next project entering preconstruction, schedule the meeting, send the five-block agenda in advance, and assign someone to keep the open questions log. The output of that first session is a single page — every open question with an owner and a date. Review it at the start of every session; closed questions stay closed. That one page is what the next three months of the project run on.
Early clarity is cheaper than late correction. The alignment meeting does not eliminate surprises; it moves them to the phase of the project where they cost the least. That is what preconstruction is for.
For builder-side teams that want a production partner in the room for this kind of alignment, Creo's partnership model is built around exactly this coordination — keeping design intent, documentation, and field reality in sync before questions get expensive.
Ready to work with a studio that moves at your pace?
Get In Touch