Submittal
Submittals — shop drawings, product data, samples, method statements, test plans — are how the contractor's intended reality is checked against the designer's documented intent. The contract specifications define what must be submitted for each work section; the contractor assembles and schedules them; the designer reviews and returns each with an action code on the order of approved, approved as noted, revise and resubmit, or rejected.
The submittal log is therefore a shadow schedule. Long-lead equipment cannot be ordered until its submittal clears, which places review turnaround directly on the procurement critical path, and a designer's review backlog converts quietly into site delay.
Two misunderstandings cause most submittal disputes. First, approval of a submittal does not transfer design responsibility — the standard review stamps say, in effect, "consistent with design intent", not "we have re-engineered your shop drawing." Second, a submittal that deviates from the specification does not become compliant by being approved unless the deviation was explicitly flagged and accepted; buried deviations surface later as nonconformances with an approval stamp attached, which satisfies nobody.
See this workflow in practice.
Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work.