Skip to content
English - United States
Contact us
  • There are no suggestions because the search field is empty.

Corrective Actions: How They Work and Common Issues

Understanding the Corrective Action lifecycle, who gets notified, and what to do when CAs behave unexpectedly.

What is a Corrective Action?

A Corrective Action (CA) is a follow-up task generated when a hazard or deficiency is identified — usually during an observation, inspection, or audit. The CA tracks what needs to be fixed, who is responsible, and when it was resolved. CAs remain open until they are formally closed in the system.

 

How the Corrective Action lifecycle works

  1. A CA is created — either automatically when a failed item is noted on a form, or manually.
  2. The CA is assigned to a Responsible Party (the person who needs to fix the issue).
  3. A notification is sent to the Responsible Party and the person who created the CA.
  4. The Responsible Party addresses the issue and uploads evidence (typically a photo) to close the CA.
  5. The CA is marked as resolved/closed in the system.

 

INFO  CAs should only notify the Responsible Party and the submitter. If users outside of those two roles are receiving CA notifications, check the subscription settings for that form. See KB-004 for notification troubleshooting.

 

Common Corrective Action issues

"Corrected on the spot" CAs still showing as open

Marking a CA as "corrected on the spot" on the form itself does not automatically close the CA in the Corrective Actions list. You still need to go into the CA list, open the record, and formally close it by uploading your evidence and marking it resolved. This is current system behavior — the on-the-spot flag is informational, not a closure trigger.

 

Can't add a name to a CA from a form

Some forms have Corrective Action fields that require a name or email address for the responsible party. If the name field won't save, or saving the form as a draft clears the CA information:

  • Try leaving the name field blank and saving first, then editing the record to add the responsible party.
  • If the issue persists, contact support with the form name — this has been reported as a bug on specific form types.

 

CA count on web doesn't match mobile

If the number of open CAs shown on web differs from what the mobile app shows, try refreshing both views. If the discrepancy persists after logging out and back in on both platforms, report it to support with your account name and a screenshot of both views.

 

Receiving CA notifications for the wrong project

If you're getting CA alerts for projects you're not involved with, your notification subscription settings may be too broad. A Super Admin can audit and correct your subscriptions from the account settings. See KB-004 for more detail on managing notification subscriptions.

 

CA description field showing code instead of text

In some accounts, the CA description field displays raw code instead of the formatted text. This is a known display bug being tracked by engineering. The underlying data is intact — the issue is with how it renders on screen. Report this to support if you're seeing it, including the form name and a screenshot.

 

Closing a Corrective Action

  1. Go to the Corrective Actions list (accessible from the main menu).
  2. Find and open the CA you need to close.
  3. Upload a photo or other evidence showing the issue has been resolved.
  4. Add any relevant notes.
  5. Mark the CA as resolved/closed and save.

 

TIP  You need a photo to close most CAs. If the photo upload fails, see KB-005 for image troubleshooting. If the submit button is unresponsive when trying to close a CA, see KB-002 for form submission error guidance.

 

Need help?

Contact support@getmojo.ai with the account name, form type, and a description of the CA issue. A screenshot is especially helpful for display bugs.