Most actions are raised automatically by a checklist, audit or risk assessment. Sometimes you just need to create one directly — a repair someone mentioned, a job from a site walk, anything that needs an owner and a deadline.
From the Actions page
Available to admins and client admins.
Go to Work > Actions.
Choose Add action.
From the Work page
Available to anyone who can see Work, and usually the quicker route.
Go to Work.
Choose Add, then Action.
This opens the same form, with your current site and your own name filled in as a starting point.
Filling in the form
The dialog is titled Add action, described as "Create an action for a site without an audit report."
Sites — required. Pick one or more.
Title — required. Keep it short and specific, along the lines of the example shown: "e.g. Update cleaning schedule".
Description — required. Explain what needs doing and why, so the owner isn't left guessing.
Owner — required. The person responsible. They'll be notified.
Due date (optional) — a date and time. Worth setting, because it's what drives reminders and the overdue flag.
Finish with Create action.
Creating the same action for several sites
Select multiple sites and ASR creates a separate action for each one, all with the same title, description and owner. That's the right approach for something every site has to do — each site then gets its own action to close, so you can track them individually.
If something's missing
The form tells you what it needs:
"At least one site is required"
"Title is required"
"Description is required"
"Owner is required"
If Add action is greyed out on the Actions page, it's because the organisation has no sites set up yet, or no users who could own an action.
What happens next
You'll see Action created and go straight to the new action, where you can add more detail or start recording progress.
It now appears in Work > Actions with a Site action badge, counts towards the open actions badge on Work, and shows up for its owner.
If you created actions for several sites and only some worked, you'll see a message telling you how many failed so you can retry the rest.
Raising an action from something else instead
If the job came out of a check or an inspection, raise it from there rather than creating it here. The action then keeps a link back to the task or finding that caused it, which is much better evidence later. See Where actions come from.