Fill in the eight sections of your response to an audit finding. The builder flags empty sections, a root cause that stops at a person, training as the only fix and evidence written as a plan. Then it gives you a clean response to copy or print. Each flag comes with an example of a better answer.
Nothing you type leaves your browser. Clearing or closing the page removes it.
What it checks
| Section | What it flags |
|---|---|
| Requirement and finding | Empty, or too short to be the exact wording and the objective evidence. |
| Correction | Too short to say what was fixed, or reads like a system change instead of a fix for the instance found. Checking all parts made since the problem started counts as part of the correction. |
| Root cause | Blames a person, leans on lack of training, or names no process, responsibility or check. |
| Extent | Does not say what you checked beyond the sample. |
| Corrective action | Training or reminders as the only action, or no change to the system. |
| Owner and due date | No date. |
| Evidence | Written as a plan, or names no records. |
Worked example
The example is made up. A torque wrench was in use past its calibration due date. The root cause says the technician forgot to send it out, the corrective action says to remind all technicians, and the evidence says the records will be reviewed at the next audit. The extent section is empty.
The builder passes the requirement, the finding and the correction. It flags the root cause as stopping at a person, the extent as missing, and the corrective action as weak because reminders fade. It flags the owner line for having no date, and the evidence for being a plan. A stronger answer asks why the system relied on a technician remembering, and changes the calibration schedule or the check so it does not.
Why responses get sent back
A finding is a system failure found in a sample. The response has to fix the instance, show you looked beyond the sample, change the system and prove it worked. Responses that end at a person or at training come back, because nothing in the system changed. The path is laid out in audit finding, and the difference between the fix and the corrective action is in corrective vs preventive action.
The builder reads the words you wrote. It cannot tell if the content is true or if it satisfies a specific requirement. Follow your auditor's or registrar's response format and deadlines first. This is a screening check, not a review.