Chapter 25 — Further Reading

This chapter's reading list is different from the others in this book, and it is worth saying why.

There is no standard for submittals. There is no code section that tells you how to write an RFI. The discipline in this chapter is almost entirely governed by your contract, your project manual, and your own procedure — which is why the single most valuable hour of reading available to you is not a book at all. It is the general conditions of the contract you are working under, read slowly, with a pen, looking specifically for the submittal certification, the review-limitation language, the notice periods, and the list of instruments authorized to change the work.

Everything below either helps you read that document better or helps you build the procedure it assumes you have. Where I am not certain of an exact title, form number, edition, or section, I describe the source rather than invent a citation, and you should hold every other author to the same standard. Contract forms are revised on cycles of roughly a decade, and the provisions in this chapter have moved between editions — always work from the edition your contract actually incorporates, not the one you learned.

How the documents are organized

1. The Construction Specifications Institute (CSI) — MasterFormat, SectionFormat and PageFormat, UniFormat, and the Project Resource Manual. MasterFormat is the numbering system that organizes the project manual by division and section. SectionFormat is the one that builds your log. It defines the three-part structure inside every technical specification section, and it puts the submittal requirements in a specific, findable place: Part 1 — General, in the "Submittals" article, with "Quality Assurance" immediately alongside it. That article is the source of every row in your submittal register. Part 3 carries field quality control. UniFormat organizes by building system rather than by trade and is what conceptual estimates and early coordination documents use.

Once you know that structure, building a submittal log stops being an act of imagination: open every section, read Part 1, write down what it requires, and then — this chapter's entire argument — go put a date next to each one. CSI's Certified Construction Documents Technologist (CDT) credential is built on exactly this material, and it is the single most useful early-career credential I know of for a project engineer or a young PM. For: anyone building the Willow Street log in the Project Checkpoint. See also Chapter 7.

The contract families, described by function

You do not need to memorize form numbers. You need to know that several complete, internally consistent families exist, that they allocate the responsibilities in this chapter differently, and that the family your project uses determines what "the review period" and "notice" actually mean.

2. The AIA contract documents family. The most widely used family on U.S. building work. It consists of matched owner–contractor agreements for the common delivery and pricing arrangements (stipulated sum, cost of the work with a guaranteed maximum price, construction manager as constructor), a general conditions document that the agreements incorporate — this is where the substance of this chapter lives — matched owner–architect and contractor–subcontractor agreements, and a family of administrative forms: transmittals, requests for information, architect's supplemental instructions, construction change directives, change orders, and the application-and-certificate-for-payment pair (G702 and G703).

Read the general conditions specifically for: the contractor's certification made by submitting (that you have reviewed, verified field measurements and criteria, and coordinated), the limitation on the design professional's review, the treatment of deviations and what is required to obtain approval of one, the review period and how it is measured, the definition and authority of the various change instruments, and the notice obligations and their time limits. Note the structural feature that surprises people most often: the general conditions and the agreement are separate documents, and supplementary conditions edit both — so the clause you are relying on may have been rewritten in a document you have not opened. For: everyone on a private building project. Do not quote it from memory; open it.

3. ConsensusDocs. A family drafted by a coalition of industry associations representing owners, contractors, subcontractors, suppliers, and sureties — rather than by a single professional body — and its orientation shows. It is generally regarded as more balanced toward the construction side and more explicit about collaborative processes, and it treats several of this chapter's mechanisms (information flow, notice, and the resolution of disputes at the project level before they escalate) somewhat differently in emphasis. Reading a ConsensusDocs general conditions article next to the AIA equivalent, on the same subject, is genuinely the fastest way to understand what is a convention and what is a choice. For: anyone who wants to see that the allocation they think is "how it works" is actually a drafting decision somebody made.

4. EJCDC — the Engineers Joint Contract Documents Committee family. Developed by the engineering professional societies, and the family you will meet on water, wastewater, utility, and much heavy civil and public infrastructure work. Its shop drawing and sample provisions are unusually explicit about the contractor's review obligation before submission, which makes them useful reading even if your project uses a different family. For: readers heading toward infrastructure work. Pairs with Chapter 38.

5. FIDIC. The international family, used on cross-border and multilateral-development-bank-financed work, with its own vocabulary (the Engineer, notices, determinations) and its own approach to claims and time bars — which are typically strict and, unlike much U.S. practice, apply symmetrically. For: readers working internationally, and for anyone who wants to see how differently "notice" can be treated.

6. Your jurisdiction's building department, on construction documents and deferred submittals. The model building codes contain provisions for deferred submittals — portions of the design not submitted at permit issuance, submitted later for review — including who must review them before they reach the building official. Whether a given component may be deferred at all, and how long review takes, varies by jurisdiction and by building official. This is the step people leave out of the back-schedule in §25.6, and it is the one you cannot escalate with a phone call. Ask in the preconstruction meeting; write down the answer; put a duration in the chain. For: anyone with delegated design on the job — which is everyone.

Records, claims, and what evidence actually looks like

7. AACE International — recommended practices on forensic schedule analysis and on the documentation required to support a claim. AACE publishes a family of recommended practices that is the closest thing this industry has to a methodological standard for analyzing delay and disruption. Read them here not for the schedule methods — those belong to Chapter 33 — but for what they say about records: which contemporaneous documents each analysis method requires, and what an analyst can and cannot do when those documents do not exist. It is the most direct answer available to the question "what should I have been keeping?", written by the people who later have to work with whatever you kept. For: anyone who wants a checklist derived from the far end of the process.

8. The Society of Construction Law Delay and Disruption Protocol. A widely referenced, freely available, internationally oriented framework covering delay and disruption analysis. Its treatment of the hierarchy of evidence — why records made at the time outrank reconstructions, and how tribunals actually weigh them — is the best plain-language statement I know of the threshold concept in §25.9. It is also refreshingly candid about the limits of after-the-fact analysis. For: a rigorous second opinion, and for the argument you will one day need to make to a project executive who thinks documentation is overhead.

9. The American Bar Association's Forum on Construction Law, and the construction practice literature generally. The construction bar publishes continuously on notice provisions, waiver, course of dealing, the effect of RFI responses, and the treatment of electronic records and text messages in construction disputes — much of it written for practitioners rather than for other lawyers, and much of it available through free articles, webinars, and conference materials. This is where you go when you want to know how a court has actually treated a fact pattern, rather than how a textbook says it should be treated. It is also where you will find the standing reminder that notice provisions, waiver doctrine, and limitation periods vary substantially by state. For: the PM who wants to understand why §25.10 says what it says about writing legal conclusions.

10. Your company's counsel and your jurisdiction's statutes — on records retention. There is no single answer, and I refused to give you a number in the chapter for a reason. Retention is driven by at least four clocks running at once: your contract's own record-retention and audit provisions (particularly on cost-reimbursable and GMP work), your jurisdiction's statute of limitations for contract and construction claims, its statute of repose — a separate, generally longer outer limit measured from completion rather than discovery — and regulatory requirements including OSHA recordkeeping, certified payroll on prevailing-wage work, environmental and stormwater records, and tax records. All of these vary by state, some vary by project type and funding source, and they change. Get the number from counsel, put it in the document-control procedure at the start of the job, and follow it. The general shape of the answer is longer than you think, measured in years, measured from completion. For: the last section of your document-control procedure.

The tools

11. The cloud construction document platforms — evaluated as a category. The category is mature and the products are genuinely good. What they solve is real: one served current set; automatic timestamped transmittals with a download audit trail; aging and ball-in-court reports generated rather than maintained; rules-based distribution that enforces your matrix; the current sheet on a tablet at the work face, which is where the superseded-sheet failure actually happens; linking of RFI to drawing to submittal to change order to schedule activity; and a searchable archive, which is the difference between assembling a claim in three days and three weeks.

How to learn one without buying it: every major vendor in this category runs a free training and certification academy, publishes extensive documentation, and offers trial or student access. Pick one, complete the submittal and RFI modules, and build the Willow Street log inside it. That is a weekend, and it is a line on a résumé that hiring managers actually recognize.

And the warning, restated because it matters more than the feature list: a platform does not create discipline. It makes the absence of discipline visible faster. A log sorted by specification section becomes a beautifully rendered, mobile-accessible, permission-controlled log sorted by specification section. Choose the tool second and the procedure first. For: everyone. Nobody should reach a first PM role without having driven one of these. Software is also surveyed in Appendix H.

12. The model-coordination standards: the BIM Forum's Level of Development specification, and the National BIM Standard published through the National Institute of Building Sciences. Increasingly, shop drawings are models, submittals are model deliverables, and the interface conflicts that generate resubmittals are found — or missed — in coordination rather than in review. The LOD specification gives the industry's common vocabulary for how developed a model element is and who is responsible for it at each stage, which is precisely the language you need to close the "by others" gap that cost the curtain wall nine weeks. For: anyone whose project has a BIM execution plan. See Chapter 35.

13. Your own project manual, your own general conditions, and your own submittal register. Not a filler entry. Before you read anything else on this list: open the project manual, pick three specification sections at random, read the Part 1 "Submittals" article in each, and check whether every item it requires appears in your register with a date. On most jobs, on most days, the answer is no — and finding that out costs you twenty minutes. For: you, today.

Inside this book

• Chapter 7 — drawings, specifications, order of precedence, and the $340,282 superseded-sheet failure in detail.
• Chapter 14 — the CPM schedule the required-on-site dates come from.
• Chapter 16 — long-lead back-scheduling, award-by dates, and the scope gaps that live between subcontracts.
• Chapter 22 and Chapter 24 — safety-critical delegated design, and why no component gets loaded before the sealed approval is on site.
• Chapter 23 — the submittal-to-installation chain, and the one log column that closes it.
• Chapter 26 — the daily report, and the meeting record as the other half of the project's memory.
• Chapter 31 — what to do the moment an RFI response changes the contract.
• Chapter 33 — entitlement, causation, and damages, and what your records have to prove.
• Appendix D — submittal register, RFI form, transmittal, and the distribution matrix.
• Appendix G — the clauses behind the review period, the notice provision, and the change instruments.
• Appendix K — the project package for the Willow Street submittal log and RFIs.

A note on jurisdiction and currency. Notice periods, the enforceability of no-damages-for-delay and waiver provisions, what constitutes authority to direct a change, deferred-submittal procedures, and record-retention obligations all vary by state, by owner, and by project type, and public work is routinely stricter and less forgiving than private work. Contract forms are revised, and provisions in this chapter have genuinely moved between editions. Nothing here is legal advice: the framework is above, the specifics belong to your contract and your attorney, and the cheapest time to ask is the week you sign — not the week you file.