Chapter 26 — Key Takeaways

A one-page reference card. Print it and put it above your desk in the trailer. Everything on it is meant to be usable at 4:15 on a Thursday afternoon.

Key Takeaways

  • A meeting on a construction project is a decision-manufacturing device, not a communication event. For a couple of hours a week the meeting is the organization — the only interval in which six companies on five platforms with eleven different contracts exist in one place, able to make a decision that binds. Judge it by what it produces per hour of the resources it consumes.
  • The honest test: if a meeting produced no decisions and no commitments, it was not a meeting. It was a distribution list — and a distribution list costs about four cents to send. Fourteen people for ninety-one minutes is roughly 21 person-hours; at an illustrative blended $105 an hour that is about $2,200 of professional time, call it $3,000 all-in with preparation. The same agenda, restructured, produced eleven logged decisions in forty minutes. Nobody got smarter. Four structural things changed, all of them free.
  • The four changes: agenda in advance with decisions first; status distributed, never performed; a single named person and a date on every action item; start and end on time.
  • "Cardinal Mechanical will look into it" is not an action item. You cannot call a company. A company cannot forget, be reminded, be mildly embarrassed next Tuesday, or be held. Diffusion of responsibility does the rest.
  • The OAC meeting exists for the decisions only the owner and the designer can make — not the ones you can make, not the ones the trades can settle among themselves. That is a much smaller category than it sounds, and it is the entire justification for putting fourteen expensive people in a room.
  • End every meeting pointing at them. The last agenda item is what the owner and designer owe the project in the next thirty days, dated. It is the same look-ahead discipline you apply to your trades, applied to the two parties whose late decisions cause a large share of the delay claims in this industry.
  • Minutes record decisions, commitments, and facts. Never narrative, characterization, blame, tone, speculation, or how anybody seemed to feel. Those are the parts that are wrong within a year and indefensible in a deposition.
  • Never accept responsibility in your own minutes. "Kestrel will handle it" is worth more to the other side than any argument they could construct themselves.
  • Many contracts deem minutes accepted if not objected to within a stated period — five days, seven, ten, fourteen, "before the next meeting," or nothing at all. Find yours. Then read the minutes the other parties issue, and object in writing when they are wrong. Silence is agreement.
  • The daily report is the single most valuable document a construction project produces — the only one that is created every day, by someone with direct knowledge, before anybody knew there would be a dispute, entirely under your control, and cumulative across the whole job. No other document has all five properties.
  • The impact statement is the field that decides claims, and it is almost always blank. "Waiting on RFI" is worth nothing. Five elements, every time: who · where · how long · why · what you did about it.
  • Contemporaneous records are worth roughly ten times reconstructed ones — made before anyone knew there would be a dispute, by a person with direct knowledge, routinely, in a form that can be cross-checked against batch tickets, delivery receipts, payroll, and timestamped photographs. That is not a legal technicality. They are simply more likely to be true, and everyone knows it.
  • The reverse of that principle is equally true: if it is written down, it happened, exactly the way you wrote it. Be careful what you write.
  • A verbal directive is not a change order. Standard general conditions give an owner two written paths — an executed change order, or a unilateral directive with price and time determined later. A sincere instruction from a senior person is neither. The confirming letter is what converts a hallway conversation into an instrument, and it takes twelve minutes.
  • CO #14, in one line: $186,400 incurred · $121,000 substantiable · $142,750 settled · $43,650 absorbed · 9 CD claimed, 4 granted — against about 4.1 hours of writing that was never done. Roughly $10,600 per hour, a return ratio near 125 to 1. $19,800 of the gap lives entirely in the first four days, before anyone opened a T&M ticket.
  • A near-miss with no injury is still a record, because near-misses are the leading indicator and they arrive in patterns. Northgate's reports captured 22 near-misses in weeks 34–36 against a running average near 2.5 a week. It sat unread. A leading indicator that nobody reads is a lagging indicator.
  • The retrieval test: can somebody who was never on this job find the complete record of a random past date — report, weather, manpower, photos, correspondence, inspections, directives — in under five minutes? If not, the record does not functionally exist.
  • Report bad news early, in writing, with two priced options. An owner who hears about an eleven-day slip from you in week 40 has a construction problem. The same owner who hears it in week 48 from their own consultant has a trust problem, and trust problems do not have recovery schedules.

Action Items — What to Do on Your Job This Week

  1. Find your minutes objection period. Open the general conditions and Division 01, find the number of days, and write it on the trailer wall. Then put it in your file naming convention: OAC-032_2026-11-21_OBJECTION-DUE-2026-12-05.pdf. Ten minutes, once.
  2. Assign minute review to a named person as a recurring calendar task — for minutes you issue and minutes anybody else issues. Ten minutes a week, and among the highest-return ten minutes on the job.
  3. Add one instruction to your daily report form: no field is left blank; write "none." Then add the impact-statement prompt directly on the form — who / where / how long / why / what you did — so the person filling it out at 3:30 in the building has the five questions in front of them.
  4. Pull last week's five daily reports and read the "problems" box. Count how many contain a crew, an area, a headcount, clock times, computed labor hours, a reference number, and a mitigation sentence. Whatever the count is, you now know your exposure.
  5. Write your daily exposure at the top of the daily report form. Northgate: $10,650/CD ($5,150 extended general conditions + $5,500 liquidated damages). Willow Street: $2,800/CD ($1,600 + $1,200). Everyone on the team should know it by heart, because every impact statement is measured against it.
  6. Draft your confirming-letter template today, before you need it. Six sections, one page, on letterhead, saved where the superintendent can reach it from a phone at 4:40 on a Friday.
  7. Take the last four sets of minutes you issued and count the decisions and the dated, named commitments in each. Then multiply attendee-hours by a loaded rate. Some of what you find will be uncomfortable.
  8. Run the retrieval test once, with a real person and a stopwatch. Pick a random date from four months ago. Watch where they get stuck. Fix that one thing.
  9. Ask the quiet person a specific question by name this week. "Hank, is there anything in the fabrication sequence that worries you in the next month?" The silent person in a construction meeting is frequently holding the information that will cost the most.

Common Mistakes — and the Fix

Mistake What it costs The fix
Reading logs and schedules aloud in the OAC meeting ~50 minutes a week × 14 people, and no record that the owner was told Distribute every log, narrative, and report 24 hours ahead; discuss only exceptions. Summarize in two sentences for whoever didn't read it, then continue
"Cardinal Mechanical will look into it" The item is still open in six weeks and nobody can be called One named person, one deliverable, one date — said out loud in the room before the topic changes, so the person can object to the date now
Skipping the commitment read-back at the top of the meeting Twice in a row and the whole discipline evaporates Read last week's items aloud, first item, every week, without exception
Decisions at agenda item 9 The room has downshifted by minute 61; Sofia Marchetti leaves with the same question she came in with Decisions first, time-boxed, with the decider named and the cost of delay stated
Letting an item be deferred a third time The clock runs at $10,650/CD while the agenda makes it look managed Three-strike rule, stated publicly: log it · quantify the cost of delay in the minutes · then it leaves the meeting and becomes a written notice
Writing "the owner is frustrated" in the minutes A guess about someone's interior state, read aloud to them under oath Facts only. Last names and companies. "Cardinal states that…" separates what was said from what is true
"Kestrel will handle it" in your own minutes An unbounded admission on a disputed issue, binding on day 14 Record the facts, the options, the actions, and: "No agreement was reached regarding responsibility. All parties reserve their rights."
Not reading the architect's minutes Silence is agreement, and by day 15 their version is the project's version A two-paragraph correction letter inside the period, copied to everyone who got the minutes. Do it four times and those sentences stop appearing
"Waiting on RFI" Nothing. Twenty of them are a shrug Five elements: crew, area/grids, clock times and computed labor hours, the RFI number with its issue date and agreed turnaround, and the mitigation plus why no other released work existed
"Rain. Lost time." No time extension, because the redeployment question is unanswered Measured precipitation with times, temperatures, ground condition, the controlling activity stopped, hours lost per worker, and "no other dried-in released area was available"
Daily report written at 4:55 at a desk by someone who wasn't there Two hundred beautiful reports that say "crews progressing on levels 2 and 3" — perfect records of nothing Written in the building, area by area, at 3:30, by the person who walked it. Ten to fifteen minutes. Ugly and true beats beautiful and blind
Leaving a field blank Ambiguity — did nothing happen, or did nobody look? Write "none." One word, 565 times, and your credibility is different
Acting on a verbal directive without paper $43,650 on CO #14, plus 5 unrecovered calendar days Confirming letter the same day, cost code and T&M ticket opened before the first hour, entry in the daily report with time, place, witnesses, and exact scope
T&M tickets presented weeks later An invoice somebody has a reason to dispute One ticket per day per change, names and classifications, equipment by unit with operated and standby hours, signed the same day — signature acknowledges hours and quantities only
Ticket signature refused, and nothing done The cost disappears Note the date, time, who it was presented to, and that signature was declined; transmit in writing the same day
Equipment logged as "on site" $5,600 of crane time unsubstantiated on CO #14 Hours operated and hours idle or standing by, by unit number, with the reason
Photographs with no protocol and no captions A picture of a wall Fixed vantage points on a fixed cadence · YYYYMMDD_Area_Level_Sequence · concealed conditions before they're covered · photo numbers cited in the daily report
Filing by sender Eight months later nobody remembers who sent it File by document type, then number or date; sender is a searchable field, not a folder
Committing, pricing, directing, or admitting by text message Often the most damaging document in the case Texts are for logistics. Anything consequential goes in an email, in complete sentences, with a subject line, today
A notice letter with no clause reference and no request A letter, not a notice — and it invites no response Five elements: clause · event and date · impact (say so if incomplete) · rights reserved · direction requested by a specific date
Sitting on bad news A construction problem in week 40 becomes a trust problem in week 48 Write it down, price two options, send it. It costs nothing but nerve

Decision Framework

A question just arrived. Which room does it belong in?

                            A QUESTION ARRIVES
                                    |
                +-------------------+--------------------+
                |                                        |
        Can the field answer it?               Needs someone outside the field
                |                                        |
      +---------+---------+                    +---------+----------+
      |                   |                    |                    |
   Today's work      Next 2-6 weeks     Design intent /       Owner decision /
   (this shift)      (trade sequence)   drawing conflict      scope or money
      |                   |                    |                    |
   6:20 a.m.         Weekly sub          RFI, or model         OAC decision log.
   foreman           coordination        coordination          If it moves scope
   huddle            meeting             meeting if it         or cost, it is a
                                         is a clash            change

Route it; do not host it. A field logistics question consumed eleven minutes of the most expensive room on the project, and it could have been settled in the hallway in ninety seconds.

Somebody just gave you a verbal directive

  1. SAY IT ON THE SPOT.      "This is outside our scope, no price is established,
                               and we'll track it on time and material."
                               Witnesses hear you say it. That matters later.

  2. DAILY REPORT, TODAY.     Time · place · who directed · who was present ·
                               exact scope · what you advised · what you did.

  3. CONFIRMING LETTER, TODAY. Six sections. To the person who said it, copy the
                               architect and the file. Under one page. 12 minutes.

  4. COST CODE + TICKET,      Opened BEFORE the first hour is worked. Not after.
     BEFORE WORK STARTS.

  5. SIGNED TICKET, SAME DAY. Signature = hours and quantities only. If declined,
                               note it on the ticket and transmit it anyway.

  6. DON'T START without written direction unless the owner directs otherwise
     in writing — and say that in the letter.

Skip step 3 and you have costs with no directive. Skip step 4 and you have a directive with no substantiation. The gap between those two is where CO #14's $43,650 went.

Is this entry worth anything eight months from now?

Ask If no
Does it name a subcontractor and trade and a headcount? It is an assertion, not a record
Does it give an area, level, and grids? Nobody can locate it on a drawing
Does it give clock times and a computed labor-hour total? The loss cannot be priced
Does it name the cause with a reference number and a date? Causation is missing, and causation is the whole proof
Does it say what you did about it and why no other released work was available? The redeployment question defeats you
Could a stranger read it and reconstruct the day without asking you a question? Rewrite it

The four rules that fix a meeting

Rule What it replaces What it produces
Agenda in advance, decisions first An improvised order that reaches the expensive item at minute 61 Decisions made by fresh people with authority
Status distributed, not performed Fifty minutes of reading logs aloud Fifty minutes back, plus a dated record of what the owner was told
A named person and a date on every item "Cardinal Mechanical will look into it" An obligation somebody can be called about
Start and end on time A meeting people arrive late to because it always runs long Credibility that transfers to every date you commit to

The one test for the whole system

Hand your files to somebody who was never on this job and ask them to reconstruct a random past date in five minutes. If they can, you have a project record. If they cannot, you have files — and somebody will bill forty hours to turn them into a record at the exact moment you can least afford it.