Site Inductions, Permits & Document Control

A site induction that's really just a signature sheet, and a permit system nobody quite understands, are two of the most common weak points on a commercial project — not because anyone's being careless, but because both are easy to treat as administrative steps rather than genuine communication.

Chapter 9 — Site inductions and permits to work

A good induction does more than record that someone was told the rules. It should leave every operative able to answer a handful of basic questions: where the muster point is, who the first aider is today, what the site's specific hazards are this week, and what's expected of them if something changes. An induction that's rushed through as a formality tends to produce a signature without producing that understanding — and the signature is the part that gets checked later, so the gap often isn't noticed until it matters.

Permit-to-work systems exist for a related reason: some activities carry risks that reach beyond the person doing the task, so they need sign-off from someone who can see the whole site picture, not just the immediate job. Hot works, confined space entry and working at height are common examples on commercial sites — not because the activity itself is unusual, but because getting them wrong can affect people who aren't involved in the task at all.

• Understand which activities on your scope of work are likely to need a permit before you arrive, not after
• Treat a permit as coordination with the wider site, not paperwork standing between you and the job
• Keep evidence of visitor and subcontractor inductions, not just your own team's
• Know who on site actually issues and signs off permits — this varies by project

Chapter 10 — Document control on a live project

On a job that runs for weeks or months, documents change. Scope shifts, a risk assessment gets revised, a method statement gets updated after a site visit reveals something the original plan didn't account for. Document control is simply the discipline of making sure everyone on site is working from the current version — not last month's.

Five different versions of the same RAMS, on five different phones, is a document control failure even if every version was correct when it was written.

This doesn't need to be complicated to be effective. A simple, consistently applied system beats a sophisticated one nobody follows: date every revision, note what changed and why, and make sure the person actually doing the work has the current copy — not just that a current copy exists somewhere.

Ownership matters here too. On a small job, it's obvious who updates the paperwork when something changes. As a business takes on more commercial work, it's worth deciding explicitly who's responsible for keeping documentation current, rather than assuming it will happen by default.

The full series

Seven parts. Each part stands alone; together they build a complete commercial documentation system.