Skip to main content

Actions: how they work in ASR

What an action is, where they come from, the lifecycle from raised to closed, and who can do what.

D
Written by Darragh Jones

An action is a job that someone needs to do — fix a fault, replace a missing sign, chase a certificate, deal with something a check picked up. Actions give every one of those jobs an owner, a due date and a record of how it was resolved.

Where to find them

Go to Work > Actions. That's the full list of every action across the sites you can see.

The Work menu item carries a badge showing how many actions are still open, so you can see at a glance whether anything needs picking up. Your Work page also lists today's actions alongside your checks.

Clicking an action opens its own page, where you update it, comment on it, and close it.

Where actions come from

Most actions aren't typed in by hand — they're raised automatically when something else finds a problem. Every action shows a badge telling you where it came from, with a link back to the source:

  • Checklist — someone flagged an issue on a checklist task and chose Raise Action.

  • Audit — a finding from an audit. These appear once the audit is published.

  • Risk assessment — a measure needed because risk remains after existing controls.

  • Incident — an action from a reported event. These are managed on the event itself.

  • Document store — a reminder that required documents still need uploading.

  • Site action — created by hand for a site, without an audit behind it.

Each of these is explained in Where actions come from.

The basic lifecycle

  1. An action is raised and given an Owner and usually a Due date.

  2. The owner is notified by email and in the app.

  3. While work is ongoing, the owner records progress with Mark as pending.

  4. When it's done, they add a comment (and evidence if useful) and choose Close action.

  5. If it turns out it wasn't finished, anyone can choose Reopen action.

You always have to leave a comment to close an action. That comment is the record of what was actually done, so it's worth writing properly.

Who can do what

  • See actions — everyone with a role in the organisation. Team members and viewers only see actions for the sites they're assigned to; admins and auditors see them all.

  • Create an action from the Actions page — admins and client admins. The Add action button is hidden for everyone else.

  • Create an action from the Work page — anyone with access to Work, using Add > Action.

  • Update, close and reopen — members of the organisation. For actions linked to an audit, that also includes the auditor who ran it.

  • Change the owner — from the list or the action itself. Incident actions are the exception; their owner is set on the event.

One restriction to know about: an action tied to an audit can't be deleted once that audit has been published or closed, because it forms part of the audit record.

Keeping on top of them

The list opens filtered to Open by default, so you see live work rather than everything ever raised. From there:

  • Filter to Overdue to see what has slipped.

  • Use the Owner filter and pick yourself to see just your own actions.

  • Sort by Due Date to work through them in order.

Your Work page shows Open Actions and Overdue Actions counts, and the reporting dashboard has an Actions Breakdown card showing status across all sites and open actions by severity.

Did this answer your question?