Keep one drawing set valid for downstream work.
Elevator cab shop drawing revision control means naming one released drawing set as the governing engineering record, preserving earlier sets as unusable history, and tying every purchase and shop packet to that record. When engineering changes, affected downstream work stops until an authorized person reviews and re-releases it.
Published
A version is a saved state. Designers create versions while laying out panels, checking clearances, correcting notes, or testing details. Those saves matter for recovery and internal review, but they do not authorize another department to act.
A revision is a formally identified state that crosses a gate. It has a revision identifier, issue status, date, release authority, change description, and distribution record. Once issued outside engineering, recipients may rely on it according to its status. That reliance is why a revision needs more control than a file version.
The distinction should be written into the elevator submittal and drawing approval process. Working files belong to engineering. Released PDFs belong to the controlled job record. Native files can support the record, but a modifiable source file should not be mistaken for the released instruction.
Keep revision identity separate from issue status. The revision tells people which released technical state they hold. The status tells them what they may do with it.
| Status | Purpose | Permitted use | Required control |
|---|---|---|---|
| Preliminary | Coordinate an incomplete design internally or with named reviewers. | Review and coordination only. | Display a clear preliminary banner and expiry or next-review point. |
| Issued for Approval | Request a recorded decision on the submitted design. | Approval review, not purchasing or fabrication. | Identify recipients, response due date, and open exceptions. |
| Approved for Construction | Authorize defined downstream work from an approved design. | Purchasing and fabrication within stated release limits. | Require release authority and links to affected packets and commitments. |
| Final for Record | Freeze the approved design as the immutable preproduction record. | The governing basis for purchasing, fabrication, and later verification. | Lock the file against further edit; any change after this point needs a change order and a new release. |
| Superseded | Retain evidence of what was previously released. | History and audit only. | Block selection for new work and point users to the governing revision. |
Use a stable job number, drawing number, sheet number, and revision in the title block and file name. Avoid labels such as “latest,” “new final,” or dates used as revision identity. Dates help establish sequence, but they do not explain status or permit use.
Editing permission and release authority are different. A drafter may prepare a change without authority to commit purchasing or the shop. Name release roles by project or drawing class.
Identify the approved submittal, field dimensions, specification, finish selections, interface details, and accepted clarifications that govern the drawing. If two sources conflict, resolve the conflict before assigning a releasable revision.
Mark changed sheets and views, write a concise revision-block description, and attach the decision or request that caused the change. A reader should understand what moved without comparing every line on every sheet.
Review person-entered BOM lines, vendor requirements, open purchasing actions, released shop packets, work in process, and field preparation. Name each affected item rather than issuing a general warning that drawings have changed.
Complete the required engineering approval and decide whether scope, price, lead time, or contract responsibility changed. Technical release cannot be used to bypass a pending commercial decision.
Record the revision, status, releaser, timestamp, recipients, and withdrawn documents. Require owners of affected work to acknowledge whether they stopped, replaced, or confirmed each commitment.
Do not delete or overwrite it. Preserve the exact released PDF, title block, approval evidence, revision description, issue date, recipients, and any acknowledgements. That record may be needed to explain why material was ordered, what the customer reviewed, or which instruction was active when work occurred.
Then separate retention from availability. Move the file out of current-work views, show a visible superseded banner, make it read-only, and remove it from selectors used to create a shop packet or purchase request.
Paper needs the same treatment. Withdraw controlled copies, stamp retained copies as superseded, and post the replacement where work is performed. Asking everyone to remember which set is current is not a control.
Stop work based on impact, not department. Review quotes awaiting acceptance, purchase requests, released orders, vendor drawings, material already received, cut parts, outsourced work, active assembly, packing instructions, and field preparation. Dimensions, quantities, material, finish, interfaces, hardware, and sequence can each invalidate different work.
The stop remains until an owner dispositions every affected commitment: cancel, replace, rework, use as-is with approval, or confirm unaffected. Record who made that determination and from which revision comparison. A broad “new drawings attached” email does not establish whether anyone stopped.
Put the governing drawing revision on every purchase request, purchase order, vendor attachment, traveler, cut list, and shop packet. Also record who released the document and when. Those fields create a traceable comparison against the revision register; a folder location or matching file date does not.
Run the check at release and again when a revision changes. Flag blank revision fields, references to superseded drawings, and documents released before the current revision. A timestamp mismatch is a review trigger, not proof of error: an earlier order may remain valid if the changed feature does not affect that item. The disposition must say why.
For a manual audit, choose one bought-out component and one fabricated assembly. Follow each backward from order or packet to BOM line, drawing sheet, revision register, and approval.
A revision records a technical state. A change order records an approved commercial change. One does not automatically prove the other. A corrected spelling error may require a drawing revision with no price effect. A finish substitution, changed dimensions after approval, added scope, or accelerated delivery obligation may require both.
At revision review, ask whether the change alters contracted scope, material, labor, vendor cost, lead time, delivery, warranty, or responsibility. Record “no commercial impact” when that is the decision. If an impact exists, hold affected release until the required authorization follows the defined elevator cab change order process.
Keep the links in both directions: the revision cites the change order or no-impact decision, and the change order cites the affected drawing revision. That prevents approved money from being paired with the wrong technical instruction.
Software should preserve immutable releases, control who can change status, show one governing revision, retain superseded history, and connect technical and commercial decisions to the job timeline. It should make stale references visible; it should not silently decide that every earlier order or packet is wrong.
Build It Track It provides engineering drawing revisions, change orders, and a Final for Record lock today within the job record. Purchasing, purchase orders, inventory, capacity, scheduling and delivery dates, production scheduling, installation, inspection and final payment, invoicing and accounting are planned for the Q3 2026 launch and are not available today. It has no external CAD or ERP integration, DXF or DWG parsing or export, AI features, or automatic BOM generation from CAD. See how those controls fit the broader elevator cab project management workflow.
Elevator cab shop drawing revision control is the process of identifying one governing drawing set, limiting who may release it, preserving earlier revisions as history, and preventing superseded information from authorizing purchasing or fabrication. It connects every downstream packet and order to the engineering state used for release.
A version is any saved working state created while a drawing develops. A revision is an identified, formally released state that crosses a control gate and may be relied on by another party. Working versions can remain inside engineering; revisions need a revision mark, status, date, release authority, and recorded distribution.
Release authority should belong to named roles, not everyone who can edit or upload a drawing. The releaser verifies required technical and commercial approvals, confirms the revision block and changed sheets, records the release date and recipients, and accepts responsibility for withdrawing affected downstream work if the revision changes.
Keep superseded drawings immutable and searchable in revision history, with their former status, release date, approver, and distribution record intact. Remove them from current-work views and new-release pickers, watermark or banner them as superseded, and require shop packets and purchasing records to reference only the governing revision.
Stop any unverified activity affected by the changed dimensions, material, finish, quantity, interface, or sequence. That can include quote acceptance, purchase release, material cutting, outsourced fabrication, assembly, packing, and field preparation. An owner must review each open commitment and either cancel it, replace it, or document why it remains valid.
Require the governing drawing revision on every purchase request, purchase order, traveler, cut list, and shop packet. Compare that reference with the current released-revision register. A blank reference, a superseded identifier, or a release timestamp earlier than the latest engineering release is an exception that needs human review, not automatic cancellation.
A revision requires a change-order review when it changes contracted scope, price, lead time, delivery obligation, approved finish, performance requirement, or responsibility. Not every revision becomes a change order: drafting corrections and clarifications may have no commercial effect. Record that determination instead of assuming that a technical change is commercially neutral.
Review Build It Track It's current revision controls and the workflow planned for the Q3 2026 launch.
Request a demo