Part of the Compliance series on the Mobtag platform.

In short: Replacing a filing cabinet is a programme, not a weekend. A QR-first habit lets you migrate in slices so each success is proof the field prefers the new path—and the pack you hand over grows in the system, not on a print queue.

The failure mode is a big-bang paper purge before behaviour has moved. The winning pattern: pilot a site or a work type, put forms and sign-off on the same record the code opens, and let the old way become obviously slower (lost sheets, not “we have a policy”).

QR-first does not mean “a QR code exists.” It means the first place someone looks for the truth on an asset is the live profile behind the scan—not a folder someone hopes is current.

What “QR-first” is not

  • It is not “we have a code on a poster and still keep the truth in Word.”
  • It is not “the QR links to a PDF in SharePoint and nothing else is structured.”
  • It is “one scan opens one current record, and what you are allowed to do or sign is the same in front of an engineer and an assessor.”
Phase A healthy milestone
1 One work type, one site, a weekly feedback loop on friction
2 The export your regulator (or customer) asked for, from the register—not a pivot rebuilt the night before
3 The old way is visibly slower—until retiring a parallel process is the obvious next move

Why the “rip out paper on Monday” plan backfires

Compliance is not only a control design problem; it is a ritual problem. People have routines around clipboards and signing in the trailer. If the digital path is slower or less trusted on a wet Tuesday, the paper comes back in week three—and your evidence splits again.

  • Adopt before you ban the old tools—or you get two systems of record and a standing argument about which one is “for real”.
  • Make the new path faster for the person in gloves—fewer taps, clearer defaults, and a line of work that remembers who they are.
  • Measure scans and completions the way you measure safety incidents—lagging counts in a spreadsheet will miss a reversion until month nine.

How a defensible chain looks on the day

Assessors do not reward volume of paper; they reward a line of evidence you can walk in order: which item, who did what when, and which rule version applied when the world changed.

flowchart LR Q[Scan QR on asset] --> R[Current profile and allowed actions] R --> F[Form or check with validation] F --> S[Sign-off or result on same record] S --> H[History and export from register]

When history, signatures, and structured answers point at the same row, you are not rebuilding a narrative from email and a staple the afternoon the visitor arrives.

One profile behind the code

If asset identity and compliance state live in different lists, the QR is a link to dissonance, not a front door. Tie tags, sites, and permit or inspection families to the same profile the code opens—so a filter in the register and a pin on a map still align in a board review.

Symptom Healthier habit
“We print for the audit” Run a rehearsal export monthly; fix gaps when nobody is in a suit
Champions in HQ only Named sponsors on each pilot site with rota time for feedback
PDF is the only “signed” copy Signed PDF on the item and structured pass/fail in the register for search and trends

Summary: A practical path is scan-led evidence growing in the run-up to a visit—not a heroic reassemble from paper and three systems the week before the auditor lands.