NOTE This standard establishes the administrative framework that governs how the Contractor submits information for review and how quality is controlled and verified on the Work. (1.1)

NOTE It consolidates two closely related but distinct regimes into one anchor standard: the submittal workflow (how shop drawings, product data, samples, and other deliverables move through review) and the quality program (the contractor's quality-control plan plus independent testing and inspection). These are administered together but are not the same process, and this standard keeps them separate where they must be kept separate. (1.2)

NOTE The submittal and quality requirements stated here apply to the Work of every technical specification section in the project manual unless a technical section states a more specific requirement, in which case the more specific requirement governs. (1.3)

NOTE Statutory special inspections and structural testing mandated by the building code are administered under Special Inspections And Testing and are outside the scope of this standard. (1.6)

NOTE Functional performance testing of integrated building systems is administered under Commissioning and is outside the scope of this standard. (1.7)

NOTE The contract's general conditions are the operative authority for submittal and review obligations; the standards below supplement, but do not supersede, the executed contract. (2.3)

NOTE Submittals are the means by which the Contractor demonstrates, in advance of fabrication or installation, that the proposed products and methods conform to the contract documents. (3.1)

NOTE Under AIA A201-2017 §3.12, shop drawings, product data, and samples are not themselves contract documents; they are the Contractor's representation of how the contract will be satisfied, and review of them does not relieve the Contractor of responsibility for conformance. (3.2)

NOTE The Architect's review and approval of a submittal is for general conformance with the design intent only. (3.3)

NOTE Stating the limits of approval expressly in the specification prevents the recurring dispute in which a contractor treats an approval stamp as the Architect's verification of dimensions or quantities it never undertook to check. (3.5)

NOTE Every required submittal shall be classified as either an action submittal or an informational submittal. (3.7)

NOTE An action submittal requires the Architect's review and approval before the related Work may proceed; an informational submittal is provided for the record only and does not require approval. (3.8)

NOTE The single most common submittal dispute arises from blurring these two categories: a contractor proceeds on an item the Architect merely received for record, or waits for approval the Architect was never obligated to give. The specification must state which class each item falls into. (3.9)

NOTE The submittal types below cover the deliverables this standard governs; each technical section selects which apply to its Work. (3.14)

NOTE Shop drawings are Contractor-prepared drawings showing fabrication, assembly, connection, and installation detail for a specific element of the Work; they are an action submittal. (3.15)

NOTE Product data are the manufacturer's published technical data, performance characteristics, and installation instructions for a proposed product; they are an action submittal. (3.16)

NOTE Samples are physical specimens of a material, product, or finish submitted to confirm color, texture, pattern, and quality; they are an action submittal where exposed finishes, cladding, or millwork are involved. (3.17)

NOTE Delegated-design submittals are Contractor-furnished, professional-engineer-sealed calculations and drawings for systems the contract documents performance-specify rather than fully detail. (3.18)

NOTE Operation and maintenance (O&M) data are manufacturer manuals and maintenance schedules compiled into the project O&M manual; they are an informational submittal delivered at closeout. (3.19)

NOTE The submittal register is the master log that lists every required submittal by specification section, type, required submission date, and review status; it is the central control document for the entire submittal process. (3.26)

NOTE On most commercial projects the register is maintained in project-management software that links each item to the construction schedule and tracks review turnaround automatically. (3.27)

NOTE The submittal schedule embedded in the register sets when each submittal must be received so that review can be completed before the item is needed for fabrication or installation. (3.30)

NOTE A submittal schedule that is not coordinated with the construction schedule is the root of most submittal-driven delay claims: the submittal arrives too late for a full review cycle to close before the installation date, and the resulting compression is then blamed on the reviewer. (3.31)

NOTE Submittal lead time is inherently item-specific: the review-and-fabrication horizon for a stock lamp is nothing like that for a medium-voltage switchgear lineup, so no single figure can govern every product. The governing submission date for each item is the one fixed in the submittal schedule, which accounts for that item's own review cycle and fabrication lead time. The fields below set only the project-wide default minimum that applies to an item until the submittal schedule establishes a longer, item-specific date. (3.32)

NOTE AIA A201-2017 §4.2.7 obligates the Architect to review submittals "with reasonable promptness," but that phrase is not a schedulable duration; on any project with a meaningful submittal volume it must be replaced with a stated calendar-day count. (3.36)

NOTE Specifying a definite review period in calendar or business days is the single highest-value clarification in this section: it converts an open-ended contractual standard into a schedulable commitment for both parties and forecloses the chronic RFI traffic that "reasonable promptness" generates. (3.37)

NOTE Distinguishing the initial and resubmittal periods, and stating that incomplete submittals do not start the clock, prevents the two most common scheduling arguments at the review stage. (3.41)

NOTE Delegated design transfers responsibility for engineering a specified system from the design team to a professional engineer retained by the Contractor, typically for performance-specified systems such as cold-formed steel framing, pre-engineered components, and post-installed anchorage. (3.43)

NOTE The boundary between what is delegated and what the Engineer of Record (EOR) designs must be drawn explicitly, because an EOR cannot legally review, approve, or take responsibility for engineering outside the delegated scope, and an ambiguous boundary produces sealed submittals no one can properly act on. (3.44)

NOTE Quality assurance comprises the contractor quality-control (QC) plan and the independent testing and inspection program; together they verify, during construction, that the Work conforms before it is concealed or accepted. (4.1)

NOTE This standard's quality regime is distinct from the building code's special-inspection program. Where the IBC Chapter 17 program applies, the Statement of Special Inspections, the special inspector's qualifications, and the structural reporting chain are administered under Special Inspections And Testing, and the agency engaged for code special inspections is not interchangeable with the agency engaged for general quality testing unless the contract expressly authorizes one agency to perform both. (4.2)

NOTE Using a single agency for both general quality testing and statutory special inspection without express contract authorization creates code-compliance exposure, because the two roles carry different qualification, independence, and reporting obligations. (4.4)

NOTE The contractor QC plan is the Contractor's written description of how it will organize, execute, and document control of quality on the Work, including the personnel responsible, the inspection procedures, and the records to be kept. (4.6)

NOTE On federal and public projects the plan is mandatory and is typically structured on the USACE three-phase control model: a preparatory phase before each definable feature of work, an initial phase at the start of that work, and a follow-up phase of continuing checks. On VA and large healthcare projects the plan is often required to be ISO 9001-aligned. (4.7)

NOTE A QC requirement with no stated consequence for non-submission or non-compliance is unenforceable; the specification must tie the plan to a hold on the affected Work so the requirement has effect. (4.8)

NOTE Independent testing and inspection agencies provide the third-party verification — material sampling, laboratory testing, and field inspection — that the Contractor's own QC cannot impartially provide. (4.15)

NOTE Their competence is established by accreditation rather than assertion: ASTM E329-21 sets the personnel, equipment, and quality-system requirements for construction testing and inspection agencies, and ASTM D3740-19 does the same for soil and rock testing laboratories. Accreditation programs such as AASHTO (AAP), CCRL, AMRL, and IAS provide the independent confirmation that an agency meets those requirements. (4.16)

NOTE Whether the testing agency is engaged and paid by the Owner or by the Contractor must be stated, because an unstated arrangement leads contractors either to assume they bear no testing cost or to retain an unqualified low-bid laboratory. (4.17)

NOTE A pre-installation meeting convenes the parties responsible for a definable feature of work before it begins, to confirm that submittals are approved, conditions are ready, and the installation sequence is understood. (4.24)

NOTE Holding the meeting before work starts, rather than diagnosing problems after, is the cheapest quality control available on most assemblies, particularly those with multiple trades or critical interfaces. (4.25)

NOTE A field mock-up is a full-scale, in-place prototype of a critical assembly, built and reviewed before production work begins, so that workmanship, appearance, and performance can be approved against a physical benchmark rather than a drawing. (4.30)

NOTE Mock-ups are standard on curtain wall, precast, masonry, and storefront scopes, and the approved mock-up becomes the standard of acceptance for the balance of that work — see also Architectural Precast Concrete and Cast Stone. (4.31)

NOTE A mock-up loses its value the moment it is demolished, so the specification must state a retention period; otherwise the Contractor removes the mock-up to recover materials and the quality benchmark for the rest of the work disappears. (4.32)

NOTE Non-conforming work is any portion of the Work that does not comply with the contract documents, whether discovered by the Contractor's QC, an independent agency, or the design team. (5.1)

NOTE A defined non-conformance process — prompt written notice, a documented disposition decision, and a record of the resolution — keeps defects from being quietly concealed and gives the Owner a basis to choose among repair, replacement, or acceptance with a price adjustment. (5.2)

NOTE At closeout the submittal and quality records are assembled into the permanent project record that the Owner relies on to operate, maintain, and warrant the building. (6.1)

NOTE This standard governs only the submittal and quality records — the closed submittal register, test and inspection reports, the non-conformance log, and QC records. Assembly of the full O&M manual and record drawings is a separate Division 01 closeout function handled outside this standard. (6.2)