Appendix D — Forms and Templates Library

This is the most-used appendix in the book. Nearly every chapter's Project Checkpoint sends you here, because nearly every deliverable in the Willow Street Project Notebook is one of these documents, filled in.

D.0 How to adapt these

Every company already has its own forms. Yours will have a logo, a numbering convention, a platform behind it, and probably a legal department with opinions. That is fine. Nothing here is prescriptive. These templates are structural — they show what a document of this kind has to contain in order to do its job — and the structure is what transfers.

The transferable part is the field-by-field notes. A blank form teaches nothing. A blank form with a sentence explaining what each field is actually for teaches the thing that took most people six years to learn: that a form is not a record-keeping obligation, it is a set of questions somebody once lost money by not asking.

So every entry below has four parts:

1. What it is for, and who reads it.
2. The template, as a table or a structured block you can copy.
3. Field notes — what each entry is actually for.
4. The field that decides a dispute — and why it is usually filled in badly. This is the part that makes the appendix worth having.

Five rules for adapting anything here.

One: keep the fields that decide disputes. They are marked. Delete anything else you like.

Two: delete fields nobody will fill in. A form with eleven fields, six of which are always blank, teaches your team that blank fields are normal — and then the one that mattered is blank too. Fewer fields, honestly completed, beat more fields half-completed every time.

Three: never delete a field because it is uncomfortable. The impact statement on the daily report, the cause line on a rejected inspection, and the third finding in an incident investigation are the three most commonly softened entries in construction, and all three are the entries that decide who pays. Discomfort is a signal that the field is load-bearing.

Four: put the deadline in the form, and in the file name. Objection periods on minutes, review periods on submittals, notice periods on events. OAC-032_Year1-11-21_OBJECTION-DUE-Year1-12-05.pdf tells you the type, the number, the date, and the deadline without opening anything.

Five: where a form is statutory or contractual, use theirs, not yours. Lien waivers are prescribed by statute in some states and not in others. Force-account and change-order forms are frequently prescribed on public work. Certified payroll has a required format. Public bid forms must be used exactly as issued — a "helpful" modification makes a bid non-responsive. Check before you substitute.

⚖️ A note on what is not reproduced here. Several documents in this appendix have widely used industry standard forms behind them — the AIA G702/G703 application and certificate for payment and its continuation sheet, ConsensusDocs and EJCDC equivalents, and the standard general conditions that govern change directives and notices. Those are copyrighted published forms. This appendix describes them by function — what each column does, why it is there, and which entry decides a dispute — and never reproduces their text or layout. Get the actual forms from the publisher, and read the ones your contract requires you to use.

And the standing caution from the front of the book applies here most of all: this is an educational text, not legal advice. Notice periods, waiver forms, retention limits, prompt-payment requirements, and lien procedure vary by jurisdiction and change over time. Read your contract, and ask your attorney.

D.1 Daily report

What it is for, and who reads it. The daily report is the single most valuable document a construction project produces. It is the only document that is created every day, by a person with direct knowledge, before anybody knows there will be a dispute, entirely under your control, and cumulatively — 565 of them on Northgate, forming one continuous narrative of an entire project. No other record has all five properties.

Its immediate readers are your own project manager and superintendent. Its eventual readers are a scheduling analyst, a claims consultant, an owner's auditor, and possibly an arbitrator, none of whom were ever on your job. Write it for them.

Written by the person who walked the building — superintendent, assistant superintendent, or field engineer. Not an administrator transcribing a whiteboard. Ten to fifteen minutes, in the field, same day, ideally before leaving the site.

The template

DAILY CONSTRUCTION REPORT No. _______

Project: ____________________  Date: ______  Day: ______  Prepared by: ______  Completed at: ______

1. WEATHER
| Low | High | Precipitation (amount + times, source) | Wind | Site condition | Weather delay? |
|-----|------|----------------------------------------|------|----------------|----------------|
|     |      |                                        |      |                | Yes / No       |

2. MANPOWER
| Contractor / trade | Workers | Hours ea. | Labor hours | Area worked |
|--------------------|--------:|----------:|------------:|-------------|
|                    |         |           |             |             |
| TOTAL CRAFT        |         |           |             |             |
| Staff (non-craft)  |         |           |             |             |

3. EQUIPMENT
| Unit / ID | Hours operated | Hours idle | Reason if idle |
|-----------|---------------:|-----------:|----------------|
|           |                |            |                |

4. WORK PERFORMED
| Schedule activity ID | Description | Area / level / grid | Quantity installed |
|----------------------|-------------|---------------------|-------------------:|
|                      |             |                     |                    |

5. DELIVERIES RECEIVED
| Time | Item | Supplier | Ticket no. | Qty | Condition / exceptions taken |
|------|------|----------|------------|----:|------------------------------|

6. VISITORS
| Name | Company | In | Out | Purpose |
|------|---------|----|-----|---------|

7. INSPECTIONS AND TESTS
| Inspection / test | By whom | Scope and location | Result | Corrections required | Re-inspection date |
|-------------------|---------|--------------------|--------|----------------------|--------------------|

8. PROBLEMS, DELAYS, AND INTERFERENCES — WITH IMPACT
   (One numbered impact statement per event. Five elements. See below.)

9. DIRECTIVES RECEIVED  (including verbal)
   Time · who directed · where · exactly what was said · who was present ·
   what Kestrel advised on the spot · confirming letter number and time issued ·
   cost code and T&M ticket opened · work performed today: yes / no

10. SAFETY
    Incidents · near-misses with report number · corrective action ·
    toolbox talks conducted · safety walk findings · week-to-date and rolling near-miss count

11. PHOTOGRAPHS
    Reference numbers, by area

Signed: ____________________   Reviewed: ____________________

Field notes

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.

🔴 The field that decides a dispute: the impact statement

Almost every daily report in the industry has a field called "Delays," "Problems," or "Remarks." Almost every one of them is either blank or says "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 its date.
5. What you did about it — the mitigation, and why no other released work was available.

Element 5 is the one people skip and the one an analyst attacks first. Any reviewer of a delay or 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 claim.

The two versions, side by side.

❌ Vague — the version almost everyone writes:

"Framing in Area B still shut down waiting on RFI 112. Architect has had it forever and still nothing. Total mess up there, guys standing around all week. This is going to blow up the whole level 2 schedule and somebody needs to light a fire under H+P."

Count what is missing: no sheet, no revision, no crew size, no clock times, no labor hours, no issue date, no agreed turnaround, no mitigation, no statement about alternative work. "Forever" is not a duration. "Total mess" is not a condition. And the last sentence is a prediction of failure, which in a dispute is used to establish that you foresaw the problem and did not prevent it.

✅ Evidentiary — the same day, same author, with a method:

8.1 — Framing crew idled, Level 3 Area B, awaiting RFI response. Sightline Interiors framing crew, Level 3 Area B, grids C–F: 6 carpenters idle 0700–1130 = 27 labor hours. Cause: no response received to RFI 112 (head-of-wall detail at the rated corridor), issued 4/2, response due 4/16 under the ten-work-day turnaround established at the preconstruction meeting of March 12, Year 1 and recorded in those minutes. No other released work was available in Area B; Area C is not released pending in-wall inspection. Mitigation: crew redeployed 1130 to Area D at reduced efficiency (unfamiliar layout, materials relocated). Kestrel notified H+P by email at 0740 that the crew was idle. Photos 0416-L3B-01 through -03.

Same frustration. Same amount of typing. The entire difference is that the second author knew what the document was for. One of these is the atomic unit of a disruption claim; twenty of them are a claim. Twenty of the first one are a shrug.

Why the field is usually filled in badly: it is written at 4:55 p.m. by somebody who wants to go home, about an event that is over, on a day when nobody has told them the day will ever matter. The fix is not exhortation. It is writing the report in the field as you walk at 3:30, area by area, on a phone or tablet — because you cannot remember an idle crew you did not write down while you were standing in front of it.

A second field worth guarding: the cause line on a rejected inspection. It is the entry a young engineer is most tempted to soften, and it is the one that decides whose float got consumed. "In-wall rough REJECTED. Firestopping incomplete at 11 penetrations, rated corridor wall at grid E (Cardinal Mechanical and Halcyon Electric penetrations); two unsupported EMT runs (Halcyon). Both notified in writing 1215 with corrections required by end of shift 4/17." Without that entry, the delay is a general contractor problem by default, because nobody can prove otherwise.

D.2 Confirming letter

What it is for, and who reads it. A same-day written record of a verbal instruction, sent to the person who gave it. Its reader is the owner's representative — and, months later, whoever is deciding whether you gave notice.

It is not a claim, a notice of dispute, or an accusation. It is short, neutral, and factual, and it works precisely because it is not adversarial. Most owner's 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.

This is the practice that would have recovered $43,650 on CO #14. Pri Sethi gave a verbal go-ahead on a Thursday; Kestrel's assistant superintendent let the concrete crew build the deeper depressed slab on Monday; no written directive, no agreed price, no time-impact analysis, and no time-and- material tickets for the first four days. Kestrel incurred $186,400, could substantiate $121,000, settled at $142,750, and absorbed $43,650 — against roughly 4.1 hours of writing that nobody did.

Twelve minutes. Six sections.

The template

CONFIRMING LETTER CL-______ Date: [the same day] · Sent: [time] Project: ____ To: [the person who gave the direction] Copy: [architect] · [project file — Notices folder] Subject: Confirmation of verbal direction — ______

[Name],

This letter confirms our conversation on site today at approximately [time] at [specific location], attended by [every person present, by name].

What we understood you to direct. [The instruction, in plain language, in their words as you understood them. Describe scope, not price.]

What [Contractor] advised. We advised that this work is outside the scope on which the [contract sum / 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 [Contractor] is doing. Beginning immediately, [Contractor] is tracking all labor, material, equipment, and subcontractor costs for this work on a time-and-material basis under cost code __, 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. [Contractor] will submit a priced change proposal and a time-impact analysis within ____ days.

What [Contractor] needs from [Owner]. 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 [Owner]'s behalf.

Rights reserved. [Contractor] 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 that we can correct it.

---

[Title, Company]

Field notes

One optional sentence, used carefully. "[Contractor] will not begin this work until written direction is received, unless you direct otherwise in writing." Use it when you have not started and the schedule permits waiting. Do not use it when work is already underway, because it is then untrue.

🔴 The field that decides a dispute: "What [Contractor] advised"

Everything else in the letter is administration. That paragraph is the whole instrument.

Its job is to establish that at the moment of the direction — before any work, before any argument — the contractor said out loud that this was a change, that no price existed, and that costs would be tracked. In every dispute about a verbal directive, the owner's position eventually becomes some version of "we thought that was included" or "we understood it would be about $60,000." That paragraph is the only document that answers it.

Why it is usually filled in badly: because writing it feels confrontational, and the relationship is good, and the owner's rep has been reasonable, and you do not want to seem like you are building a file. So people write a friendly note that recaps the scope and omits the position. That letter proves you were told what to build. It does not prove you told them it would cost money.

⚖️ Standard general conditions typically give an owner two written paths to order a change: a mutually executed change order (scope, price, and time agreed first) and a unilateral construction change directive or equivalent (proceed now, price later). A verbal instruction is generally neither, however sincerely given and however senior the person giving it. Contracts also almost always contain a notice provision with a hard deadline. A confirming letter is not a substitute for contractual notice; on many projects it is the first step of it and on some it satisfies it. Read your changes clause and your notice clause in week one, put the deadlines on a one-page sheet, and tape it to the trailer wall.

D.3 Request for information (RFI)

What it is for, and who reads it. A written request for clarification of the contract documents where they are genuinely ambiguous, internally conflicting, incomplete, or in conflict with an actual field condition. Its reader is the architect or an engineer — an overloaded professional with a fixed fee and a stack of other people's questions.

That is the whole legitimate scope. An RFI is not for a decision that is yours to make (means and methods), not a substitution request, not a question the documents already answer, and not a vehicle for a demand.

💡 Your RFI log is a reputation. Every unnecessary RFI spends a little of the design team's willingness to take you seriously, and you will need that willingness intact on the day you send the one that matters. Northgate closed with 287 RFIs on $47.5M and a 9.4-day mean response. Curtis Boone's Rivermont Elementary closed with 496 on $22.4M, a 21-day mean, and 63 items open past thirty days at substantial completion — by RFI 300 the architect had stopped reading them carefully, because most of them did not deserve careful reading.

The six-element anatomy

Element 4 does most of the work. An architect who receives a question has to design an answer, which takes hours they do not have. An architect who receives a proposed answer has to evaluate one, which takes minutes. Same information, a tenth of the effort — and, the part that surprises people, a materially better outcome for you, because the answer that gets approved is usually the one you proposed.

❌ The bad RFI, in full

RFI 112 Subject: Level 2 dimensions Date: [date]

The dimensions on level 2 don't work. Please advise ASAP as this is holding up framing and we are incurring costs.

That comes back in eleven days reading "Contractor to verify field conditions and coordinate," which is not an answer, which starts round two, and which is entirely the fault of the person who wrote the RFI. No sheet, no revision, no grid, no dimension, no statement of the actual discrepancy, no proposed resolution, no quantified impact, no date. The only concrete content is a threat.

✅ The good RFI, in full

RFI 112 — Level 2 Area B clinic module: dimension string does not close, grids 6–9 Project: Northgate Outpatient Pavilion · To: Dale Whitcomb, Halvorsen + Pike · From: D. Okonkwo, Kestrel Construction Group Date issued: [date] · Required response date: [date + 7 CD] · Priority: Schedule-critical

References Sheet A-103 (Level 2 Floor Plan), Rev. 2 · Sheet A-421 (Enlarged Plan — Level 2 Clinic Module), Rev. 2 · Specification Section 09 22 16 (Non-Structural Metal Framing) · Grids 6 through 9, column line C.

Observed condition 1. Sheet A-103 dimensions the overall distance from grid 6 to grid 9 as 72'-0". 2. Sheet A-421 dimensions the same run as a string of seven exam rooms and one corridor: 11'-4", 11'-4", 11'-4", 11'-4", 5'-8" (corridor), 11'-4", 11'-4", 11'-4". These dimensions sum to 71'-7 1/2". 3. The difference is 4 1/2 inches. No dimension on either sheet is designated HOLD or CRITICAL. 4. Exam rooms 2-118 through 2-124 have a 10'-6" clear requirement noted on A-421 for equipment clearance; casework shop drawings (Submittal 087, approved as noted) are dimensioned to the A-421 room widths.

Question Where should the 4 1/2 inches be absorbed: (a) in the corridor width, (b) distributed among the seven exam rooms, or (c) at the grid-9 end wall?

Contractor's proposed solution Absorb the full 4 1/2 inches at the grid-9 end wall (option c), holding all exam-room dimensions and the corridor dimension as shown on A-421. This preserves the 10'-6" clear equipment dimension in all seven exam rooms, preserves the approved casework dimensions in Submittal 087, and places the variance in a wall with no fixed equipment, no casework, and no accessibility clearance governed by the ADA Standards for Accessible Design. Kestrel proposes to proceed on this basis unless directed otherwise. This proposal carries no cost or time impact.

Impact if not answered by the required response date Metal stud layout for Area B level 2 is scheduled to start [date + 8 CD] with a crew of six. If layout cannot start on that date, the crew has no alternate work available in Area B, since Area C in-wall inspection is not released. Estimated idle exposure: 6 workers × 8 hours × [rate] per day, plus a corresponding slip in the Area B in-wall inspection date, which is a predecessor to drywall in the level-2 finish sequence.

Attachments: Marked-up excerpts of A-103 and A-421 with the dimension string highlighted; photograph of the as-built grid-6 to grid-9 slab dimension taken [date], measured at 72'-0 1/8".

Copies: P. Sethi (Meridian) · R. Caldwell (Caldwell Structural) · M. Deacon (Kestrel) · Submittal 087 file

Four things that document does which the first one does not: it removes the reviewer's work; it states an actual field measurement, which forecloses an entire round of "verify field conditions"; it proposes a resolution with a reason expressed in terms the architect cares about (clearance, approved casework, accessibility) rather than terms the contractor cares about; and it quantifies the impact without threatening.

Use "Contractor proposes to proceed on this basis unless directed otherwise" only when your proposal is genuinely no-cost, low-risk, and reversible. Never when it involves cost, changes design intent, or touches a life-safety or code-governed condition.

🔴 The field that decides a dispute: the impact statement (element 5)

Not because it pressures the reviewer — it should not — but because it is a contemporaneous record of the exposure, created before anyone knows whether it will be needed. That is what makes it evidence rather than argument. Written on the day the problem was found, it establishes the crew size, the date, the absence of alternate work, and the downstream milestone. Reconstructed eight months later by somebody who wants it to matter, it establishes nothing.

Why it is usually filled in badly: people either leave it blank ("I don't want to seem aggressive") or fill it with a threat ("we will be seeking costs"). Both fail. Blank gives you nothing to prove later; a threat converts a technical question into a commercial fight and makes the reviewer defensive on an item you needed answered quickly.

And the question to ask on every response

Did the answer change the contract?

An RFI response that adds scope, arrives on a form with your own number on it, in a paragraph that sounds like a clarification — and the crew builds it and nobody prices it. That is how contractors donate work by the millions of dollars a year.

D.4 RFI log and submittal log

D.4.1 The RFI log

What it is for, and who reads it. Tracking, aging, and escalation. Read weekly by your project team, distributed to the design team and the owner's representative.

🔴 The field that decides a dispute: "what it gates"

An aging report sorted only by days outstanding tells you which item is oldest. It does not tell you which item is expensive. An RFI twelve days out that gates nothing is fine. An RFI nine days out that gates a fabrication release in two days is an emergency. Rank by days out; decide on what it gates.

Usually filled in badly because it requires somebody to open the schedule and think, and it is easier to type a subject line. The consequence is that escalation energy goes to whatever is loudest instead of whatever is costliest.

D.4.2 The submittal log — back-scheduled

What it is for, and who reads it. Everything. This is the document that decides whether material arrives.

A submittal log is not an inventory. A submittal log is a schedule. Its rows are dated obligations, its sort order is the order in which those obligations come due, and reading it should feel like reading a look-ahead, not a bibliography.

Most logs in this industry are transcriptions: somebody opens the project manual, reads the "Submittals" article in Part 1 of each specification section, and types what they find in the order they encounter it. That produces an accurate inventory sorted by an accident of the alphabet, and it tells you nothing about what to do on Monday. It is how Northgate's anchor-bolt chain sat in a spreadsheet, fifteen days infeasible on the day it was signed, and nobody saw it.

Build it by working backward from the only fixed point in the chain.

  SUB          GC          A/E        [REVISE +    RELEASE     FABRICATE    SHIP    ON
  PREPARES ->  REVIEW  ->  REVIEW  -> [RE-REVIEW]-> TO SHOP -> / MANUF.  -> /    -> SITE
                                                                           DELIVER
   <-------------------- you compute in this direction ------------------------------|
                                                                    required-on-site
                                                                    is the ONLY fixed
                                                                    point in the chain

The template — the columns, in computation order

Status codes — keep them few and unambiguous. Six is plenty:

Resist "pending," "in progress," and "with Bob." Every one of those hides the only question that matters.

The two reports that run the log:

• The aging report — what is out, for how long, ranked by days out, decided on the "gates" column.
• The ball-in-court report — 214 rows collapsed to five numbers: subcontractors (NR + RR), GC review, design team (OUT), released and pending action (AAN), closed. This is the single most useful management report in document control and almost nobody produces it. On Northgate in week seven the answer was 138 items not yet submitted at all — the subcontractors, and behind them Kestrel, because nobody had asked in writing. It is almost never the architect first. Publish it every Monday to the whole team including the architect and the owner's rep, without editorial comment. The effect is not informational. It is social. Nobody wants to be the top row.

🔴 Two fields decide disputes here

One: the resubmittal allowance. A chain built with one review cycle and no allowance for a "revise and resubmit" is a chain that only works if nothing goes wrong. Northgate's anchor-bolt subcontract was executed March 7; run with one resubmittal cycle, it had to be executed February 20. The chain was fifteen days infeasible on the day everyone shook hands, and nobody knew, because nobody ran the calculation with a resubmittal in it.

The allowance is usually omitted because including it makes the log look pessimistic and makes an award date look late. That is precisely the information you needed.

And the honest limit: a resubmittal allowance protects you against comments. It does not protect you against a question the documents cannot answer. Northgate's curtain wall carried a correctly sized 21-day allowance and still lost nine weeks, because forty percent of the north-elevation transition details came back marked "by others" and "others" turned out to be nobody — a scope gap between two subcontracts. You cannot buy your way out of a scope gap with schedule float. You find those in the scope review, months earlier.

Two: the fabricator's release date — which is a different date from your approval date.

Kestrel's back-schedule tracked an approval milestone of April 15. Ironbridge Steel's actual constraint was a mill release date of April 18 — the last day Hank Duffy could commit steel against a reserved rolling slot. Three days of margin existed between those dates and nobody at Kestrel knew, because nobody had asked to see Ironbridge's production schedule. Approval landed April 21. The slot was gone; the next opening was five weeks out.

Ask every long-lead supplier, in writing, at buyout: what is the last date you can release, and what happens if you miss it? Put the answer in a column. There is no crew, crane, or machine on a job site that burns $28,000 a day. The most expensive thing on your project is paper that is not moving.

D.5 Submittal transmittal and the review stamp

What the transmittal is for, and who reads it. A cover record: what was sent, to whom, on what date, in what form, by whom, and what response is expected. Its reader is the recipient today and a claims analyst in two years. It exists to answer a question that will absolutely be asked: did they have it, and when?

The template

The review stamps, described by function

Design firms use different words. The vocabulary and what each does to your risk and your schedule:

The gap between "approved as noted" and "revise and resubmit" is worth weeks — on Northgate it was the difference between hitting a mill slot and missing it. One of the cheapest conversations available to you happens at the preconstruction meeting: name the four to eight submittals that gate a long-lead release and ask that, for those specific items, reviewers use "approved as noted" wherever their comments do not go to design intent. Nobody is being asked to lower a standard. You are asking for a stamp choice on items where the difference between two stamps is a manufacturing slot.

🔴 The field that decides a dispute: the declaration of deviations

By submitting, you certify. Standard general conditions provide that the contractor represents it has reviewed and approved the submittal, verified materials and field measurements, and coordinated the information with the work. And review does not relieve you of responsibility for a deviation from the contract documents unless you specifically informed the design professional of that deviation in writing and received written approval of that specific deviation.

So: every submittal that deviates from the contract documents in any respect carries a cover letter listing the deviations, item by item, asking for specific written approval of each one. Not a note in the corner of sheet 147. A letter, on the front, numbered.

Why it is usually filled in badly: declaring a deviation invites a rejection, and the fabricator would rather the reviewer not notice. So a 1/2-inch perimeter joint against a specified 3/4 inch goes in as though it conforms, comes back stamped approved as noted with comments about a mullion cap finish, and 38,500 SF of unitized panels get built wrong. That is yours, almost certainly and almost entirely — and the fix costs one page.

One more discipline that belongs on the transmittal: a submittal the GC has not reviewed should never reach the architect. If you are transmitting packages you have not opened, you are not running a submittal process — you are running a mail room, and you have also just falsely certified that you checked it.

D.6 Change order request / change proposal

What it is for, and who reads it. Your priced proposal for a change, submitted to the owner's representative and usually reviewed by the architect and an owner's cost consultant. It becomes the basis of a negotiation and, eventually, an executed change order.

Price it in five layers, in order. Most people price layer one and stop.

   LAYER 5   IMPACT AND DISRUPTION      <- proved, or it is worth nothing
   LAYER 4   TIME AND EXTENDED GC       <- the layer everyone forgets
   LAYER 3   CONTRACT MARKUPS           <- the rate is fixed; the base is not
   LAYER 2   CREDITS FOR DELETED WORK   <- always disputed
   LAYER 1   DIRECT COST                <- everyone gets this far

The template

CHANGE ORDER REQUEST No. ______ · Date: __ · Project: _ Originating document: [bulletin / ASI / RFI response / CCD / field condition / owner request] No. , dated Description of change: _____ Notice given: [date, method, reference] — state this, always

Northgate's contract percentages, for worked consistency (yours will differ — find them in Division 01 and the general conditions before you price your first change, not after):

Two traps in layer 1. The burdened-rate trap: price a change at the base wage and you have donated the burden — typically 35% to 55% on top. The idle-equipment trap: when a change stops a crew, the excavator does not go home; idle or standby time is legitimate and is priced differently from operating time. State which you are claiming on every line. A reviewer who finds operating rates on idle hours will discount your whole submission, including the parts that were right.

And in layer 2: you do not credit what you already built. If the wall is framed and boarded and the owner deletes the room, that is not a credit, it is a demolition cost.

🔴 The field that decides a dispute: the time extension and its extended general conditions

A change order that adds time without addressing extended general conditions has given away $5,150 per day.

Every change gets three questions, and the third is the one that gets skipped: does it add work to a critical-path activity; does it add an activity or change logic; and does it consume float that belonged to somebody — whose float was it?

Work the offer that arrives at every negotiating table: "I'll sign this $75,223 today, right now, if the extension is no-cost." Seven calendar days:

   7 CD × $5,150/CD = $36,050

The offer is not $75,223. It is $75,223 for something worth $111,273 — you are being asked to donate 32%. A great many owner's representatives sincerely believe a time extension is a favor they are granting rather than a cost you are absorbing, and they are not being sharp; they simply have never seen the arithmetic. Your general conditions do not pause.

The answer is not a fight. It is: "I'll sign today too. The seven days are $36,050 of extended general conditions at the rate in our contract, and here's the fragnet showing the seven days. Same page, same signature."

Why the field is usually filled in badly: because pricing time requires a time impact analysis, and a TIA requires the schedule to be updated and accepted, and that is work. So people write "no time impact" to keep the change simple, and then discover in month sixteen that eleven changes each "with no time impact" have consumed the entire float on the finish sequence. Run the TIA contemporaneously, against the accepted current update, not the baseline. A TIA run in week one is evidence. One run eight weeks later against a reconstructed schedule is an argument.

And a word on layer 5. Impact costs are real, and they are also the most abused line item in construction. A contractor who prices only the visible work has donated the rest; an owner billed for unsubstantiated "impact" has been overcharged. The discipline is proving it — a measured mile comparing an unimpacted period of the same work by the same crew against an impacted one, or discrete cost tracking from the first hour. A number derived from a published factor table and nothing else will be attacked, and it will lose.

D.7 Construction change directive and the T&M ticket

What the CCD is for, and who reads it. A construction change directive is the instrument that exists for exactly one situation: the owner needs work to proceed before price and time are agreed. It is issued by the owner (usually through the architect), it obligates you to proceed, and it establishes the cost-accounting basis from hour one. Its readers are you, your accounting group, and eventually whoever audits the resulting cost.

A CCD is a good thing. It is not an escalation and it is not a sign of trouble. It is the mechanism that would have prevented CO #14's $43,650, because it converts "just start, we'll figure out the paperwork" into a written instrument with a cost basis attached.

The CCD — what it must contain

The T&M ticket — the record that gives the CCD teeth

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

TIME AND MATERIAL TICKET No. ________       CCD / Change ref: ________
Project: ______________  Date: __________  Cost code: ____________
Description of work performed and location (area, level, grid): ______________________

LABOR
| Name | Classification | ST hours | OT hours | Task performed |
|------|----------------|---------:|---------:|----------------|

EQUIPMENT
| Unit no. | Description | Hours OPERATED | Hours STANDBY |
|----------|-------------|---------------:|--------------:|

MATERIAL
| Description | Qty | Unit | Delivery ticket no. attached |
|-------------|----:|------|------------------------------|

SUBCONTRACTOR / OTHER: ______________________________________________

Contractor's representative: ____________________  Time submitted: ______

Owner's representative signature: ____________________  Date: ______
SIGNATURE ACKNOWLEDGES THE HOURS AND QUANTITIES SHOWN ONLY.
IT IS NOT AGREEMENT ON PRICE, MARKUP, OR ENTITLEMENT.

If signature declined: presented to ____________ at ______ on ______; declined.
Transmitted in writing same day: ______

Field notes

• One ticket per day per change, numbered sequentially. Never combine across days or across changes.
• Names, classifications, and hours — not "5 laborers, 8 hours." Which five, at what classification. Certified payroll, the daily report, and the ticket must agree, because somebody will eventually compare them.
• Equipment by unit number, with operated and standby hours separately.
• Material with quantities and delivery ticket numbers attached.
• A one-line description tied to the area and grid — so the ticket can be matched to the daily report.
• Signed the same day by the owner's designated representative.

🔴 The field that decides a dispute: the signature block's limiting language — and the "declined" line

Put "signature acknowledges hours and quantities only; it is not agreement on price or entitlement" on the form, so nobody has to say it out loud every afternoon. Without it, owner's representatives learn to refuse to sign — reasonably, because they are being asked to endorse a number they cannot evaluate. With it, signing costs them nothing and refusing looks unreasonable.

And when they still will not sign, use the declined line. Note the date, the time, to whom it was presented, and that signature was declined — then transmit the ticket 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.

Why this is usually filled in badly: the first four days. Every one of these disputes has the same shape. On days 5 through 17 of CO #14, Kestrel did all of this correctly and those costs came through at 100 cents on the dollar. Days 1 through 4 did not exist on paper, and $19,800 of the gap lives entirely in those four days — reconstructed six weeks later from a foreman's memory, at roughly 33 cents on the dollar. The ticket series opens in hour one, before anybody knows whether the change is big.

D.8 Change log

What it is for, and who reads it. One page that answers "where is all the money that is not in the contract yet." Read by your project manager weekly, your executive monthly, and the owner at every OAC meeting.

The pending-change exposure block

The log's most valuable output is not the list. It is the summary at the bottom:

🔴 The field that decides a dispute: "notice given — date and reference"

Nearly every contract requires written notice of a change-causing event within a stated number of days of when the contractor knew or should have known. Miss the window and you can be right about everything else and recover nothing.

The change log is the only document on the project that can prove notice was given on every single change, because it is the only one that lists all of them in one place. A blank in that column is not a missing data point. It is an unnoticed change, and depending on your contract and jurisdiction it may already be dead.

Why it is usually filled in badly: notice is given verbally or in an email in a thread, and nobody records where. Fix it by requiring a notice reference — a letter number or a correspondence log entry — not a checkbox.

The second field worth guarding: pending exposure belongs in the cost report. A project showing a healthy margin with $2.1M of unresolved pending changes is not showing you a margin. It is showing you a margin and a question, and only one of them is on the report.

D.9 Notice letter

What it is for, and who reads it. A formal, contractually specified instrument giving written notice of an event you believe entitles you to more money or more time. Read by the architect, the owner, and — if this goes badly — a tribunal.

It is not a complaint, not an email in a thread, and not a paragraph inside meeting minutes. And its delivery method matters: if your contract prescribes a method of delivery for notice, use exactly that method. Email may or may not count. Check.

The five required elements

The model text

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 the reader's workload or attitude. Notice what is present: a clause reference, dates, a quantified impact, an explicit statement that the impact is incomplete, a reservation, and a request with a date. This letter protects you completely and costs the reader nothing except an answer, which is what you actually wanted.

🔴 The field that decides a dispute: element 3, the impact statement — specifically the sentence that says it is not yet complete

Contractors lose notices in two opposite ways. They overstate — asserting a large number early, which the other side then spends two years attacking, and every subsequent number you produce inherits that credibility problem. Or they leave it blank, which lets the other side argue that no impact was known at the time and the claim was invented later.

The correct answer is both halves: here is the impact I can prove today, here is a statement that the full impact is not yet determinable, and here is my commitment to supplement. That sentence is what lets you grow the number honestly as the event unfolds.

Why it is usually filled in badly: because nobody wants to send a notice at all. It feels like declaring a fight with a partner you have eleven more months with. So it goes out as a friendly email with no clause reference and no reservation — which is a nice message and not a notice. Send the real one, in the register above, and send it every time. Do it four times and it becomes routine; nobody's feelings are hurt and your file is intact.

D.10 Schedule of values and application for payment

What they are for, and who reads them. The schedule of values (SOV) allocates the contract sum across portions of the work; the application for payment bills against it monthly. Readers: the architect (who certifies), the owner (who pays), the owner's lender and its inspecting consultant, and your own accounting group.

⚖️ Described by function only. The AIA G702 application and certificate for payment and its G703 continuation sheet, and the ConsensusDocs and EJCDC equivalents, are copyrighted published forms. What follows is the structure and the purpose of each column — not the form. Use the form your contract requires.

The schedule of values — how to build one

The continuation sheet — the columns, by function

Northgate's payment terms, for worked consistency: retention 10% until 50% complete, then 5%; pay application submitted by the 25th; owner pays in 30 days. Willow Street carries 5% retention throughout on a $6.8M municipal contract. Retention and prompt-payment rules vary by state and by public-versus-private work, and they change — check your jurisdiction and your contract, not this book.

🔴 The field that decides a dispute: percent complete, and the honesty of the schedule of values behind it

Front-loading is the SOV version of unbalanced bidding: assigning more value to early activities and less to late ones so you get paid faster than you spend. On Willow Street's $6.8M, moving $180,000 of value from finish activities into mobilization and foundations might improve your financing position by roughly $30,000–$35,000 over the job.

It is also a representation to the owner that mobilization is worth what you said it is worth, and it is not. Most owner-favorable agreements require the SOV to be submitted for the architect's approval and to "allocate the contract sum to the various portions of the work" — language that a materially front-loaded SOV does not satisfy. Architects reject them routinely.

More seriously, it leaves an unbilled liability at the end: you collected for value you have not created, so the last 10% of the work has 4% of the money behind it, and you finish the punch list on your own dime with a subcontractor who has already been paid. And when a job goes bad, a front-loaded SOV is the first exhibit in the owner's argument that your billing was never trustworthy — which follows you into every claim you file.

The legitimate neighbor, so you can tell them apart: genuine early costs belong in early line items. Mobilization really does cost money. Bonds are paid up front. Long-lead deposits are real. Putting real early costs in early lines, and being able to substantiate every one, is correct estimating. Putting finish money in early lines is something else.

Why percent complete is usually filled in badly: it is estimated from the trailer rather than measured in the building, because measuring takes a morning. The discipline that fixes it is the same one that produces good daily reports — quantities installed, recorded daily, by area. Then the pay application is arithmetic rather than a negotiation.

D.11 Conditional and unconditional lien waivers

What they are for, and who reads them. A lien waiver (often "waiver and release") gives up lien rights in exchange for payment. Readers: the paying party's accounting group, the owner, the owner's title company and lender.

⚠️ Waiver forms are statutory in some states and not in others. Several states prescribe the exact form, and a form that does not match the statute may not do what you think it does. Some states void advance waivers as against public policy; some permit them. This section describes the four flavors by function. Get the form your jurisdiction requires, and ask your attorney once, at the start of your career, and then stop guessing.

The four flavors

The fields, by function

The rhythm that makes the system work

Conditional for the current period; unconditional for the prior period. Always one period behind, because you cannot honestly release rights for money you have not received. Northgate's subcontracts condition each progress payment on delivery of (a) the sub's conditional waiver through the current billing period, (b) the sub's unconditional waiver through the prior period, and (c) the same pair from every lower-tier party that served a preliminary notice.

When your waiver matrix has a hole in it, that hole is a company that either did not get paid or did not respond — and both are things you want to know before you release a check.

🔴 The field that decides a dispute: the through date, and the exceptions block

Two abuse patterns, running in opposite directions.

Against the subcontractor: an unconditional waiver sent with "sign this and we'll cut your check Friday." The sub signs, the check does not come, and the sub has released its security for nothing. Any subcontractor signing unconditional waivers before payment clears is running an unsecured lending business without the interest rate.

Against the contractor: a final unconditional waiver that also releases claims — delay, acceleration, unresolved change orders — buried in the same paragraph as the lien release. Many states prescribe statutory forms precisely to stop this. Many do not.

So: read the through date, and read the exceptions block, on every waiver you sign. If you have a pending change order, an unresolved delay claim, or disputed retention, it goes in the exceptions block by number, in writing, before you sign — not in a phone call.

Why this is usually filled in badly: waivers are processed in bulk by an accounting group under month-end pressure, and nobody in that workflow knows which change orders are unresolved. The fix is procedural: the project manager reviews the exceptions block before the project accountant sends the waiver. It takes ten minutes a month.

The same caution applies to the certification on your own application for payment, and to any release language inside it. Know which one you are signing every month.

D.12 Subcontract scope sheet

What it is for, and who reads it. The most valuable document in buyout. A written, package-specific list of exactly what is included, exactly what is excluded, and — critically — where this subcontractor's work stops and the next one's begins. Developed before bids, issued with the bid package, refined in the scope-review call, and attached to the executed subcontract as an exhibit.

Readers: every bidder, your estimator during leveling, and your superintendent at 6:30 a.m. in month fourteen when two foremen are arguing about who owns something.

💡 Estimators price scope. Subcontractors bid specification sections. Those are not the same thing, and the difference between them is where your profit goes. Nowhere in a 900-page project manual does a section say "and also do the thing between your work and the next guy's." So it lands in nobody's number. Scope gaps live between subcontracts, not inside them.

The twenty-seam checklist — put every one on every scope sheet, for every trade

A complete scope sheet — package 09-1, metal stud framing and gypsum board

Copy the structure; change the trade.

PACKAGE 09-1 — METAL STUD FRAMING AND GYPSUM BOARD Northgate Outpatient Pavilion · Scope Exhibit A to Subcontract · Rev. 3

Part 1 — Included in the base subcontract amount

Part 2 — Explicitly excluded, and where the work goes instead

Part 3 — Clarifications (the answers from the scope-review call)

Part 4 — Schedule and manning obligations

⚖️ The clause that makes all of this work. Write the scope sheet into the subcontract as Exhibit A, list any accepted qualifications explicitly in Exhibit B, and include an order-of-precedence clause stating that qualifications, exclusions, conditions, or clarifications appearing in the Subcontractor's proposal are not part of the agreement unless expressly restated in Exhibit B. Without it, a sub can attach a two-page proposal with fourteen exclusions and argue that the exclusions came along with the price. With it, the only exclusions that exist are the ones you knowingly accepted.

🔴 The field that decides a dispute: the exclusion column, and specifically the exclusions every bidder shares

Two failure modes, and the second one is invisible.

Visible: one bidder excludes something the others include. That shows up on the bid tab, gets leveled, and gets priced. The system works.

Invisible: every bidder excludes the same item. On Northgate all three drywall bidders excluded lead-lined gypsum board. That does not change the comparison between them at all — it is invisible on the bid tab — and it is still an unbought scope. Circle shared exclusions separately, always, and assign each one somewhere before award.

Why the sheet is usually filled in badly: it takes an estimator about two hours per trade and it has to be done before the bids arrive. Written afterward, you unconsciously write a sheet that levels cleanly against the bids you already have, which teaches you nothing. Cost of finding the blocking gap on March 20: $107,000, priced at bid rates. Cost of finding it in month nine, after the walls are framed, roughed in, and boarded on one side: several times that, arriving as change orders with markup and an argument attached.

D.13 Bid tabulation / leveling sheet

What it is for, and who reads it. Leveling means adjusting every bidder's number so all of them cover the same scope, so the comparison is between prices rather than between paragraphs. Read by your chief estimator, your operations executive at the award decision, and — on cost-transparent delivery — the owner.

The template

Worked, so the shape is unmistakable — the Northgate masonry package

Budget $890,000. Three bids: Anvil $824,000 · Rivermont Block & Brick $766,000 · Castellan $851,000.

The rankings inverted completely. The bidder whose base number was the highest is the actual low at $866,000 — $105,520 below the apparent low bidder and 2.7% under budget. Rivermont's $766,000 was not a bad price; it was an incomplete price, honestly qualified. Carried as submitted, that $194,000 would have arrived over eighteen months as change orders and scope-gap arguments, with markup on top.

🔴 The field that decides a dispute: the addenda-acknowledged row

Everything else on the sheet is arithmetic you can redo. The addenda row is a fact about which building each bidder priced.

Rivermont acknowledged only Addenda 1 and 2. Addendum 3 added CMU at the generator enclosure — 1,850 SF, valued at $52,000. Their price is for a different building. When the generator enclosure shows up on the drawings in month seven, Rivermont will say "we never bid that," and they will be right.

Why it is usually filled in badly: it is a small box on a proposal, at the bottom, in a place a tired estimator's eye slides past at 12:40 p.m. on bid day. Make it a required field on your quote intake sheet, and have the scribe read it back out loud with the number.

Two more disciplines on this sheet. Compare scope-corrected numbers, never face amounts. And carry an independent in-house number for every major trade — not a full detailed estimate, a defensible order-of-magnitude number from quantity and a historical unit rate. A quote is only meaningful against an expectation: a cluster of bids close to each other and far from your number means your number is wrong; a single bid far below a cluster means that bid is wrong.

D.14 Job hazard analysis (JHA)

What it is for, and who reads it. A step-by-step analysis of one activity: what the steps are, what can hurt somebody at each one, what the control is and which level of the hierarchy it sits at, and who verifies it and when. Its readers are the crew that will do the work — and only them, really. Everyone else is secondary.

A JHA written by an office and handed to a crew is paperwork. A JHA written with the crew that will do the work is planning. The office version is not merely less effective; it is actively harmful, because it produces a signed document asserting that a hazard analysis was performed when the people exposed to the hazards have never read it. It creates the record without the safety.

The template

JOB HAZARD ANALYSIS                       JHA No. ______  Rev. ______  Date: ______
Project: __________________  Activity: ______________________________
Location / area: ____________  Trade / crew: ____________  Anticipated duration: ______
Prepared BY (must include the crew doing the work): _____________________________
Permits required: [hot work] [confined space] [energized] [excavation] [lockout] [crane/critical lift]
Competent person(s) for this activity: __________________  Rescue plan required? Y / N

| # | Step | What can hurt somebody (the mechanism) | Control (and hierarchy level) | Verified by / when |
|---|------|----------------------------------------|-------------------------------|--------------------|

Crew review and acknowledgment:
| Name | Company | Signature | Date |

The hierarchy of controls, in order: Elimination · Substitution · Engineering · Administrative · PPE. A JHA in which every control is PPE has told you something important about the JHA.

A fully worked JHA — trench excavation and 4-inch sanitary installation

Activity: Excavation and installation of 4-inch SDR-35 sanitary sewer, 4–6 ft cover, inside the building pad, using a trench box · Crew: 1 foreman, 1 pipelayer, 2 laborers, 1 operator · Prepared by: the pipe foreman, the Kestrel superintendent, and the crew, on the ground, in thirty minutes · Rev. 1 — revised after the north-line locate results came back

Two tests for whether your JHA is real. Can any crew member on that activity tell you, unprompted, the two biggest hazards in their own words? If not, they did not participate; they signed. Has it been revised? A JHA on Rev. 0 after four months describes work that is not being done the way it is described.

🔴 The field that decides a dispute: "verified by / when"

Steps and hazards are easy. Controls are easy — anybody can write "use a trench box." The verify column is what converts a document into a system, because it names a person and an interval, which means somebody can be asked on Friday whether it happened, and a record exists when they say yes.

After an incident, three documents get pulled immediately: the JHA, the pre-task plan, and the inspection log. A JHA with a rich control column and an empty verify column proves that somebody thought about the hazard and that nobody checked. That is a worse document than no document, and it is the most common form a JHA takes.

Why it is usually filled in badly: because filling it in creates an obligation for a named person, and the person filling out the form often is not that person. Write the JHA with the crew and the column fills itself.

⚠️ Note where the strongest control in this JHA came from. Step 3's trench box is an engineering control chosen partly because the site could not give up the width for sloping — a logistics and commercial decision made weeks earlier, in an estimate and a site plan. Nearly every elimination- and engineering-level control in construction lives in a schedule, a contract, a sequence, or a procurement decision, and is available only to people thinking about safety early.

D.15 Toolbox talk

What it is for, and who reads it. Five minutes on one specific hazard, delivered by somebody who will be on the job all day, to the crew that faces the hazard today. The deliverable is a changed behavior. The sign-in sheet is a byproduct, not the product.

The structure — five parts, five minutes

Record: date, topic, presenter, crew, signatures. And pick the topic from this week's look-ahead and this week's near-miss log, not from a corporate rotation calendar. If the roofers start Thursday, the Wednesday talk is roof edges and hot work.

A complete five-minute talk — ladders, the morning after NM-071

Delivered on Level 2, April 17, Year 2, to about thirty people, the morning after a Halcyon Electric apprentice reached beyond the rail of a podium ladder at grid E and caught himself on the rail.

[The work today — 30 seconds]

"Morning. Today on this level: Halcyon is pulling wire on the east corridor, Cardinal is running duct above the same corridor, and Sightline is hanging board in Areas A and D. Three companies, one ceiling, all day.

[The one hazard — 60 seconds]

"Today's hazard is the ladder you have used a thousand times. Not a bad ladder. A perfectly good six-foot podium ladder, set up right, on a flat floor — and you are eighteen inches short of where the wire needs to go, and the scaffold is two bays away, and moving it costs you four minutes. So you lean. And the moment your belt buckle passes outside the rail, that ladder is a lever and you are the weight on the end of it.

[The story — 90 seconds]

"Yesterday afternoon, 2:35, this corridor at grid E. A Halcyon apprentice reached past the rail to pull a wire. The ladder shifted. He caught himself on the rail and he is here this morning.

"Nobody got hurt. I want to be honest with you about why I am still standing here talking about it. He did nothing that most of us have not done. The four minutes he was saving are real — I know that. And I know that the reason four minutes felt expensive yesterday is that we are behind on this elevation, and that is on us, not on him.

"So this is not me telling you to be careful. This is me telling you what we changed.

[The control and who does what — 60 seconds]

"Three things, starting now.

"One. If the work is outside the rails, you get off the ladder. You get a rolling scaffold or a lift. There are two scaffolds staged at the east stair as of this morning — I put them there so nobody has to walk to the yard for one.

"Two. If the scaffold you need is not there, or somebody else has it, you call your foreman, and if he cannot solve it in ten minutes he calls me. My number is on the back of your badge. The work waits. I will back you on that in front of anybody, including your own office.

"Three. Before you set a ladder today, look at where the work actually is, not where you hope it is. If you have to reach, you have the wrong equipment.

[The ask — 30 seconds]

"Here is what I want from you today. One thing. If you see anybody reaching outside a ladder rail — your crew, another crew, me — say something to them, and then tell Ivy or your own foreman where it was. I want the locations, because if the same spot keeps showing up it means we staged the equipment wrong and that is a thing I can fix. Thanks. Go to work."

🔴 The field that decides a dispute: the attendance record — and the reason it is the weakest part of the document

Say the uncomfortable thing plainly. The sign-in sheet is the field most likely to be produced in a proceeding and the field least likely to reflect what actually happened. A sheet with thirty signatures and a topic line proves attendance at something. It does not prove that a hazard was communicated, and everyone reading it knows that.

So make it prove more, cheaply. Record: the topic, the specific location or activity it applied to, the presenter's name (the foreman, not the safety department), and the one action requested. A talk recorded as "Ladders — L2 east corridor, grid E, following NM-071; presenter I. Beaudry; action: report locations where staged access is inadequate" is a document that describes a real event. A talk recorded as "Ladder safety" is a document that describes a signature.

Why it is usually filled in badly: because the sheet is treated as the deliverable. It is not. It is the receipt.

D.16 Pre-task plan (PTP)

What it is for, and who reads it. This crew, this task, today. A half-page card, filled out by the foreman with the crew at the morning huddle, kept in a pouch at the work area. Read by the crew, spot-audited by the superintendent and safety.

Most companies do the toolbox talk and skip the pre-task plan, which is backwards. The PTP is the one that prevents today's injury.

PRE-TASK PLAN                          Date: ______  Crew / company: ______________
Task today: _______________________  Area / level / grid: __________  Foreman: ______

1. What are we doing today, and where?           ______________________________
2. What changed since yesterday?                 ______________________________
3. Who else is working near us, above us, below? ______________________________
4. Top three hazards for THIS task, TODAY:       1. ______  2. ______  3. ______
5. Controls in place (and who set them up):      ______________________________
6. Equipment / permits / tags required today:    ______________________________
   [ ] Scaffold tag current, dated today, initialed by: ____________
   [ ] Hot work permit   [ ] Confined space   [ ] Energized work   [ ] Lift plan
7. Rescue / emergency plan for this task:        ______________________________
8. Who is new to this crew or this task today?   ______________________________
9. What could stop us today (constraint)?        ______________________________
10. Anything anybody wants to raise:             ______________________________

Crew acknowledgment: ______________________________________________________

Field notes and the dispute field

Field 2 — what changed since yesterday — is the whole reason the card exists. Yesterday's plan was safe for yesterday's conditions. Overnight, a different trade moved a plank, a floor opening got uncovered, a lift went down, or the weather turned.

Field 3 — who else is working near us, above us, below — is the multi-employer question, and it is the one a crew cannot answer from inside its own company. That is what the general contractor is for.

Field 8 — who is new — because every new person restarts a learning curve, and assigning a named buddy for the first week is the cheapest intervention on this list.

🔴 The field that decides a dispute: field 6's scaffold-tag line — a verification with an initial and a date

The single most useful line on this card is a checkbox that cannot be honestly ticked without somebody physically reading a tag.

Northgate's week-34 scaffold near-miss had three findings, and the first was no competent-person inspection tag for that shift — the tag was two days stale. The corrective action was exactly this: shift-start tag verification added to the pre-task plan, initialed. It is cheap, fast, and verifiable.

Why the PTP is usually filled in badly, or not at all: it gets skipped exactly when it matters most. In Northgate's weeks 31 to 34, as overtime nearly quintupled and trade stacking went from two companies in a zone to five, pre-task plan completion dropped eighteen points and near-miss reports fell — people stopped filling them out because they were busy, and stopped reporting because reporting cost them time they did not have. Falling PTP completion during an acceleration is not an administrative problem. It is a leading indicator, and it is the one you can see coming.

D.17 Inspection and test plan (ITP)

What it is for, and who reads it. A work-package-by-work-package table saying, for every activity that can go wrong: what gets checked, against what, how, how often, by whom, whether work stops for it, what record it produces, and who signs. It converts a nineteen-hundred-page project manual into a list of things that will happen on specific days.

Readers: your quality lead, your superintendent, every subcontractor foreman, and the testing agency.

The template

The three point types — and the distinction that costs days

Getting it backwards costs money in both directions.

A hold point mislabeled as a witness point: the crew ties rebar, notifies the special inspector, nobody comes, and 180 CY goes in. That inspection is on the statement of special inspections filed with the permit, and the building official cannot issue a certificate of occupancy without a final report of special inspections that the inspector cannot write for work they did not observe. Every path from there is bad — engineering evaluation from as-built documentation and photographs, ground-penetrating radar plus selective destructive verification, or removal and replacement.

A witness point mislabeled as a hold point: the quieter error, and more common. Fourteen people stand down for two days waiting for an inspection nobody required. Idle craft, pump-truck standby, and returned concrete: roughly $22,884, generated by one wrong letter in one column of a table.

🔴 The field that decides a dispute: the notification lead time on every hold point

Every H needs three things, and if it lacks any of the three it is not a hold point — it is a wish: a named party, a notification lead time, and a written release.

The hold point that fails does not fail because somebody ignored it. It fails at 6:50 a.m. with eleven trucks ordered, a pump on site at $1,450 for the day, fourteen people standing in a hole, and an inspector who is at another site. That happens because the notification was verbal or same-day.

The fix is procedural and permanent: put a 48-hour written notification requirement for hold-point inspections into the testing laboratory's scope and into your own procedure, log every notification, and require written confirmation of receipt. Then generate the notifications from the list you already have — the hold points appearing in next week's six-week look-ahead.

And one line worth tattooing on a project engineer: a close-in release is a hold point. Nothing gets covered until somebody with a name has walked the area, confirmed every prior hold point in that area was released, and signed a piece of paper. Twenty minutes per thousand square feet, and it is the cheapest insurance on the job.

D.18 Non-conformance report (NCR)

What it is for, and who reads it. The instrument that identifies work that does not conform to the contract documents, bounds its extent, gets it dispositioned by the right person, corrects it, and verifies the correction. Readers: your quality lead, the responsible subcontractor, the design professional, and the owner.

Every project produces nonconforming work. Every one. The measure of a quality system is not whether nonconformances happen; it is whether they are found early, documented honestly, dispositioned by the right person, corrected, and prevented from recurring.

The template

The four dispositions — and who must approve each

"Use as is" is a design decision, not a field decision. The person accepting a deviation is accepting professional responsibility for whether the building still works. That is the architect's or engineer's license, not yours. If you are ever handed a "just leave it, it's fine" from anyone other than the design professional in writing, you have been handed a liability, not a permission. And write the acceptance narrowly: this condition, at these locations, for these reasons — not a blanket blessing of the detail everywhere it occurs.

🔴 The field that decides a dispute: "the requirement" — the citation

An NCR that says "the flashing looks wrong" starts an argument between two opinions. An NCR that says "lap dimension measured at 1½ in. at 14 of 22 laps inspected; approved submittal sheet 3, detail 2 requires 3 in. minimum with the upper sheet lapping over the lower" starts a disposition.

The citation is what moves the conversation from is this a problem to which of the four dispositions applies and who approves it. Without it, the installer argues classification ("it will perform fine"), which is a disposition argument made by the wrong person at the wrong stage.

Why it is usually filled in badly: because citing the requirement means going and finding it, and the person standing at the wall at 3:15 p.m. is confident and in a hurry. And because writing an NCR feels like an accusation, so people try a conversation first — which is fine, right up until the wall gets closed.

The line that is not a gray area: nonconforming work that is disclosed and dispositioned, even by a "use as is" that embarrasses you, is a managed event. The same work buried behind finish is a latent defect that somebody bought without knowing. The distinguishing fact is not the size of the defect. It is the concealment.

D.19 Punch list

What it is for, and who reads it. The list of items that must be completed or corrected before final completion. Readers: every subcontractor foreman (a 14-item list they can act on), the architect, and the owner.

First, sort it. Half the arguments at the end of a job come from conflating four different things with four different payers and four different effects on substantial completion:

The template — organized by area and by trade

Managing the list — four rules

1. The three punches, in order: your pre-punch, then the architect's, then the owner's. Never let a consultant punch an area you have not pre-punched. The list comes back roughly twice as long, half of it is your own trash and protection board, and you have destroyed your credibility for every area that follows — because the reviewer now believes the building needs to be inspected rather than verified.
2. Distribute daily, by subcontractor. A 1,847-item list sent to twenty subcontractors is ignored. A 14-item list sent to one foreman gets done.
3. The two-touch rule. Nobody closes their own item.
4. Punch continuously, by area, at every trade handoff — before the next trade starts, both trades walk it with your field engineer. Processing a punch item all-in costs roughly $85 to $140 before the repair itself; punching continuously produces a fraction of the items.

🔴 The field that decides a dispute: the verification column — because it is the one people merge into "complete"

Most punch lists have one status field, and it holds whatever the subcontractor last said. That is not a status. "I told him to fix it" is not a status.

Two fields, always: marked complete by the responsible party, and verified by the general contractor's quality control, with a name and a date. An architect's back-check that finds 30% of "completed" items untouched resets your clock and your relationship in one afternoon — and it is entirely avoidable.

Why it is usually filled in badly: verification costs a walk, and the walk happens at the exact moment the project has the least staff left on it. Budget the punch crew and the verification walk as time-dependent general conditions (see Appendix C §C.8.9), because they run on a calendar and they are routinely underfunded.

And the number that reframes the whole exercise. Of Northgate's 1,847 open items on September 9, eleven actually stood between the owner and a temporary certificate of occupancy. Sorting the list is how you convert a panic into eleven assignments — and how you get the owner working on your side of the problem instead of standing over it.

D.20 Meeting agenda and minutes

What they are for, and who reads them. The agenda manufactures decisions; the minutes create the record. Readers: everyone at the meeting, everyone who should have been, and — later — a tribunal.

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. 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.

The OAC agenda template — decisions first, time-boxed

Status is distributed, never performed. 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 RFI log, the submittal log, the schedule narrative, the cost report, safety statistics, progress photographs, and the previous minutes. Discuss only the exceptions.

The decision log — the OAC meeting's primary product

The age and cost-of-delay columns 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.

The action-item block

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

You cannot call Cardinal Mechanical. You can call Sofia Marchetti. A company cannot forget, cannot be reminded, cannot be mildly embarrassed at next week's meeting, and cannot be held to a commitment — and in the gap between "Cardinal Mechanical" and an actual human being, the item dies.

Say the rewritten version out loud in the room before moving on. The named person gets 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.

And read last week's items aloud at the top of every meeting. Skip the read-back twice in a row and the discipline evaporates, because everyone learns commitments are not checked.

Minutes — record decisions, commitments, and facts. Nothing else.

Not 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.

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. Kestrel will handle it and get back to everyone.

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.

🔴 The field that decides a dispute: the objection deadline — and the obligation to read the other party's minutes

Many owner-contractor agreements, sets of general conditions, and 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 — five days, seven, ten, fourteen, "prior to the next meeting," or nothing at all. Find yours. Write it on the wall of the trailer and in the file name.

Then do the part people forget. On many projects the architect or the owner takes the OAC minutes. You must read them, and object in writing when they are wrong. Silence is agreement.

The entry to look for is the one that accepts an obligation you did not accept. "Kestrel will handle it." "Contractor will make up the time." Both are unbounded commitments, with no cause stated and no rights reserved, written by somebody else, in a document that becomes the project's version of events on day fourteen. Nobody made you say it. Somebody wrote it down, you did not read it, and silence did the rest.

Object in a register that makes it routine rather than adversarial: "Thank you for issuing Minutes No. 32. We have two corrections and otherwise concur…" — two paragraphs, no adjectives, inside the period, copied to everyone who received the minutes. Do it four times and the minutes stop containing those sentences, because the person writing them starts being careful.

Why this is usually done badly: nobody owns minute review. Assign it to a named person as a recurring calendar task, put the deadline in the file name, and make it a standing item at your internal team meeting. Ten minutes a week, and among the highest-return ten minutes on the job.

D.21 Delivery request form

What it is for, and who reads it. One page, submitted by every subcontractor for every delivery, at least 48 hours ahead, to a single person who owns the delivery calendar. Read by that person, the superintendent, and whoever is running the crane.

An unscheduled truck occupies the gate so the next truck stages in the street; occupies the crane or forklift so the scheduled pick slides; gets unloaded wherever there is room, which guarantees a second handling; and arrives without a receiving inspection because nobody was expecting it.

🔴 The two fields that decide disputes: unloading method and destination

Unloading method is where you discover that three subcontractors have all assumed they get the crane at 9:00. Destination is where you discover that a delivery has no destination — which means it is going to be double-handled, which means you should reject it until it has one.

And the dispute this form actually prevents happens at the truck, not at the gate. Never sign a clean delivery ticket for damaged material. Write the damage on the ticket, photograph it with the truck still there, and note the driver's name. Count it — shortages discovered at installation are shortages you own. And log backorders the day they appear, on the constraint log, that morning.

Why it goes wrong: 340 hollow-metal frames, bundled and shrink-wrapped, signed clean over three weeks because nobody wanted to unwrap them in the rain. Eleven months later, forty-one frames with the hinge preps on the wrong side. The manufacturer's position was that you signed for them, and their position was better. $18,400 of new frames plus six days of finish-hardware delay in a corridor that had already been painted — and it started with a signature under a plastic tarp.

D.22 Crane pick schedule

What it is for, and who reads it. A next-day list of what gets hoisted, by whom, in what order, built the afternoon before and published in writing — posted at the gate, in the trailer, and in the group text. Read by every foreman who needs the hook.

Crane time is the scarcest resource on most sites. Twenty minutes of daily indecision, on an eleven-month crane term, runs to tens of thousands of dollars.

The template

Header block: crane make and capacity · operator and oiler · lift director by name · today's wind limit and how it will be checked.

Four things the format does that the table does not show

One: the crane move is a pick that lifts nothing. On a typical day, ninety minutes of an eight-and-a-half-hour crane day — 18% — can be spent driving from one pad to another, setting mats, and deploying outriggers. It is the single most expensive line on the schedule and it is invisible unless you write it down.

Two: hold a contingency block empty on purpose. Something will go wrong. If the schedule is 100% committed at 5:00 p.m. the day before, the first delay of the morning cascades into the afternoon and the last trade on the list — always the same trade, always the one with the least clout — gets nothing.

Three: schedule the debris pick. If taking waste down is not on the schedule, it does not happen, and then it is on the floor.

Four: put the pour on the same page. A concrete placement using the east drive and a crane move that crosses the east drive are two schedules that must be one schedule. That is the entire difference between a good Thursday and a bad one.

🔴 The field that decides a dispute: the notes/conflicts column — and the critical-lift flag behind it

The notes column is where a pick schedule stops being a queue and becomes a safety document. It is where "clinic drive: flagger and spotter, no swing over drive" and "wind check at 7:45 — sail area" live.

And it is where the critical-lift trigger gets caught. Most contractors define a critical lift at some percentage of chart capacity — commonly 75% to 90%, Northgate's threshold is 80% — plus other triggers: multi-crane lifts, personnel platforms, lifts over occupied structures or live utilities, blind picks, and anything the lift director says is one. A critical lift gets a written, signed lift plan containing: the load weight from a verified source (a shipping ticket, a certified weight, or a calculation attached — never "it looks like about"); the rigging and its total weight; the crane configuration; radius, chart capacity, deductions, net capacity, and percent of chart; the ground bearing analysis and what is under the setup area; the swing path and exclusion zone; the maximum wind speed and how it will be measured; the named operator, lift director, qualified rigger, and signal person; and the pre-lift meeting with everyone at it.

Why it is usually filled in badly: the notes column is the last thing typed at 4:45 p.m. by somebody who wants to publish the schedule and go home. The discipline is to write the notes first — walk the picks, find the conflicts, then set the times around them.

⚠️ There is no paperwork that makes an over-chart lift acceptable. A pick at 111% of chart is not a critical lift requiring extra planning. It is a prohibited lift.

D.23 Six-week look-ahead and constraint log

What they are for, and who reads them. The look-ahead is not a report; it is a screen. You start with what the schedule says should happen, interrogate each activity against a fixed list of constraints, and remove from the plan anything that fails. Its output is two lists: work that is genuinely ready, and things somebody has to go fix.

The schedule tells you what should happen; the constraint log tells you what can. Work is only ready when every constraint on it has been removed — and making work ready is a separate discipline from scheduling it.

The eight constraint categories — learn them as a list you can recite

The constraint log template

The screen output

An activity does not enter the weekly work plan until every constraint on it has been removed. Not "is likely to be removed." Not "the architect said probably Thursday." Removed. The RFI is answered and in the field. The material is on the floor. The inspection is scheduled with a confirmation number.

Screening three of five activities out of a week is not a failure of the week. It is the screen doing exactly what it exists to do, three days before those crews would have shown up and stood there. And the crews that get screened out do not go home and do not get pushed into somebody else's area — they go to pre-screened, fully ready work elsewhere in the building. That reserve is the workable backlog, and maintaining it is as important as maintaining the look-ahead. A screen without a backlog just idles people.

🔴 The field that decides a dispute: the need-by date, back-calculated

Most constraint logs carry a "target date," which is when somebody would like the constraint gone. That is a wish. A need-by date is computed backward from the activity's start, and the difference is whether the log can tell you that something is already late.

It is also the field that turns the log into a notice engine. A constraint whose need-by date has passed, owned by the architect or the owner, is not a coordination item any more. It is a written notice with a clause reference (§D.9), and the constraint log is the dated, contemporaneous record of when you knew and what you asked for.

Why it is usually filled in badly: back-calculating requires opening the schedule for each item, and typing a plausible date does not. The tell is a log where most need-by dates fall on Fridays.

D.24 Weekly work plan and PPC tracking sheet

What they are for, and who reads them. The weekly work plan is a list of commitments made by the people who control the crews, in front of each other. PPC — percent plan complete — measures how many of those commitments were kept. Readers: the foremen who made them, and the superintendent.

A commitment has four properties. Miss any one and you have a topic, not a commitment:

1. A named person who controls the crew makes it. Not a company. Not a PM relaying it.
2. A specific, finishable deliverable — "top track complete in Zone B, all 47 partitions," not "work in Zone B."
3. A date, which is this Friday.
4. It is made out loud, in front of the other trades, who are relying on it.

The fourth does most of the work. A promise made to a project manager is an administrative item. A promise made to the four foremen whose work depends on it is a promise to peers, and people keep those.

The templates

Weekly work plan

PPC tracking sheet

   PPC = commitments completed ÷ commitments made

Three rules govern the measurement.

Rule 1 — It is binary. No partial credit, ever. "We got 90% of it" scores zero. The purpose of PPC is not to measure production — you already measure that in the cost report and in earned value. The purpose of PPC is to measure whether the plan can be relied on by the next trade, and reliability is binary from the receiver's point of view. Ninety percent of a handoff is zero handoffs.

Rule 2 — The last planner scores their own commitment, and the score is not a performance review. If a foreman feels the score is a disciplinary instrument, they will commit to less and less until the number is meaningless.

Rule 3 — Track commitments made, not just PPC. PPC of 90% on nine commitments is much worse than PPC of 72% on forty. If your PPC is rising while your commitment count is falling, your team is not improving — it is learning to promise less. And 100% is a warning sign, not a triumph: a team hitting 100% is committing only to what is certain, which means it is planning below its capacity.

Practitioners commonly report first measurements in the 40s to 60s and sustained practice in the high 70s to high 80s. Treat that as practitioner folklore rather than research: PPC is not measured consistently enough across projects to compare one job's number to another's. The only PPC number that means anything is your own, trended over time.**

🔴 The field that decides a dispute: the reason code

PPC is a thermometer. The reason codes are the diagnosis.

A thermometer tells you that you have a fever. It does not tell you what to do. The score creates urgency; the reason codes create improvement. A team that collects the score without the reasons has bought a thermometer and no medicine.

The discipline: every miss gets a reason, in the foreman's words, recorded on the spot Friday morning; every reason gets a category — one of the eight constraint categories, plus weather, plus a genuine "other"; categories are counted and trended, not just listed; and the top two or three get a countermeasure with a name and a date, not a discussion.

Northgate's first six weeks: 86 missed commitments out of 187 made — PPC 54%. Prerequisite work (21), material not on site (14), and information (12) were 55% of all misses, and every one of those three categories is owned by the general contractor's coordination, procurement, and RFI process. Fifty-five percent of the misses were caused by Kestrel, not by a subcontractor.

Which is exactly why the score has to be safe to report. The moment a general contractor uses PPC as a stick to beat subcontractors with, it loses access to the data that shows the general contractor is the problem.

Why the field is usually filled in badly: the honest reason a commitment was missed is often embarrassing for whoever is holding the pen. Collect the reason from the foreman, in the foreman's words, on the spot — not from a project engineer reconstructing it on Monday.

D.25 Turnover / closeout package checklist

What it is for, and who reads it. The documents and materials the owner receives at turnover. Readers: the owner's facilities group, their maintenance technicians for the next thirty years, and their lender or insurer.

The turnover package is not a list of documents. It is a schedule of collection dates.

Write it this way at notice to proceed, embed the dates in your subcontracts, and tie a portion of each subcontractor's retention to their own closeout submittals, and you will never again have thirty-four O&M packages sitting in thirty-four inboxes nine days from substantial completion.

🔴 The field that decides a dispute: the collect-by milestone — and the subcontract clause behind it

A checklist with a "due at closeout" column is a wish list. A checklist with a date per item, a named owner per item, and a subcontract clause tying a portion of retention to that item is a system.

The two items collected too late most often are record drawings and asset data, and for the same reason: both are byproducts of the work if you capture them while the work happens, and archaeology if you do not. A field engineer redlining the control set for fifteen minutes a week produces an accurate record at zero marginal cost. A draftsman working backward from 214 RFIs, 41 change orders, and a folder of photographs is inferring, and inference produces a document that looks authoritative and is wrong exactly where it matters most — the buried, concealed, and rerouted work nobody photographed precisely because it was routine.

The consequence lands years later, on somebody you will never meet: a maintenance technician at 2 a.m. with water coming through a ceiling, looking for a shutoff valve on a drawing that shows it in the wrong corridor.

Why it is usually filled in badly: closeout is scheduled as one 60-day bar labeled "commissioning and closeout," with no internal logic, no resource loading, and no owner — and inside that bar is a long serial chain. Build the closeout sub-network at notice to proceed, with the documentation collect-by milestones loaded as real activities.

D.26 Subcontractor prequalification form

What it is for, and who reads it. A structured, scored assessment of whether a firm can perform your scope, completed before they bid rather than during the award scramble. Readers: your chief estimator, your risk manager, and your executive at award.

The template — weighted scoring

🔴 The field that decides a dispute: named supervision available for your dates

Prequalification measures the company. The field experiences the crew.

Every subcontractor of any size has a best foreman, a competent middle, and one crew they hope you never meet. A firm with a spotless balance sheet that sends you its C-team will hurt you more than a marginal firm that sends its best people because your job is the one they want. The named foreman is the single highest-correlation predictor of how a trade performs on your project, and it appears nowhere in a standard prequalification package.

So add the field, and make it specific: name, availability date, and a commitment not to reassign without written consent — carried through into the subcontract's schedule and manning obligations. Then ask one more question that nobody asks: "who do you use for your taping crew / erection crew / controls sub?" Most trades subcontract part of their own scope. You are not just buying them; you are buying whoever they hire, and knowing that in advance lets you prequalify the tier below.

Why the form is usually filled in badly — and one caution about the experience field. "Three completed projects of similar size in the last five years" excludes by definition every firm that has not already done the work, which quietly narrows your bid list every year and hits smaller and newer firms hardest. A better test is demonstrated capacity: crew size and supervision available for this scope, references from work of any size, a visit to their shop, and an interview with the foreman who would run it. It takes longer and requires judgment instead of a threshold — and it is how you keep a competitive bid list.

D.27 Lessons-learned capture sheet

What it is for, and who reads it. The document that either changes the next job or gets filed where nobody looks. Readers: your estimating group (who need the cost and productivity data), your preconstruction group (who need the subcontractor evaluations), and the project manager who inherits the same problem next year.

Five rules make the difference.

1. Hold it while the team is still assembled — about two weeks after substantial completion, not after final completion. If you wait until the team disperses, you are interviewing individuals about a collective memory that no longer exists.
2. Structure it around specific decisions, not general observations. Never "how did the submittal process go?" Instead: "On March 18, Year 1, the anchor bolt submittal arrived in our office. It left on March 29. Walk me through those eleven days."
3. Capture the historical cost and productivity data. This is the closed loop the whole book is built toward.
4. Record subcontractor performance evaluations honestly, including when the failure was yours.
5. Assign an owner and a due date to every finding. A finding without a name is a complaint.

Invite two or three subcontractor project managers for the first hour. It is unusual, and it is worth doing every time.

The findings template

And capture the wins. A lessons-learned session that only captures failures teaches your company to hide things. Northgate's enclosure was resequenced by elevation rather than by floor, running the unitized curtain wall ahead with precast trailing, which released dry-in by zone about three weeks early — documented as a planning standard with the conditions under which it applies.

The data that feeds the next estimate

🔴 The field that decides a dispute — here, with your own future estimator: the diagnosis note

A variance without a diagnosis is a number. A variance with a diagnosis is an estimating standard.

Northgate's structural steel erection came in at $712/ton against an estimated $655/ton — and the entire variance is the acceleration premium and the second crew after the steel delay. Drop $712 into the unit-cost library and you have permanently overpriced steel erection on every future bid because of one job's one-time event, and you will not know why for years. The right entry is $655, plus a documented note about what acceleration costs when it happens.

Every row needs the same judgment: is this variance a rate, or is it an event? A rate goes in the library. An event goes in the notes, where an estimator can find it when the same condition recurs.

Why the field is usually filled in badly: producing it takes an estimator and a project accountant a full day, at exactly the moment both of them have been reassigned. Put the day on the calendar at notice to proceed, not at closeout. It is the highest-return day in the entire project.

D.28 The forms, indexed by when you need them

D.29 The seven fields, in one place

If you adapt nothing else from this appendix, keep these. Each one is a field somebody lost real money by leaving blank.

The one sentence to carry out of here: a form is not a record-keeping obligation. It is a set of questions somebody once lost money by not asking — and the field you are tempted to skip is almost always the one they lost it on.

Related: Appendix C — Estimating Reference · Appendix F — Safety Reference · Appendix G — Contract Clause Decoder · Appendix K — The Willow Street Project Package · Chapter 16 · Chapter 23 · Chapter 24 · Chapter 25 · Chapter 26 · Chapter 27 · Chapter 31 · Chapter 32 · Chapter 40