Chapter 25 — Quiz

B. The obligation runs from the contractor outward. The contractor demonstrates and certifies conformance; the design professional reviews the demonstration. A is the direction most people wrongly assume, C is a substitution request or an RFI, and D is a record drawing.

C. That is the one narrow exception on most standard forms: a deviation specifically called out in writing and specifically approved in writing. Everything else — dimensions, quantities, fabrication, coordination, means and methods, safety precautions — stays with the contractor regardless of the stamp. This is why deviations belong in a numbered cover letter, not in the corner of sheet 147.

C. You must transcribe the requirements too — that is real work and it comes from the specifications — but the first organizing act is establishing the required-on-site date, because everything else is computed backward from it. A and D produce an inventory. Only C produces a schedule.

B. The back-schedule was arithmetically fine. It tracked the wrong milestone. April 15 was Kestrel's internal number; April 18 was the last date Hank Duffy could release material against a reserved rolling slot, and it existed only on Ironbridge's production schedule and in Hank's head. A is technically true and dangerously incomplete — you cannot use float you do not know exists.

C. Approved as noted (also furnish as corrected) releases production, subject to incorporating the comments. Revise and resubmit and Rejected do not. Received is a logging action, not a review status, and fabricating against it is fabricating against nothing.

C. An architect asked to design an answer needs hours they do not have. An architect asked to evaluate a proposal needs minutes. The proposed solution is also the one most often omitted — and the answer that gets approved is usually the one the contractor proposed.

B. The answer requires something the documents (on your reading) did not require. Whether it is an interpretation of an ambiguity or added scope may be argued, which is exactly why you give written notice within your contract's period and seek a directive before building. It is not automatically a CCD — a CCD is a specific instrument the owner issues. And note C's trap: work does not become free because you were the one who asked about it.

C. A is the aging report. B is a function of a back-scheduled log. C collapses hundreds of rows into a handful of numbers and answers the question everyone thinks they know: who is actually holding this up. On Northgate in week seven the answer was the subcontractors (138 items never submitted) and, behind them, Kestrel — not the architect.

B. The review period is a contract term and does not evaporate — but a submission profile that dumps a wall of paper on a reviewer and then complains is a pattern every tribunal in the industry has seen. Level the curve. It is a planning obligation, and it is also the difference between having a credible complaint and having a self-inflicted one.

B. Three reviewers, three durations, and one of them is a permit action with its own queue that you cannot escalate with a phone call from a project manager. Whether a component may be deferred at all, and how long review takes, varies by jurisdiction and by building official — ask in the preconstruction meeting.

C. Every zero-gap row on CO #14 was a row where a third party generated a document as part of its own routine — batch tickets, supplier invoices, a testing lab report, a subcontractor's executed change order. Every large-gap row required a Kestrel employee to create a record deliberately, in the moment, under pressure. That is the pattern worth memorizing.

B. The tools are genuinely good and worth having. But a log sorted by specification section, moved into a cloud platform, becomes a beautifully rendered log sorted by specification section, available on every device your team owns. The amplification runs in both directions.

False. That phrase is a limitation, not a transfer. It is the reviewer explicitly narrowing what they take responsibility for. Dimensions remain the contractor's, reinforced by the certification the contractor made at submission.

False. A late review is a breach of an obligation. A delay requires that it pushed a critical-path activity; a compensable delay additionally requires damages you can prove. Entitlement, causation, and damages are three separate proofs.

True — and it should be the base case, not the conservative case, on delegated-design and multi-reviewer packages. The Northgate anchor-bolt chain was fifteen days infeasible on the day of award once a resubmittal allowance was included, and nobody knew because nobody ran it that way.

False. It is the one deliverable whose preparation cost rises the longer you wait. Reconstructing eighteen months of buried-utility routing at month twenty produces a set that is confidently wrong — worse than none, because somebody will core a slab based on it in five years.

False, and expensively so. The audit trail proves receipt, which on the $340,282 Northgate rework helped the architect, not Kestrel. A document is not controlled until the last person who acts on it knows its revision — a physical act in a trailer that no software observes.

False. "No cost impact" is necessary but not sufficient. That sentence is inappropriate whenever the proposal affects design intent, a code-governed or life-safety condition, or anything that is not readily reversible — regardless of price.

Specification section order is an artifact of MasterFormat's organization of trades and products. It has no relationship to when anything is needed, and the relationship is not even loosely correlated: Division 03 concrete mix designs and Division 26 switchgear sit sixty rows apart on a log and have lead times that differ by a factor of nine. The log therefore looks complete and organized while concealing the only fact that would let anyone act on it. It creates confidence without information, which is worse than obvious disorder, because obvious disorder gets fixed.

The paper trail is the project's memory, and contemporaneous records are worth roughly ten times reconstructed ones. The mechanism is interest at the time of creation. A batch ticket was printed by a ready-mix plant that had no stake in a dispute that did not yet exist; a foreman's recollection was produced eight weeks later, by an interested party, in support of that party's own claim. Both may describe the same reality. Only the first one is evidence; the second is argument, and argument is discounted by everybody who weighs records — owners, controllers, mediators, and tribunals alike. The practical consequence is that you must create records before you know whether they matter, because that is the only moment at which they can be created disinterestedly.

1. Reference (sheet, detail, spec section, revision) — prevents a round spent establishing what you are asking about.
2. Observed condition, stated factually — prevents "verify field conditions," especially if you measured something.
3. The specific question — prevents an answer to a different question.
4. Your proposed solution, with a reason — prevents the reviewer having to design an answer; this is what converts weeks into minutes.
5. Quantified impact and the date it applies to — prevents the date being treated as arbitrary, and creates the contemporaneous record of exposure.
6. Required response date — prevents "ASAP," which everyone has learned to ignore.

1. Resort the submittal log by required-on-site date and back-schedule the top forty items. Before anything else, because it is the only action that tells you which of the other problems is actually urgent. Expect to find items whose due dates have passed. That list is your agenda.

2. Walk the field office and the work faces, and fix the current set that day. Two versions of a partition plan taped up is a $340,282 exposure sitting in plain sight, and it is the only item on this list that can hurt you this week. Remove the superseded copy, verify the revision against the drawing log, and establish the layout-verification rule with the superintendent and the foremen.

3. Produce a ball-in-court report and publish it. Eleven minutes. It will almost certainly show that the largest bucket is "never submitted" — which is a subcontractor problem you own — and it converts 61 anonymous rows into a small number of phone calls with names attached.

4. Triage the 22 aged RFIs into three piles: answered-in-substance and closable, genuinely open and schedule-critical, and never should have been sent. Close the first pile, escalate the second in writing with a required response date and the specific impact, and withdraw the third — withdrawing bad RFIs is one of the fastest ways to restore a design team's attention.

5. Get the superintendent's private list and merge it. Do not do this first, and do not do it as a criticism. He built that list because the official one did not work; when the official one works, the private one disappears on its own. Merging it is also the cheapest audit available of what the log is missing.

What you tell the owner at the meeting: the facts, the actions, and the dates — not a reassurance. An owner who hears "we found three items past their submittal dates, here is what we are doing, here is when you will know more" trusts you considerably more than one who hears "we've got it under control."