← Back to Home

Writing a Safety Policy

A safety policy is your organization's promise: what you value, who is responsible, and how you work. This guide covers the core sections every policy should include — written in plain language, adaptable to any region.

Why a Written Policy Matters

Without a documented policy, safety decisions become ad hoc and inconsistent. A clear policy sets expectations, assigns accountability, and gives new hires a baseline to learn from.

Core Sections to Include

Statement of commitment from leadership. Roles and responsibilities (who does what). Hazard identification and reporting process. Incident and near-miss response steps. Training and competence expectations. Review cycle (when the policy is revisited).

Keep It Usable

A policy nobody reads doesn't protect anyone. Write for the people on the floor, not for a filing cabinet.

Use plain language and short sentences
Make it one or two pages where possible
Name real people, not just "management"
Translate it for the languages your team uses
Review it at least annually and after any serious incident

Back the Policy With Checklists

A policy describes intent; checklists make it routine. Link yours to the relevant industry standard:

Build It Step by Step

Don't write the whole policy in one sitting. Start with the commitment statement and roles, then layer in reporting and review. Pair it with the Compliance Starter Kit for a practical rollout plan.

Try Jotsight Free