How wrong-revision work starts
Most wrong-revision builds start quietly. A traveler still points to an old PDF. A binder page was never swapped. Someone opens `WI-042_RevC_final.pdf` because the filename looks familiar. By the time quality notices, the cost is already in rework, containment, or a customer call.
- Scrap and rework from wrong-revision builds
- Audit non-conformances when revision proof is missing
- Engineering hours lost to chasing down which version was used
Why shared folders do not control revisions
Shared drives, email threads, Teams attachments, and local desktops can store files, but they do not answer one operational question: which revision is current for the line right now? They preserve copies. They do not manage draft, publish, current, superseded, and rollback as a controlled flow.
- No way to mark one file as the current revision for the line
- No clean first-open evidence or acknowledgement when a change needs follow-up
- Version naming chaos: v2_final_FINAL_reviewed.pdf
How the release flow works
RevQR turns revision control into an operational routine. Upload the next revision as draft, publish it when it is ready, let the previous current revision move to superseded, and keep rollback available if the released change needs to be reversed.
- Upload new revisions as Draft without disrupting the live version
- Publish to promote one revision to Current; previous becomes Superseded
- Rollback to a previous revision if a released change needs to be reversed
Latest vs Pinned Links
Not every QR should behave the same way. A workstation poster needs a latest link that follows the current revision. A traveler, PPAP pack, or shipment record may need a pinned link that stays fixed to the released revision.
- Latest (mutable): always opens the current revision — use on workstation posters
- Pinned (immutable): locked to a specific revision — use on travelers, PPAP packs, or DHR records
Where acknowledgement fits
Some changes stop at publish. Others need named acknowledgement in audit mode before the next batch, shift, or line restart. RevQR can add due dates and reader groups for those documents without pretending to be a full training matrix.
- Publish the revision first, then track which required readers still owe acknowledgement
- Reader groups keep the requirement scoped to the people who actually use that instruction
- Overdue views help supervisors chase the exception, not the whole line