The problem it solves
Picture WI-042 Rev C still taped to Line 3 after Rev D was released on second shift. RevQR exists to stop that exact failure: one controlled document, one current revision, and one QR path the workstation can trust.
- Built for controlled PDF and image instructions used at the workstation
- Latest link for daily use, pinned link where traceability must stay tied to one released revision
- Optional audit mode with Operator ID + PIN, named acknowledgement, and revision due dates where follow-up matters
What happens after a change
A new revision starts as draft. When it is published, it becomes current, the previous current revision becomes superseded, and the latest link on the workstation poster now opens the new file. If the change was wrong, you can rollback without losing the history.
- Revision lifecycle: upload as draft, publish to make it current, move the previous revision to superseded, rollback if needed
- QR delivery: latest link for workstation posters, pinned links for traveler, PPAP, or DHR traceability
- Acknowledgement options: anonymous acknowledgement for shared stations, or audit mode with Operator ID + PIN, due dates, reader groups, and overdue follow-up
Who uses it on a real floor
Quality uses it when an auditor asks what revision was current on 12 February. Supervisors use it when a line changeover has to land before the next shift. Process engineers use it when a torque spec changes from 35 Nm to 45 Nm and every station needs the new instruction now.
- Quality managers pull revision history, current status, and acknowledgement records where audit mode is used
- Production supervisors keep the line on the current revision without swapping binders
- Process engineers publish updates and keep rollback available if a change is wrong
How teams usually roll it out
Most teams start with the instructions that change most often or cause the most confusion. Put a latest link on the workstation, add pinned links only where PPAP, DHR, traveler, or batch traceability needs a fixed revision, and keep editor access separate from shop-floor scanning.
- Pilot one line first with the instructions that change most often
- Print one latest QR per workstation and add pinned links where traceability matters
- Keep named editor accounts while shop-floor access stays QR-based
What it does not try to be
RevQR does not replace your QMS, PLM, or authoring tool. It sits closer to the workstation: controlling which released revision opens, preserving revision history, and adding acknowledgement only where the process really calls for it.
- Not a QMS — your QMS handles procedures, policies, and approval chains
- Not a PLM — your PLM handles CAD, BOMs, and engineering changes
- Not an authoring tool — create the source document in Word, InDesign, or another tool, then upload the PDF or image file