Document-Control Cue
Identity, issue, revision, and status verification for the current document.
Chapter 19
Extract one defined trade or work-package scope from the construction documents and produce a build-ready checklist with references, prerequisites, materials, interfaces, inspections, closeout, exclusions, and unresolved questions.
These cues appear at the point of use. They identify document-control, scope-boundary, cross-reference, code, and clarification issues before they become misread information in the field.
Identity, issue, revision, and status verification for the current document.
A misread of this information can cause unsafe, non-compliant, or costly field work.
Guidance for using the document set safely and correctly on site.
Verify adopted jurisdiction and permit status before relying on a code citation.
Never scale a reproduced, resized, or displayed drawing without verification.
Follow a reference to its destination and back to confirm coordination.
Stop and record a clarification item instead of guessing or choosing an answer.
This chapter qualifies you to convert a coordinated construction-document package into one build-ready trade-scope checklist for a single, clearly bounded work package. The finished work product is one source register, one chronological checklist organized from preconstruction through closeout, and one open-item list, all built from the current approved documents, the Chapter 17 conflict register, and the Chapter 18 field-markup set for one project.
You will select and bound one trade or work package, collect every governing reference, extract explicit scope items from plans, notes, schedules, details, and specifications, search related disciplines for supporting or interfering work, identify materials and prerequisites only as documented, identify testing and inspection checkpoints, and record every scope gap, unclear responsibility, or missing acceptance criterion as an unresolved question rather than an assumption.
This is the nineteenth chapter in the book. It depends directly on the conflict register produced in Chapter 17 and the field-markup set produced in Chapter 18, and it converts nineteen chapters of document interpretation into the single deliverable that Book 24 uses to begin quantity takeoff and estimating.
Every prior chapter in this book produced a discipline-specific interpretation: a foundation checklist, an opening schedule summary, a finish matrix, a fixture rough-in checklist, a device checklist, an HVAC layout checklist, a roof-scope checklist, an envelope-detail checklist, a specification summary, a cross-trade conflict register, and a field-markup set. This chapter is where those separate interpretations are pulled into one execution-ready document for a single work package.
Chapter 20 reuses this exact procedure, at full project scale, to produce the capstone's build-ready trade-scope package. Book 24 begins its quantity takeoff and estimating work directly from the checklist produced here, using the materials identified in this chapter as the starting point for quantities.
This chapter covers:
This chapter does not authorize the learner to:
Any scope item, material, prerequisite, or acceptance criterion that cannot be resolved during this chapter must be recorded on the open-item list rather than assumed.
Establish these definitions before beginning the checklist, and apply them consistently across every scope item.
| Term | Definition |
|---|---|
| Work package | The approved trade or defined scope of work whose physical, contractual, and document boundaries are established before extraction begins |
| Explicit scope item | A requirement stated directly by a plan note, schedule entry, detail, or specification section that governs the work package |
| Supporting scope | Work from a related discipline that must occur before, during, or after the work package to allow it to proceed or be accepted |
| Prerequisite | A condition, approval, or completed item of work that must exist before the work package may begin |
| Hold point | A stage in the work package that requires inspection, testing, or approval before the next stage may proceed |
| Build-ready checklist | The finished, source-referenced, chronologically organized checklist covering procurement through closeout for the work package |
| Open item | An unresolved scope gap, missing material, unclear responsibility, or incomplete acceptance criterion recorded rather than assumed |
Before extracting scope, record the following directly on the document-control log:
Project name: ______________________ Selected work package: ______________________
Physical boundary: ______________________ Contractual boundary: ______________________
Document issue / revision used: ______________________ Conflict register version incorporated: ______________________
Field-markup set version incorporated: ____________ Extracted by: ____________ Date: ____________
Every checklist in this chapter is built by finding explicit scope, searching related disciplines for supporting or interfering work, separating documented fact from means-and-methods judgment, and recording anything that cannot be resolved as an open item. Applying that discipline consistently across procurement, pre-installation, installation, inspection, correction, and closeout is what makes the checklist build-ready rather than a partial summary.
Documents define required results: a wall type, a rated assembly, a rough-in location, a finish, a slope, a clearance. They do not always specify the contractor's complete method of achieving that result. This chapter extracts the required results and the explicitly stated execution requirements. It does not convert the contractor's chosen method into a design requirement unless the documents themselves require that method.
A plumbing fixture shown on an architectural plan does not by itself establish which trade installs it, which trade furnishes it, or which trade connects it. Use the project scope documents, specifications, division responsibilities, contracts, and the approved coordination process to assign responsibility. Where the scope documents are silent, record the ambiguity as an open item rather than assigning responsibility from the sheet it happens to appear on.
Record any scope item with no stated material, no stated acceptance criterion, no stated responsible party where the documents should establish one, or no stated inspection requirement as an open item. Do not fill the gap with typical practice, and do not assume a value used on a different project.
A work package's scope is rarely confined to one discipline's sheets. Before closing the extraction step for any area, confirm that architectural, structural, plumbing, mechanical, electrical, and specialty documents have all been checked for requirements that touch the same location, assembly, or component.
Pull open items from the Chapter 17 conflict register and current field information from the Chapter 18 markup set, but incorporate only items that are approved and distributed through document control. An unanswered RFI stays an open item on this checklist; it does not become an assumed field direction.
BP-109 – BP-114
Scope-Extraction / Build-Readiness Qualification
Deliverable set: one work-package boundary statement; one source register listing every governing reference and its revision; one build-ready checklist organized chronologically from preconstruction through closeout with source references, prerequisites, materials, interfaces, and inspections attached to every item; and one open-item list consolidating every scope gap, missing material, unclear responsibility, or incomplete acceptance criterion found during extraction.
| Component | Quantity | Source | Required Fields | Preparation / Purpose |
|---|---|---|---|---|
| Work-package boundary statement | 1 | Approved scope documents, contracts, division responsibilities | Physical boundary, contractual boundary, included and excluded work | Establishes the exact extent the checklist must cover |
| Source register | 1 | Every governing sheet, detail, schedule, specification, submittal, RFI, and addendum | Document type, number, title, revision, relevance to the package | Confirms every reference used in the checklist is current |
| Build-ready checklist | 1 | Extracted scope items organized chronologically | Item, source reference, responsible party if established, prerequisite, acceptance criterion, status | The primary execution-ready deliverable |
| Interface and prerequisite map | 1 | Related-discipline scope affecting the package | Interface location, adjacent trade, dependency, sequencing note | Shows where the work package depends on or affects other trades |
| Open-item list | 1 | Discrepancies and gaps found while extracting scope | Item, description, affected location, requested action, required-by date | Records unresolved items for the document-control and RFI process |
| Check | Standard |
|---|---|
| Boundary clarity | The work-package boundary statement identifies exactly what is included and excluded, with no scope item extracted that falls outside the stated boundary |
| Source completeness | Every checklist item traces to a specific sheet, detail, schedule, specification section, submittal, or RFI recorded in the source register |
| Cross-discipline coverage | Architectural, structural, and every MEP or specialty discipline touching the package has been searched for supporting or interfering scope |
| Chronological organization | The checklist is organized in field sequence from preconstruction through closeout, not grouped only by discipline or sheet |
| Conflict and markup incorporation | Every open item from the Chapter 17 register affecting this package appears on the checklist or the open-item list, and only approved Chapter 18 markup information is incorporated |
| Open-item capture | Every scope gap, missing material specification, unclear responsibility, or incomplete acceptance criterion is recorded, not silently resolved |
Inspect the finished checklist using the same checks regardless of which trade or work package is involved.
Complete the Build-Readiness Worksheet in the Inspection Checklist section below before issuing the checklist through document control.
Probable cause: the physical or contractual boundary was not clearly defined before extraction began, or extraction drifted into an adjacent trade's scope.
Confirmation: compare every checklist item against the Work Package Identity Record's stated boundary.
Correction: remove out-of-boundary items and, if they represent a genuine interface, move them to the interface and prerequisite map instead of the checklist body.
Reinspection: repeat the boundary check across the full checklist.
Probable cause: the item was extracted from memory of a similar project, or from a discussion that was never incorporated into an approved document.
Confirmation: search the source register for a matching sheet, detail, schedule, specification, submittal, or RFI.
Correction: if no source exists, remove the item from the checklist body and record it on the open-item list as a missing requirement requiring clarification.
Reinspection: repeat the source check on the corrected checklist.
Probable cause: extraction was limited to the discipline matching the work package's name rather than searching every discipline touching the same location.
Confirmation: reopen the architectural, structural, and every MEP or specialty sheet covering the work-package boundary and check for unextracted requirements.
Correction: add the missed requirement to the checklist with its source reference, or to the open-item list if it conflicts with an existing item.
Reinspection: repeat the coverage check across every discipline in the source register.
Probable cause: the conflict register was reviewed before its most recent update, or the conflict's affected location was not cross-checked against the work-package boundary.
Confirmation: compare the current conflict register against every checklist item touching the same location, assembly, or trade.
Correction: incorporate the approved response into the checklist, or add the open conflict to the open-item list if it remains unresolved.
Reinspection: repeat the coordination check once the conflict register is current.
Probable cause: a typical or convenient installation method was recorded as if the documents required it, when the documents actually left the method to the contractor.
Confirmation: trace the item back to its source reference and confirm whether the document states a required result or a required method.
Correction: revise the item to state only the documented required result; remove the assumed method.
Reinspection: repeat the source check on the corrected item.
This chapter ends with one issued, source-referenced checklist ready for build use, not a partial extraction.
| Competency | Independent Pass Standard | Not Demonstrated | With Assistance | Independently |
|---|---|---|---|---|
| BP-109 | Correctly extracts explicit scope items for the defined work package from plans, notes, schedules, details, and specifications, with a source reference for each | |||
| BP-110 | Organizes every extracted scope item by trade and by chronological field sequence from preconstruction through closeout | |||
| BP-111 | Identifies required materials, products, and accessories only as documented, and correctly distinguishes them from quantities reserved for Book 24 takeoff | |||
| BP-112 | Identifies every testing, inspection, special-inspection, and manufacturer-review checkpoint controlling the work package | |||
| BP-113 | Identifies unanswered questions, scope gaps, and responsibility ambiguities and converts each into a neutral RFI-style question | |||
| BP-114 | Produces a complete build-ready scope checklist with source references, prerequisites, interfaces, inspections, closeout requirements, and visible open items |
Mark one column per competency. Only Demonstrated Independently awards the competency; Demonstrated with Assistance authorizes additional supervised practice but does not complete the requirement.
| Deliverable | Status | Items Logged | Verified By | Date | Notes |
|---|---|---|---|---|---|
| Work-package boundary statement | |||||
| Source register | |||||
| Build-ready checklist | |||||
| Interface and prerequisite map | |||||
| Open-item list |
Total checklist items: ____________ Total source documents registered: ____________ Open items logged: ____________
Checklist declared build-ready: ______ (Pass/Fail) Date: ____________ Reviewer name: ____________
With all five deliverable components complete, review the finished trade-scope checklist package against the Acceptance Standards table and confirm every checklist item falls within the approved work-package boundary, every item carries a specific and current source reference, every related discipline was searched for supporting or interfering scope, the checklist is organized chronologically from preconstruction through closeout, every applicable Chapter 17 conflict and approved Chapter 18 markup item has been incorporated or logged, and every scope gap, missing material, or responsibility ambiguity has been recorded rather than assumed. Complete the Build-Readiness Worksheet and route any unresolved item through the project's document-control and RFI process before issuing the checklist.
You have completed the nineteenth chapter in the blueprint-reading sequence: building a trade scope checklist from construction documents. This chapter required you to extract explicit scope items for a defined work package (BP-109), organize those items by trade and chronological field sequence (BP-110), identify required materials only as documented (BP-111), identify testing and inspection checkpoints (BP-112), identify unanswered questions and convert them into neutral RFI-style questions (BP-113), and produce a complete build-ready scope checklist with source references, prerequisites, interfaces, inspections, closeout requirements, and visible open items (BP-114).
You now have a source register, a chronologically organized build-ready checklist, an interface and prerequisite map, and an open-item list for one work package on one project. That checklist carries directly into the next chapter: the complete residential capstone, where this same extraction procedure is applied at full project scale.
Retain your completed checklist package. You will reuse this exact extraction discipline, at full project scale, for the capstone trade-scope deliverable in Chapter 20.