The stamp is not the control. The control is the project-defined meaning of the disposition and the evidence that every condition reached the records used for procurement and fabrication.
A window drawing returns ‘approved as noted’. Engineering reads the comments as minor drafting corrections; purchasing orders glass; the factory treats the stamp as full release; the reviewer expects a corrected set before work. One phrase has produced four production states. The remedy is not a universal dictionary of stamps. It is a project-approved disposition matrix that defines authority, permitted action, resubmission, incorporation and dependency by scope.
Contractual meaning boundary: Approval codes and their consequences are project-specific. The executed contract and submittal procedure govern, including whether review limits or preserves contractor responsibilities. Never import the labels in this article into a live project without authorised adoption.
1. Define every disposition before the first submittal
UFGS 01 33 00 is an official US Department of Defense example of a detailed submittal process: it uses a submittal register, review routes, resubmission and Government approval controls. It is useful evidence that status must be procedural. It is not a universal private-project contract and its labels must not be copied without checking applicability.
For each project label—whether approved, approved as noted, revise and resubmit, rejected, reviewed, no exception taken or another term—record who may issue it, what technical review it represents, whether correction/resubmission is required, what work may proceed, and which separate release remains necessary. If the contract is silent or inconsistent, obtain an authorised clarification before relying on the stamp.
Separate technical disposition from commercial release and factory release. A drawing can be technically acceptable while colour, performance evidence, field dimensions or commercial change remains open. Conversely, an internal factory release is not project approval.
| Project code/label | Meaning and authority | May proceed | Must remain held | Resubmission/incorporation |
|---|---|---|---|---|
| [Approved equivalent] | [project-defined] | [named scope only] | [other gates] | [record rule] |
| [Approved as noted equivalent] | [project-defined] | [only if expressly permitted] | [conditions/dependencies] | [corrected-set rule] |
| [Revise/resubmit equivalent] | [project-defined] | [none or named unaffected work] | [affected scope] | [resubmit requirement] |
| [Rejected equivalent] | [project-defined] | [unaffected scope only if authorised] | [submitted scope] | [new submission route] |
| [For information/reviewed] | [project-defined] | [do not infer] | [production unless separately released] | [archive/action rule] |
2. Make the review package capable of receiving a bounded decision
A reviewer cannot safely dispose of a drawing whose baseline and deviations are hidden. The supplier submission should identify document number/revision, opening marks, source design revisions, system/configuration, dimensions and datum, glass, hardware/handing, finish, interfaces, performance assumptions, supplied scope and unresolved RFIs. Show departures explicitly; silence is not an approval request.
Coordinate sheets before submission. A correct elevation with an obsolete glass schedule or interface section is not a coordinated package. Include a supplier check record appropriate to the procedure so the project reviewer is not asked to perform the supplier's internal coordination.
A review should leave traceable comments tied to sheet, detail, mark and requirement. Distinguish mandatory correction, clarification, advisory observation and question. Ambiguous redlines turn ‘approved as noted’ into guesswork.
| Control area | Evidence in submission | Possible dependent hold |
|---|---|---|
| Identity | Document/revision, marks and source baseline | All affected work |
| Geometry | Elevations, sections, datum and survey status | Cutting/fabrication |
| Configuration | System, glass, hardware, handing, finish | Material order/machining/coating |
| Interfaces | Structure, sill, waterproofing, finishes and supplied scope | Subframes/installation |
| Performance | Requirement and scope-matched evidence route | Configuration release |
| Deviations/open items | Explicit list with RFI/change references | Affected activity only |
3. Convert every note into a responsible action and dependency
For a conditional disposition, transcribe each note into a comment-resolution log. Record the affected marks, required correction, responsible party, due document, dependency and verifier. Do not let a handwritten note remain only on one returned PDF while the schedule, model and work order continue unchanged.
Classify whether a note is confirmatory or configuration-changing. A typo correction may be incorporated without changing product. A revised dimension, glass build-up, safety classification, hardware, drainage, interface, finish or performance basis can affect procurement, testing, price and programme. Route the latter through the required design/change authority; the stamp alone does not settle every consequence.
If notes conflict with one another or with controlling documents, place the affected scope on hold and seek clarification. Do not choose the most convenient annotation.
| Comment ID | Sheet/marks | Required action | Dependency/hold | Resolution evidence | Verifier |
|---|---|---|---|---|---|
| [C-01] | [detail / marks] | [exact correction] | [activity] | [new revision/reference] | [role/date] |
| [C-02] | [schedule / marks] | [clarification/change route] | [activity] | [RFI/change reference] | [role/date] |
| [C-03] | [general note] | [scope population check] | [named scope] | [affected-mark list] | [role/date] |
4. Release production by configuration and activity—not by stamp colour
Build a release matrix linking the disposed shop drawing to separate gates for profile/material commitment, glass order, hardware order, machining, coating, assembly, inspection and packing. State which marks are released. A broad stamp cannot prove that field dimensions, samples, RFIs, tests or commercial changes are closed.
Use the narrowest safe partial release where the authorised procedure permits it. For example, repeat profiles may be released while special-mark glass remains held—but only after dependencies are checked. Record any irreversible commitment and the authority accepting its risk. Do not use partial release to imply approval of dependent work.
Before start, verify factory-facing records against the disposed and corrected baseline. Check work order, cut/machining instructions, purchase orders, inspection criteria and labels. This turns the review outcome into a controlled production state.
| Activity | Drawing disposition sufficient? | Other prerequisite to identify | Mark scope/status | Verification |
|---|---|---|---|---|
| Profile/material order | [project rule] | System/finish/commercial release | [marks / held-released] | [record] |
| Glass order | [project rule] | Glass schedule/evidence and dimensions | [marks / held-released] | [record] |
| Machining/assembly | [project rule] | Handing, hardware, survey and RFIs | [marks / held-released] | [record] |
| Coating | [project rule] | Finish/sample approval | [marks / held-released] | [record] |
| Packing/shipment | No assumption | Inspection, labels and shipment release | [marks / held-released] | [record] |
5. Resubmit visibly and audit incorporation at the point of use
A corrected resubmittal should show the prior disposition, each comment response, revised locations and any unchanged rejected proposal. Do not erase clouds or annotations until the reviewer can verify the correction. Preserve the returned set and transmittal as history.
After final disposition, reconcile the accepted set with schedules, RFIs, change records and production instructions. Withdraw superseded copies at engineering, purchasing, workshop, quality and packing points. ISO 10007 configuration-management guidance is relevant to this lifecycle control; it does not define the contract's approval labels.
Report truthfully: ‘revision C technically accepted for listed marks; finish and survey gates remain held’ is stronger than ‘drawings approved’. The status statement should survive handover and later explain what was authorised to proceed.
FAQ
Does ‘approved’ always permit fabrication?
No. Its meaning comes from the project procedure, and separate field, evidence, commercial or production-release gates may remain.
Can ‘approved as noted’ be treated as full approval?
Only to the extent explicitly defined by the applicable procedure. Every note still needs a controlled owner, incorporation route and dependency check.
Who owns errors in shop drawings after review?
That is a contract- and law-dependent question. Do not infer a transfer of responsibility from this guide or from a stamp label alone.
Must every comment cause a complete resubmission?
Follow the project procedure. Some states require resubmission; others may permit incorporation, but the evidence and allowed work must be explicit.
What if the reviewer changes the design in a redline?
Hold affected work and route the change through the authorised design, contract and information-control process rather than treating the annotation as self-executing.
Continue the project review
Connect this guide with the proposed window and door systems, then review how Cavorlen approaches manufacturing and quality control. When your schedule is ready, send it through the project review form.
Official sources used
WBDG / DoD — UFGS 01 33 00 Submittal Procedures ↗ISO — ISO 19650-2:2018 information management during delivery ↗ISO — ISO 10007:2017 configuration management guidance ↗USACE — Construction Quality Management Student Study Guide ↗Related buyer guides
This guide does not define the legal effect of a shop-drawing review, transfer design responsibility, waive deviations, authorise fabrication, set review periods or decide liability. Its example states are placeholders, not a universal approval code.