Work
What are flags?
Learn how audit flags work in LambdaAssetCheck, so findings raised from inspections are assigned, remediated with tasks, reviewed, and closed with a clear record.
Last updated: October 2026
What you'll need
| Tier | All plans |
| Platform | Web app (same flows on phone) |
| Permission | flags.read to view. flags.update to change status. flags.assign to assign. flags.review, the assigned reviewer, or the inspection's conductor when no reviewer is recorded, to approve or send back. Task create permission to add remediation tasks. |
| Where | Work Management → Flags |
A flag is raised when a response option is set to raise a flag on an audit inspection. A logic rule with the raise-flag action does the same and can set the severity. Asset inspections raise work, not flags. Incident inspections do not raise flags. Flags are not the same as incidents.
What a flag is
An audit flag is a compliance finding from an inspection answer. Each flag has:
- Audit type — from the source audit template (for example Safety Audit)
- Severity — Critical, High, Medium, or Low
- Status — NEW → IN PROGRESS → REVIEW → CLOSED
View flags
1. Open Work Management → Flags. 2. Filter by status, severity, or assignee. My flags limits the list to flags you are involved in. Roles with flags.view_own always see only those. Other roles see flags at their sites; owners and admins see the organisation. 3. Open a flag for the source inspection, answers, photos, tasks, and assignment.
Assign and start work
1. Open the flag. 2. Select Assign Flag (header) or Assign (Assignment card). The list includes only people who can own a flag at that site. 3. In Status, use Change status and select IN PROGRESS (needs flags.update).
Add tasks
1. Open the flag. 2. Select Create Task. 3. Enter title, description, assignee, priority, and due date, then save. 4. Complete each task from the flag's task list. Every task on the flag needs a root cause and a resolution.
Remediation is tracked as tasks linked to the flag — there is no separate corrective-actions tab.
Resolve and close
Status flow: NEW → IN PROGRESS → REVIEW → CLOSED.
1. Complete or cancel every linked task. 2. Change the flag to REVIEW when remediation is ready. 3. The reviewer uses Approve & close or Send back (in progress) — review notes are required either way. That person has flags.review, is the assigned reviewer, or conducted the source inspection when no reviewer is recorded.
Before review or close, the product requires:
- At least one linked task - Every linked task COMPLETED or CANCELLED - A root cause and a resolution on every COMPLETED task (cancelled tasks do not need them)
The flag moves to REVIEW only when those conditions are met. A flag cannot go to review while one task has a root cause and resolution and another completed task does not.
Users with flags.update can also move status from the dropdown. Review is not offered while the flag is New. Leaving REVIEW for CLOSED or IN PROGRESS still prompts for review notes.
Audit type and severity
On an audit, Audit type comes from the template. Admins manage types under Templates → Template Configurations → Audit Types. There is no separate flag-category list.
Severity comes from the response option — its flag severity, or that option's work priority when severity is not set — or from the audit logic rule. The default is Medium. You cannot raise a flag by hand.
Frequently asked questions
How are flags created?
When an answer on an audit template uses a response option with the raise-flag action. An audit template can also raise one from a logic rule. Asset templates raise work instead. Incident templates do not raise flags.
Can I delete a flag?
No. Close it and keep the history.
What if a flag is overdue?
The list shows the due date as plain text. There is no overdue highlight or filter. Overdue counts appear in the flag summary figures.
Related articles
- What are incidents? - What are inspections? - What is work management? - Create a template
Was this page helpful?
