Measured defects
| Finding | Consequence |
|---|---|
| The system lives in five separate places | No single answer for the number of open permits |
| The critical record is a single paper copy | Risk of loss against a long retention duty |
| Six dated versions of the form side by side | The current version is guessed from the file name |
| Two questions under one question code | A non-conformity report cannot be traced to a question |
| The approver list is an empty template | No source for "who may approve" |
| No link between equipment tag and inspection form | The tag on site leads nowhere |
What the defects share
None of them is an error in a rule. The rules are written correctly; what is missing is somewhere to show whether they were followed. Paper carries a rule but cannot prove the rule worked.
Checklist versus gate
Every checklist item in a permit system can become a gate in software. No permit without the device record read, no selection of non-conforming equipment, no approval without the required attachment, no team member whose certificate has expired — all of them are the same items, made enforceable.
A misunderstanding about digitising
Scanning the form into a folder is not digitising; it is a picture of the same paper. The gain comes not from moving the form onto a screen but from tying decisions to records.
What must be preserved
Paper systems also have strengths worth carrying over: the toolbox talk, the sense of personal accountability a wet signature creates, and the shared reference of one document physically present on site. Software that loses these solves the problem while weakening the system.