Every finding in your response marked accept, strengthen or rewrite, with the reason given and the evidence an auditor will expect attached to each one.
An audit finding response review is a check of the corrective action response you have already drafted, carried out before it is submitted to your certification body. Each finding is marked accept, strengthen or rewrite, with the reason stated and the evidence an auditor will expect attached to each one. It exists because a rejected response costs you time you may not have inside a closure window, and resubmission is scrutinised harder than the first attempt.
A rejection costs more than the rework it creates. You lose days inside a closure window that was already short, and the certification body reads everything you send afterwards more closely. A response that comes back once gets scrutinised harder the second time.
You have written the response. This checks it against what an auditor will look for, and returns it marked up and ready to submit. Delivered remotely, usually faster than the investigation itself, and quoted on scope.
Every finding in the response receives one of three verdicts, so you know exactly where the work is and where it is not.
| Verdict | What it means | What you receive |
|---|---|---|
| Accept | The response addresses the finding, the cause is sound and the evidence will demonstrate closure. | Submit as written. |
| Strengthen | The substance is right but something is thin, usually the preventive action or the closure evidence. | Specific additions supplied, no rewrite needed. |
| Rewrite | The root cause is a symptom, or the action would not prevent recurrence. | Replacement wording supplied, and the investigation revisited where needed. |
Nine questions are applied to every finding in the response.
Responses frequently answer a slightly different question from the one raised, usually a narrower one. The finding wording is the specification.
Human error and lack of training describe what happened. They do not explain why the system allowed it, which is the question an auditor is asking. A response resting on either will usually be challenged.
Auditors expect all three and expect them distinguished. A response that only corrects the instance found is incomplete.
The link between the stated cause and the stated action has to be visible. Actions that would not prevent the cause recurring get rejected even when the cause is correct.
The same risk on other lines, products, shifts or sites has to be addressed, or explicitly ruled out with a reason.
A revised procedure proves a document changed. Evidence has to show the change implemented and working.
Dates set to fit the closure window instead of the work, and actions with no named owner, are both common causes of rejection.
The response should state when and how the business will confirm the action worked, and who signs that off.
Certification bodies and customers each have their own response formats and portals. A strong response in the wrong structure still creates friction.
These eight account for most rejections. Each is checked explicitly before anything is marked accept.
A finding about label approval across the site is answered with a fix for one product. The auditor raised the finding at the scope they wrote it at, and that is the scope the response has to meet.
Operator error, forgot, did not follow the procedure. All describe the event. None explain why the system permitted it, which is the question being asked.
A cause is stated correctly and then the action addresses something else. The reasoning chain has to be visible from finding, to cause, to action.
A single line saying the action will be applied across the site, with nothing indicating it has been assessed anywhere else.
Training attendance sheets, a revised procedure, a photograph of a new sign. All prove something happened. None prove the nonconformity cannot recur.
Actions dated before the submission date with no completion evidence attached read as a plan written to satisfy the deadline, not a record of work done.
A response that does not acknowledge the finding is a repeat, or explain why the earlier action failed, invites a much harder conversation.
Free text where the portal expects structured fields, or a narrative where an 8D is expected. It does not change the substance and it does delay acceptance.
Certified operations preparing to submit a corrective action response, and businesses responding to a customer audit or a regulatory inspection. It suits any situation where a rejection would cost more than the review does.
You have drafted a response and want it checked before submission.
A previous response was rejected and you cannot afford a second rejection.
The closure window is short and there is no time for a failed attempt.
The finding is a major and the consequence of getting it wrong is certification.
Several findings came from one audit and you suspect the responses conflict.
The person who wrote the response is new to the certification process.
A customer has asked for an 8D and you do not normally use that format.
A finding is a repeat and you need the response to acknowledge that properly.
You send the audit report with the findings as written, your drafted response, and the closure deadline.
Each response is read against the finding it answers, at the scope the auditor raised it at.
The stated root cause is tested for whether it is a system reason and not a description of what happened.
Actions are checked against the cause, and closure evidence against whether it would demonstrate effect and not merely activity.
Each finding is marked accept, strengthen or rewrite, with the reason stated.
Wording is supplied for anything marked strengthen or rewrite, so the response can be corrected and submitted directly.
The review checks a response you have written. Carrying out the investigation itself is CAPA and root cause analysis support, quoted separately.
Where a finding needs a fresh investigation, we say so plainly. A well written response built on the wrong cause only delays the rejection.
Submission is made by you, so the response is signed off by the business that owns it.
Every review is quoted against your own scope. One minor finding and a set of majors with a short window are very different pieces of work. These factors set the price.
These are the primary sources this work is built on. Where a market you sell into has its own requirement, that takes precedence and we assess against it.
It is a check of the corrective action response you have drafted, carried out before you submit it to your certification body. Each finding in the response is marked accept, strengthen or rewrite, with the reason given and the evidence an auditor will expect identified. The purpose is to have the response accepted first time, so you never discover the problem after submission.
CAPA support carries out the investigation and builds the response from the finding. This service starts from a response you have already written and checks it. If you have done the work and want it verified before submission, this is the shorter and cheaper route. If you have a finding and no response yet, CAPA support is the right service.
Restate the finding as written, record what was done immediately with affected product and process, investigate why the failure was possible instead of who was involved, define corrective action that removes that cause, define preventive action covering the same risk elsewhere, attach evidence demonstrating the actions were implemented and effective, and state when effectiveness will be reviewed. Submit it in the format your certification body requires.
A visible chain from the finding, to a cause that is a system reason and not a person, to actions that would plausibly prevent recurrence, to evidence that demonstrates the actions worked. They also check that correction, corrective action and preventive action are separated, that dates and owners are realistic, and that an effectiveness review is defined.
It depends on your scheme, the grade of the finding and your certification body. Major nonconformities generally carry a short window measured in weeks, and minor ones are often reviewed at the next audit. Your audit report states the window that applies to you, and that is the figure to work to.
You resubmit, usually with less time remaining and with the certification body reading more closely. A rejection normally signals that the root cause did not convince them, so a resubmission built on a fresh investigation stands a better chance than a rewrite of the same argument. This review exists to avoid that position.
Yes, and it is usually better. Findings from one audit often share an underlying cause, and reviewing them together shows where responses contradict each other or where a systemic cause has been split into several unrelated ones.
No. Submission is made by you, so the response is signed off by the business that owns it. The review returns the response marked up and ready, and you send it.
As part of a response, yes. As the whole response, rarely. Retraining relies on memory and attention, which are the things that failed. A strong response usually changes something structural and retrains people on the change.
You receive replacement wording, and where the problem sits in the investigation we explain what the analysis missed. Where a finding needs a fresh investigation, we say so plainly. A well written response built on the wrong cause only delays the rejection.
Yes. The same review applies to customer audit responses, regulatory inspection responses and internal audit findings. What changes is the format and who has to be satisfied, both of which are confirmed at the start.
A marked up assessment covering every finding in the response, each with an accept, strengthen or rewrite verdict, the reason for it, the evidence an auditor will expect, and replacement wording wherever it is needed. It is written so you can act on it directly and submit.
Confi Food assigns work by subject. HACCP, labelling, certification standards, regulatory compliance, supplier assurance and monitoring are separate disciplines, and each piece goes to someone who works in that area. Every deliverable is reviewed internally by a second specialist before it reaches you.
Our technical positions are built from primary sources, meaning the legislation, the competent authority, Codex Alimentarius, the certification scheme owner or the relevant standards body. We set out how that works in our technical review and editorial policy, and what happens at each stage of an engagement in how Confi Food works.
Structured root cause analysis and corrective action planning for findings that need to close properly and stay closed.
Read about CAPA and Root Cause Analysis Support →Hands on support closing a major nonconformity inside the window your certification body has given you.
Read about Major Nonconformity Support →Certificated course covering investigation method, action planning and closure evidence.
View Certified Root Cause Analysis and CAPA Specialist →Expert IFS Food consulting worldwide. Version 8 gap assessments, certification prep, mock audits, Higher Level grading and ongoing compliance for food manufacturers.
See IFS Food Consulting →Send the audit report and your drafted response, and receive a written quote covering the scope, the timeline and the price.