{"id":72,"date":"2026-08-10T12:25:45","date_gmt":"2026-08-10T12:25:45","guid":{"rendered":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/?p=72"},"modified":"2026-08-10T12:25:47","modified_gmt":"2026-08-10T12:25:47","slug":"construction-submittal-log-checklist","status":"publish","type":"post","link":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/submittal-management\/construction-submittal-log-checklist\/","title":{"rendered":"Construction Submittal Log Checklist"},"content":{"rendered":"\n

There are two ways a submittal log fails, and they need different checklists.<\/p>\n\n\n\n

The first failure is structural. The log itself is wrong: requirements missing from the register, no need dates, no lead times, numbering that cannot be audited against the specifications. A structurally broken log runs smoothly and produces bad outcomes, because every notification fires correctly about an incomplete list.<\/p>\n\n\n\n

The second failure is transactional. The log is fine and individual submittals move through it badly: incomplete packages forwarded, deviations unnoticed, review cycles consumed by avoidable rejections, approvals filed without reading the notes.<\/p>\n\n\n\n

Most guidance on submittal management addresses the second and ignores the first, which is backward. A structurally sound log with sloppy transactions loses days. A structurally broken log loses months, and it loses them invisibly, because nothing in the process ever reports on a requirement that was never entered.<\/p>\n\n\n\n

This checklist covers both. Parts A through C audit the log as an instrument. Parts D through F screen and manage individual submittals. Parts G and H handle closeout and log health. Run A through C once per project at setup and again at roughly the halfway point. Run D through F continuously.<\/p>\n\n\n\n

How to Use This Checklist<\/strong><\/h2>\n\n\n\n

Audit the log before trusting it.<\/strong> Parts A through C take about a day on a live project and they determine whether anything downstream means what it appears to mean.<\/p>\n\n\n\n

Every check gets a disposition.<\/strong> Four outcomes: compliant, corrected, not applicable with a stated reason, or accepted risk with a named approver. A checkmark records that somebody looked.<\/p>\n\n\n\n

Part D is the daily instrument.<\/strong> It is written to be run per submittal at intake, in ten to twenty minutes, by whoever screens submissions. The type-specific blocks matter, because screening a shop drawing and screening a test report are different exercises.<\/p>\n\n\n\n

Assign Part C to someone who can read a schedule.<\/strong> The backward calculation is the highest-value part of this checklist and it requires access to the construction schedule and current lead times, which the person managing submittal paperwork often does not have.<\/p>\n\n\n\n

Table 1. Checklist Parts and Cadence<\/strong><\/p>\n\n\n\n

Part<\/strong><\/th>Target<\/strong><\/th>When<\/strong><\/th>Duration<\/strong><\/th>Owner<\/strong><\/th><\/tr><\/thead>
A, Register completeness<\/strong><\/td>The register against the specifications<\/td>Setup, and at 50 percent<\/td>4 to 8 hours<\/td>Project engineer<\/td><\/tr>
B, Log structure and fields<\/strong><\/td>The log as an instrument<\/td>Setup<\/td>1 hour<\/td>Project engineer<\/td><\/tr>
C, Backward schedule<\/strong><\/td>Scheduling adequacy per item<\/td>Setup, before buyout sequencing is fixed<\/td>4 to 8 hours<\/td>Project manager with scheduler<\/td><\/tr>
D, Intake screening<\/strong><\/td>Each individual submittal<\/td>Continuous, per submission<\/td>10 to 20 minutes each<\/td>Project engineer<\/td><\/tr>
E, Review cycle management<\/strong><\/td>Open items in aggregate<\/td>Weekly<\/td>30 minutes<\/td>Project engineer<\/td><\/tr>
F, Disposition and release<\/strong><\/td>Each returned submittal<\/td>Continuous, per return<\/td>5 to 10 minutes each<\/td>Project engineer<\/td><\/tr>
G, Closeout submittals<\/strong><\/td>Closeout register<\/td>Monthly from 75 percent<\/td>1 hour<\/td>Project engineer<\/td><\/tr>
H, Log health metrics<\/strong><\/td>The process<\/td>Monthly<\/td>30 minutes<\/td>Project manager<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
FIELD REALITY<\/strong>
The part that gets skipped is C, and it gets skipped because the person maintaining the log usually cannot run it. Backward scheduling needs the construction schedule, current supplier lead times, and authority to influence buyout order. Assign it explicitly to someone who has all three, or it will not happen on any project.<\/th><\/tr><\/thead><\/table><\/figure>\n\n\n\n

Key Definitions<\/strong><\/h2>\n\n\n\n

Register.<\/strong> The list of required submittals extracted from the contract documents. The log is the register plus tracking data.<\/p>\n\n\n\n

Action submittal.<\/strong> Requires design team approval before work proceeds. Informational submittal.<\/strong> Provided for record only.<\/p>\n\n\n\n

Required on site.<\/strong> The date material must arrive to support installation without delaying the schedule. Comes from the construction schedule, not from a subcontractor estimate.<\/p>\n\n\n\n

Float to need.<\/strong> Working days between projected approval and the latest approval date that avoids delaying installation. The single most useful derived field in a log.<\/p>\n\n\n\n

Ball in court.<\/strong> Which party owes the next action.<\/p>\n\n\n\n

Deviation.<\/strong> Any departure in a submittal from the specified requirement, whether or not the submitter identified it.<\/p>\n\n\n\n

Contractor return.<\/strong> A submission returned at intake without going to the design team. Should not consume a revision number.<\/p>\n\n\n\n

First-pass approval rate.<\/strong> Items approved on the first design team review divided by items reviewed. The most improvable metric in submittal management.<\/p>\n\n\n\n

Objectives<\/strong><\/h2>\n\n\n\n
    \n
  • Verify the register is complete against the actual project manual rather than a template<\/li>\n\n\n\n
  • Confirm the log carries the fields required to schedule rather than merely to report<\/li>\n\n\n\n
  • Ensure every long-lead item has been scheduled backward from its need date<\/li>\n\n\n\n
  • Screen submissions so review cycles are not consumed by avoidable rejections<\/li>\n\n\n\n
  • Catch deviations before they are approved by inattention<\/li>\n\n\n\n
  • Prevent the closeout submittal crunch<\/li>\n\n\n\n
  • Produce metrics that indicate health before failure<\/li>\n<\/ul>\n\n\n\n

    Part A: Register Completeness Audit<\/strong><\/h2>\n\n\n\n

    The unrecoverable failure. A requirement never entered is invisible until somebody asks for the document, which on closeout items means the final week.<\/p>\n\n\n\n

    Audit by source location rather than by section, because the missing items cluster by where they are stated rather than by which trade owns them.<\/p>\n\n\n\n

    Table 2. Register Completeness Checks by Source<\/strong><\/p>\n\n\n\n

    #<\/strong><\/th>Source Location<\/strong><\/th>Check<\/strong><\/th>Typically Missing<\/strong><\/th><\/tr><\/thead>
    A.1<\/strong><\/td>Part 1 submittals article, every section<\/td>Every listed item appears in the register<\/td>Rarely missing; this is the article everyone reads<\/td><\/tr>
    A.2<\/strong><\/td>Part 1 quality assurance article<\/td>Installer and manufacturer qualifications, mockups, preconstruction test reports, field samples<\/td>Very frequently missing<\/td><\/tr>
    A.3<\/strong><\/td>Part 1 closeout submittals article<\/td>Warranties, record documents, maintenance data where listed separately<\/td>Very frequently missing<\/td><\/tr>
    A.4<\/strong><\/td>Part 2 source quality control<\/td>Factory test reports, certifications, source inspection records<\/td>Frequently missing<\/td><\/tr>
    A.5<\/strong><\/td>Part 3 field quality control<\/td>Field test reports, startup reports, inspection records, balancing reports<\/td>Frequently missing<\/td><\/tr>
    A.6<\/strong><\/td>Division 01 submittal procedures<\/td>Schedule of values, submittal schedule itself, construction schedule submissions<\/td>Sometimes missing<\/td><\/tr>
    A.7<\/strong><\/td>Division 01 quality requirements<\/td>Testing agency qualifications, special inspection coordination, mockup requirements<\/td>Frequently missing<\/td><\/tr>
    A.8<\/strong><\/td>Division 01 closeout procedures<\/td>Record drawings, final cleaning certification, punch procedures<\/td>Frequently missing<\/td><\/tr>
    A.9<\/strong><\/td>Division 01 O&M data<\/td>Manual format, quantity, content requirements per trade<\/td>Frequently missing<\/td><\/tr>
    A.10<\/strong><\/td>Division 01 demonstration and training<\/td>Training plans, session records, recordings<\/td>Very frequently missing<\/td><\/tr>
    A.11<\/strong><\/td>Division 01 commissioning<\/td>Pre-functional checklists, functional test procedures, seasonal test documentation per trade<\/td>Very frequently missing<\/td><\/tr>
    A.12<\/strong><\/td>Delegated design triggers, all divisions<\/td>Sealed calculations, sealed drawings, deferred submittal packages to the AHJ<\/td>Frequently incomplete<\/td><\/tr>
    A.13<\/strong><\/td>Drawing general notes<\/td>Submittal requirements stated on drawings and not repeated in specifications<\/td>Occasionally missing<\/td><\/tr>
    A.14<\/strong><\/td>All addenda<\/td>Requirements added or modified after the original issue<\/td>Frequently missing<\/td><\/tr>
    A.15<\/strong><\/td>Sustainability or certification sections<\/td>Documentation for credits, material data, recycled content, VOC data<\/td>Frequently missing<\/td><\/tr>
    A.16<\/strong><\/td>Owner-furnished equipment coordination<\/td>Submittals required from the contractor relating to OFCI items<\/td>Sometimes missing<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

    Audit method: pick three technical sections at random plus all of Division 01. Extract every requirement from every article type. Compare against the register. Extrapolate the miss rate. Most template-derived registers come back sixty to seventy-five percent complete, and the shortfall is heavily weighted toward rows A.2, A.3, A.10, and A.11.<\/p>\n\n\n\n

    Table 3. Register Audit Verification<\/strong><\/p>\n\n\n\n

    #<\/strong><\/th>Check<\/strong><\/th>Disposition<\/strong><\/th><\/tr><\/thead>
    A.17<\/strong><\/td>Register built from this project’s specifications, not a prior project’s template<\/td>Source confirmed<\/td><\/tr>
    A.18<\/strong><\/td>Sample audit of three sections plus Division 01 completed; miss rate recorded<\/td>Miss rate documented<\/td><\/tr>
    A.19<\/strong><\/td>Every specification section present in the manual is represented in the register, or explicitly marked as requiring none<\/td>Coverage confirmed<\/td><\/tr>
    A.20<\/strong><\/td>Each register entry cites the specification section and article that requires it<\/td>Traceability confirmed<\/td><\/tr>
    A.21<\/strong><\/td>Each entry is typed as action or informational<\/td>Types assigned<\/td><\/tr>
    A.22<\/strong><\/td>Consolidated submittals are documented as consolidations, with all constituent requirements listed<\/td>Consolidations traceable<\/td><\/tr>
    A.23<\/strong><\/td>Register reissued after each addendum<\/td>Version current<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
    WARNING<\/strong>
    Check A.20 is what makes the register defensible. An entry without a specification citation cannot be verified, cannot be used as the screening baseline in Part D, and cannot be defended if a subcontractor disputes that the submittal was required.<\/th><\/tr><\/thead><\/table><\/figure>\n\n\n\n

    Part B: Log Structure and Field Audit<\/strong><\/h2>\n\n\n\n

    Fast, mechanical, and it determines whether the log can support decisions.<\/p>\n\n\n\n

    Table 4. Log Structure Checks<\/strong><\/p>\n\n\n\n

    #<\/strong><\/th>Check<\/strong><\/th>Why<\/strong><\/th><\/tr><\/thead>
    B.1<\/strong><\/td>Numbering by specification section, then sequential, then revision<\/td>Makes the log auditable against the documents; gaps reveal missing items<\/td><\/tr>
    B.2<\/strong><\/td>Numbering is not by date received or by subcontractor<\/td>Both make specification auditing impossible<\/td><\/tr>
    B.3<\/strong><\/td>Specification section and article field present and populated<\/td>Traceability and screening baseline<\/td><\/tr>
    B.4<\/strong><\/td>Description field specific enough to identify the item in a meeting<\/td>Prevents ambiguity in status review<\/td><\/tr>
    B.5<\/strong><\/td>Type field distinguishes action from informational, and states the specific type<\/td>Wrong routing and wrong urgency otherwise<\/td><\/tr>
    B.6<\/strong><\/td>Responsible subcontractor field populated<\/td>Nobody to chase otherwise<\/td><\/tr>
    B.7<\/strong><\/td>Required on site date present and sourced from the construction schedule<\/td>Without it the log cannot be scheduled<\/td><\/tr>
    B.8<\/strong><\/td>Lead time after release present and sourced from a supplier<\/td>Backward schedule impossible otherwise<\/td><\/tr>
    B.9<\/strong><\/td>Submit-by date present and derived, not copied from the specification<\/td>The specification clock and the building clock are unrelated<\/td><\/tr>
    B.10<\/strong><\/td>Float to need calculated and visible<\/td>The field that enables prioritization<\/td><\/tr>
    B.11<\/strong><\/td>Date received from subcontractor recorded separately from date transmitted<\/td>Separates subcontractor delay from review delay<\/td><\/tr>
    B.12<\/strong><\/td>Date returned recorded<\/td>Cycle time unmeasurable otherwise<\/td><\/tr>
    B.13<\/strong><\/td>Disposition code field using the contract’s actual codes<\/td>Ambiguity about whether work may proceed<\/td><\/tr>
    B.14<\/strong><\/td>Revision number field, incremented only by design team cycles<\/td>Preserves first-pass approval rate as a real metric<\/td><\/tr>
    B.15<\/strong><\/td>Ball in court field<\/td>Nobody knows who owes the next action otherwise<\/td><\/tr>
    B.16<\/strong><\/td>Days aged in current position, calculated<\/td>Items stall unnoticed otherwise<\/td><\/tr>
    B.17<\/strong><\/td>Deviation flag field<\/td>Deviations approved silently otherwise<\/td><\/tr>
    B.18<\/strong><\/td>Related RFI or change order cross-reference field<\/td>Circular waiting invisible otherwise<\/td><\/tr>
    B.19<\/strong><\/td>Release-for-fabrication date field<\/td>Lead time disputes unresolvable otherwise<\/td><\/tr>
    B.20<\/strong><\/td>Distribution record field or attachment<\/td>Field builds from superseded submittals otherwise<\/td><\/tr>
    B.21<\/strong><\/td>Log accessible to subcontractors in read form, or extracts issued regularly<\/td>Subcontractors cannot manage against a log they cannot see<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

    The four bolded checks, B.7 through B.10, are the ones that separate a schedule from a filing system. On most projects those four are the ones absent.<\/p>\n\n\n\n

    Part C: Backward Schedule Audit<\/strong><\/h2>\n\n\n\n

    The highest-value part of this checklist. Run it during preconstruction if possible, because the output should influence buyout sequencing.<\/p>\n\n\n\n

    Table 5. Backward Schedule Checks<\/strong><\/p>\n\n\n\n

    #<\/strong><\/th>Check<\/strong><\/th>Method<\/strong><\/th><\/tr><\/thead>
    C.1<\/strong><\/td>Every item has a required-on-site date traced to a schedule activity<\/td>Cross-reference the schedule activity ID<\/td><\/tr>
    C.2<\/strong><\/td>Long-lead items identified and listed separately<\/td>Threshold, typically 12 weeks or more after release<\/td><\/tr>
    C.3<\/strong><\/td>Lead times confirmed with suppliers this quarter, not carried from a prior project<\/td>Written confirmation or quote<\/td><\/tr>
    C.4<\/strong><\/td>Backward calculation performed for every long-lead item<\/td>Documented calculation per item<\/td><\/tr>
    C.5<\/strong><\/td>Calculation includes a second review cycle for delegated, complex, or historically rejected items<\/td>Check the assumption per item<\/td><\/tr>
    C.6<\/strong><\/td>Calculation includes contractor intake screening time<\/td>Usually 3 to 5 working days<\/td><\/tr>
    C.7<\/strong><\/td>Calculation includes subcontractor preparation time after award<\/td>Usually 10 to 20 working days<\/td><\/tr>
    C.8<\/strong><\/td>Calculation includes shipping, transit, and a site staging buffer<\/td>Separate from manufacturing<\/td><\/tr>
    C.9<\/strong><\/td>Resulting latest award date compared against the planned buyout schedule<\/td>Variance identified per package<\/td><\/tr>
    C.10<\/strong><\/td>Packages requiring earlier award than trade sequence suggests are escalated<\/td>List issued to project manager and executive<\/td><\/tr>
    C.11<\/strong><\/td>Items with negative float at setup are flagged and a recovery strategy documented<\/td>Early release packages, alternates, or expedite premiums<\/td><\/tr>
    C.12<\/strong><\/td>Mockup and preconstruction testing approvals treated as additional gates ahead of fabrication release<\/td>Extends effective lead time<\/td><\/tr>
    C.13<\/strong><\/td>Items dependent on unresolved RFIs or design decisions identified with the dependency<\/td>Escalate the dependency, not the item<\/td><\/tr>
    C.14<\/strong><\/td>Items dependent on owner decisions or owner-furnished equipment identified<\/td>Owner notified with dates<\/td><\/tr>
    C.15<\/strong><\/td>Utility company equipment and coordination lead times included<\/td>Frequently the longest item on a project<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
    EXPERT TIP<\/strong>
    Check C.10 is why this part exists. On most commercial projects three to six packages need to be awarded earlier than trade sequence would suggest, purely because of submittal and fabrication arithmetic. Discovering that during preconstruction costs a buyout conversation. Discovering it during construction costs the schedule.<\/th><\/tr><\/thead><\/table><\/figure>\n\n\n\n

    Part D: Intake Screening<\/strong><\/h2>\n\n\n\n

    The operational core. Run per submission before forwarding anything to the design team. A rejected submittal costs a full review cycle on both sides; screening costs twenty minutes.<\/p>\n\n\n\n

    Start with the universal block, then run the type-specific block.<\/p>\n\n\n\n

    Table 6. Universal Intake Screening Checks<\/strong><\/p>\n\n\n\n

    #<\/strong><\/th>Check<\/strong><\/th><\/tr><\/thead>
    D.1<\/strong><\/td>Submittal matches a register entry; number assigned per the log convention<\/td><\/tr>
    D.2<\/strong><\/td>Every component the specification’s submittal article requires is present, checked against the register citation<\/td><\/tr>
    D.3<\/strong><\/td>Correct specification section referenced on the submittal<\/td><\/tr>
    D.4<\/strong><\/td>Subcontractor has reviewed and stamped it, as most general conditions require<\/td><\/tr>
    D.5<\/strong><\/td>Submitted product is the specified product, not a similar one<\/td><\/tr>
    D.6<\/strong><\/td>Deviations from the specification identified in writing by the submitter<\/td><\/tr>
    D.7<\/strong><\/td>Where deviations exist and were not identified, they are flagged by the contractor before forwarding<\/td><\/tr>
    D.8<\/strong><\/td>Referenced attachments and appendices actually attached<\/td><\/tr>
    D.9<\/strong><\/td>Legible, complete, correctly oriented, and paginated<\/td><\/tr>
    D.10<\/strong><\/td>Related items that should be submitted together are packaged together, or the separation is deliberate<\/td><\/tr>
    D.11<\/strong><\/td>No unresolved RFI or prior approval on which this submittal depends<\/td><\/tr>
    D.12<\/strong><\/td>Coordination with adjacent trades’ approved submittals verified where interfaces exist<\/td><\/tr>
    D.13<\/strong><\/td>Submitted within the submit-by date, or the variance recorded and the float impact assessed<\/td><\/tr>
    D.14<\/strong><\/td>If a substitution, the Division 01 substitution procedure has been followed rather than submitted as product data<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

    Table 7. Type-Specific Intake Screening<\/strong><\/p>\n\n\n\n

    Submittal Type<\/strong><\/th>Additional Checks<\/strong><\/th><\/tr><\/thead>
    Shop drawings<\/strong><\/td>Shows actual project conditions, not catalog details; dimensions reflect field verification where required; gridlines and elevations match the contract documents; adjacent trades’ work shown where interfaces exist; fabrication and erection information complete; connection details included where delegated<\/td><\/tr>
    Product data<\/strong><\/td>Covers the specified model and options, not a product family; performance data addresses every specified criterion; options and accessories specified are included; irrelevant catalog content struck or marked; compliance with referenced standards stated<\/td><\/tr>
    Samples<\/strong><\/td>Correct quantity per specification; labeled with section, item, and location; range samples show the full range where variation is expected; finish, color, and texture match what was specified; retention arrangements understood<\/td><\/tr>
    Mockups<\/strong><\/td>Location and size per specification; scheduled before fabrication release of the represented work; acceptance criteria stated; retention duration understood and space allocated; protection arranged<\/td><\/tr>
    Delegated design<\/strong><\/td>Sealed by an engineer licensed in the project jurisdiction; design criteria cited match the structural general notes and specifications; calculations included; scope of the delegation clearly bounded; deferred submittal package to the AHJ identified and responsibility assigned<\/td><\/tr>
    Test reports, source<\/strong><\/td>Testing performed by a qualified agency; test method matches the specified standard; results address every specified criterion; sample identification traceable to the lot supplied<\/td><\/tr>
    Test reports, field<\/strong><\/td>Test performed at the specified frequency and stage; agency qualified and independent where required; failures identified with retest results; retest cost responsibility clear<\/td><\/tr>
    Certificates and qualifications<\/strong><\/td>Current and not expired; issued by the required authority; installer or manufacturer meets the stated experience threshold; project-specific where required<\/td><\/tr>
    Coordination drawings<\/strong><\/td>All required disciplines represented; based on current backgrounds; clearances shown; sign-off from participating trades present<\/td><\/tr>
    Warranties<\/strong><\/td>Duration, start date basis, and coverage match the specification; manufacturer and installer warranties both present where required; executed rather than sample forms<\/td><\/tr>
    O&M data<\/strong><\/td>Format matches Division 01; covers the equipment actually installed; parts lists and service contacts included; organized to the required structure<\/td><\/tr>
    Training documentation<\/strong><\/td>Plan submitted in advance where required; duration meets the specified hours; audience and recording requirements met<\/td><\/tr>
    Closeout and record documents<\/strong><\/td>Reflects as-built conditions; changes incorporated; format and media per Division 01<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

    Table 8. Intake Screening Outcomes<\/strong><\/p>\n\n\n\n

    Outcome<\/strong><\/th>Condition<\/strong><\/th>Action<\/strong><\/th>Log Effect<\/strong><\/th><\/tr><\/thead>
    Forward<\/strong><\/td>Complete and compliant<\/td>Transmit with review duration stated<\/td>Ball in court to design team<\/td><\/tr>
    Forward with contractor comment<\/strong><\/td>Complete, with an identified deviation or coordination issue<\/td>Transmit with a cover note<\/td>Deviation flag set<\/td><\/tr>
    Return to subcontractor<\/strong><\/td>Incomplete, unstamped, illegible, or wrong product<\/td>Return with a written deficiency list<\/td>Revision counter does not advance<\/td><\/tr>
    Hold on dependency<\/strong><\/td>Requires an unresolved RFI or prior approval<\/td>Hold with the dependency recorded<\/td>Dependency logged; escalate if float threatened<\/td><\/tr>
    Reclassify<\/strong><\/td>Submitted as product data but is actually a substitution<\/td>Return; require the substitution procedure<\/td>Recorded as returned, not as reviewed<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
    BEST PRACTICE<\/strong>
    Check D.7 earns its place repeatedly. Most general conditions require the submitter to identify deviations in writing, and most submitters do not. A deviation that reaches the design team unflagged and is approved has arguably been accepted, and unwinding that later is expensive and awkward. Comparing the submitted product against the specification takes five minutes.<\/th><\/tr><\/thead><\/table><\/figure>\n\n\n\n

    Part E: Review Cycle Management<\/strong><\/h2>\n\n\n\n

    Run weekly against all open items.<\/p>\n\n\n\n

    Table 9. Weekly Review Cycle Checks<\/strong><\/p>\n\n\n\n

    #<\/strong><\/th>Check<\/strong><\/th>Threshold and Action<\/strong><\/th><\/tr><\/thead>
    E.1<\/strong><\/td>Ball in court current for every open item<\/td>No item without an owner<\/td><\/tr>
    E.2<\/strong><\/td>Days aged calculated for every open item<\/td>Reported, not just stored<\/td><\/tr>
    E.3<\/strong><\/td>Items aged beyond the contractual review duration identified<\/td>Written notice to design team, copy owner, on the day it expires<\/td><\/tr>
    E.4<\/strong><\/td>Items with float to need under 15 working days flagged as at risk<\/td>Project manager tracks weekly<\/td><\/tr>
    E.5<\/strong><\/td>Items with float to need under 5 working days escalated<\/td>Project manager and owner notified; consider partial release<\/td><\/tr>
    E.6<\/strong><\/td>Items with negative float subject to a formal delay notice and recovery plan<\/td>Documented contemporaneously<\/td><\/tr>
    E.7<\/strong><\/td>Items on a third revision identified<\/td>Intervention meeting rather than another cycle<\/td><\/tr>
    E.8<\/strong><\/td>Items held on dependency over 10 days escalated<\/td>Escalate the dependency itself<\/td><\/tr>
    E.9<\/strong><\/td>Long-lead items not yet submitted at 80 percent of available preparation time<\/td>Escalate to subcontractor management<\/td><\/tr>
    E.10<\/strong><\/td>Open items sorted by float to need, not by date received, for the working list<\/td>Priority reflects consequence<\/td><\/tr>
    E.11<\/strong><\/td>Circular dependencies between the submittal log and the RFI log identified<\/td>Cross-reference both logs and break the loop<\/td><\/tr>
    E.12<\/strong><\/td>Subcontractors with multiple overdue submissions identified<\/td>Addressed at the subcontractor level, not item by item<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

    Part F: Disposition and Release<\/strong><\/h2>\n\n\n\n

    Run per returned submittal. Short, and it prevents a category of quiet risk transfer.<\/p>\n\n\n\n

    Table 10. Disposition and Release Checks<\/strong><\/p>\n\n\n\n

    #<\/strong><\/th>Check<\/strong><\/th>Why<\/strong><\/th><\/tr><\/thead>
    F.1<\/strong><\/td>Disposition code recorded using the contract’s actual codes<\/td>Ambiguity about whether work may proceed<\/td><\/tr>
    F.2<\/strong><\/td>Where “approved as noted,” every note read and assessed rather than filed<\/td>Notes can conflict with the specification, another trade, or field conditions<\/td><\/tr>
    F.3<\/strong><\/td>Notes conflicting with the specification or another approved submittal raised in writing before proceeding<\/td>Proceeding accepts the conflict<\/td><\/tr>
    F.4<\/strong><\/td>Conditional approvals closed before release rather than treated as approvals<\/td>Otherwise work is built with the condition unresolved<\/td><\/tr>
    F.5<\/strong><\/td>Deviations that were approved recorded explicitly in the log<\/td>Compliance record for inspection and warranty<\/td><\/tr>
    F.6<\/strong><\/td>Release for fabrication communicated to the subcontractor and the date recorded<\/td>Starts the lead time clock everyone later asks about<\/td><\/tr>
    F.7<\/strong><\/td>Approved submittal distributed to superintendent, affected trades, and any relevant consultant<\/td>Field building from superseded submittals is a distribution failure<\/td><\/tr>
    F.8<\/strong><\/td>Distribution acknowledged and recorded<\/td>Verifies currency rather than assuming it<\/td><\/tr>
    F.9<\/strong><\/td>Superseded revisions marked as void in the controlled location<\/td>Prevents crews using older versions<\/td><\/tr>
    F.10<\/strong><\/td>Procurement notified so the purchase order and delivery date can be confirmed<\/td>Approval without procurement action changes nothing<\/td><\/tr>
    F.11<\/strong><\/td>Schedule updated where the approval date differs materially from the plan<\/td>Keeps float calculations honest<\/td><\/tr>
    F.12<\/strong><\/td>Where rejected, the deficiency understood before resubmission is prepared<\/td>Prevents the third revision<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

    Part G: Closeout Submittals<\/strong><\/h2>\n\n\n\n

    Run monthly from roughly 75 percent completion. The failure here is predictable and preventable.<\/p>\n\n\n\n

    Table 11. Closeout Submittal Checks<\/strong><\/p>\n\n\n\n

    #<\/strong><\/th>Check<\/strong><\/th><\/tr><\/thead>
    G.1<\/strong><\/td>Closeout register extracted from Part 1 closeout articles, Division 01 closeout, O&M, training, and commissioning sections<\/td><\/tr>
    G.2<\/strong><\/td>Every subcontractor has received their closeout submittal list with dates<\/td><\/tr>
    G.3<\/strong><\/td>Closeout dates derived backward from substantial completion, not from it<\/td><\/tr>
    G.4<\/strong><\/td>Specific closeout items tied to specific payment applications rather than to final payment alone<\/td><\/tr>
    G.5<\/strong><\/td>Collection started at approximately 75 percent completion<\/td><\/tr>
    G.6<\/strong><\/td>Outstanding closeout submittals reported monthly by subcontractor<\/td><\/tr>
    G.7<\/strong><\/td>Warranties executed rather than sample forms, with correct start date basis<\/td><\/tr>
    G.8<\/strong><\/td>Warranty start basis confirmed for phased projects, whether substantial completion or first beneficial use<\/td><\/tr>
    G.9<\/strong><\/td>O&M data covers the equipment actually installed, including approved substitutions<\/td><\/tr>
    G.10<\/strong><\/td>Record drawings reflect changes, RFIs, and approved deviations<\/td><\/tr>
    G.11<\/strong><\/td>Training scheduled with the owner’s personnel, with required hours and recording<\/td><\/tr>
    G.12<\/strong><\/td>Attic stock and spare parts delivered, inventoried, and storage location confirmed<\/td><\/tr>
    G.13<\/strong><\/td>Commissioning documentation complete, including seasonal testing where deferred<\/td><\/tr>
    G.14<\/strong><\/td>Final test and inspection reports received, including any retests<\/td><\/tr>
    G.15<\/strong><\/td>Special inspection reports and deferred submittal approvals from the AHJ obtained<\/td><\/tr>
    G.16<\/strong><\/td>Subcontractors with outstanding items identified before their final payment is processed<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
    COMMON MISTAKE<\/strong>
    Check G.3 is the one that matters most and reads as pedantry. Closeout submittal dates derived from substantial completion means requesting documents from crews who demobilized weeks earlier, under retention pressure, from people who no longer have the project loaded. Derived backward, with items tied to progress payments, the same documents arrive routinely.<\/th><\/tr><\/thead><\/table><\/figure>\n\n\n\n

    Part H: Log Health Metrics<\/strong><\/h2>\n\n\n\n

    Run monthly. Four numbers, reported to the project manager and the owner.<\/p>\n\n\n\n

    Table 12. Log Health Metrics<\/strong><\/p>\n\n\n\n

    #<\/strong><\/th>Metric<\/strong><\/th>Definition<\/strong><\/th>Useful Target<\/strong><\/th>What a Miss Indicates<\/strong><\/th><\/tr><\/thead>
    H.1<\/strong><\/td>First-pass approval rate<\/td>Approved on first design team review divided by items reviewed<\/td>Above 70 percent<\/td>Below 50 percent: ambiguous specifications, weak intake screening, or a reviewer applying unstated standards<\/td><\/tr>
    H.2<\/strong><\/td>Average cycle time by discipline<\/td>Submission to disposition, working days, against contractual duration<\/td>At or under the contractual duration<\/td>Consistent overage is a contractual issue to raise with the owner<\/td><\/tr>
    H.3<\/strong><\/td>Items with float to need under 15 days<\/td>Count, trended weekly<\/td>Trending down after month three<\/td>Rising count predicts procurement delay<\/td><\/tr>
    H.4<\/strong><\/td>Closeout submittals outstanding<\/td>Percentage of the closeout register from 75 percent completion<\/td>Below 40 percent at 90 percent completion<\/td>Predicts the retention dispute<\/td><\/tr>
    H.5<\/strong><\/td>Register completeness<\/td>Miss rate from the Part A sample audit<\/td>Under 5 percent<\/td>Above 20 percent means the log cannot be trusted<\/td><\/tr>
    H.6<\/strong><\/td>Contractor return rate<\/td>Submissions returned at intake divided by submissions received<\/td>10 to 25 percent<\/td>Near zero means screening is not happening<\/td><\/tr>
    H.7<\/strong><\/td>Third-revision item count<\/td>Items on revision 3 or higher<\/td>Near zero<\/td>Each one is a process failure needing intervention<\/td><\/tr>
    H.8<\/strong><\/td>Deviation detection rate<\/td>Deviations flagged at intake divided by deviations ultimately identified<\/td>Above 80 percent<\/td>Deviations reaching the design team unflagged<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

    Metric H.6 is counterintuitive and worth stating plainly. A contractor return rate near zero is not a good sign. It means submissions are being forwarded without screening, and the rejections will happen at the design team instead, at the cost of a full review cycle each.<\/p>\n\n\n\n

    Importance: What These Checks Prevent<\/strong><\/h2>\n\n\n\n

    Submittal failures cost schedule rather than direct cost, which is why they are underweighted. A late shop drawing does not appear as a change order. It appears as a delayed fabrication release, then a delayed delivery, then a work activity that starts three weeks late, then either acceleration cost or a milestone miss.<\/p>\n\n\n\n

    The categories that dominate are consistent. Long-lead equipment where the arithmetic was never run. Closeout submittals discovered at substantial completion. Review cycles consumed by avoidable rejections. Register entries that never existed. Every one of those has a check on this list, and none of the checks requires software.<\/p>\n\n\n\n

    The second effect is contractual position. Delay claims turn on documentation: when it was submitted, when it was returned, what the disposition said, and whether overages were raised contemporaneously. A log that records those things is an asset in a dispute. A log that records status without dates is not.<\/p>\n\n\n\n

    Stakeholders<\/strong><\/h2>\n\n\n\n

    Table 13. Who Runs Which Part<\/strong><\/p>\n\n\n\n

    Part<\/strong><\/th>Owner<\/strong><\/th>Contributors<\/strong><\/th>Approver<\/strong><\/th><\/tr><\/thead>
    A, Register completeness<\/strong><\/td>Project engineer<\/td>Estimating, contracts<\/td>Project manager<\/td><\/tr>
    B, Log structure<\/strong><\/td>Project engineer<\/td>Project manager<\/td>Project manager<\/td><\/tr>
    C, Backward schedule<\/strong><\/td>Project manager<\/td>Scheduler, purchasing, subcontractors<\/td>Project executive<\/td><\/tr>
    D, Intake screening<\/strong><\/td>Project engineer<\/td>Superintendent for coordination checks<\/td>Project engineer<\/td><\/tr>
    E, Review cycle management<\/strong><\/td>Project engineer<\/td>Project manager for escalation<\/td>Project manager<\/td><\/tr>
    F, Disposition and release<\/strong><\/td>Project engineer<\/td>Superintendent, purchasing<\/td>Project manager<\/td><\/tr>
    G, Closeout submittals<\/strong><\/td>Project engineer<\/td>Project manager, commissioning agent<\/td>Project manager<\/td><\/tr>
    H, Log health metrics<\/strong><\/td>Project manager<\/td>Project engineer<\/td>Project executive<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

    Part C is the assignment most organizations get wrong. It is listed under the project manager because it requires the schedule, current lead times, and authority over buyout sequencing. Assigning it to the person who maintains the log guarantees it does not happen.<\/p>\n\n\n\n

    Required Documentation<\/strong><\/h2>\n\n\n\n

    Table 14. Documents Required to Run This Checklist<\/strong><\/p>\n\n\n\n

    Document<\/strong><\/th>Parts<\/strong><\/th>Consequence If Absent<\/strong><\/th><\/tr><\/thead>
    Complete project manual, all divisions<\/strong><\/td>A, D<\/td>Register incomplete; no screening baseline<\/td><\/tr>
    Division 01 submittal, quality, closeout, O&M, training, commissioning sections<\/strong><\/td>A, G<\/td>Cross-cutting submittals missing entirely<\/td><\/tr>
    All addenda<\/strong><\/td>A<\/td>Requirements added silently<\/td><\/tr>
    Construction schedule with installation activities<\/strong><\/td>C<\/td>No required-on-site dates; log cannot be scheduled<\/td><\/tr>
    Buyout and award schedule<\/strong><\/td>C<\/td>Cannot identify packages needing early award<\/td><\/tr>
    Current supplier lead time confirmations<\/strong><\/td>C<\/td>Backward schedule built on stale assumptions<\/td><\/tr>
    Delegated design register<\/strong><\/td>A, D<\/td>Sealed submissions and deferred packages missed<\/td><\/tr>
    Structural general notes with design criteria<\/strong><\/td>D<\/td>Delegated design criteria unverifiable<\/td><\/tr>
    Commissioning plan<\/strong><\/td>A, G<\/td>Commissioning submittals unregistered<\/td><\/tr>
    Division 01 substitution procedures<\/strong><\/td>D<\/td>Substitutions handled procedurally wrong<\/td><\/tr>
    Executed subcontracts with submittal schedules<\/strong><\/td>C, E<\/td>Dates unenforceable<\/td><\/tr>
    Controlled approved-submittal location<\/strong><\/td>F<\/td>Field currency unverifiable<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

    Technology Integration<\/strong><\/h2>\n\n\n\n

    Table 15. Checklist Execution by Method<\/strong><\/p>\n\n\n\n

    Part<\/strong><\/th>Spreadsheet<\/strong><\/th>Construction Management Platform<\/strong><\/th>Platform Plus Specification Extraction<\/strong><\/th><\/tr><\/thead>
    A, Register completeness<\/strong><\/td>Manual and rarely complete<\/td>Manual entry; platform indifferent to completeness<\/td>Register generated from the actual manual<\/td><\/tr>
    B, Log structure<\/strong><\/td>Manual field setup<\/td>Fields usually preset; the four scheduling fields often absent<\/td>Same, plus derived fields<\/td><\/tr>
    C, Backward schedule<\/strong><\/td>Possible; rarely done<\/td>Rarely supported natively<\/td>Rarely supported natively<\/td><\/tr>
    D, Intake screening<\/strong><\/td>Manual against the specification<\/td>Manual, with attachment handling<\/td>Automated comparison against section requirements<\/td><\/tr>
    E, Review cycle management<\/strong><\/td>Manual, decays<\/td>Automated aging and notifications<\/td>Same<\/td><\/tr>
    F, Disposition and release<\/strong><\/td>Manual distribution<\/td>Automated distribution with acknowledgment<\/td>Same<\/td><\/tr>
    G, Closeout submittals<\/strong><\/td>Manual<\/td>Supported if registered<\/td>Register generated including closeout<\/td><\/tr>
    H, Log health metrics<\/strong><\/td>Manual calculation<\/td>Usually automated<\/td>Automated<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

    The pattern is worth naming. Platforms are strong at Parts E and F, which are workflow, and largely indifferent to Parts A and C, which are the ones that determine outcomes. A platform with excellent notifications tracking an incomplete register that has no need dates will run smoothly toward a bad result, and the smoothness is the problem, because it feels like control.<\/p>\n\n\n\n

    AI-Assisted Opportunities<\/strong><\/h2>\n\n\n\n

    Two parts of this checklist are constrained by document volume, and they are the two that fail invisibly.<\/p>\n\n\n\n

    Part A requires reading four article types in every section of a project manual that may run 1,200 pages, plus Division 01, plus delegated design triggers, plus addenda. Nobody completes that inside a buyout window, which is why registers get built from templates.<\/p>\n\n\n\n

    Part D requires comparing each submission against the governing specification requirements item by item, including identifying deviations the submitter did not flag. On a large submittal that is careful reading, which is why it gets done fast or not at all.<\/p>\n\n\n\n

    Platforms that index construction documents address both. iFieldSmart AI, for example, extracts submittal requirements across every section and article with citations back to the source, and checks submitted documents against the governing specification requirements to flag missing or non-compliant content. That turns register construction from sampling into coverage and gives screening a baseline rather than a memory.<\/p>\n\n\n\n

    Table 16. Checklist Parts Mapped to AI Capability<\/strong><\/p>\n\n\n\n

    Part or Check<\/strong><\/th>AI Contribution<\/strong><\/th>What Still Requires You<\/strong><\/th><\/tr><\/thead>
    A, Register extraction<\/strong><\/td>Pulls requirements from all article types plus Division 01, with citations<\/td>Verifying completeness; deciding consolidations<\/td><\/tr>
    A.10 to A.11, Training and commissioning<\/strong><\/td>Extracts per-trade obligations from Division 01<\/td>Scheduling and payment linkage<\/td><\/tr>
    A.12, Delegated design<\/strong><\/td>Detects triggers and the submissions each requires<\/td>Assigning engineering and inspection responsibility<\/td><\/tr>
    A.14, Addenda<\/strong><\/td>Differences revisions to identify added requirements<\/td>Notifying subcontractors; reissuing the register<\/td><\/tr>
    B, Log structure<\/strong><\/td>Not addressed; a configuration decision<\/td>All of it<\/td><\/tr>
    C, Backward schedule<\/strong><\/td>Not addressed; needs schedule and supplier data<\/td>All of it<\/td><\/tr>
    D.2, Component completeness<\/strong><\/td>Compares submitted content against the section’s requirement list<\/td>Technical adequacy<\/td><\/tr>
    D.5 to D.7, Deviations<\/strong><\/td>Flags submitted products and values differing from specified<\/td>Whether the deviation is acceptable<\/td><\/tr>
    D, Type-specific checks<\/strong><\/td>Partial; retrieves the governing criteria for comparison<\/td>Judgment against the criteria<\/td><\/tr>
    G, Closeout register<\/strong><\/td>Extracts closeout requirements per trade<\/td>Collection strategy and payment linkage<\/td><\/tr>
    H, Metrics<\/strong><\/td>Automated where the log is in a platform<\/td>Interpretation and escalation<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
    IMPORTANT<\/strong>
    Note what is absent. Part C, the backward schedule, is the part that protects the project and it is not addressed by any of this, because it needs a real construction schedule and current supplier commitments. A complete register with no need dates is a better filing system, not a schedule.<\/th><\/tr><\/thead><\/table><\/figure>\n\n\n\n

    Implementation<\/strong><\/h2>\n\n\n\n
      \n
    • Run the Part A sample audit this week on a live project. Three sections plus Division 01. The miss rate will tell you whether the log can be trusted.<\/li>\n\n\n\n
    • Add the four scheduling fields from B.7 through B.10. This is the change that converts the log from a filing system into a schedule.<\/li>\n\n\n\n
    • Assign Part C explicitly to someone with schedule access and buyout authority. Not to the person maintaining the log.<\/li>\n\n\n\n
    • Adopt Part D with the type-specific blocks and institute written deficiency returns. Do not let returns consume revision numbers.<\/li>\n\n\n\n
    • Start reporting the four metrics in Part H monthly, including the counterintuitive one, contractor return rate.<\/li>\n\n\n\n
    • Extract the closeout register and begin collection at 75 percent, with items tied to progress payments.<\/li>\n\n\n\n
    • Treat every third-revision item as an intervention rather than a cycle.<\/li>\n\n\n\n
    • At project completion, list the items that caused schedule impact and identify which check would have caught each. Revise the checklist.<\/li>\n<\/ul>\n\n\n\n

      Table 17. Implementation Roadmap<\/strong><\/p>\n\n\n\n

      Phase<\/strong><\/th>Weeks<\/strong><\/th>Activity<\/strong><\/th>Deliverable<\/strong><\/th>Gate<\/strong><\/th><\/tr><\/thead>
      Audit<\/strong><\/td>1<\/td>Part A sample audit; miss rate recorded<\/td>Register gap report<\/td>Miss rate quantified<\/td><\/tr>
      Restructure<\/strong><\/td>1 to 3<\/td>Add the four scheduling fields; apply section numbering<\/td>Restructured log<\/td>All four fields populated<\/td><\/tr>
      Backward schedule<\/strong><\/td>2 to 5<\/td>Part C on long-lead items; compare against buyout<\/td>Early-award package list<\/td>Escalated to executive<\/td><\/tr>
      Screening<\/strong><\/td>3 to 6<\/td>Part D adopted with type blocks and deficiency returns<\/td>Screening procedure<\/td>Nothing forwarded incomplete<\/td><\/tr>
      Measurement<\/strong><\/td>5 to 8<\/td>Part H metrics reported monthly<\/td>Standard report<\/td>Issued to owner and design team<\/td><\/tr>
      Closeout<\/strong><\/td>8 to 12<\/td>Closeout register; payment linkage<\/td>Closeout schedule<\/td>Collection starts at 75 percent<\/td><\/tr>
      Improve<\/strong><\/td>Ongoing<\/td>Post-project mapping of schedule-impacting items<\/td>Checklist revision<\/td>Two consecutive project reviews<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

      Best Practices<\/strong><\/h2>\n\n\n\n

      Table 18. Checklist Discipline Best Practices<\/strong><\/p>\n\n\n\n

      Practice<\/strong><\/th>Why<\/strong><\/th><\/tr><\/thead>
      Audit the register before trusting the log<\/strong><\/td>The unrecoverable failure is the entry that never existed<\/td><\/tr>
      Extract from all four article types plus Division 01<\/strong><\/td>Single-article extraction is roughly 60 percent complete<\/td><\/tr>
      Cite the specification section on every register entry<\/strong><\/td>Makes the register defensible and gives screening a baseline<\/td><\/tr>
      Populate need dates from the schedule, lead times from suppliers<\/strong><\/td>Both from their only legitimate source<\/td><\/tr>
      Assign the backward schedule to someone with schedule access<\/strong><\/td>Otherwise the highest-value part never runs<\/td><\/tr>
      Screen at intake and return in writing<\/strong><\/td>Saves a full review cycle per avoided rejection<\/td><\/tr>
      Keep contractor returns out of the revision counter<\/strong><\/td>Preserves first-pass approval rate as a real metric<\/td><\/tr>
      Flag deviations yourself when the submitter has not<\/strong><\/td>Unflagged approved deviations become your compliance problem<\/td><\/tr>
      Sort the working list by float to need<\/strong><\/td>Consequence, not chronology<\/td><\/tr>
      Give written notice the day a review duration expires<\/strong><\/td>Contemporaneous documentation is what supports a claim<\/td><\/tr>
      Read the notes on “approved as noted” returns<\/strong><\/td>Notes can conflict with the specification or another trade<\/td><\/tr>
      Record the release-for-fabrication date<\/strong><\/td>It starts the clock everyone later disputes<\/td><\/tr>
      Distribute approved submittals with acknowledgment<\/strong><\/td>Field currency verified rather than assumed<\/td><\/tr>
      Derive closeout dates backward and tie items to progress payments<\/strong><\/td>Retention leverage arrives too late<\/td><\/tr>
      Report contractor return rate and worry if it is near zero<\/strong><\/td>Near zero means screening is not happening<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

      Common Mistakes<\/strong><\/h2>\n\n\n\n

      Table 19. Common Failures<\/strong><\/p>\n\n\n\n

      Mistake<\/strong><\/th>Consequence<\/strong><\/th>Fix<\/strong><\/th><\/tr><\/thead>
      Trusting a template-derived register<\/strong><\/td>Quality and closeout requirements absent<\/td>Part A audit; extract from this manual<\/td><\/tr>
      Log with no need dates or lead times<\/strong><\/td>Reports status; cannot support decisions<\/td>Add B.7 through B.10<\/td><\/tr>
      Backward schedule assigned to the log maintainer<\/strong><\/td>Never runs; procurement risk invisible<\/td>Assign to project manager with scheduler<\/td><\/tr>
      No intake screening<\/strong><\/td>Review cycles consumed by avoidable rejections<\/td>Part D with written returns<\/td><\/tr>
      Contractor returns counted as revisions<\/strong><\/td>First-pass approval rate meaningless<\/td>Separate counters<\/td><\/tr>
      Deviations unflagged at intake<\/strong><\/td>Approved by inattention; risk transferred<\/td>D.6 and D.7 enforced<\/td><\/tr>
      Working list sorted by date received<\/strong><\/td>Critical items wait behind trivial ones<\/td>Sort by float to need<\/td><\/tr>
      Review overages raised informally and late<\/strong><\/td>Contractual position weakened<\/td>Written notice on expiry day<\/td><\/tr>
      “Approved as noted” filed without reading<\/strong><\/td>Conflicting notes built into the work<\/td>F.2 and F.3 enforced<\/td><\/tr>
      Conditional approvals treated as approvals<\/strong><\/td>Work built with conditions open<\/td>F.4 enforced<\/td><\/tr>
      No distribution record<\/strong><\/td>Crews build from superseded submittals<\/td>F.7 through F.9<\/td><\/tr>
      Closeout discovered at substantial completion<\/strong><\/td>Documents produced late and badly<\/td>Part G from 75 percent<\/td><\/tr>
      Metrics not reported<\/strong><\/td>Nobody accountable for cycle time or approval rate<\/td>Part H monthly to owner<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

      Applied Examples<\/strong><\/h2>\n\n\n\n

      Class A office tower, 340,000 square feet.<\/strong> Part C on unitized curtain wall. The backward calculation showed release for fabrication needed eleven weeks earlier than the buyout schedule contemplated, because enclosure gated every interior trade. The glazing award moved ahead of three other packages on submittal arithmetic alone.<\/p>\n\n\n\n

      Regional hospital expansion, 190 beds, occupied campus.<\/strong> Check D.7. A submitted air handling unit differed from the specified unit in filtration configuration and the deviation was not identified by the submitter. On healthcare work filtration is a licensing matter, and an approved deviation would have surfaced during infection control commissioning with occupancy exposed.<\/p>\n\n\n\n

      Hyperscale data center, 60 MW.<\/strong> Checks C.11 and C.15. Switchgear, transformers, and utility coordination all carried lead times putting required award dates before the design was complete enough to buy from. The recovery strategy was an early release package with a defined change mechanism, which is a strategy decision only visible if Part C runs during preconstruction.<\/p>\n\n\n\n

      Advanced manufacturing facility, food grade.<\/strong> Check C.13 and the hold-on-dependency outcome in Table 8. Process vendor documents were known to arrive after the building submittals closed, so dependent items were logged as held with the dependency recorded rather than as overdue, and review capacity was reserved.<\/p>\n\n\n\n

      University science building, 11 floors.<\/strong> Check E.7. Three laboratory casework items reached a fourth revision, triggering the intervention meeting, which revealed the reviewer was applying a standard the specification did not state. Two closed on the next cycle once the requirement was clarified by RFI.<\/p>\n\n\n\n

      Multifamily podium, 240 units.<\/strong> Part G across twenty-two subcontractors demobilizing progressively as buildings turned over. Deriving closeout dates backward and tying specific items to progress payments converted what had been a retention fight on the prior project into routine collection.<\/p>\n\n\n\n

      Highway interchange, design-bid-build.<\/strong> Checks A.4 and A.5. Certified material test reports and field test documentation dominated the register, and requirements sat in measurement and payment sections as much as in technical sections. On unit-price work a missing certification means unpaid work rather than delayed work, which changes what register completeness is worth.<\/p>\n\n\n\n

      Historic warehouse conversion to hotel, 140 keys.<\/strong> Checks A.2 and C.12. Three sections required mockups approved before fabrication release, inserting an extra gate ahead of the normal cycle and extending effective lead time on custom millwork and window assemblies. Mockup requirements live in Part 1 quality assurance articles, which template-derived registers do not capture.<\/p>\n\n\n\n

      Frequently Asked Questions<\/strong><\/h2>\n\n\n\n

      How long does the full checklist take?<\/strong><\/h3>\n\n\n\n

      Parts A through C take about a day to a day and a half at project setup, with Part A being the largest piece. Part D is ten to twenty minutes per submission, run continuously. Part E is thirty minutes weekly. Part F is five to ten minutes per return. Part G is an hour monthly from 75 percent completion. Part H is thirty minutes monthly.<\/p>\n\n\n\n

      Which checks matter most if we can only do some?<\/strong><\/h3>\n\n\n\n

      Part A’s sample audit, checks B.7 through B.10, and Part C on long-lead items. That combination is roughly a day and it addresses register completeness, whether the log can be scheduled at all, and the procurement arithmetic that causes the largest schedule losses. Add Part D universal checks next, because they are the highest-frequency saving.<\/p>\n\n\n\n

      How is this different from what our construction management platform already does?<\/strong><\/h3>\n\n\n\n

      Platforms handle Parts E and F well: routing, aging, notifications, distribution. They are generally indifferent to Part A, because they track whatever register you enter, and they rarely support Part C natively. So a platform gives you excellent control over an incomplete, unscheduled list. The checks the platform does not perform are the ones that determine outcomes.<\/p>\n\n\n\n

      Should subcontractors see the log?<\/strong><\/h3>\n\n\n\n

      Yes, in read form or as regular extracts, with their submit-by dates. A subcontractor cannot manage against a schedule they cannot see, and most disputes about submittal timeliness dissolve when the dates were visible and contractual from the start. Keep the float calculations and internal risk flags to yourself.<\/p>\n\n\n\n

      Is a contractor return rate of 20 percent too high?<\/strong><\/h3>\n\n\n\n

      No. Ten to twenty-five percent is healthy, and it means screening is working. A rate near zero almost always means submissions are being forwarded unscreened, so the rejections happen at the design team instead and each one costs a full review cycle on both sides. The rate to worry about is the low one.<\/p>\n\n\n\n

      How do we handle submittals for owner-furnished equipment?<\/strong><\/h3>\n\n\n\n

      Register them, because the contractor usually owes coordination submittals, rough-in dimensions, and connection details even where the owner furnishes the equipment. The failure pattern is that nobody registers anything because the equipment is not the contractor’s, and then the rough-in dimensions arrive after the walls close. Check A.16 exists for this.<\/p>\n\n\n\n

      What if the design team consistently exceeds review durations?<\/strong><\/h3>\n\n\n\n

      Document it contemporaneously with written notice on the day each duration expires, and report average cycle time by discipline monthly to the owner. Consultants are under contract to the owner, not to you, so persistent overage is an owner conversation. Having it early with data is far more effective than having it late as part of a claim.<\/p>\n\n\n\n

      How should the log handle consolidated submittals?<\/strong><\/h3>\n\n\n\n

      Register each underlying requirement and note the consolidation, so the register remains auditable against the specifications. Consolidating a section’s product data, shop drawings, and samples into one submission is often sensible operationally, and it becomes a completeness problem if the register only shows one entry where the specification required three things.<\/p>\n\n\n\n

      Is it worth registering informational submittals?<\/strong><\/h3>\n\n\n\n

      Yes. They are contract requirements, they are frequently conditions of payment or closeout, and they are among the most commonly missing items at the end because nobody chases something that requires no approval. Register them, mark them informational so they are routed and prioritized correctly, and track receipt.<\/p>\n\n\n\n

      How does this checklist apply to design-build or CMAR delivery?<\/strong><\/h3>\n\n\n\n

      Part C improves substantially, because you can influence both the design release sequence and the buyout sequence, which means long-lead procurement can drive early design packages rather than colliding with them. Parts A and D are unchanged. The trap on progressive delivery is building the register against an incomplete manual and treating it as final; version it at each design release.<\/p>\n\n\n\n

      What is the single most commonly missing register category?<\/strong><\/h3>\n\n\n\n

      Commissioning and training submittals from Division 01, followed closely by Part 1 quality assurance items such as mockups and qualification statements. All of them are imposed across every trade by sections nobody reads, and all of them surface late, when the labor to produce them has left the project.<\/p>\n\n\n\n

      How do we prevent this checklist from becoming a formality?<\/strong><\/h3>\n\n\n\n

      Report Part H metrics monthly to someone outside the project team. Metrics that reach a project executive or an owner get maintained; internal checklists decay. And prune the list annually using post-project data, removing checks that never produce findings and adding whatever caused schedule impact.<\/p>\n\n\n\n

      Expert Recommendations<\/strong><\/h2>\n\n\n\n

      Run the Part A sample audit on your current project this week. Three sections plus Division 01, a few hours, and the miss rate will tell you whether your log means anything.<\/p>\n\n\n\n

      Add the four scheduling fields before doing anything else structural. Required on site, lead time, submit-by, float to need. Without them the log can only report.<\/p>\n\n\n\n

      Assign Part C to your project manager with the scheduler, in writing, and give them authority to change buyout order based on the result. This is the highest-value part of the checklist and it is the one that never happens by default.<\/p>\n\n\n\n

      Institute written deficiency returns at intake and keep them out of the revision counter. Two small conventions that make first-pass approval rate a real number you can improve.<\/p>\n\n\n\n

      Report contractor return rate monthly and be suspicious of a low one. It is the clearest available indicator of whether screening is actually happening.<\/p>\n\n\n\n

      Derive closeout dates backward from substantial completion and tie specific items to progress payments. Retention is the wrong lever because it arrives after the people who could help have left.<\/p>\n\n\n\n

      Treat every third-revision item as a meeting rather than a cycle. Repeated rejection is information about the requirement or the reviewer, not only about the submitter.<\/p>\n\n\n\n

      Using This From Here<\/strong><\/h2>\n\n\n\n

      A submittal log checklist is unglamorous, and it addresses one of the few construction failure modes that is almost entirely preventable with arithmetic. The items that cause schedule damage are knowable in advance: they are the long-lead ones, and the calculation that reveals them takes an afternoon.<\/p>\n\n\n\n

      The reason it goes wrong is structural rather than technical. Register completeness depends on reading a document nobody reads, and backward scheduling depends on data held by three different people. Both are solvable by assignment.<\/p>\n\n\n\n

      Run the Part A audit and the Part C calculation on the project you are on now. One will tell you what your log is missing, and the other will probably tell you something uncomfortable about a package you have not bought yet, which is exactly when you want to hear it.<\/p>\n\n\n\n

      <\/p>\n","protected":false},"excerpt":{"rendered":"

      There are two ways a submittal log fails, and they need different checklists. The first failure is structural. The log itself is wrong: requirements missing from the register, no need dates, no lead times, numbering that cannot be audited against the specifications. A structurally broken log runs smoothly and produces bad outcomes, because every notification […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5],"tags":[],"class_list":["post-72","post","type-post","status-publish","format-standard","hentry","category-submittal-management"],"yoast_head":"\nConstruction Submittal Log Checklist | iFieldSmart AI<\/title>\n<meta name=\"description\" content=\"Use this construction submittal log checklist to verify register completeness, improve review quality, reduce delays, and strengthen project controls.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.ifieldsmart.ai\/knowledge-center\/submittal-management\/construction-submittal-log-checklist\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Construction Submittal Log Checklist | iFieldSmart AI\" \/>\n<meta property=\"og:description\" content=\"Use this construction submittal log checklist to verify register completeness, improve review quality, reduce delays, and strengthen project controls.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.ifieldsmart.ai\/knowledge-center\/submittal-management\/construction-submittal-log-checklist\/\" \/>\n<meta property=\"og:site_name\" content=\"knowledge-center\" \/>\n<meta property=\"article:published_time\" content=\"2026-08-10T12:25:45+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-08-10T12:25:47+00:00\" \/>\n<meta name=\"author\" content=\"ifieldsmart.ai\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"ifieldsmart.ai\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"31 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.ifieldsmart.ai\\\/knowledge-center\\\/submittal-management\\\/construction-submittal-log-checklist\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.ifieldsmart.ai\\\/knowledge-center\\\/submittal-management\\\/construction-submittal-log-checklist\\\/\"},\"author\":{\"name\":\"ifieldsmart.ai\",\"@id\":\"https:\\\/\\\/www.ifieldsmart.ai\\\/knowledge-center\\\/#\\\/schema\\\/person\\\/51f5e238c4ca5a90257a3a2a63299411\"},\"headline\":\"Construction Submittal Log Checklist\",\"datePublished\":\"2026-08-10T12:25:45+00:00\",\"dateModified\":\"2026-08-10T12:25:47+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.ifieldsmart.ai\\\/knowledge-center\\\/submittal-management\\\/construction-submittal-log-checklist\\\/\"},\"wordCount\":6808,\"commentCount\":0,\"articleSection\":[\"Submittal Management\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.ifieldsmart.ai\\\/knowledge-center\\\/submittal-management\\\/construction-submittal-log-checklist\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.ifieldsmart.ai\\\/knowledge-center\\\/submittal-management\\\/construction-submittal-log-checklist\\\/\",\"url\":\"https:\\\/\\\/www.ifieldsmart.ai\\\/knowledge-center\\\/submittal-management\\\/construction-submittal-log-checklist\\\/\",\"name\":\"Construction Submittal Log Checklist | iFieldSmart AI\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.ifieldsmart.ai\\\/knowledge-center\\\/#website\"},\"datePublished\":\"2026-08-10T12:25:45+00:00\",\"dateModified\":\"2026-08-10T12:25:47+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.ifieldsmart.ai\\\/knowledge-center\\\/#\\\/schema\\\/person\\\/51f5e238c4ca5a90257a3a2a63299411\"},\"description\":\"Use this construction submittal log checklist to verify register completeness, improve review quality, reduce delays, and strengthen project controls.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.ifieldsmart.ai\\\/knowledge-center\\\/submittal-management\\\/construction-submittal-log-checklist\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.ifieldsmart.ai\\\/knowledge-center\\\/submittal-management\\\/construction-submittal-log-checklist\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.ifieldsmart.ai\\\/knowledge-center\\\/submittal-management\\\/construction-submittal-log-checklist\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.ifieldsmart.ai\\\/knowledge-center\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Construction Submittal Log Checklist\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.ifieldsmart.ai\\\/knowledge-center\\\/#website\",\"url\":\"https:\\\/\\\/www.ifieldsmart.ai\\\/knowledge-center\\\/\",\"name\":\"knowledge-center\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.ifieldsmart.ai\\\/knowledge-center\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.ifieldsmart.ai\\\/knowledge-center\\\/#\\\/schema\\\/person\\\/51f5e238c4ca5a90257a3a2a63299411\",\"name\":\"ifieldsmart.ai\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/90da01ed02edb6771e02823045695eb8320e44660e511fb3d1127d83b67543e8?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/90da01ed02edb6771e02823045695eb8320e44660e511fb3d1127d83b67543e8?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/90da01ed02edb6771e02823045695eb8320e44660e511fb3d1127d83b67543e8?s=96&d=mm&r=g\",\"caption\":\"ifieldsmart.ai\"},\"sameAs\":[\"https:\\\/\\\/www.ifieldsmart.ai\\\/knowledge-center\"],\"url\":\"https:\\\/\\\/www.ifieldsmart.ai\\\/knowledge-center\\\/author\\\/ifieldsmart-ai\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Construction Submittal Log Checklist | iFieldSmart AI","description":"Use this construction submittal log checklist to verify register completeness, improve review quality, reduce delays, and strengthen project controls.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/submittal-management\/construction-submittal-log-checklist\/","og_locale":"en_US","og_type":"article","og_title":"Construction Submittal Log Checklist | iFieldSmart AI","og_description":"Use this construction submittal log checklist to verify register completeness, improve review quality, reduce delays, and strengthen project controls.","og_url":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/submittal-management\/construction-submittal-log-checklist\/","og_site_name":"knowledge-center","article_published_time":"2026-08-10T12:25:45+00:00","article_modified_time":"2026-08-10T12:25:47+00:00","author":"ifieldsmart.ai","twitter_card":"summary_large_image","twitter_misc":{"Written by":"ifieldsmart.ai","Est. reading time":"31 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/submittal-management\/construction-submittal-log-checklist\/#article","isPartOf":{"@id":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/submittal-management\/construction-submittal-log-checklist\/"},"author":{"name":"ifieldsmart.ai","@id":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/#\/schema\/person\/51f5e238c4ca5a90257a3a2a63299411"},"headline":"Construction Submittal Log Checklist","datePublished":"2026-08-10T12:25:45+00:00","dateModified":"2026-08-10T12:25:47+00:00","mainEntityOfPage":{"@id":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/submittal-management\/construction-submittal-log-checklist\/"},"wordCount":6808,"commentCount":0,"articleSection":["Submittal Management"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.ifieldsmart.ai\/knowledge-center\/submittal-management\/construction-submittal-log-checklist\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/submittal-management\/construction-submittal-log-checklist\/","url":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/submittal-management\/construction-submittal-log-checklist\/","name":"Construction Submittal Log Checklist | iFieldSmart AI","isPartOf":{"@id":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/#website"},"datePublished":"2026-08-10T12:25:45+00:00","dateModified":"2026-08-10T12:25:47+00:00","author":{"@id":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/#\/schema\/person\/51f5e238c4ca5a90257a3a2a63299411"},"description":"Use this construction submittal log checklist to verify register completeness, improve review quality, reduce delays, and strengthen project controls.","breadcrumb":{"@id":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/submittal-management\/construction-submittal-log-checklist\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.ifieldsmart.ai\/knowledge-center\/submittal-management\/construction-submittal-log-checklist\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/submittal-management\/construction-submittal-log-checklist\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/"},{"@type":"ListItem","position":2,"name":"Construction Submittal Log Checklist"}]},{"@type":"WebSite","@id":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/#website","url":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/","name":"knowledge-center","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/#\/schema\/person\/51f5e238c4ca5a90257a3a2a63299411","name":"ifieldsmart.ai","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/90da01ed02edb6771e02823045695eb8320e44660e511fb3d1127d83b67543e8?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/90da01ed02edb6771e02823045695eb8320e44660e511fb3d1127d83b67543e8?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/90da01ed02edb6771e02823045695eb8320e44660e511fb3d1127d83b67543e8?s=96&d=mm&r=g","caption":"ifieldsmart.ai"},"sameAs":["https:\/\/www.ifieldsmart.ai\/knowledge-center"],"url":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/author\/ifieldsmart-ai\/"}]}},"_links":{"self":[{"href":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/wp-json\/wp\/v2\/posts\/72","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/wp-json\/wp\/v2\/comments?post=72"}],"version-history":[{"count":1,"href":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/wp-json\/wp\/v2\/posts\/72\/revisions"}],"predecessor-version":[{"id":73,"href":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/wp-json\/wp\/v2\/posts\/72\/revisions\/73"}],"wp:attachment":[{"href":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/wp-json\/wp\/v2\/media?parent=72"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/wp-json\/wp\/v2\/categories?post=72"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.ifieldsmart.ai\/knowledge-center\/wp-json\/wp\/v2\/tags?post=72"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}