How to Pass an OSHA Audit Without Spreadsheets.

The morning-of audit binder · and why it breaks

01 · The spreadsheets problem — what breaks the morning a regulator walks the trailer.

Most EHS teams still rebuild the audit binder the night before a regulator visit. Eight Google sheets: the gas-sensor log downloaded as a CSV, the permit registry pulled at midnight, a hand-written narrative the safety officer drafted that week, and three separate folders of CCTV clips the supervisor expects the auditor to skip through. The packets reconcile, but they reconcile after the fact, with timestamps that drift apart and a narrative written by a different hand than the ones that captured the signals. The the auditor’s question is the same across all three standards — "show me the evidence pack you held when the rule was breached" — and the answer is too often a binder reconstructed from people who were asleep when the breach fired.

The audit-ready PDF replaces the morning-of binder with a record written at the same step as the alert. Two or more signals — a sensor reading, a permit-registry state, a timestamped CCTV frame — confirm a breach before a record leaves the correlator. The incident record carries the same evidence an auditor opens, from the same ledger the alarm was raised against, hash-chained and verifiable off-platform. We have written the worked example below three ways — refinery, construction, chemical plant — so the audit officer can map it to the standard their inspector opens against.

Worked example · refinery

02 · Refinery — H₂S excursion inside an open entry permit, written against OSHA PSM 14-element coverage.

The refinery matrix on the Pactwell for refineries page enumerates the 14 OSHA PSM 29 CFR 1910.119 elements a refinery EHS manager signs for — operating procedures, mechanical integrity, hot work, permit-required confined spaces, management of change, control of work, incident investigation. The worked example below is the moment of a breach inside §1910.119(g) Permit-required confined spaces and §1910.119(i) Personal protective equipment.

Worked example · construction

03 · Construction — fall-zone breach, audit trail, and the corrective work order.

On a high-rise floor the morning shift walked the leading edge without the retrieval line uncrossed. The fall clearance permit was open, no overhead anchor was registered to the harness, and the man-gate reader showed the worker inside the envelope. The Pactwell for construction matrix covers this against OSHA 1926 §1926.501 (duty to have fall protection) and §1926.502 (fall protection systems criteria), and the audit-ready PDF the correlator writes at the same step references the same subpart the inspector opens on a Subpart M walk, alongside Subpart AA (confined spaces in construction) and Subpart H (materials handling, rigging, cranes).

Worked example · chemical plant

04 · Chemical plant — process upset, written into the management-of-change log before the operator clears the panel.

On a reactor the pressure sensor diverges outside the operating-limit envelope at 02:48. The SIS trips in the same second; no MOC entry is open against the deviation. The Pactwell for chemical plants matrix pairs this against OSHA PSM 29 CFR 1910.119(d) (operating procedures), (l) (management of change), and (m) (incident investigation), plus EPA RMP 40 CFR Part 68 §68.69 (process information) and §68.71 (process hazard analysis). The audit pack the correlator writes is the same shape the RMP inspector opens; the append-only, hash-chained ledger keeps the deviation trace verifiable off-platform by independent computation.

What the audit-ready PDF replaces

05 · The audit-ready PDF replaces four manual surfaces — close them out in pairs.

The morning-of binder survived because nobody trusted the system of record enough to delete it. The audit-ready PDF is the system of record — close out the manual surfaces in pairs as you wire Pactwell onto your highest-risk bay.

• Manual evidence packs → the audit-ready PDF written at the same step as the alert. Every correlated incident carries a timestamped CCTV frame, the sensor reading, and the permit-registry state that was active when the rule was breached — no retrofitted narrative.
• Ad-hoc downloads → on-demand export from the same ledger the alert was raised against. Quarter-end drives for an external auditor become a one-click action rather than three days of CSV joining.
• Incomplete timestamps → server-side correlator timestamps every signal at ingest. The frame the correlator selected and the permit state it reasoned across are the same write — the PDF bytes and the ledger cannot drift, because they are the same write.
• Hand-keyed corrective logs → work-order dispatch that closes itself on a verification signal. The corrective action is verified before the incident record leaves the audit window.

Pricing hook

06 · The audit-ready PDF export is wired into Professional and Enterprise.

The audit-ready PDF is the line item the procurement evaluator opens the pricing matrix against. Quarterly export ships on Starter. On-demand export with the supervisor review workflow ships on Professional. DPA-bound export with legal-hold retention ships on Enterprise. Per-bay pricing — never per seat — so the floor crew sees every flagged incident without a licence-friction wall on the path to it.