Checklists and SOPs: procedures and runs

Write a procedure once with how-to for each step, then run it with an owner, a due date and a record of who did what.


A procedure is a list of steps. Each step can carry how-to text, a role, a time estimate, a link to a handbook page and a Needs approval mark. The how-to is plain text with simple formatting (bold, lists, links).

Needs approval is a mark, not a lock: it tells whoever runs the procedure that someone should sign the step off, but anyone on the run can still tick it. For a real sign-off, use Approvals.

Running a procedure

  1. 1Open the procedure and press Start a run.
  2. 2Name the run, choose who it is assigned to and when it is due, and link a project or a task if it belongs to one.
  3. 3Tick steps as they are done. The run shows who ticked each step and when, the step it is waiting on, and an activity history.

What the list shows

  • Procedures: every procedure, its steps, where it is used, runs in progress and the last run.
  • Runs in progress and History: every run, with its progress and when it finished.
  • On a procedure, Last 90 days shows how many runs finished, the typical length and the step that waits longest. Navalo works these out from the runs; it never estimates them.

Anyone in the workspace can tick steps. The person who started a run, the person it is assigned to and admins can change its details. A run linked to a project shows that link only to people who can see the project.

Still stuck? Open a support ticket and we'll help you out - tracked right inside Navalo.