AUDITACTION: Corrective Action
A corrective or preventive action raised from an audit finding, nonconformity, or incident, with root cause analysis and effectiveness verification.
Default definition. This article describes the default
AUDITACTION definition shipped with DemandFlow. Administrators can add, remove, rename, or re-type fields, change which ones are required, and alter the layout from the Definitions screen in Settings. Your tenant's current schema may differ from what is shown here. To read the current definition at any time, GET the DEFINITION object whose id matches AUDITACTION.Entity properties
| Property | Value |
|---|---|
| Entity code | AUDITACTION |
| Display name | Corrective Action |
| Plural | Corrective Actions |
| Level | 90010 |
Use cases
AUDITACTION is the CAPA (Corrective And Preventive Action) entity required by ISO 9001 clause 10.2 and ISO 27001 clause 10.1. It tracks the full lifecycle from identification through root cause analysis, action planning, implementation, and effectiveness verification. The actionType field distinguishes corrective (fix the problem) from preventive (stop it recurring) actions. Source traceability is provided via objectLookup links to AUDIT, AUDITFINDING, and NCREPORT.
Fields
General: Action Details
| Field | Type | Required | Notes |
|---|---|---|---|
name | text | Yes | Action Title. |
actionType | enum | Yes | Action Type. Valid ids: corrective (Corrective Action), preventive (Preventive Action), improvement (Improvement). |
status | enum | Yes | Status. Valid ids: open (Open), investigating (Investigating), planned (Action Planned), inProgress (In Progress), implemented (Implemented), verified (Verified Effective), closed (Closed). |
priority | enum | Priority. Valid ids: critical (Critical), high (High), medium (Medium), low (Low). |
General: Source
| Field | Type | Required | Notes |
|---|---|---|---|
sourceAudit | reference → AUDIT | Source Audit. | |
sourceFinding | reference → AUDITFINDING | Source Finding. | |
sourceNCR | reference → NCREPORT | Source Nonconformity. | |
isoClause | text | ISO Clause Reference. Placeholder: e.g. 9001:2015 clause 8.5.1. |
General: Assignment
| Field | Type | Required | Notes |
|---|---|---|---|
assignedTo | reference → user | Yes | Assigned To. |
dueDate | date | Yes | Due Date. |
completedDate | date | Completed Date. |
General: Description
| Field | Type | Required | Notes |
|---|---|---|---|
description | text (multi-line) | Yes | Describe the nonconformity, problem, or opportunity for improvement |
immediateContainment | text (multi-line) | What was done immediately to contain the issue |
Root Cause & Action Plan: Root Cause Analysis
| Field | Type | Required | Notes |
|---|---|---|---|
rcaMethod | enum | RCA Method Used. Valid ids: 5why (5 Whys), fishbone (Fishbone / Ishikawa), fta (Fault Tree Analysis), pareto (Pareto Analysis), other (Other). | |
rootCause | text (multi-line) | The underlying root cause identified through analysis | |
contributingFactors | text (multi-line) | Contributing Factors. |
Root Cause & Action Plan: Action Plan
| Field | Type | Required | Notes |
|---|---|---|---|
correctiveAction | text (multi-line) | What actions will be taken to correct the nonconformity | |
preventiveAction | text (multi-line) | What actions will prevent recurrence | |
processChanges | text (multi-line) | Any policies, procedures, or work instructions that need updating |
Verification: Effectiveness Verification
| Field | Type | Required | Notes |
|---|---|---|---|
verificationMethod | text (multi-line) | How will you verify the action was effective? | |
verificationDate | date | Verification Date. | |
verifiedBy | reference → user | Verified By. | |
effectivenessRating | enum | Effectiveness Rating. Valid ids: effective (Effective), partiallyEffective (Partially Effective), notEffective (Not Effective), pending (Pending Verification). |
Verification: Verification Evidence
| Field | Type | Required | Notes |
|---|---|---|---|
verificationEvidence | text (multi-line) | Describe the evidence that demonstrates the action was effective | |
recurrenceCheck | boolean | Recurrence confirmed prevented. | |
lessonsLearned | text (multi-line) | Lessons Learned. |
Attachments
| Field | Panel | Allowed types | Max files |
|---|---|---|---|
(unnamed) | Documents | any | multiple |
Relationships
- Lookups:
sourceAuditpoints at aAUDITrecord;sourceFindingpoints at aAUDITFINDINGrecord;sourceNCRpoints at aNCREPORTrecord. - Activity: activity timeline panel attached.
Creating a Corrective Action via the API
POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json
{
"entity": "AUDITACTION",
"level": 90010,
"comboKey": "SUB:<your-sub-id>|ENT:",
"name": "Action Title",
"actionType": "corrective",
"status": "open",
"description": "Nonconformity / Problem Description"
}Listing Corrective Actions records
GET /v1/entities/AUDITACTION/SUB