Chapter 26 — Meetings and Field Documentation: OAC Meetings, Coordination, Daily Reports, and the Project Record

The Hook: Ninety-One Minutes, Zero Decisions

Week 38 on Northgate. A Tuesday in late November of Year 1, two weeks after topping out. Ten o'clock, the big room in the trailer, the OAC meeting — owner, architect, contractor — which is the one recurring event on this project where everybody who can actually change the outcome sits in the same room at the same time.

Fourteen people. Let me name them, because the roster is the first half of the problem.

Pri Sethi and two others from Meridian Health System — a facilities director and someone from their finance group whose function nobody has ever explained. Dale Whitcomb from Halvorsen + Pike, plus an interior designer and a project architect who is sitting in "to get up to speed." Ruth Caldwell's engineer on the phone. Somebody from Trellis Engineering on the phone. Amara Boateng, the commissioning agent. Me, Margo Deacon, Wei Chen, and Dani Okonkwo from Kestrel. And, because we were entering mechanical and electrical rough-in, Sofia Marchetti from Cardinal Mechanical and Devlin Achebe from Halcyon Electric.

Here is what happened for ninety-one minutes.

Dale read the RFI log aloud. All of it — forty-one open requests for information (RFIs), one at a time, including the eleven that had been answered since Friday and were already on the log everyone received Friday afternoon. Twenty-two minutes.

Wei Chen presented the schedule. Wei had emailed a two-page narrative and an updated look-ahead on Monday morning. Wei presented it anyway, because that is what had happened at the previous thirty-one meetings, and because presenting it felt like doing the job. Fourteen minutes. During those fourteen minutes two people were visibly answering email on laptops and one was on his phone under the table, which is worse, because he thought nobody could see.

The facilities director asked about parking during the January curtain-wall crane picks. Good question, wrong meeting — it belonged to Margo and could have been settled in the hallway in ninety seconds. It took eleven minutes because three people had partial answers.

At minute sixty-one, Sofia Marchetti raised the only genuinely expensive item on the table. The coordinated model showed 8 feet 11 inches of clear height in the imaging-suite corridor against the 9 feet 2 inches shown on the architectural sheet. Three ways out: reroute the main supply duct, accept the lower ceiling, or modify the structure. Each one costs money and each one costs a different number of days, and every day of delay on this job is worth $10,650 — $5,150 of extended general conditions plus $5,500 of liquidated damages.

The room discussed it for nine minutes. Then somebody said: "We should probably loop in Meridian's imaging vendor before we decide."

And that was that. Item deferred. Sofia Marchetti walked out of that room at 11:31 with exactly the same question she had carried in at 10:00, except now it was ninety-one minutes closer to the date her sheet-metal crew needed an answer.

Zero decisions. I checked my notes twice.

Hold one number in your head. Fourteen professionals for ninety-one minutes is about 21 person-hours. At an illustrative blended loaded rate of $105 an hour — some of these people cost more, some less, and your market will differ — that meeting consumed roughly $2,200 of professional time, before Wei's three hours of preparation and Dani's two hours of minutes. Call it $3,000 all-in. We held one nearly every week for eighty weeks. That is on the order of a quarter of a million dollars of professional time across the job, most of it not in Kestrel's general-conditions budget but every dollar of it real money to somebody.

The following Tuesday, the same agenda items produced eleven logged decisions in forty minutes, and Sofia left with a written answer and a date.

Nothing about the people changed. Nobody got smarter, more disciplined, or more cooperative. I changed four structural things, all of them boring, all of them free.

That is what this chapter is about — and then, in its second half, about the humblest and most valuable document a construction project produces.

🏃 Fast Track: If you have run projects for a few years, skim §26.1 and §26.2, then read §26.4 (the action-item discipline), §26.5 (minutes as a record-creating instrument — the objection obligation is the part people miss), §26.6 (the impact statement, which is the most valuable half-page in this book), and §26.7 (the confirming letter). If you have never written a confirming letter on the same day you received a verbal directive, do not skim §26.7.

🔬 Deep Dive: The document systems these meetings feed — submittals, RFIs, drawing control — are Chapter 25. The coordination meeting's field mechanics are Chapter 19; its genuine upgrade is the Last Planner System in Chapter 27. What the daily report feeds is Chapter 28 and Chapter 29; what it eventually decides is Chapter 33. Reality capture and 360-degree walkthroughs are Chapter 39. Blank forms are Appendix D.

26.1 Why Meetings Matter More in Construction Than in Almost Any Other Industry

In a normal company, a meeting is one of several ways information moves. There is an org chart. There are shared systems. There is a payroll everyone is on and a set of incentives that at least point roughly the same direction. If a meeting is bad, information routes around it.

A construction project has none of that.

Look at what the Northgate "organization" actually is. Meridian Health System employs Pri Sethi. Halvorsen + Pike employs Dale Whitcomb, and H+P's subconsultants work for H+P, not for Meridian. Kestrel Construction Group employs me and Margo. Cardinal Mechanical employs Sofia. Halcyon Electric employs Devlin. Ironbridge Steel employs Hank Duffy. None of these people reports to any of the others. None of them share an accounting system, an email domain, a scheduling tool by default, a document platform by default, or a bonus formula.

They share exactly three things: a site, a set of contract documents, and a deadline.

That is why the meeting matters. On a construction project, the meeting is not a supplement to the organization. For a couple of hours a week, the meeting is the organization — the only interval in which the temporary enterprise building this building exists in one place, able to make a decision that binds.

That table is also the honest answer to the person who says "we have too many meetings." Usually they are right about the volume and wrong about the cause. The problem is almost never that a project holds meetings. It is that the project holds meetings that decide nothing, so the deciding has to happen somewhere else — in hallways, in text messages, in a phone call at 6:40 p.m. that nobody records — and then the decision is invisible, unowned, and undocumented until it surfaces as a change order eight months later.

💡 Aha moment. A meeting on a construction project is not a communication event. It is a decision-manufacturing device. Judge it the way you would judge any other piece of equipment on the job: by what it produces per hour of the resources it consumes. A ninety-minute meeting that produces zero decisions has the productivity of an idle crane, and costs about as much.

🔄 Check your understanding. Two projects hold the same number of weekly meetings. One finishes on time; the other ends in a claim. What structural difference between the two meeting systems would you look for first?

26.2 The Project Meeting Architecture

A well-run job does not have "meetings." It has an architecture — a defined set of recurring events, each with a purpose that does not overlap the others, a defined owner, a defined output, and a defined attendee list. If you cannot state the purpose and the output of a recurring meeting in one sentence each, delete it and see who complains.

Here is the full set. Build yours from this and publish it at the preconstruction meeting (Chapter 17) so nobody has to guess which room a question belongs in.

(MEP = mechanical, electrical, and plumbing. VDC = virtual design and construction. GC = general contractor.)

Fourteen recurring events sounds like a lot until you notice that most are short, most involve fewer than eight people, and each one exists because the alternative is a decision made badly in a hallway.

Three of them deserve a note before we move on.

The subcontractor coordination meeting is the field's meeting, run by the superintendent, attended by the person who assigns people rather than the person who sells work. Chapter 19 walks its agenda and Margo's three questions for the foreman who says "we'll try." It is deliberately not run by the project manager, and it is deliberately not the OAC meeting: the owner does not belong in a room where trades negotiate sequence with each other. Its genuine upgrade — a structured pull plan, a constraint log with owners and need-by dates, and a measured percent plan complete — is Chapter 27, and it is the single highest-return change most projects can make to this meeting.

The pre-installation conference is required by many specification sections, almost universally skipped, and the cheapest quality control that exists. Roofing and waterproofing sections commonly require one; so do many flooring, curtain-wall, and firestopping sections. The meeting costs an hour and gets the installer, the manufacturer's representative, the designer, and the testing agency to agree — before material arrives — on substrate conditions, tolerances, transitions to adjacent work, mockup requirements, the acceptance criteria, and who calls the manufacturer when something goes sideways. Skipping it is how you end up with a roofing warranty the manufacturer declines to issue because substrate moisture was never tested, which is a five-figure problem discovered at the worst possible moment. Chapter 23 develops the quality system these conferences feed.

The internal project team meeting is the one young project managers skip, and it is the one that keeps you honest. This is where Wei Chen says the schedule update will show eleven days of slip before you show it to Meridian; where Lorena Vasquez says the concrete cost code is running six percent over and here is why; where Margo says the electrical foreman is being set up to fail by his own office; and where I say what I am actually worried about. If your team's only forum is the OAC meeting, your team has no forum — because there are things you cannot say in front of an owner without converting a management problem into a contractual one.

⚖️ What the contract says. Some of these meetings are not optional. General conditions and Division 01 sections routinely require progress meetings at a stated frequency, require the contractor to attend, and often assign responsibility for recording and distributing minutes. Individual technical specification sections frequently require a pre-installation conference and sometimes require documented attendance by named parties before the work may begin. Read Division 01 and every "Administrative Requirements" and "Quality Requirements" article in your specifications before you build your meeting calendar — a required meeting you did not hold is a contractual noncompliance an owner can raise later, entirely apart from the practical harm. What your specific contract requires, and what follows if you do not do it, is a question for your contract and your attorney, not for a textbook.

📊 Diagram (described): where a question goes. Think of the architecture as a routing tree. A question arrives — from a foreman, an inspector, an email, or your own walk of the building. Route it by who can answer it, not by who is standing nearby.

                          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 (Ch 25);         OAC decision log;
 foreman           coordination        model coordination    if it changes
 huddle            meeting             meeting if it is      scope or cost,
 (Ch 18)           (Ch 19, Ch 27)      a clash (Ch 35)       change process
                                                             (Ch 31)

The failure mode this prevents is the one that produced the parking conversation in the hook: a field logistics question consuming eleven minutes of the most expensive room on the project. Route it; do not host it.

26.3 The OAC Meeting Is a Decision Meeting, Not a Status Meeting

Ask ten project managers what the owner-architect-contractor meeting is for and nine will say "to report progress." That is the disease, stated as though it were the diagnosis.

Progress reporting is a document. It is a schedule narrative, a cost summary, a set of logs. It can be written once, distributed to fourteen people, and read by each of them at their own speed, at whatever hour suits them, skipping whatever does not concern them. Reading it aloud converts a five-minute individual task into a ninety-minute collective one and adds nothing except the sensation of thoroughness.

The OAC meeting exists for the decisions only the owner and the designer can make. Not the ones Kestrel can make. Not the ones the trades can settle among themselves. The ones requiring an owner's authority to spend money or change scope, or a designer's authority to interpret intent or modify a document.

That is a much smaller category than it sounds, and it is the entire justification for putting fourteen expensive people in a room.

26.3.1 The agenda that works

Every item gets a time box, an owner, and a rule. Publish the agenda with the invitation and never improvise the order.

Sixty minutes is the box. The improved Northgate meeting in the hook ran forty because six of the nine items had nothing open that week. A meeting that ends early is a meeting people show up to.

Item 8 surprises owners the first time. Most contractors treat the OAC meeting as an occasion to be examined. Reversing it — ending every meeting with a short, specific, dated list of what the owner and designer owe the project in the next thirty days — changes the relationship. It is not aggressive. It is the same look-ahead discipline you apply to your own trades, applied to the two parties whose late decisions cause a large share of the contractor delay claims in this industry.

26.3.2 Status is distributed, never performed

The rule is simple, and it is the single change that saved fifty minutes a week on Northgate: anything that is a state of the world at a point in time goes out as a document at least twenty-four hours before the meeting and is not read aloud.

The first three weeks you do this, two things happen. Some people will not have read the material and will ask you to summarize. Summarize in two sentences, then continue. And someone senior will say the meeting "feels thin." That feeling is the sensation of no longer spending an hour listening to things you already knew. It passes in about a month.

🔍 Why this works. Three mechanisms, and they compound. First, reading is several times faster than listening, and it is selective — a facilities director can skip the submittal log entirely, which she cannot do when it is being read at her. Second, a room's collective attention is a genuinely scarce resource with a measurable price; spending it on retrieval rather than on judgment is the same error as using a tower crane to carry coffee. Third, and least obvious: when status is a document, it becomes a record. A schedule narrative distributed every Monday for eighty weeks is a contemporaneous, dated, delivered series showing exactly what the owner was told and when. The same narrative delivered verbally is worth almost nothing eight months later, because nobody can prove what was said. You are not merely saving fifty minutes. You are manufacturing the evidence that you gave notice — the Chapter 25 principle applied to a meeting.

26.3.3 The decision log

The OAC meeting's primary product is not the minutes. It is the decision log — a standing document carried meeting to meeting, listing every open decision the owner or designer owes the project.

(WD = work days.)

Look at what the "age" and "cost of delay" columns do. They are not passive-aggressive. They are the mechanism by which a decision stops being a topic and becomes a cost with an owner's name attached. D-29 is the honest, uncomfortable entry: the decision was needed on 11/15, it was made on 11/18, and the consequence is a change order rather than a free adjustment. Putting that in the log — calmly, factually, without adjectives — is how a professional says "this cost money" without writing a sentence an attorney would wince at.

Notice the log doing double duty. It runs the meeting and it builds the record. Eight months later, if Meridian argues that Kestrel caused the finish-sequence slip, the decision log is a dated, distributed, unobjected-to series establishing what was asked, of whom, when, and what Kestrel said the delay would cost. That is Theme 5 doing its quiet work: documentation is the memory of the project, and the cheapest documentation is the kind that is a byproduct of running the job well anyway.

🔄 Check your understanding. Your decision log shows an item opened 63 days ago, still open, now blocking two trades. What do you do with it in the meeting, and what do you do after?

26.4 How to Run a Meeting That Works: The Craft

The four things I changed between the ninety-one-minute meeting and the forty-minute one: I published the agenda with decisions first; I moved status into a distributed document; I refused to log an action item without a person and a date; and I started and ended on time. Everything below is the detail underneath those four.

26.4.1 The agenda goes out in advance, decisions first

Not "an agenda." The agenda — the same one every week, in the same order, with time boxes, distributed with the invitation, decision items listed first and marked as decisions.

Listing decisions first does something to a room that is hard to appreciate until you have watched it. When the first fifteen minutes are decisions, the people who can decide are still fresh, still present, and have not yet mentally filed the meeting as informational. When decisions are item nine, they arrive at minute sixty-one to a room that has already downshifted — which is precisely what happened to Sofia Marchetti.

26.4.2 The action-item discipline

Every item leaves the room with a single named person and a date. Not a company. A person.

This is the rule people nod at and then violate within four minutes, so let me be concrete about why "Cardinal Mechanical will look into it" is not an action item.

You cannot call Cardinal Mechanical. You can call Sofia Marchetti. Cardinal Mechanical cannot forget, cannot be reminded, cannot be mildly embarrassed at next week's meeting, and cannot be held to a commitment — it is a legal entity with 140 employees, and in the gap between "Cardinal Mechanical" and an actual human being, the item dies. When it is read at the next meeting, the answer is "we're still looking into it," and it will be the same answer the week after, because no individual person ever accepted it.

Add a date for the same reason. "Soon," "by the end of the month," "as quickly as we can," and "this week" are not dates. A date is a day on a calendar.

Here is the rewriting drill. This is what Dani does in real time as the minutes are taken — out loud, in the room, before the topic changes.

Say the rewritten version out loud in the room before moving on. Two things happen. The named person gets a chance to object to the date right there, which is far better than discovering the objection in the minutes. And the room learns, within about three meetings, to phrase commitments that way in the first place — at which point the meeting starts running itself.

🔍 Why this works. The named-person rule defeats diffusion of responsibility: the well-documented tendency for a felt obligation to act to shrink as the number of people who could act grows. "Cardinal Mechanical will look into it" spreads the obligation across a company and therefore across nobody. "Sofia Marchetti, Friday the twenty-first" concentrates it in one person who was present, heard it, did not object, and knows it will be read aloud next week in front of everyone whose work depends on it. The date does the second half of the work: an open-ended commitment competes against every urgent item on that person's desk and loses; a dated one enters their calendar. And reading last week's items aloud at the top of every meeting closes the loop — the same mechanism that makes the field coordination meeting work in Chapter 19 and that the Last Planner System formalizes in Chapter 27. The corollary is absolute: skip the read-back twice in a row and the discipline evaporates, because everyone learns commitments are not checked.

26.4.3 The three people who break a meeting, and what to do about each

The person who talks too much. Usually not malicious, and often the most knowledgeable person in the room — which is exactly why the room defers. Three tools, escalating. Time-box the item out loud before it starts ("we have six minutes on this"). Redirect to the specific question ("I want to be sure I have your answer: can the duct be rerouted without a structural change — yes or no?"). And when it is chronic, take it offline explicitly and log it: "Sofia, you and Dale and I will settle the routing at two o'clock today, and I will bring the answer back to this group Friday." That last one is not a brush-off if you actually do it, and the log entry is what proves you did.

The person who does not talk at all. This is the expensive one, and almost nobody manages it. The silent person in a construction meeting is frequently holding the piece of information that will cost the most. It is the fabricator's project manager who knows the mill slot is soft. It is the electrical foreman who knows the gear submittal has not actually been approved. It is the owner's facilities director who knows the hospital operations committee will not accept the corridor width. They do not speak because they are junior, because they are outnumbered, because English is their second or third language, because their boss is in the room, or simply because nobody asked them anything and the meeting never paused.

You fix it by asking, by name, a specific question you actually want answered.

Not "does anybody have anything else?" — which reliably produces nothing. Instead: "Hank, you've been quiet. Is there anything in the fabrication sequence that worries you in the next month?"

On this job, that exact question, asked eight months earlier, was worth a mill slot. The anchor-bolt and embed submittal sat in Kestrel's office for eleven days before it went to Caldwell Structural. Caldwell took its full contractual fourteen-day review. Ironbridge missed its rolling slot; the next opening was five weeks out. Steel erection slipped from August 4 to August 27 of Year 1 — twenty-three calendar days, on the critical path — and Kestrel spent $168,000 accelerating to recover seventeen of them.

I am not claiming one question in one meeting would have prevented all of that. I am claiming that the information existed, in a room, inside a person, and no structure asked for it. That is a design flaw in the meeting, and it is free to fix. It is also, underneath, a leadership problem rather than a procedural one — the reason people stay quiet in rooms, and what a project manager can do about it, is Chapter 41.

The decision that keeps getting deferred. Every project has one, and it is always the expensive one, because deferral is how a room handles an item where somebody will have to spend money or admit an error. Use a three-strike rule and state it publicly the first time you invoke it:

1. First deferral: fine. Log the reason, the person who must act, and a date.
2. Second deferral: the item gets a written, quantified cost-of-delay statement in the minutes and an escalation date.
3. Third deferral: it leaves the meeting. It becomes a written notice under the contract, addressed to the party who owes the decision, referencing the clause, stating the impact, and requesting direction.

Escalation is not aggression. It is the honest recognition that this forum has failed twice, and that continuing to carry the item on an agenda is a way of appearing to manage a problem while the clock runs at $10,650 a day.

26.4.4 Start on time, end on time

Start at the stated minute with whoever is present. Do not recap for latecomers. End at the stated minute even if items remain, and carry the remainder with a stated plan.

This looks like a manners issue. It is a credibility instrument. A project manager whose meetings begin and end when they say they will is a project manager whose schedule dates people believe, and those two beliefs are the same belief. I have watched an owner's representative discount a contractor's recovery schedule — a genuinely sound one — substantially, because that contractor had never once started a meeting on time in fourteen months. Fair? No. Real? Completely.

26.4.5 The honest test

Here is the test I apply to every recurring meeting on every job I run:

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.

Apply it retroactively for one month. Pull your minutes 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. The Northgate OAC meeting in the hook produced zero of both and cost roughly $3,000.

🧩 Productive struggle. Before you read on, spend three minutes on this. Here are five action items exactly as they appeared in a set of minutes from Curtis Boone's Rivermont Elementary School #12 job. Rewrite each so it would actually get closed. Then decide which single one, left as written, is the most dangerous to the contractor — and why.

1. "Contractor to review the roof drain locations."
2. "Architect will provide clarification on the gym flooring."
3. "Owner is looking into the furniture delivery date."
4. "Team to resolve the door hardware discrepancy."
5. "Discussed the delay to the electrical rough-in. Contractor will make up the time."

26.5 Minutes as a Contract Document

This is the part most people underestimate, and it is why the drill above ends where it does.

Meeting minutes are not a courtesy. On most projects they are a record-creating instrument — frequently a self-executing one. Many owner-contractor agreements, many sets of general conditions, and many Division 01 administrative-requirements sections provide that minutes are deemed accepted unless a party objects in writing within a stated period. The period varies enormously: some contracts say five days, some seven, some ten, some fourteen, some say "prior to the next regularly scheduled meeting," and plenty of contracts say nothing at all — in which case the practical effect is murkier but the practical risk is not much smaller. Find your period. Write it on the wall of the trailer. How strictly any of this is enforced, and how a tribunal weighs minutes against other evidence, varies by jurisdiction and forum and is a question for your attorney, not for me.

What is not murky is the practical consequence: what appears in the minutes becomes the project's version of events, and the version of events is what everything downstream gets argued from.

26.5.1 What minutes record, and what they must not

Minutes record three things: decisions, commitments, and facts.

They do not record narrative, characterization, blame, tone, speculation, legal conclusions, or how anybody seemed to feel — not because those are impolite, but because they are the parts that are wrong within a year and indefensible in a deposition. A fact is durable. "The owner was frustrated" is a guess about another person's interior state, written by a 24-year-old field engineer, that will one day be read aloud to that owner under oath.

The side-by-side is the fastest way to learn this. Both entries describe the same nine minutes of the same meeting.

Badly written — do not do this:

4.3 Imaging Suite. Sofia from Cardinal said the ductwork won't fit and that this is a design problem. Dale disagreed and said the contractor should have caught this during coordination. Lengthy discussion followed. The owner is frustrated with the lack of progress and asked why this keeps coming up. Kestrel will handle it and get back to everyone.

Count the failures. It characterizes a party's emotional state. It records an unresolved allegation of fault from each side, in a document read by people who were not there. It contains no decision, no owner, no date, and no dollar or day consequence. It uses first names, which are ambiguous a year later when there have been three Sofias on the job. And the last five words — "Kestrel will handle it" — are an unbounded, unqualified acceptance of responsibility for an issue whose cause is actively disputed, written by the contractor, in the contractor's own minutes, in a document that becomes binding if nobody objects.

That single clause is worth more to the other side than any argument they could construct themselves.

Well written:

4.3 Imaging suite ceiling height (Decision D-31; opened 11/04; age 17 days)

Fact. The coordinated composite model dated 11/12 indicates 8'-11" clear at the imaging suite corridor between grids D-6 and D-9. Drawing A-231 indicates 9'-2" clear. The interference is between the main supply duct at elevation 12'-4" and the structural beam at grid D-7.

Options presented by Kestrel. (a) Reroute the duct — Cardinal Mechanical estimates 3 weeks and a cost to be priced. (b) Accept 8'-11" — requires H+P confirmation of code compliance and equipment clearance. (c) Modify the structure — requires Caldwell Structural review.

Actions. A-118: S. Marchetti to issue a marked-up section showing achievable clear height with current routing by 11/21. A-119: D. Whitcomb to confirm by 11/24 whether 8'-11" is acceptable to Meridian's imaging vendor and to code.

Decision required by: 12/01. Impact of delay beyond that date, as stated by Kestrel in the meeting: duct rework after ceiling grid installation would add approximately $18,000 and 6 work days in this area.

Note. No agreement was reached regarding responsibility for the interference. Nothing in this entry constitutes an acknowledgment of responsibility by any party, and all parties reserve their rights.

That entry is longer, and it is the only version worth writing. It is neutral, it is checkable, it advances the work, and if this becomes a dispute it helps whoever was actually right — which, if you are running an honest job, is the outcome you want.

Four rules that generate entries like that:

1. Last names and companies, never first names alone. "S. Marchetti (Cardinal Mechanical)," not "Sofia."
2. Separate fact from position. "Cardinal states that…" is a fact about what was said. "The duct will not fit" is an assertion you may not be able to prove.
3. Never characterize. No "frustrated," "unhappy," "heated," "finally agreed," "reluctantly."
4. Never accept responsibility in your own minutes. If fault is genuinely unresolved, say so and reserve rights. If your company genuinely erred, that belongs in an internal record and a conversation with your project executive — not in a distributed document that becomes binding on the fourteenth day.

⚖️ What the contract says. Two obligations run in opposite directions here, and you owe both. First: if you take and distribute the minutes, you are creating the record, and you must make it accurate rather than favorable — an obviously slanted record is worth less than no record at all, because it destroys your credibility on every other document you produced. Second, and the one people forget: you must read the minutes the other parties issue, and object in writing when they are wrong. On many projects the architect or the owner takes the OAC minutes while the contractor takes only the subcontractor coordination minutes. If the architect's minutes say something inaccurate about your performance and you say nothing for fourteen days, you may have agreed with it. Silence is agreement. Build the review into somebody's calendar as a recurring task, put the objection deadline in the file name, and never let the period run out on a document you have not read.

26.5.2 Objecting, without starting a war

Most people avoid objecting because it feels like picking a fight with the architect over a typo. Do it anyway, and do it in a register that makes it routine rather than adversarial. This is the whole letter:

Subject: Northgate Outpatient Pavilion — OAC Meeting Minutes No. 32 dated November 21, Year 1 — Correction Requested

Dale,

Thank you for issuing Minutes No. 32. We have two corrections and otherwise concur.

Item 4.3, Imaging Suite. The minutes state that "Kestrel will handle it." Kestrel did not accept responsibility for the interference and does not do so now. The interference between the main supply duct and the beam at grid D-7 was identified by Kestrel in the coordinated model dated November 12 and reported at the meeting. Kestrel has committed to facilitating a resolution and to pricing the options; responsibility for the interference remains unresolved and Kestrel reserves its rights.

Item 6.1, Schedule. The minutes state that Kestrel reported "no impact" from the pending imaging decision. Kestrel reported that there is no impact to date, and that framing in four rooms will be blocked if Decision D-36 is not made by November 26.

Please issue a correction or reflect these items in the next set of minutes. We are otherwise in agreement with Minutes No. 32.

Ray Alvarez Senior Project Manager, Kestrel Construction Group

Two paragraphs, no adjectives, sent inside the objection period, copied to everyone who received the minutes. Nobody's feelings are hurt and the record is now correct. Do this four times and the minutes stop containing those sentences, because the person writing them starts being careful.

🔄 Check your understanding. Your contract says minutes are deemed accepted if not objected to within seven days. The architect's minutes from three weeks ago contain a sentence stating that the contractor agreed to accelerate the interior finishes at no cost. You never agreed to that. What is your position now, and what do you do?

26.6 The Daily Report: The Most Valuable Half-Page on the Job

Here is the book's position, stated without hedging:

The daily report is the single most valuable document a construction project produces.

It is also, on most projects, filled out at 4:55 p.m. by somebody who wants to go home, using seven words and a headcount that is a guess.

Both of those statements are true at the same time, and the gap between them is where a great deal of money lives.

Understand what the daily report actually is. It is the only document on the project that is:

• Created every single day, whether or not anything notable happened.
• Created by a person with direct knowledge, standing in the building.
• Created before anybody knows there will be a dispute, which is the property that gives it weight.
• Created by you, under your control, in your format, without needing anyone's approval.
• Cumulative — 565 of them on Northgate, forming a continuous, internally consistent narrative of an entire project.

No other document has all five properties. The schedule update is periodic and interpretive. The pay application is monthly and financial. The RFI is episodic. The photograph shows a moment without context. The daily report is the spine that everything else attaches to.

26.6.1 What it must contain, and why each field exists

Every field on a good daily report earns its place by winning or losing something specific. Learn the why, not the form.

Notice which fields most projects actually fill in: date, weather (one word), a headcount, and a sentence about the work. Notice which ones decide disputes: manpower hours, quantities, equipment idle time, inspections, impacts, and directives.

26.6.2 The impact statement: the most valuable half-page in this book

If you take one thing from this chapter, take this.

Almost every daily report in the industry has a field called "Delays," "Problems," or "Remarks." Almost every one of them is either blank or contains something like "waiting on RFI."

Three words. Worth nothing.

An impact statement answers five questions, always, in this order:

1. Who was affected — by subcontractor, trade, and headcount.
2. Where — by area, level, and grid.
3. How long — with clock times and a computed labor-hour total.
4. Why — the specific cause, with its reference number and date.
5. What you did about it — mitigation, because an unmitigated loss is a smaller loss.

Watch three real entries get rewritten.

Example 1 — the idled crew.

❌ As written: "Waiting on RFI."

✅ As it should be written: "Framing crew (Sightline Interiors), Level 3 Area B, grids C–F: 6 carpenters idle 0700–1130, 27 labor hours, awaiting response to RFI 112 (head-of-wall detail at rated corridor), issued 4/2, response due 4/16 per the 10-work-day turnaround agreed at the preconstruction meeting; not received as of this report. No other released work available in Area B — Area C is not released pending in-wall inspection. Crew redeployed 1130 to Area D at reduced efficiency. Photos 0416-B-01 through -03."

At an illustrative burdened carpenter rate of $54.12 per hour, those 27 labor hours are $1,461 on one day. The number is not the point. The provability is the point: this entry names the crew, the area, the hours, the RFI, the issue date, the agreed turnaround, the absence of alternative work, and the mitigation. It is one paragraph, it takes ninety seconds, and it is the atomic unit from which a disruption claim is built. Twenty of them are a claim. Twenty entries reading "waiting on RFI" are not.

Example 2 — the weather day.

❌ As written: "Rain. Lost time."

✅ As it should be written: "Precipitation 0.62 in. between 0540 and 0915 (site rain gauge); high 47°F, low 39°F; wind NW 12–18 mph. Deck placement at Level 3 grids 5–9 (activity C-3320, the controlling activity per Schedule Update No. 14) cancelled at 0530 by J. Foster; ready-mix cancelled 0545, pump truck cancelled 0545. Concrete crew of 12 redeployed to interior form stripping at Level 1, estimated 60% productive; 4.0 productive hours lost per worker = 48 labor hours. No other dried-in released area was available for this crew. Standing water at grids 5–9 through 1400. Photos 0417-SITE-01 through -04."

Point four is the whole ballgame, as Chapter 18 argues at length. Any analyst reviewing your weather claim will ask why the crew could not have worked somewhere else. If your report does not answer that, on that day, in writing, you do not have a weather day.

Example 3 — the verbal directive.

❌ As written: "Owner directed extra work at imaging."

✅ As it should be written: "1345 — P. Sethi (Meridian Health System) directed Kestrel verbally, on site at the Level 1 imaging suite, to proceed with the deeper depressed slab and the additional framing required for the revised MRI unit, stating a written directive would follow. Present: P. Sethi, R. Alvarez, J. Foster. Kestrel advised on the spot that this work is outside the GMP scope and will be tracked on time-and-material pending a price. Confirming letter CL-026 issued the same day at 1620 to P. Sethi, copy D. Whitcomb. T&M ticket TM-0141 opened. No work performed today."

(GMP = guaranteed maximum price. T&M = time and material.)

The bad version is a note to yourself. The good version is an instrument. It fixes a time, a place, a person, a scope, three witnesses, a statement of position, a written follow-up with a document number, and the opening of a cost-tracking record — all before anybody knew there would be an argument.

🔍 Why this works. Records made contemporaneously — as events occur, in the ordinary course of running the job — carry weight that reconstructed records cannot, for four compounding reasons. First, they were created before anyone knew there would be a dispute, so the author had no incentive to shade anything. Second, they were made by a person with direct knowledge, standing in the building, rather than by a consultant reading files two years later. Third, they were made routinely, in a consistent format, over hundreds of days, so any single self-serving entry stands out against its own neighbors. Fourth, they can be cross-checked against completely independent records — batch tickets, delivery receipts, certified payroll, inspection reports, timestamped photographs — and consistency across independent sources is what makes a story believable. How any particular tribunal or forum treats such records is a matter of jurisdiction and procedure and belongs to your attorney. But the underlying reason contemporaneous records win is not legal technicality. It is that they are simply more likely to be true, and everyone in the room knows it.

26.6.3 Who writes it, and how long it should take

The daily report should be written by the person who was there — the superintendent, the assistant superintendent, or the field engineer who walked the building. Not by an administrator in the trailer transcribing a whiteboard. Not by the project manager from the office.

It should take ten to fifteen minutes, and it should be written the same day, ideally before leaving the site.

🏗️ From the field. Early in my career, on a job I would rather not name, we had a wonderful office administrator who produced the most beautiful daily reports I have ever seen. Complete sentences, consistent formatting, never a typo, filed by 4:30 every afternoon. She had never been on the third floor.

Fourteen months later we were defending a disruption claim, and I sat down with two hundred of those beautiful reports. They said things like "crews progressing on levels 2 and 3." They did not say which crews, in which areas, at what headcount, blocked by what. They were perfectly written records of nothing. The claim consultant we hired read forty of them and asked me a question I have never forgotten: "Was anybody actually watching this job?"

A ten-minute ugly report written by the person who walked the building beats a beautiful one written by somebody who did not, every single time, by an enormous margin. If you have to choose between good handwriting and direct knowledge, take direct knowledge.

Two more practices worth adopting:

Write it in the field, not in the trailer. A phone or tablet in the building, filled out area by area as you walk at 3:30, produces a fundamentally different document than a blank form at a desk at 4:55. You cannot remember an idle crew you did not write down while you were standing in front of it.

Never leave a field blank. If nothing happened, write "none." A blank field is ambiguous — did nothing happen, or did nobody look? "None" is a positive statement by a person who checked, and across 565 reports the difference in credibility is substantial.

⚠️ Safety alert: the near-miss field, and the pattern nobody read. Every near-miss goes in the daily report and into the near-miss reporting system — no injury, no first aid, no damage, still recorded. The reason is not paperwork. It is that near-misses are the leading indicator, and they arrive in patterns.

On Northgate, the daily reports captured 22 near-misses across weeks 34, 35, and 36 — six, nine, and seven — against a running average of roughly two and a half a week over the preceding month. That is a spike of nearly three times, sitting in plain text in the daily reports, in a folder, on a server, unread.

One of those twenty-two was the week-34 scaffold event on the north elevation at Level 3: a frame scaffold partially modified overnight by a trade that had not erected it, a plank lifted for conduit and not re-secured, and Emiliano "Milo" Serrano, a mason tender, stepping onto it at 7:20 a.m. The plank shifted; he went down onto the platform and caught himself on the top rail. Nobody was hurt. Bea Salgado stopped work on that elevation for the day.

Her investigation found three failures: a competent-person inspection tag that was two days stale; a scaffold modified by a trade that did not erect it, with no re-inspection; and a crew running behind after the steel acceleration under an unwritten pressure to make it up. The third finding is the one nobody wanted to write down, and it is the one the near-miss curve had been signaling for two weeks.

The record captured it. Nobody read the record. A leading indicator that nobody reads is a lagging indicator. Put weekly near-miss counts by trade and by area on the first slide of the coordination meeting and the first item of the OAC agenda, plot them, and make somebody responsible for looking at the trend rather than the individual events. This is Theme 4 and it is Chapter 24's entire argument: safety is a property of the production system, and schedule pressure is a hazard exactly like an unguarded edge.

🔄 Check your understanding. A daily report for a rainy day reads, in full: "Rain all day. No work. 0 men." What are the three biggest problems with it?

26.7 Verbal Directives and the Confirming Letter

Now the expensive one. This is the story this book keeps returning to, and here we look at it strictly from the documentation angle.

Meridian's imaging vendor selected a different MRI unit after the guaranteed maximum price was set. The new unit needed a deeper depressed slab, added structural framing, additional radio-frequency shielding, and a larger electrical feed. Pri Sethi gave a verbal go-ahead on a Thursday. Kestrel's assistant superintendent, under schedule pressure and genuinely trying to help, let the concrete crew build it on Monday.

No written directive. No agreed price. No time-impact analysis. And no time-and-material tickets for the first four days.

💰 Money check: what the missing paper cost, line by line.

The headline numbers on CO #14 are canonical: Meridian's verbal understanding of the cost was "about $60,000." Kestrel's actual incurred cost was $186,400. The cost Kestrel could substantiate with contemporaneous records was $121,000. The negotiated settlement eight weeks later was $142,750. Kestrel's unrecovered cost was $43,650. Kestrel claimed 9 calendar days of time impact and was granted 4.

Here is the part that is usually left out — where the $65,400 gap between incurred and substantiable actually came from.

Cost element	Actual incurred	Substantiated	Gap	Why the gap exists
Excavation, over-excavation, haul-off (days 1–4)	$14,200 | $5,100	$9,100	No T&M tickets days 1–4; reconstructed from a foreman's memory six weeks later
Formwork, shoring, and placement labor (days 1–4)	$18,600 | $7,900	$10,700	Daily reports said "concrete crew — imaging area" with no split between base scope and change
Formwork and placement labor (days 5–17)	$16,400 | $16,400	$0	Tickets started on day 5. Everything after that was clean
Reinforcing steel, added	$12,900 | $12,900	$0	Purchase order and delivery tickets exist
Concrete, added volume and mix change	$8,700 | $8,700	$0	Batch tickets exist
Added structural framing and embeds	$24,800 | $20,300	$4,500	Ironbridge field labor performed on verbal direction with no signed field work order
RF shielding subcontract change	$38,500 | $38,500	$0	Executed subcontract change order
Electrical feed upsize	$21,400 | $11,200	$10,200	Halcyon's added labor was mixed with base-scope labor on their own reports; no separate cost code at the source
Disruption to the adjacent slab-on-grade sequence	$13,900 | $0	$13,900	No impact statements. Three days of displaced crews, never written down
Crane and equipment time on the change	$5,600 | $0	$5,600	Equipment log said "on site," never "hours by activity"
Extended supervision on the change	$4,700 | $0	$4,700	Supervision time never coded to the change in the daily report
Rework: two embeds set to a superseded dimension	$6,700 | $0	$6,700	No nonconformance report, no photo, no transmittal establishing when the dimension changed
Totals	$186,400	$121,000	$65,400

Meridian settled at $142,750 — $21,750 above the substantiated figure, as a negotiated compromise on work everyone agreed had been performed. Kestrel absorbed $43,650.

Now price the paperwork that would have closed the gap. Four days of T&M tickets at about twenty minutes a day (80 min). Seventeen days of cost-coded manpower entries and impact statements at about six extra minutes a day (102 min). An equipment log entry at two minutes a day for seventeen days (34 min). One confirming letter (12 min). One nonconformance report with photographs (20 min). Total: 248 minutes — about 4.1 hours.

$43,650 ÷ 4.1 hours ≈ $10,600 per hour of writing. An assistant superintendent's fully burdened cost is on the order of $85 an hour. The return ratio is roughly 125 to 1, and that is the conservative version — measured against the full $65,400 gap it is closer to $16,000 an hour.

This is the entire economic argument for field documentation, and it is why Theme 5 is a theme: documentation is the memory of the project, and on this job the memory that was not made cost $43,650 and five calendar days of unrecovered time.

26.7.1 The confirming letter

The instrument that would have prevented most of that is a confirming letter: a same-day written record of what was said, by whom, and what you are doing about it, sent to the person who said it.

It is not a claim. It is not a notice of dispute. It is not an accusation. It is a short, neutral, factual document that converts a hallway conversation into a record, and it works precisely because it is not adversarial. Most owners' representatives read one and think, "good, we're on the same page." That is the correct reaction, and it is also exactly what you needed.

Here is the template. Adapt the wording to your contract's terminology and your relationship, and keep it under a page.

CONFIRMING LETTER CL-026 Date: [date sent — the same day] Project: Northgate Outpatient Pavilion To: P. Sethi, Meridian Health System Copy: D. Whitcomb (Halvorsen + Pike); Kestrel project file Subject: Confirmation of verbal direction — imaging suite depressed slab and associated work

Pri,

This letter confirms our conversation on site today at approximately 1:45 p.m. at the Level 1 imaging suite, attended by you, me, and Jamal Foster.

What we understood you to direct. You directed Kestrel to proceed with the deeper depressed slab, the additional structural framing, the additional RF shielding, and the enlarged electrical feed required by Meridian's revised MRI unit selection, and advised that a written directive would follow.

What Kestrel advised. We advised that this work is outside the scope on which the GMP was established and that it will constitute a change to the contract. We advised that no price has been established and that no time impact has been evaluated.

What Kestrel is doing. Beginning immediately, Kestrel is tracking all labor, material, equipment, and subcontractor costs for this work on a time-and-material basis under cost code 03-3100-14, on daily tickets that we will present to you or your designee for signature at the end of each working day. Signature acknowledges the hours and quantities shown; it does not constitute agreement on price or entitlement. Kestrel will submit a priced change proposal and a time-impact analysis within [number] days.

What Kestrel needs from Meridian. A written change directive or change order consistent with the contract's changes provision, and identification of the person who will sign daily tickets on Meridian's behalf.

Rights reserved. Kestrel reserves all rights under the contract with respect to cost and time associated with this change, including impacts to unchanged work.

If any part of this letter does not match your understanding, please advise in writing within [the period stated in your contract, or promptly] so we can correct it.

Ray Alvarez Senior Project Manager, Kestrel Construction Group

Six short sections. Twelve minutes to write. Note what each one is doing:

⚖️ What the contract says. Standard general conditions typically give the owner a right to order changes through two paths: a mutually executed change order (scope, price, and time agreed before the work), and a unilateral construction change directive or equivalent (the owner orders the work now; price and time are determined later, usually on a cost basis with defined markup). Both are written instruments. A verbal instruction is generally not one of them, however sincerely it was given and however senior the person giving it. Contracts also almost always contain a notice provision — a number of days within which you must notify the owner in writing of any event you believe entitles you to more money or more time — and missing it can forfeit an otherwise valid claim. How strictly that is enforced varies by jurisdiction and by how the clause is drafted. A confirming letter is not a substitute for contractual notice; on many projects it functions as the first step of it, and on some it satisfies it. Read your changes clause and your notice clause in week one, extract the deadlines onto a one-page sheet, and put it on the trailer wall. Whether your confirming letter satisfies your notice requirement is a question for your attorney, and it is worth one phone call at the start of a job rather than one deposition at the end of it.

26.7.2 Time-and-material tickets: get them signed the same day

A T&M ticket that is signed today is a record. The same ticket presented three weeks later is an invoice somebody has a reason to dispute.

The rules are simple and almost nobody follows all of them:

• One ticket per day per change, numbered sequentially, never combined across days or across changes.
• Names, classifications, and hours — not "5 laborers, 8 hours." Which five, at what classification. Certified payroll and the daily report must agree with the ticket, because somebody will eventually compare them.
• Equipment by unit number, with hours operated and hours standing by, separately.
• Material with quantities and delivery ticket numbers attached.
• A one-line description of the work performed and where, tied to the area and grid.
• Signed the same day by the owner's designated representative, with the signature block stating plainly that signature acknowledges hours and quantities only and is not agreement on price or entitlement. Say that on the form so no one has to say it out loud every afternoon.
• If they will not sign, note on the ticket the date and time it was presented, to whom, and that signature was declined, then transmit it in writing the same day. An unsigned ticket that was demonstrably presented on the day of the work is worth vastly more than one that appears for the first time in a claim binder.

On days 5 through 17 of CO #14, Kestrel did exactly this. Those costs came through at 100 cents on the dollar. Days 1 through 4 did not, and $19,800 of the gap lives entirely in those four days.

26.8 Photographs and the Visual Record

Photographs are free to take and nearly worthless if they cannot be found. That second half is the part everyone gets wrong.

Daily progress photography with a protocol. Not "take pictures." A protocol means: the same defined vantage points, in the same order, at the same rough time of day, every day or on a fixed cadence. On Northgate we ran eight fixed vantage points — four exterior corners, two interior stair cores, the imaging suite, and the main mechanical room — plus whatever the day required. Same points, every week, for eighty weeks. The value of a fixed vantage point is that consecutive images become directly comparable: you can lay week 34 next to week 38 and see exactly what did and did not happen, which no amount of assorted snapshots will give you.

Photograph concealed conditions before they are covered. Underslab plumbing and electrical before the vapor barrier. Reinforcing steel before the pour. Firestopping before the wall is closed. Above-ceiling MEP before the grid goes in. Waterproofing and flashing before the cladding. This costs a few minutes and prevents an entire category of argument, because the alternative to a photograph is opening a finished wall.

Photograph adjacent property before you begin. A preconstruction condition survey — photographs and video of neighboring structures, sidewalks, curbs, and landscaping, dated, before mobilization. On Northgate the north property line abuts an active clinic that stays open throughout construction. Every crack in that clinic's parking structure existed either before we arrived or after, and there is exactly one document in the world that settles which. That survey costs a few hundred dollars and it is the cheapest insurance on the job.

Organize them so they can be retrieved eight months later, because that is the only reason they exist. A photograph that cannot be located from a date and a location is not a record; it is a file.

Video and reality capture — 360-degree walkthroughs, laser scanning, drone photogrammetry — extend all of this dramatically. A weekly 360-degree walk of every floor, tied to a floor plan, means that eight months later you can stand anywhere in the building on any past week and look around. On a job with heavy above-ceiling MEP, that record is worth real money, and Grace Lindqvist's scanning work on this project fed both coordination and the closeout record. The technology, its costs, and what it actually returns belong to Chapter 39 and Chapter 35.

One caution worth stating plainly: a photograph without a caption is ambiguous, and ambiguity helps whoever is arguing against you. 20260416_L3AreaB_004 with a daily-report line reading "Photo 004 — head-of-wall condition at grid D-4 pending RFI 112 response" is a record. The same photograph alone is a picture of a wall.

26.9 The Rest of the Field Record

The daily report is the spine. These are the ribs.

(JHA = job hazard analysis.)

A caution about the personal diary. There is a real and consequential distinction between a project record — a document created in the ordinary course of the project's business, on the project's forms, kept in the project's files — and a personal diary kept by an individual. People will tell you confidently that one is discoverable and the other is not. Be careful with that advice. Whether a personal diary is protected, discoverable, or admissible depends on the jurisdiction, on how the document was actually created and kept, on whether it was used to prepare other records, and on the forum. It is genuinely not something a textbook can resolve for you.

What I can tell you is the practical rule I follow and teach: write every diary entry as though it will be read aloud in a deposition, because it may be. Record observations, facts, and your own decisions and reasoning. Do not record insults, speculation about other people's motives, jokes about the owner, or legal conclusions ("we're clearly going to lose this one"). A diary full of facts is an asset in almost any circumstance. A diary full of opinions is a liability in almost any circumstance. If you want a real answer about your jurisdiction and your company's document policy, ask your attorney — once, at the start of your career, and then stop guessing.

26.10 Correspondence Discipline: Letters, Email, and the Text Message Problem

Everything in this chapter so far has been a record you create deliberately. Correspondence is a record you create constantly, mostly without thinking about it, and it is where most people damage themselves.

Two of these deserve more than a table row.

The notice letter is a specific instrument, and it has required elements. Not a complaint, not an email in a thread, not a paragraph inside minutes. A notice letter does five things, and a notice missing any of them is weaker than it needed to be:

1. Reference the clause. Cite the provision under which you are giving notice. This is what makes it a notice rather than a letter.
2. State the event and its date. Specific. "On April 2 Kestrel issued RFI 112…" — not "recently we have experienced."
3. State the impact — the impact known to date, and if the full impact is not yet determinable, say so explicitly and say you will supplement. Never overstate; never leave it blank.
4. Reserve your rights, in one sentence, for cost and time including impacts to unchanged work.
5. Request direction. End by asking the other party to do something specific by a specific date. A notice that asks for nothing invites no response.

Here is one, complete, in the register that keeps a relationship intact:

Subject: Northgate Outpatient Pavilion — Notice of Delay — RFI 112, Level 3 Area B head-of-wall detail

Dale,

Pursuant to the notice provisions of the contract, Kestrel provides notice of an event that has affected and continues to affect the work.

The event. Kestrel issued RFI 112 on April 2, Year 2, requesting clarification of the head-of-wall detail at the Level 3 Area B rated corridor. Under the ten-work-day turnaround established at the preconstruction meeting of March 12, Year 1 and recorded in those minutes, a response was due April 16, Year 2. As of the date of this letter no response has been received.

The impact to date. Framing in Level 3 Area B between grids C and F cannot proceed. On April 16, six carpenters were idled from 0700 to 1130 (27 labor hours) and were redeployed at reduced efficiency. No other released work was available in Area B. Kestrel's daily reports for April 16 and forward record the affected crews, areas, and hours. The full cost and time impact cannot be determined until a response is received, and Kestrel will supplement this notice.

Rights reserved. Kestrel reserves all rights under the contract with respect to cost and time associated with this event, including impacts to unchanged work.

Direction requested. Please provide a response to RFI 112 by April 22, Year 2, or advise by April 20 of the date on which a response will be issued so that Kestrel can resequence the affected work.

Ray Alvarez Senior Project Manager, Kestrel Construction Group

Notice what is absent: any adjective, any accusation, any characterization of Dale's workload or attitude. Notice what is present: a clause reference, dates, a specific quantified impact, an explicit statement that the impact is incomplete, a reservation, and a request with a date. This letter protects Kestrel completely and costs Dale nothing except an answer, which is what you actually wanted.

And now the uncomfortable one: project text messages are discoverable, and they are frequently decisive.

I am not going to dress this up. In disputes I have been involved in, the text messages were often the most revealing documents produced — more revealing than the formal correspondence, because people write formal letters carefully and text messages the way they talk. A superintendent's 6:40 p.m. text saying "just build it, we'll figure out the money later" does more damage than any letter the other side could have written, and it does that damage to the company that employs the person who sent it.

They are also frequently on personal phones, which creates a second problem nobody enjoys: the scope of what a company can be required to produce from an employee's personal device, and the employee's own position in that process, varies by jurisdiction and by your company's policy. Ask your attorney what your company's practice is. Do not guess.

The working rule is one sentence, and I say it to every new project engineer on the first day:

Write every text message as though it will be read aloud in a deposition, because it may be.

That is not paranoia and it is not a reason to stop using text messages — they are genuinely useful for immediate field logistics. It is a reason to keep them to logistics. Anything that commits, prices, directs, admits, blames, or speculates goes in an email, in complete sentences, with a subject line, today.

🔄 Check your understanding. Your superintendent gets a text from the owner's rep at 7:15 p.m.: "Go ahead and start the sidewalk relocation tomorrow, we'll sort out the paperwork." What are the two things that must happen before that crew starts, and in what order?

26.11 Filing, Retrieval, and Reporting Up

26.11.1 File by document type, not by sender

The most common filing failure in construction is organizing by who sent it. It feels natural — a folder for the architect, a folder for Cardinal Mechanical, a folder for the owner — and it fails completely, because eight months later nobody remembers who sent the thing. They remember what it was and roughly when.

File by document type, then by number or date, with the sender as a searchable field rather than a folder.

Northgate-Outpatient-Pavilion/
├── 01-Contract/                  Agreement, GCs, exhibits, bonds, insurance
├── 02-Drawings/                  Current set, superseded set, sketches, ASIs, bulletins
├── 03-Specifications/            Original, addenda, revisions
├── 04-Submittals/                By submittal number; log at the root
├── 05-RFIs/                      By RFI number; log at the root
├── 06-Meeting-Minutes/
│   ├── OAC/                      OAC-032_2026-11-21_OBJECTION-DUE-2026-12-05.pdf
│   ├── Coordination/
│   └── Pre-Installation/
├── 07-Daily-Reports/             By date: DR-0291_2026-04-16.pdf
├── 08-Photographs/               By date, with a parallel index by area and by issue
├── 09-Schedule/                  Baseline, updates by number, narratives, TIAs
├── 10-Cost/                      Budget, cost reports, pay applications, lien waivers
├── 11-Changes/                   By change number: proposals, directives, executed COs
├── 12-Correspondence/            Chronological, by number, with a correspondence log
├── 13-Notices/                   Every notice given or received. Small folder, enormous value
├── 14-Quality/                   ITP, test reports, NCRs, mockups, pre-installation records
├── 15-Safety/                    Orientations, toolbox talks, JHAs, inspections, incidents
├── 16-Testing-Inspection/        Third-party agency reports, AHJ inspection records
└── 17-Closeout/                  O&M, warranties, as-builts, training, attic stock

(ASI = architect's supplemental instruction. TIA = time impact analysis. ITP = inspection and test plan. O&M = operations and maintenance.)

Three conventions make this work:

Name files so they sort and so they say what they are. OAC-032_2026-11-21_OBJECTION-DUE-2026-12-05.pdf tells you the type, the number, the date, and the deadline without opening it. Date first in YYYY-MM-DD form so chronological order is alphabetical order. Never Minutes_final_FINAL_v3.pdf.

Give folder 13 its own life. Notices given and notices received, in one small folder, chronological. On a job that goes badly, that folder is the first thing your attorney asks for, and on a job that goes well it takes ninety seconds a month to maintain.

Decide the closeout archive at the beginning, not at the end. Who owns the record when the job finishes, in what format, on whose system, for how long, and how it is retrieved after the project team has scattered. Retention periods depend on your jurisdiction's statutes of limitation and repose, your contract, and your insurer's requirements — they vary substantially, and the time to find out is the first month, not the last one. Chapter 25 sets this system up; Chapter 40 closes it out.

26.11.2 The retrieval test

Here is the only test of a filing system that matters. Hand it to somebody who was never on this project:

Can a person who was not on this job find the complete record of what happened on August 12 — the daily report, the weather, the manpower, the photographs, the correspondence sent and received, the inspections, and any directive given — in under five minutes?

If not, the record does not functionally exist. It exists physically, on a server, in a way that will require someone to bill forty hours to reconstruct at the exact moment you can least afford it.

Run the test twice a year with an actual person and an actual stopwatch. Pick a random date. Watch where they get stuck. Fix that. It takes twenty minutes and it is the single most useful audit of a project's documentation I know of.

26.11.3 The weekly and monthly owner report

Owners are not looking for reassurance. They are looking for six things, and a report that delivers those six things concisely is read; a report that buries them in twenty pages of narrative is not.

And one professional norm that is worth more than any format: report bad news early, in writing, with a plan.

An owner who learns about an eleven-day slip from you, in week 40, with two priced recovery options attached, is dealing with a construction problem. The same owner who learns about the same eleven days in week 48 because their own consultant found it is now dealing with a trust problem, and trust problems do not have recovery schedules. Every project manager knows this. A surprising number still wait, because they hope the slip will absorb itself. Occasionally it does. The rest of the time you have traded a difficult conversation in week 40 for a much worse one in week 48 plus a permanent discount on everything you say afterward.

Write the bad news down, propose the options with prices, and send it. It is the most reliable trust-building act available to a contractor, and it costs nothing but nerve.

26.12 📋 Try it: One Day on Northgate

Here is a single real day. Write the daily report in full, including the impact statements, and write the confirming letter for the verbal directive. Then decide which three entries will matter most in a claim eight months from now, and why.

The day: Thursday, April 16, Year 2. Northgate Outpatient Pavilion. Daily Report No. 291.

Weather. Low 41°F at 0600, high 58°F. Light rain from 0620 to 0745, measured 0.11 inches at the site gauge. Wind west, 8–14 mph. Site wet but workable; no work stopped for weather.

Manpower. Kestrel self-perform concrete: 9 workers plus 1 foreman, 8.0 hours each. Sightline Interiors framing: 14 workers, 8.0 hours. Sightline Interiors board: 8 workers, 8.0 hours. Cardinal Mechanical: 16 workers, 8.0 hours. Halcyon Electric: 13 workers, 8.0 hours. Ashcroft Masonry: 6 workers, 8.0 hours. Thermaline insulation: 4 workers, 8.0 hours. Vertex Elevator: 3 workers, 8.0 hours. Kestrel staff: 5.

Equipment. Tower crane: operated 4.5 hours, idle 3.5 hours. Two telehandlers, in service. Three 60-foot boom lifts; lift #3 idle all day with a hydraulic leak, service call placed 0800. Concrete pump: scheduled 0700, stood by, released 1500.

Events, in the order they happened.

• The loading dock slab placement (schedule activity S-4410, 74 CY planned) was scheduled for 0700. At 0705 the ready-mix supplier called: a plant breakdown at 0640. First truck arrived 0925. The concrete crew of nine plus the foreman stood by from 0700 to 0930. The pump truck stood by as well, at $185 per hour. Placement ran from 0930 to 1420; 62 CY placed, and Jamal Foster cut the pour at the construction joint at grid line 3 because truck rotation would not support finishing the full pour before the finishers lost the window. The remaining 12 CY moved to 4/17.
• At 0700 the Sightline Interiors framing crew reported to Level 3 Area B, grids C through F, and could not start: RFI 112 (head-of-wall detail at the rated corridor), issued 4/2 with a response due 4/16 under the ten-work-day turnaround agreed at the preconstruction meeting, had not been answered. Six carpenters were idle from 0700 to 1130 and were redeployed at 1130 to Area D. No other released work was available in Area B; Area C was not released pending in-wall inspection.
• Frank Petrosyan, the building official, was on site 1030 to 1140 for the in-wall rough inspection of Level 2 rooms 2C-04 through 2C-12. Rejected. Firestopping incomplete at eleven penetrations in the rated corridor wall at grid E, and two unsupported EMT runs. Corrections required before re-inspection; re-inspection requested for 4/18. Board on one side of those walls is blocked until it passes.
• Delivery 1, at 0815: curtain wall unit shipment 4 of 9 from Crossline Glass, 42 units, delivery ticket CG-1147. One unit arrived with a damaged corner gasket; it was photographed, tagged, set aside, and rejected in place pending Crossline's disposition.
• Delivery 2, at 1105: gypsum board for Sightline Interiors, 1,240 sheets of 5/8-inch type X, ticket GS-88210. Complete and undamaged, stocked on Level 2 by area per the hoisting plan.
• A technician from Talbot Testing & Inspection was on site 0900 to 1500 for concrete testing: four sets of cylinders cast from the loading dock placement, slump 4.5 inches, air 5.2 percent, concrete temperature 64°F, ambient 54°F; report TT-0466.
• Pri Sethi was on site from 1315 to 1410. At approximately 1330, in the Level 1 lobby with Ray Alvarez and Dani Okonkwo present, she directed Kestrel to add a floor box with power and data for a check-in kiosk at column line C-4, stating that Meridian's IT group made the decision that morning and that a written directive would follow. The work requires core drilling the slab and a conduit run. No work was performed on it today.
• Dale Whitcomb was on site 1400 to 1530 and walked the Level 3 finishes mockup.
• At 1435, on the Level 2 corridor at grid E, a Halcyon Electric apprentice on a six-foot podium ladder reached beyond the rail to pull wire; the ladder shifted and he caught himself on the ladder rail. No injury, no first aid. The foreman stopped the task. Bea Salgado was notified at 1450. Near-miss report NM-071 was initiated. Corrective action: the task was reassigned to a rolling scaffold, and a ladder-use toolbox talk was scheduled for 4/17 for all trades.

Write the report. Then write the confirming letter. Take twenty-five minutes. Then compare.

Spaced Review

Three things to pull forward. Answer each one before you read the response.

1. From Chapter 25: why is a contemporaneous record worth roughly ten times a reconstructed one — and what is the reverse of that principle?

The forward half: a record made as events occurred was made by someone with direct knowledge, before anyone knew there would be a dispute, in the ordinary routine of the job, and it can be cross-checked against independent records. Every one of those properties makes it more likely to be true, and everyone reading it knows that.

The reverse half is the one people forget, and this chapter should have made it concrete: if it isn't written down it didn't happen — and if it is written down, it happened, exactly the way you wrote it. "Kestrel will handle it" in a set of minutes. "We'll make up the time" in an action item. "Just build it, we'll figure out the money later" in a text message at 6:40 p.m. Be careful what you write. The discipline is not writing more; it is writing facts, decisions, and commitments and leaving out narrative, characterization, blame, and speculation.

2. From Chapter 19: what does Margo ask, and in what order, when a foreman says "we'll try"?

"What would have to be true for you to say yes?" Then: "Which of those is on me?" Then: "So what date can you commit to?" It is not a rhetorical trick — about half the time the answer to the second question is something the general contractor can fix in a day, and the rest of the time it produces an honest date instead of a polite lie. The same discipline drives the action-item rule in §26.4.2: a commitment without a named person and a date is a topic, not a commitment. "Cardinal Mechanical will look into it" cannot be called, cannot be reminded, and cannot be held.

3. The deep callback, from Chapter 17: what was the one question in the preconstruction meeting that was worth more than the other eleven agenda items combined?

"Who, specifically, has authority to direct the contractor — and by what mechanism does an instruction become one we can bill for?" Asked out loud, answered in the minutes, distributed. It takes ninety seconds.

Nobody asked it on Northgate. Pri Sethi gave a verbal go-ahead on a Thursday, believing in a loose sense that she had the authority — and in a loose sense she did. An assistant superintendent, trying to help, let the crew build it Monday. The chain from that unasked question to the $43,650 Kestrel absorbed on CO #14 runs through every topic in this chapter: no written directive, no daily-report entry recording the direction, no confirming letter, and no T&M tickets for four days. The meeting that would have prevented it happened in week one. The bill arrived in month nine.

Project Checkpoint: The Willow Street Meeting and Field Documentation System

In Chapter 25 you built the document machinery for the Willow Street Community Center — the back-scheduled submittal log, three written RFIs, and the document-control procedure. That system handles the paper that moves between companies. This checkpoint builds the system that captures what happens on the site.

Willow Street: $6.8M, 24,000 SF, two stories, a wood-framed second floor over a structural steel and CMU first floor, for the City of Rivermont Parks & Recreation. Design-bid-build, lump sum, 425 calendar days, liquidated damages $1,200 per calendar day, prevailing wage. Full package in Appendix K.

Add six artifacts to your notebook.

1. The meeting architecture. One page, in the format of the table in §26.2, adapted to a $6.8M municipal job. You will not run fourteen meetings on this project — decide which ones survive, and defend each cut in one line. Suggested keepers: a preconstruction meeting, an OAC meeting (biweekly is defensible at this size), a weekly subcontractor coordination meeting, pre-installation conferences for roofing, the gym flooring, and the commercial kitchen, a pre-pour meeting for the slab-on-grade, a daily foreman huddle, weekly toolbox talks, and a weekly internal team meeting. State purpose, attendees, frequency, duration, owner, and output for each.

2. Two agenda templates. One OAC agenda with time boxes totaling 45 minutes, decisions first. One coordination-meeting agenda with the commitment read-back as item 2. Use §26.3.1 as the model and cut it to fit the job.

3. An action-item log format, with at least eight sample entries drawn from a plausible Willow Street week — each with a single named person and a date. Include at least two entries that started life as "we'll look into it" and show them rewritten.

4. Five completed daily reports covering one representative week. Pick a week during the first-floor CMU and structural steel work. Fill every field from §26.6.1 — no blanks; write "none" where nothing happened. At least one of the five must contain a genuine impact statement in the form of §26.6.2, with five elements: who, where, how long with computed labor hours, why with a reference number and date, and what you did about it. A good candidate: the City's inspector rejects the underslab plumbing rough because a required cleanout is missing, and the slab-on-grade placement scheduled for the following morning has to be pushed. Write it the way you would want to read it eight months later.

5. A photo-documentation protocol. Define six to eight fixed vantage points on a 2.1-acre flat site with a two-story building — sketch them on the site plan from your Chapter 17 logistics work. Specify the naming convention, the cadence, the concealed-condition list (underslab utilities before the vapor barrier, reinforcing before placement, in-wall firestopping and blocking before board, above-ceiling before grid), the preconstruction condition survey of the adjacent right-of-way and the water-main relocation area, and where files live in your folder structure.

6. A confirming-letter template on your letterhead, following §26.7.1, with the six sections. Then use it: draft a real one for a plausible Willow Street verbal directive — for instance, the City's project manager telling you on site to relocate two hose bibs and add an exterior receptacle at the gym entry.

One calculation before you file it. Willow Street's liquidated damages are $1,200 per calendar day. Take your general-conditions figure from the Chapter 13 estimate, divide it by 425 calendar days, and add it to the $1,200. That sum is your daily exposure — the Willow Street equivalent of Northgate's $10,650. Write it at the top of your daily report form. Every impact statement you write is measured against that number, and everyone on your team should know it by heart.

Next: Chapter 27 takes the coordination meeting you just designed and upgrades it — a six-week look-ahead, a pull plan for the enclosure sequence, a constraint log, and percent plan complete, which is the first honest measurement of whether your own commitments mean anything.

Chapter Summary

Reference-grade version. Come back to this page.

The four rules that fix a meeting

The honest test: if a meeting produced no decisions and no commitments, it was a distribution list.

Minutes

• Record decisions, commitments, and facts. Never narrative, characterization, blame, or speculation.
• Last names and companies. Separate fact from position. Never accept responsibility in your own minutes.
• Many contracts deem minutes accepted if not objected to within a stated period — find yours.
• Read the other party's minutes and object in writing when they are wrong. Silence is agreement.

The daily report — the five properties nothing else has: written every day, by someone with direct knowledge, before anyone knew there would be a dispute, entirely under your control, and cumulative across the whole job.

The impact statement — five elements, every time

1. Who (subcontractor, trade, headcount) · 2. Where (area, level, grid) · 3. How long (clock times and computed labor hours) · 4. Why (the specific cause with its reference number and date) · 5. What you did about it (mitigation, plus why no other work was available).

"Waiting on RFI" is worth nothing. "Framing crew, Area B, 6 workers idle 0700–1130, 27 labor hours, awaiting response to RFI 112 issued 4/2" is worth what the day cost.

Verbal directives — the sequence, in order

1. Say on the spot that it is a change and that no price is established.
2. Enter it in the daily report with time, place, witnesses, and exact scope.
3. Issue a confirming letter the same day to the person who said it: what was directed, what you advised, what you are doing, what you need, rights reserved.
4. Open the cost code and the T&M ticket series before the first hour is worked.
5. Get every ticket signed the same day, with a signature block stating that signature acknowledges hours and quantities only.

CO #14: $186,400 incurred, $121,000 substantiable, $142,750 settled, $43,650 absorbed — against about 4.1 hours of writing that was never done. Roughly $10,600 an hour.

The retrieval test: can someone who was never on this job find the complete record of a random past date in under five minutes? If not, the record does not functionally exist.

Correspondence: notices go by the contract's prescribed method with five elements — clause, event and date, impact, rights reserved, direction requested. Emails are exhibits. Texts are for logistics only, and every one should be written as though it will be read aloud in a deposition.

What's Next

You now have the meetings and the record. What neither of them tells you is whether the work you are about to schedule can actually be done on Monday.

Chapter 27 takes the coordination meeting apart and rebuilds it as the Last Planner System: pull planning with the people who do the work, a six-week look-ahead that is a making-ready process rather than a report, a constraint log with owners and need-by dates, and percent plan complete — the number that tells you, honestly and uncomfortably, what fraction of your own promises you keep. Its threshold concept reframes everything you learned about scheduling in Chapter 14: the schedule tells you what should happen; the constraint log tells you what can.