Create and assign actions

Raise work from findings or from scratch, with the owner, due date and type that make it real.

4 min read · Last reviewed 18 August 2026

Raise actions where the finding is

  • From a failed inspection response — the action carries the exact question and inspection it came from.

  • From a hazard report — the fix for what was reported.

  • From an approved incident finding — created exactly once, with owner and due date confirmed at approval.

  • From a failed fire-safety check — raised by default when a check fails.

  • Or standalone, from the Actions register, for work that starts as work.

Make it assignable

  1. 1

    Give every action an owner — one person, not a team. Shared ownership is how actions rot.

  2. 2

    Set a due date and a priority the owner can defend.

  3. 3

    Pick the type — corrective, preventive, improvement or maintenance by default; your own types and categories under Settings → Actions.

Tip: A good action reads as an instruction: what to do, where, by when. “Investigate options” is a meeting, not an action.

Close with evidence

  1. 1

    The owner attaches photos or files showing what was done — the fixed guard, the new signage, the invoice.

  2. 2

    Closing writes the completion onto the record, and the source — inspection, report, incident — reads it back.

About this moduleActionsOne board for everything that must get done — wherever it was raised, whoever owes it.