Knowella

Audit Follow Up Record

The recurring failure is closing findings on paper the day the corrective action is written, not on the day the fix is actually verified working. Evidence Provided gets marked Yes because a revised procedure was emailed round, Verified On Site never gets a real answer, and the same nonconformity resurfaces at the next audit wearing a new finding reference, with nobody able to say whether anything actually changed on the floor.

KnowComplyReviewCMP-005Pinned in navigation42 fields across 4 sectionsFull researchSee the form

Reviewed by Siddarth SinghCSPLast reviewed 16 August 2026

Basis
ISO 19011 cl.6.7
Workspace
KnowComply
Form type
Review
Completed by
Carried out by the auditor, 30 to 90 days after the audit
Review trigger
At the review interval, and after any trigger event

The short version

  • A follow up record checks whether findings were actually closed and the fix works, run 30 to 90 days after the original audit — not immediately, so the fix has had time to either hold or fail.
  • Scoring is Closure Percent, where high is good, but the template also separately tracks Critical Or Major Still Open and Weak Actions Accepted so a high closure rate built on weak fixes doesn't read as success.
  • Action Strength scores Eliminate or engineer at 4 and Reminder or reissue at 0 — the form is built to penalise closing a finding with a memo rather than a process change.
  • Verified On Site scores above Record only, which itself scores above No — evidence filed in a folder is treated as weaker than evidence an auditor actually walked the floor to confirm.

What this is

What is an audit follow up record?

What is an audit follow up record?

An audit follow up record is a review, carried out 30 to 90 days after an audit, that checks whether each finding raised was actually closed and whether the fix works — not just whether a corrective action was written. It is built against ISO 19011 cl.6.7 and scores a closure percentage across the whole batch of findings from one audit.

How is a follow up different from closing a single finding?

Closing a single finding (on the Audit Finding Record, CMP-004, or a linked CAPA) is a one-off action against one nonconformity. The follow up record looks across every finding from a specific audit at once — closure percent, average days to close, how many actions were genuinely strong versus a reminder — so a pattern of weak, repeat or overdue closures is visible at the programme level.

What does ISO 19011 clause 6.7 actually require?

Clause 6.7 requires the programme owner to monitor the status of corrective actions arising from findings and confirm their completion and effectiveness, within an agreed timeframe. It is the clause that stops a finding being closed the moment a corrective action plan is submitted, rather than when the plan has actually worked.

Scope

When is an audit follow up record required?

This review looks backward at findings from a specific audit that already happened. Using it to raise or close a single finding, rather than to check a batch of them, produces a review that duplicates work the finding record and CAPA process already do.

Use this template when

  • A previous audit (CMP-002) raised findings that are now due, or close to due, for closure
  • 30 to 90 days have passed since the audit, giving corrective actions time to actually be tested rather than just written
  • You need a closure percentage and pattern across a batch of findings, not just the status of one
  • A linked record needs this one to exist: links Audit, CAPA
  • The next audit is approaching and unclosed findings from the last one need to be checked before it starts

Do not use it for

  • Internal Audit Programme, which sets out what will be audited, when, by whom and against which standard, across the whole year.
  • Internal Audit Report, which records an audit against a standard or process, with findings and evidence, at the time it happens.
  • Audit Plan, which sets out the scope, criteria, schedule and people involved before a single audit begins, not after.
  • Audit Finding Record, which records one finding's own detail and evidence — use that to close a single item, this one to check the batch.
  • Anything outside KnowComply, which belongs in the workspace that owns that process

Compliance mapping

Which ISO 19011 cl.6.7 requirements does this satisfy?

ISO 19011 cl.6.7 covers conducting the follow up: confirming that corrective actions were taken, checking they were effective, and reporting the residual risk if they were not.

ClauseRequirementWhere it lands
ISO 19011 cl.6.7Monitor the status of corrective actions arising from each finding raised in the auditFindings status
ISO 19011 cl.6.7Confirm the corrective action taken and record evidence that it was actually implementedFindings status
ISO 19011 cl.6.7 / ISO 9001 cl.10.2.2Verify the effectiveness of the corrective action, not merely that an action was takenFindings status
ISO 19011 cl.6.7Report the aggregate closure position across all findings from the auditSummary
ISO 19011 cl.6.7Escalate findings that remain open, overdue or blocked beyond the agreed timeframeEscalation
ISO 9001 cl.9.3.2 / ISO 45001 cl.9.3Feed unresolved or high-risk findings into management reviewEscalation

What it does not cover

  • Evidence Provided marked Yes with Verified On Site left as Record only or No, which means a document was filed but nobody confirmed the fix actually works where the finding happened.
  • Action Strength recorded as Retraining or Reminder or reissue against a Critical or Major grade, which the form itself scores lowest — a weak action against a serious finding is exactly the pattern this record exists to catch.
  • Days Overdue left blank on a finding past its Due Date, which hides an overdue item inside what otherwise reads as a clean closure percentage.
  • Escalation Required marked No while Critical Or Major Still Open is greater than zero, which contradicts its own summary numbers on the same record.
  • Next Follow Up Due left blank when Closure Percent is under 100, which leaves no scheduled point at which the remaining findings get checked again.

Global

Audit Follow Up Record requirements by country

ISO 19011 cl.6.7 is guidance rather than a certifiable requirement on its own, but the certifiable standards behind most audits, and the customers who rely on them, treat follow-through as the part that actually gets tested.

International

ISO 19011:2018 cl.6.7

The clause is explicit that an audit's value depends on corrective actions being confirmed as effective, not merely taken — it is the basis every certification body auditor uses to ask 'how do you know this worked' rather than 'do you have a plan'.

A follow up record that only tracks Evidence Provided, without a genuine Verified On Site answer, satisfies the letter of most internal procedures but not what cl.6.7 is actually asking for.

UK

ISO/IEC 17021-1:2015, UKAS-accredited surveillance audits

UKAS-accredited certification bodies running annual surveillance visits treat unclosed findings from the last internal audit cycle as a direct line of questioning, since they show whether the site's own follow up process actually functions.

Repeat findings appearing in Repeat Findings Since, carried over cycle to cycle, are one of the fastest routes to a major nonconformity at surveillance, independent of the original finding's own severity.

United States

GFSI-benchmarked schemes (SQF, BRCGS) and second-party customer audits

Retail and brand-owner customer audits in the US often request the follow up record directly, using closure percent and average days to close as a proxy for whether a supplier's quality system is actively managed or just documented.

A low Closure Percent or high Average Days To Close can affect supplier approval status independently of any single finding's grade, since it signals a systemic gap rather than a one-off miss.

How to complete it

How to complete an audit follow up record, step by step

The fields are simple to fill in. What decides whether the record is defensible is the judgement behind four specific answers.

Whether Verified On Site is a real inspection or a rubber stamp

Yes should mean an auditor actually walked the floor, watched the process or checked the record where the finding occurred. Record only should be used honestly when verification was desk-based — a document or photo reviewed rather than the fix observed in operation — not upgraded to Yes because the paperwork looked complete.

How Action Strength gets scored when the plan and reality diverge

Action Strength should reflect what was actually implemented at follow up, not what the corrective action plan proposed. A plan to eliminate or engineer a hazard that has not yet been built should score against what exists today — likely Supervision or verification or lower — until the change is confirmed in place.

Where the line sits between Complete and genuinely Closed

Complete and Closed both score at the top of the scale, but mean different things: Complete can mean the action was done and awaits verification, while Closed should mean Verified On Site already returned a real answer. Treating the two as interchangeable inflates Closure Percent without the verification the clause actually requires.

When Weak Actions Accepted should trigger escalation rather than just a count

The help text is explicit that a programme dominated by retraining will keep producing repeat findings. The judgement call is the threshold at which a rising Weak Actions Accepted count, on its own, should force Escalation Required to Yes even if every individual finding shows as closed.

What auditors find

Most common audit follow up record findings

These are the patterns that actually surface when follow up records are reviewed across a cycle, not theoretical gaps in the form.

FindingClauseWhat fixes it
Evidence Provided marked Yes for every finding in a batch, but Verified On Site left as Record only throughoutISO 19011 cl.6.7Require a minimum proportion of Verified On Site answers of Yes per audit batch before Closure Percent can be reported as final, rather than accepting document review alone.
A Critical grade finding closed using Retraining as the Action StrengthISO 19011 cl.6.7Block Status moving to Closed on a Critical or Major finding unless Action Strength is Supervision or verification or stronger, without a documented exception.
Days Overdue tracked per finding but never rolled up, so a site's true backlog is invisible until the next auditISO 19011 cl.6.7Surface Overdue Findings and Days Overdue on a standing dashboard, not only inside each follow up record.
Repeat Findings Since climbing across three consecutive cycles at the same site with no escalation raisedISO 19011 cl.6.7 / ISO 9001 cl.10.2Trigger Escalation Required automatically once Repeat Findings Since exceeds an agreed threshold, rather than relying on the auditor to notice.
Action Required marked Yes with CAPA ID left blankLinks Audit, CAPAMake CAPA ID a required field whenever Action Required is Yes, since it is the only link between this record and the corrective action process actually doing the work.
Feeds Management Review checked but Reported To Management Review never subsequently answeredISO 9001 cl.9.3.2Treat Feeds Management Review as an open task, reconciled against actual management review minutes before the follow up record is closed.

Case in point

Case in point: the finding that closed twice

An internal audit raised a Major finding against permit-to-work practice at a manufacturing site. The corrective action plan proposed retraining supervisors, Evidence Provided was marked Yes once the training register was filed, and the finding was marked Closed within three weeks — well inside target. Verified On Site was left as Record only.

The next scheduled audit, eight months later, raised what looked like a new finding against the same process. Only when the two records were compared did it become clear this was a repeat of the same root cause: training had been delivered, but nothing about the process had changed, so the lapse recurred under a new supervisor. Repeat Findings Since was never incremented, because the follow up had treated the first finding as fully closed rather than closed on a weak action.

The template

The template, field by field

The form exactly as it installs. Every field, option, score and conditional rule is editable, and the links to other templates come with it.

42fields
4 sections
Reference
CMP-005
Archetype
Review
Record ID
AFU-2026-000
Scoring
Closure percent
Direction
High is good
Singleton
No
Basis
ISO 19011 cl.6.7
Links
Links Audit, CAPA
Tags
Audit, Verification
Sections
4
Fields
42
Follow up fields
3
Repeating sections
1
Links out
3
Field typesOwn ID, generated on saveCase thread and parentPick list from a registryLinked to another templateFollow up, dashed outlineScored

Header

10 fields
Text

Record ID*

Generated on save

Auto sequence. Format AFU-2026-000.

The record's own ID. Other templates point at this value.

Single Choice

Status*

Scored

Drives who this goes to next.

  • Planned2 pts
  • In progress2 pts
  • Complete3 pts
  • Deferred0 pts
  • Open0 pts
  • Closed3 pts
  • Overdue0 pts
Date & Time

Date and Time*

Users

Completed By*

Pick List

Site*

From FDN-001 Site NameFilter: Status is Active
Text

Site ID*

Linked

Format SITE-000.

Links to FDN-001 Site ID

Text

Audit ID*

Linked

Links to CMP-002 Audit ID

Date & Time

Original Audit Date*

Numeric Answer

Days Since Audit*

Scored
Info

The Audit Only Pays Off Here

Findings raised and never closed cost more than not auditing, because everybody learns the process is theatre.

Findings status

Repeats9 fields
Text

Finding Reference*

Single Choice

Grade*

Scored
  • Critical0 pts
  • Major1 pt
  • Minor2 pts
  • Observation3 pts
  • Opportunity for improvement3 pts
Users

Owner*

Date & Time

Due Date*

Single Choice

Status*

Scored
  • Planned2 pts
  • In progress2 pts
  • Complete3 pts
  • Deferred0 pts
  • Open0 pts
  • Closed3 pts
  • Overdue0 pts
Numeric Answer

Days Overdue

OptionalScored
Single Choice

Action Strength*

Scored

Rewriting the procedure and retraining is weak. Changing the process so the error cannot happen is strong.

  • Eliminate or engineer4 pts
  • Process change3 pts
  • Supervision or verification2 pts
  • Retraining1 pt
  • Reminder or reissue0 pts
Single Choice

Evidence Provided*

Scored
  • Yes3 pts
  • Partly1 pt
  • No0 pts
Single Choice

Verified On Site*

Scored
  • Yes3 pts
  • Record only1 pt
  • No0 pts

Summary

9 fields
Numeric Answer

Findings Raised*

Numeric Answer

Findings Closed*

Scored
Numeric Answer

Closure Percent*

Scored
Numeric Answer

Critical Or Major Still Open*

Scored
Numeric Answer

Overdue Findings*

Scored
Numeric Answer

Average Days To Close*

Scored
Numeric Answer

Weak Actions Accepted*

Scored

Count them. A programme where most actions are retraining will keep producing repeat findings.

Numeric Answer

Effectiveness Verified*

Scored
Numeric Answer

Repeat Findings Since*

Scored

Escalation

14 fields
Single Choice

Escalation Required*

Scored
  • No3 pts
  • Yes0 pts
Single Choice

Escalated To

Optional
Department managerSite managerGroupManagement review
Single Choice

Blocker Identified

Optional

Resource, budget, conflicting priority, unclear ownership or disagreement with the finding.

NoneResourceBudgetConflicting priorityUnclear ownershipDisagreement
Checkbox

Feeds Management Review*

Single Choice

Reported To Management Review

Optional
YesNo
Date & Time

Next Follow Up Due*

Single Choice

Action Required*

Scored

Raise the action record, then enter its reference here.

  • No2 pts
  • Yes0 pts
Single Choice

Priority

OptionalScoredShows if Action Required equals Yes
  • High0 pts
  • Medium1 pt
  • Low3 pts
Text

CAPA ID

OptionalLinkedShows if Action Required equals Yes

Format CAPA-2026-00000.

Links to FDN-014 CAPA ID

Users

Action Owner

OptionalShows if Action Required equals Yes
Users

Lead Auditor*

Signature

Signature*

Users

Compliance Lead*

Signature

Second Signature*

CMP-005 · record IDs look like AFU-2026-000 · Links Audit, CAPA

Open in Knowella

Run it with agents

From a document you fill in to a programme that runs itself

The form is the easy part. Chasing overdue findings before the next audit, telling a genuine process fix from a reissued memo, and getting a real answer on Verified On Site is the work that actually slips.

KnowComply

Holds the follow up record against the original audit and its findings, tracks Closure Percent and Repeat Findings Since across cycles, and flags a site stuck at Record only.

KnowMaintain

Links Action Strength answers of Eliminate or engineer to the actual work order that changed the equipment, so a follow up record can't claim a fix that was never scheduled.

KnowSafe

Surfaces Critical Or Major Still Open findings against live risk assessments, so a hazard-related finding doesn't sit closed on paper while the underlying risk is unchanged.

Ella
Ella

Chases Days Overdue and Next Follow Up Due before they lapse, rolls escalation and repeat-finding patterns into one view, and holds every write for your approval before it touches a record.

This template lives in KnowComply — audit and governance. Audit programmes, legal register, management review, risk and certification.

Meet KnowComply→

Glossary

Audit Follow Up Record definitions and key terms

Closure percent
The proportion of findings from a given audit that have reached Closed status by the time the follow up is carried out, used here as the template's primary score, where high is good.
Action strength
A ranking of how durable a corrective action is likely to be, from weakest (a reminder or reissued instruction) to strongest (eliminating or engineering out the cause), independent of whether the action was completed on time.
Effectiveness verification
Confirming a corrective action not only happened but actually prevented the original problem recurring — the distinction between Evidence Provided and Verified On Site here.
Repeat finding
A nonconformity that reappears in a later audit against the same root cause as one already closed, usually signalling that the original corrective action addressed the symptom rather than the cause.
Second-party audit
An audit carried out by, or for, a customer rather than an internal team or accredited certification body — the audience most likely to request this record directly.

FAQ

Frequently asked questions about audit follow up record

What is the audit follow up record template based on?+

It is built against ISO 19011 cl.6.7, which covers monitoring and confirming the completion and effectiveness of corrective actions arising from audit findings.

What sections does the audit follow up record contain?+

Four sections: Header, Findings status, Summary and Escalation. Findings status repeats once for each finding being followed up from the original audit.

How soon after the audit should a follow up be run?+

30 to 90 days after the original audit — soon enough that findings haven't been forgotten, late enough that a corrective action has had time to actually hold or fail under normal operating conditions.

How is the audit follow up record scored?+

Scoring is Closure Percent, where high is good, but the template separately tracks Critical Or Major Still Open, Weak Actions Accepted and Repeat Findings Since so a high closure rate built on weak actions doesn't read as a clean pass.

What's the difference between Evidence Provided and Verified On Site?+

Evidence Provided is a document, photo or record showing an action was taken. Verified On Site means an auditor confirmed the fix in operation where the original finding occurred. The two are scored separately because one is regularly satisfied without the other.

Can the audit follow up record template be changed?+

Yes. Every field, option and score is editable, including the Action Strength ranking and escalation triggers. Most teams install it as it is, run one cycle, then adjust.

Keep going

Related templates and programmes

Siddarth Singh

Written and reviewed by

Siddarth Singh

Founder & Chief Executive Officer, Knowella

Certified Safety Professional and industrial and systems engineer with more than a decade inside food supply chain, freight and manufacturing operations. This page was written against the current text of the standards it cites, not against secondary summaries of them.

  • Certified Safety Professional (CSP), Board of Certified Safety Professionals
  • MBA, University of Chicago Booth School of Business
  • MS and BS, The Ohio State University, Industrial and Systems Engineering
  • Six Sigma Black Belt
Verify with BCSP →

Sources and last review. Reviewed 16 August 2026 against:

  • ISO 19011:2018 cl.6.7 — Conducting the audit
  • ISO 9001:2015 cl.10.2.2 — Nonconformity and corrective action, effectiveness review
  • ISO 45001:2018 cl.10.2 — Incident, nonconformity and corrective action
  • ISO/IEC 17021-1:2015 — Requirements for certification bodies

This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.

Start in Minutes, Not Weeks

Launch a Ready-Made Template and Customize It Your Way

Every template is fully editable. Adjust fields, workflows, and branding to match your processes, then deploy to your team instantly.