Permit, maintenance and inspection forms your site can trust

A facilities team's paperwork usually exists for one reason: if something goes wrong, someone needs to be able to show what was checked, who signed it off, and when. That's a fine reason for a form to exist, but it's a terrible brief to hand a form designer, because it tends to produce documents built for the inspector rather than the person filling them in on site with cold hands and five minutes before the next job.

The better approach is to design for the person on site first — short, clear, mobile-first — and treat the audit trail as something the system builds automatically underneath, not something the user has to painstakingly construct field by field.

Build the record as a byproduct, not the point

If a form's main job is to be filled in accurately and quickly, the compliance record should come from timestamps, photo evidence and signatures the system captures automatically, not from asking someone to type out a paragraph explaining what they did.

• Capture location precisely — building, floor, room or zone as a dropdown or a scanned QR code, never a free-text description that varies by who's writing it. - Photo evidence over description. A photo of a completed isolation or a finished repair is faster to submit and harder to dispute than a written account. - Auto-capture what the system knows — submitter identity, timestamp, device — rather than asking for it.

The core forms behind a safe, well-run site

1. Permit to work

This is the form with the least tolerance for ambiguity. Specify the exact task, location, equipment involved, and required isolations as structured fields, not a description box. Build in a clear authorisation step separate from the request — the person raising the permit and the person approving it should never be able to be the same signature. Add an explicit closure step too; a permit that's opened but never formally closed is a common audit finding.

Common mistake: no expiry or shift-handover field, leaving a permit technically "live" long after the work and the crew that raised it have gone.

2. Hot works permit

Builds on the general permit but needs its own fire-watch and extinguisher-check fields, plus a mandatory post-work monitoring period (commonly 30–60 minutes) with its own sign-off, separate from the work completion sign-off. Don't let these two closures be a single checkbox — they happen at different times and by different people in many sites.

3. Contractor induction

Cover site-specific hazards, required PPE, emergency procedures and an acknowledgement that the contractor has read and understood them, alongside basic details — company, named individuals on site, insurance and relevant certifications. Make this reusable per visit rather than per person where contractors return regularly, so it doesn't become a barrier that gets skipped under time pressure.

4. Risk assessment

Structure around hazard, who might be harmed, existing controls, and residual risk rating, with a clear reviewer and review date field. Avoid one huge free-text hazard box — a repeatable table-style structure (even simulated with repeating field groups) makes assessments genuinely comparable across a site rather than each one reading completely differently.

5. Maintenance request

Keep the reporting form itself very short — location, issue, urgency, photo — so it gets used the moment something's noticed rather than put off until end of shift. Route by urgency and asset type automatically; a "no hot water" report and a "flickering light" report should never sit in the same queue with the same priority.

6. Building inspection checklist

Use a repeatable, structured checklist rather than a single form filled in differently by every inspector — same items, same order, every time, so results can be compared across dates and across sites. Photo fields against specific checklist items (not just one general upload at the end) make it far clearer exactly what was inspected and what condition it was in.

Making the audit trail hold up

Every safety-related form in this category should record who submitted it, when, and — where relevant — who approved or closed it, without asking the user to manually log any of that themselves. Keep historical versions of checklists and permit templates; if wording changes, old records should still show what was actually asked at the time. Export routinely into whatever system your safety or compliance team already reviews, since a form that's perfectly designed but never reviewed doesn't actually reduce risk.

A quick checklist before you publish

• Is location captured as a structured field or QR scan, not free text? - Is the person requesting a permit always different from the person approving it? - Does every permit or hot works form have an explicit closure step? - Are urgency and asset type used to route maintenance requests automatically? - Is photo evidence attached to specific checklist items, not just bundled at the end? - Is submitter identity and timestamp captured automatically rather than typed in?

Get those right and the paperwork stops being something people fill in to satisfy an audit, and becomes something that actually keeps the site safer day to day.