Skip to main content

Corrective Actions Overview

Manage follow-up tasks when inspections identify issues.

What Are Corrective Actions?​

Corrective actions are tasks created to address issues found during inspections. When an inspection reveals a problem, a corrective action ensures:

  • The issue is documented
  • Someone is assigned to fix it
  • Progress is tracked
  • Resolution is verified

When Are Corrective Actions Created?​

Automatic Creation​

Corrective actions are automatically created when:

  • An inspection fails
  • A critical element fails
  • Specific conditions are met (configurable)

Manual Creation​

Create corrective actions manually:

  • During an inspection
  • After reviewing results
  • From item details
  • Standalone (not tied to inspection)

Corrective Action Workflow​

Basic Flow​

Issue Identified → Action Created → Assigned → In Progress → Completed → Verified

Status States​

StatusDescription
OpenNewly created, not started
In ProgressWork has begun
CompletedWork finished, pending verification
VerifiedConfirmed resolved
ClosedNo longer relevant

Key Concepts​

Priority Levels​

PriorityDescriptionExpected Response
CriticalSafety risk, must fix immediatelySame day
HighImportant, fix soon1-3 days
MediumShould address1 week
LowMinor issueWhen convenient

Assignment​

Each action is assigned to:

  • A specific user
  • Or a team/role
  • With optional due date

Due Dates​

Due dates help ensure timely resolution:

  • Set based on priority
  • Can be adjusted
  • Triggers reminders
  • Appears in reports

Where to Find Corrective Actions​

Corrective Actions List

Corrective Actions Page​

  1. Go to Corrective Actions in main navigation
  2. View all actions
  3. Filter by status, priority, assignee

On Items​

  1. Open item details
  2. View Corrective Actions tab
  3. See actions for that item

On Inspections​

  1. Open inspection results
  2. See related corrective actions
  3. Create new actions if needed

Dashboard​

Widget shows:

  • Open actions count
  • Overdue actions
  • Recently completed

Permissions​

Who Can Create​

  • Anyone performing inspections
  • System (automatic from failures)
  • Managers and admins

Who Can Edit​

  • Action creator
  • Assignee
  • Managers and admins

Who Can Complete​

  • Assignee
  • Managers and admins

Who Can Verify​

  • Managers and admins
  • Original inspector (if different from assignee)

Corrective Action Components​

Required Information​

  • Title/Description
  • Related item
  • Priority
  • Assignee

Optional Information​

  • Due date
  • Category
  • Detailed description
  • Attachments
  • Related inspection

Attachments​

Support for:

  • Photos of issue
  • Documents
  • Before/after images
  • Work orders

Integration with Inspections​

Failed Inspections​

When inspection fails:

  1. Failure recorded
  2. Corrective action created
  3. Assigned based on rules
  4. Item status updated

Inspection Elements​

Link actions to specific elements:

  • Which check failed
  • Expected vs actual
  • Photos from inspection

Re-Inspection​

After resolution:

  • Perform new inspection
  • Verify issue resolved
  • Link to corrective action
  • Complete action if passed

Benefits​

For Organizations​

  • Ensure issues are addressed
  • Track compliance
  • Document resolutions
  • Prevent recurring issues

For Managers​

  • Visibility into open issues
  • Monitor team workload
  • Prioritize resources
  • Track metrics

For Inspectors​

  • Clear follow-up tasks
  • Document their work
  • Close the loop on issues

Reporting​

Corrective Action Reports​

Track:

  • Open vs closed
  • Average resolution time
  • Overdue rate
  • By priority
  • By location
  • By assignee

Trend Analysis​

  • Issues over time
  • Resolution efficiency
  • Recurring issues
  • Improvement metrics

Configuration Options​

Automatic Creation​

Configure when actions are auto-created:

  • On any failure
  • On critical failures only
  • Based on element type
  • Based on item type

Default Assignment​

Set default assignees:

  • By location
  • By item type
  • By failure type

Due Date Rules​

Set due dates automatically:

  • Based on priority
  • Based on item type
  • Based on failure type

Best Practices​

Creating Actions​

  1. Be specific about the issue
  2. Set appropriate priority
  3. Assign to capable person
  4. Set realistic due date
  5. Attach supporting documentation

Managing Actions​

  1. Review regularly
  2. Follow up on overdue
  3. Verify completions
  4. Document resolutions
  5. Look for patterns

Closing Actions​

  1. Confirm work completed
  2. Verify issue resolved
  3. Document resolution
  4. Consider follow-up inspection
  5. Close the action

Next Steps​