Chapter 26 — Further Reading

Ten pointers. Everything here is either a primary source you can verify yourself or the published guidance of a well-established institution. Where I am not certain of an exact document number or title, I describe the source rather than invent a citation — go to the organization's own site and search from there.

A standing warning for this chapter's subject matter. Whether meeting minutes are deemed accepted after a stated period, whether a confirming letter satisfies a contractual notice requirement, how long you must retain project records, what a personal field diary is and is not, and how any tribunal weighs a contemporaneous record all vary by contract, by jurisdiction, and by forum, and they change over time. Nothing below is legal advice, and neither is anything in the chapter. The framework is mine to teach; the answer for your project belongs to your contract and your attorney.

1. Your own contract — the general conditions and Division 01

Why: This is by a wide margin the most valuable reading on the list, it is free, and almost nobody does it. Find and read, in the documents governing the job you are on right now: the progress-meeting requirement (frequency, who must attend, who records and distributes minutes); any provision governing minutes and objections to them, and the exact number of days; the changes clause and the two written instruments it recognizes — a mutually executed change order and a unilateral directive; the notice provision, including how many days, to whom, and by what method of delivery; and the record-keeping and audit articles, which frequently prescribe what daily records you must keep and what the owner may inspect.

For whom: Every project engineer, in week one of a new job. Extract the deadlines onto one page and put it on the trailer wall. One hour of reading in month one beats one deposition in month twenty.

2. The published standard contract families — AIA, ConsensusDocs, and EJCDC

Why: The AIA's A201 general conditions, the ConsensusDocs family, and EJCDC's documents are the three most widely used published contract families in United States building and engineering work, and each publishes its own general conditions plus a set of administrative forms — applications for payment, change orders, change directives, and certificates. Reading two of them side by side is the fastest way to learn what the differences between contracts actually do, particularly on changes, directives, notice, and the contractor's record-keeping obligations. Read them for structure and function; do not quote the text, and do not assume that the form your company uses says what the published form says — most large contractors and most public owners write their own.

For whom: Anyone who has read only one contract and is starting to believe all contracts say roughly the same thing. They do not.

3. CSI MasterFormat and the Division 01 general-requirements sections

Why: §26.2 argues that some of your meetings are contractually required and most people never check. The requirement usually lives in Division 01 — in the "Administrative Requirements," "Project Management and Coordination," and "Quality Requirements" sections — and in individual technical specification sections that mandate a pre-installation conference before that scope may begin. The Construction Specifications Institute is the body behind MasterFormat and publishes practice guidance on how project documentation and specifications are organized and used.

For whom: Project engineers building a meeting calendar and a submittal log. Read your project manual's Division 01 before you build either one, and list every pre-installation conference the specifications require — expect twenty to forty on a mid-size commercial job.

Why: This chapter argues that a daily report's impact statements are the atomic units from which a disruption or delay claim is later assembled. AACE's recommended practices are where you find out what the people who will eventually analyze your records are actually looking for — how delay is analyzed rigorously, what a defensible as-built record consists of, and which methods for estimating lost productivity are considered reliable and which are not. Read them before you design your daily report form, not after you need one.

For whom: Anyone who will ever price, defend, or attack a delay or disruption claim, and every superintendent who thinks the daily report is paperwork. Described, not quoted — go to AACE for the current versions.

5. The Society of Construction Law Delay and Disruption Protocol

Why: A widely used international framework for analyzing delay and disruption, notable for being explicit about the value of contemporaneous records and about how records should be kept during the works rather than reconstructed afterward. It is a second, independently developed view of the same problem AACE addresses, which makes it useful precisely because it does not always agree.

For whom: Readers working outside the United States, and anyone who wants to test this chapter's claims against a framework written by a different community.

6. The Associated General Contractors of America (AGC) and the Construction Management Association of America (CMAA)

Why: AGC publishes practical guidance on project administration and documentation written by contractors for contractors, and its local chapters run most of the training where working project managers actually learn this material. CMAA publishes standards of practice defining the construction manager's role — including the CM's responsibilities for meetings, reporting, and the project record — and is the professional home of the owner's-representative side of the table this chapter keeps describing from the outside.

For whom: AGC for project engineers moving into management. CMAA for anyone working for or against an owner's rep, and anyone pursuing certification — see Chapter 42.

7. Public-agency construction manuals and standard daily report forms — your state DOT and the U.S. Army Corps of Engineers

Why: State departments of transportation publish construction manuals and standard inspector's daily record forms, and the Corps of Engineers requires contractors to maintain a daily quality control report under its contractor quality control requirements. These are the most rigorously specified daily reports in general circulation, they are free, and they exist because these owners have litigated a great many claims and learned exactly which fields decide them. Compare three of them against §26.6.1 and note what each includes that the others do not — particularly whether any of them has a genuine impact-statement field or merely a "remarks" box.

For whom: Anyone designing or defending a daily report form. Also the fastest way to see what an owner will expect on public work — including the Willow Street Community Center.

8. OSHA's construction standards (29 CFR Part 1926) and its injury and illness recording and reporting rule (29 CFR Part 1904)

Why: Part 1926 is the substance of construction safety regulation in the United States and is available in full at no cost. Part 1904 is a different animal and worth understanding separately: it governs which injuries and illnesses must be recorded and which events must be reported, and it is the source of the recordable-incident numbers everyone quotes. Read it for what it does not require — near-misses are generally not federally recordable, which is precisely why capturing them is a voluntary discipline that lives or dies on your daily report. OSHA also publishes voluntary recommended practices for safety and health programs that discuss leading versus lagging indicators.

For whom: Every superintendent and safety lead. Read the actual rule text on OSHA's own site rather than a summary; requirements for reporting serious events are time-limited and specific, and some states operate their own OSHA-approved plans with additional requirements.

9. Your attorney, once, on three specific questions — plus your company's document-retention and legal-hold policy

Why: This chapter deliberately stops short of legal conclusions in four places, and each of them has a real answer that depends on your jurisdiction, your contract, and your company's own policy. Ask, once, early in your career, and then stop guessing: (a) does a confirming letter satisfy the notice requirement in our standard contracts, or is it only the first step; (b) what is our document-retention schedule and what triggers a legal hold; (c) what is our policy on text messages and personal devices, and what can be required of an employee's own phone; and (d) what is the practical status of a superintendent's personal field diary here. The underlying reason contemporaneous records carry weight is not a technicality — U.S. evidence law has long recognized an exception for records of a regularly conducted activity, made at or near the time of the event by someone with knowledge, in the ordinary course of business, which is exactly the description of a well-kept daily report. How that principle is applied is a question for counsel and varies by forum.

For whom: Everyone, once. It is a thirty-minute conversation that changes how you write for the rest of your career.

10. Engineering News-Record (ENR), and any published construction dispute or claim narrative you can get your hands on

Why: ENR covers disputes, defaults, and claims as they happen, and reading about other people's document failures is the cheapest education available. Better still, if your company or a professional association will let you, read an actual claim submission or an expert's delay report end to end — a real one, with the exhibits. You will notice within twenty pages that the persuasive parts are almost never the argument. They are the daily reports, the ticket signatures, the timestamped photographs, and the letters somebody wrote on the day it happened, and the weak parts are always the months where somebody wrote "waiting on RFI."

For whom: Anyone who needs to be convinced that the half-page in §26.6.2 is worth ninety seconds a day. Nothing in this chapter persuades as effectively as one afternoon with a real claim binder.