DemandFlow Support Centre

AUDIT: Audit

ReferenceEntity Reference16/04/2026Updated 16/04/2026
An internal or external audit record covering scope, schedule, team, and overall conclusion with linked findings and corrective actions.

AUDIT: Audit

An internal or external audit record covering scope, schedule, team, and overall conclusion with linked findings and corrective actions.

Default definition. This article describes the default AUDIT 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 AUDIT.

Entity properties

PropertyValue
Entity codeAUDIT
Display nameAudit
PluralAudits
Level90000

Use cases

AUDIT is the parent entity for the audit programme required by ISO 9001 clause 9.2 and ISO 27001 clause 9.2. Each audit has a type (Internal, External, Certification, Surveillance), scope, criteria, and team. The schedule fields (plannedDate, actualDate) support audit programme planning. Status tracks the audit lifecycle from Planned through to Closed. The Findings panel shows child AUDITFINDING records via comboKey SUB|AUDIT. The Actions panel shows AUDITACTION records raised from this audit. The conclusion and summary fields capture the overall audit outcome.

Fields

General: Audit Details

FieldTypeRequiredNotes
nametextYesAudit Title. Placeholder: e.g. ISO 9001 Internal Audit Q2 2026.
auditTypeenumYesAudit Type. Valid ids: internal (Internal), external (External), certification (Certification), surveillance (Surveillance), supplier (Supplier Audit).
standardmultiselectStandard(s).
statusenumYesStatus. Valid ids: planned (Planned), inProgress (In Progress), awaitingReview (Awaiting Review), completed (Completed), closed (Closed).

General: Schedule

FieldTypeRequiredNotes
plannedDatedatePlanned Start Date.
plannedEndDatedatePlanned End Date.
actualDatedateActual Start Date.
actualEndDatedateActual End Date.

General: Scope & Criteria

FieldTypeRequiredNotes
scopetext (multi-line)YesProcesses, departments, or areas to be audited
criteriatext (multi-line)Standard clauses, policies, or procedures being audited against

General: Audit Team

FieldTypeRequiredNotes
leadAuditorreference → userYesLead Auditor.
auditTeamarray of references → userAudit Team.
auditeetextAuditee / Department.
auditeeContactreference → userAuditee Contact.

General: Certification Body

FieldTypeRequiredNotes
certBodyreference → VENExternal certification body (for external/certification audits)
externalAuditorNametextExternal Auditor Name.

Conclusion: Audit Outcome

FieldTypeRequiredNotes
conclusionenumOverall Conclusion. Valid ids: conforming (Conforming), minorNC (Minor Non-conformities), majorNC (Major Non-conformities), notApplicable (Not Applicable).
summarytext (multi-line)Executive Summary.

Conclusion: Statistics

FieldTypeRequiredNotes
totalFindingsnumberTotal Findings.
majorNCsnumberMajor NCs.
minorNCsnumberMinor NCs.
observationsnumberObservations.
opportunitiesnumberOpportunities for Improvement.
positiveFindingsnumberPositive Findings.

Conclusion: Recommendations

FieldTypeRequiredNotes
recommendationstext (multi-line)Recommendations.

Attachments

FieldPanelAllowed typesMax files
(unnamed)Documentsanymultiple

Relationships

  • Lookups: certBody points at a VEN record.
  • Related lists: AUDITFINDING (format SUB|AUDIT), AUDITACTION (format SUB|AUDIT).
  • Activity: activity timeline panel attached.

Creating a Audit via the API

POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json

{
  "entity":   "AUDIT",
  "level":    90000,
  "comboKey": "SUB:<your-sub-id>|ENT:",
  "name": "Audit Title",
  "auditType": "internal",
  "status": "planned",
  "scope": "Audit Scope"
}

Listing Audits records

GET /v1/entities/AUDIT/SUB

See also

auditaudits

Was this article helpful?

← Back to Knowledge Base