Browse docs
3. Digitize, inspect, and improve

Compliance and flags

Last updated: June 2026

Learn how to view audit flags, assign and start work, create linked tasks, and close flags through review.

What you'll need

- A LambdaAssetCheck account with appropriate role - Access to audit flags - (To change flag status) flags.update permission (typically site manager or admin) - (To assign flags) flags.assign permission - (To create tasks from a flag) task create permission for your role

What is a flag?

An audit flag is a compliance finding raised from an inspection — usually when an answer is marked non-compliant or has a “raise flag” action on its response option.

Flags are not the same as incidents (events reported directly by users). For incidents, see Incidents.

Each flag has:

- Audit type — which audit program the source inspection belonged to (e.g. Safety Audit, Maintenance Audit) - Severity — how urgent the finding is (Critical, High, Medium, Low) - Status — workflow from NEW through CLOSED

Viewing audit flags

Web app

Step 1: Navigate to flags

- Click Flags under Work in the navigation menu - Or go to /flags

Step 2: Browse flags

- View the list of audit flags you can access - Filter by status, severity, or assigned user - Use My flags when you only want items you are involved in - The Audit type column shows which program each flag belongs to (e.g. Safety Audit)

Step 3: View flag details

- Click a flag to open details - See source inspection, answers, photos, linked tasks, and assignment

Example:

1. Go to Flags
2. Filter Status: NEW
3. Filter Severity: HIGH
4. Scan the Audit type column for "Safety Audit"
5. Open flag FLAG-2024-001

PWA

Open Flags from the menu and use the same filters and detail view on mobile.

Starting work on a flag

To show that someone has taken ownership and work has started:

Web app

Step 1: Open the flag

- Go to Flags - Click the flag - Review details, source inspection answers, and photos

Step 2: Assign (if needed)

- Click Assign Flag (header) or Assign (Assignment card) - Choose the person responsible for remediation - Save

Step 3: Move status to In progress

- In the Status card, use Change status - Select IN PROGRESS - Requires flags.update permission (typically site manager or admin)

You can create linked tasks at any time (see below).

Example:

1. Open flag FLAG-2024-001 (status NEW)
2. Assign to Jane Smith
3. Change status to IN PROGRESS
4. Click Create Task and add remediation work

PWA

Use the same flow on the flag detail screen: assign the flag, then change status to IN PROGRESS if your role has permission to update flags.

Adding tasks (remediation)

Remediation work is tracked as tasks linked to the flag (not a separate “Corrective Actions” tab).

Web app

Step 1: Open the flag

- Go to Flags → open the flag

Step 2: Create a task

- Click Create Task (header or Tasks section) - Enter title, description, assignee, priority, and due date - Save — the task is linked to this flag

Step 3: Complete tasks

- Open each task from the flag’s task list - Complete work and record closure details on the task (root cause and resolution where required)

Example:

Flag: "Safety guard missing" (IN PROGRESS)
Task: "Install safety guard on pump P-101"
  Assigned to: John Doe
  Due date: 2026-06-15
  Status: COMPLETED (with closure root cause + resolution)

PWA

Open the flag and create tasks the same way when Create Task is available for your role.

Resolving flags

Flags are closed after remediation tasks are done and, when required, a reviewer approves the flag.

Web app

Step 1: Complete linked tasks

- Finish every task linked to the flag (or cancel tasks that are no longer needed) - Completed tasks should include closure root cause and resolution where your process requires it

Step 2: Send flag to review

- In Status, change the flag to REVIEW when remediation is ready for verification - Requires flags.update

Step 3: Review and close

- The assigned reviewer (or a user with flags.review) sees Approve & close and Send back (in progress) in the Status card - Approve & close sets the flag to CLOSED (review notes required) - Send back returns the flag to IN PROGRESS for more work (review notes required)

Users with flags.update can also change status from the dropdown (for example to CLOSED or IN PROGRESS from REVIEW); moving out of REVIEW to CLOSED or IN PROGRESS prompts for review notes.

Closing rules (summary):

- At least one linked task must exist before the flag can close - All linked tasks must be COMPLETED or CANCELLED - At least one completed task must have closure root cause and resolution recorded

Example:

1. Complete task "Install safety guard"
2. Change flag status to REVIEW
3. Reviewer adds notes and clicks Approve & close
4. Flag status becomes CLOSED

PWA

Follow the same status and task completion steps on the flag detail screen when those actions are available for your role.

Flag lifecycle

Status flow

NEW → IN PROGRESS → REVIEW → CLOSED

StatusMeaning
NEWFlag was raised from an inspection; not yet in active remediation
IN PROGRESSSomeone is working on remediation (tasks, assignment)
REVIEWRemediation is ready for reviewer approval or send-back
CLOSEDFlag is closed after review (or permitted status change)

Linked task flow

Tasks use the standard task statuses (PENDING, IN_PROGRESS, ON_HOLD, BLOCKED, COMPLETED, CANCELLED, etc.). Flag closure depends on linked tasks being finished, not on a separate “corrective action” entity.

Audit types and severity

Audit type (program)

Flags inherit audit type from the inspection template used for the source inspection.

- Example: A “Maintenance Procedures” template linked to audit type Safety Audit → flags show Safety Audit in the list - Use the Audit type column on the Flags page to see how many open findings belong to each program - Administrators manage audit types under Templates → Template Configurations → Audit Types

There is no separate flag category to maintain. Audit type is the classification dimension for flags.

Severity (priority)

Severity is set on the response option in the template (or when the flag is raised) and drives urgency and due dates.

SeverityTypical use
CriticalImmediate risk; escalate quickly
HighSignificant compliance or safety gap
MediumShould be addressed in normal cycle
LowMinor finding; track and close

Filter by severity on the Flags page to focus on the highest-risk items first.

Frequently asked questions

What is an audit flag?

A compliance issue identified during an inspection that requires corrective action.

How are audit flags created?

Automatically when inspection answers have the raise flag action on their response option.

How do I add remediation work?

Open the flag and click Create Task. Tasks are linked to the flag and tracked on the flag detail page.

How do I close a flag?

Complete (or cancel) all linked tasks, move the flag to REVIEW, then have a reviewer Approve & close, or use permitted status changes with review notes.

What is audit type vs severity?

Audit type = which inspection program (Safety Audit, etc.). Severity = how urgent the finding is. Both appear on the Flags list.

Can I delete a flag?

Flags are not deleted; they are closed and kept for audit history.

What happens if I don't resolve a flag on time?

Overdue flags are highlighted in lists and dashboards where overdue filtering is available.

- Incidents — Reporting events (separate from flags) - Start, edit, and complete inspections - Work management

Need help? Use Support → Report an issue in the app to raise a ticket, or email support@lambdaassetcheck.com.

Was this page helpful?

Top