Seed-stage B2B SaaS startup
Sample for a fictional organisation · 3,126 words[Company] Nonconformity and Corrective Action Procedure
- Version: 1.0
- Owner: CTO
- Approved by: CEO
- Effective date: [Effective date]
- Next review date: [Review date]
5. Correction and Cause
- Where what was found puts [Company]'s information or systems at risk until it is put right, the responsible role puts it right, or limits the harm it can do, as soon as it is found, without waiting for the nonconformity to be entered in the nonconformity log or for its cause to be found.
- The responsible role finds the cause of each nonconformity. The work done to find it is in proportion to what the nonconformity affects.
- A cause is never recorded as a person's mistake alone. Where a person's mistake led to the nonconformity, the cause records why the mistake could be made and why it was not caught.
- The responsible role also checks whether the same cause has led, or could lead, to the same nonconformity in another part of the management system, and the nonconformity log records the result. Each nonconformity found in this way is raised under section 3.
- Where a nonconformity is the same as one closed in the 12 months before it was raised, the nonconformity log names the earlier one, and the cause is found again, including why the earlier corrective action did not stop it.
6. Corrective Action
- For each nonconformity, the responsible role agrees with the CTO the correction, unless it has already been made, and a corrective action, each with a due date. Where the responsible role is the CTO, the CEO agrees them instead.
- The due date of each action on a major nonconformity is no later than 3 months after the date it was raised, and of each action on a minor nonconformity no later than 6 months after the date it was raised.
- Where a contract or the law sets an earlier date for an action, or the person outside [Company] who raised the nonconformity sets one, its due date is no later than that date.
- Only the CEO changes the due date of an action, never to a date later than one that a contract, the law or the person outside [Company] who raised the nonconformity sets, and the nonconformity log records the reason.
- A corrective action deals with the cause that section 5 finds. Telling or training staff again is a corrective action only where the cause is that they did not know what the requirement asks of them.
- Where a corrective action changes a policy or a procedure, that document is changed and approved in the way it sets for its own changes.
- Where a nonconformity shows a risk that the risk register does not record, or records as less likely or less harmful than the nonconformity shows it to be, the CTO has that risk assessed again and the risk register changed.
- The nonconformity log records the correction and the date it was made, the cause, the corrective action, the due date of each action, who agreed the actions and when, and each document and each risk that a corrective action changed.
11. Appendix A: Nonconformity Log
The nonconformity log has one entry for each nonconformity. The table gives what each entry holds.
| Field | What it holds |
|---|---|
| Reference | The reference that the audit gave it, where an audit raised it and gave it one, and otherwise a reference that is never reused |
| Raised by | What raised it, with the reference of the audit, the report or the security incident |
| Date raised | The date it was raised, as section 3 sets it |
| Requirement | The requirement that was not met, and where it is written |
| What was found | What was found, and the evidence for it |
| Responsible role | The role responsible for the part of the management system where it was found |
| Kind | Major nonconformity or Minor nonconformity, and who decided it |
| Correction | What was done to put right what was found, and the date it was made |
| Cause | The cause and, where a person's mistake led to the nonconformity, why the mistake could be made and why it was not caught |
| Elsewhere | Whether the same cause has led, or could lead, to the same nonconformity in another part of the management system, and the reference of each nonconformity raised as a result |
| Earlier nonconformity | The reference of an earlier nonconformity that this one is the same as, and why its corrective action did not stop this one |
| Corrective action | The corrective action, and who agreed the actions and when |
| Due dates | The due date of each action, and the reason for any change to a due date |
| Changes made | Each document and each risk that a corrective action changed |
| Others told | Who outside [Company] was told of it under a contract, and when |
| Check | Who checked that the actions are complete and the cause dealt with, the date and the result |
| Status | Open or Closed, and the date closed |
| Later check | For a major nonconformity, who checked that the corrective action is still working, the date and the result |
Read the full example
[Company] Nonconformity and Corrective Action Procedure
- Version: 1.0
- Owner: CTO
- Approved by: CEO
- Effective date: [Effective date]
- Next review date: [Review date]
1. Purpose and Scope
This procedure sets how [Company] deals with each nonconformity in its management system: how a nonconformity is raised and recorded, how what was found is put right, how its cause is found and dealt with so that it does not happen again, and how the actions taken are checked before it is closed.
This procedure applies to every nonconformity, whatever raises it, and to everyone who reports one, is responsible for putting one right or checks what was done about one. A security incident, a risk or a weakness in a system, such as a missing update, is not in itself a nonconformity: it is one only where it shows that a requirement was not met, such as a rule that was not followed or a control that did not work.
- Management system: the policies, roles, processes, controls and records that [Company] uses to manage information security.
- Requirement: something that [Company]'s policies and procedures, the obligations that [Company] has taken on in contracts and under the law, or a standard that [Company] has chosen to follow say must be done or must be in place.
- Nonconformity: a requirement that is not met, of one of the two kinds that section 4 gives.
- Correction: what is done to put right what was found.
- Cause: why a requirement was not met, traced back far enough that dealing with it stops the nonconformity from happening again.
- Corrective action: what is done to deal with the cause of a nonconformity so that it does not happen again.
- Responsible role: the role responsible for the part of the management system where a nonconformity is found.
- Internal audit: an audit that [Company] carries out, or has carried out on its behalf, to check its own management system.
- Nonconformity log: [Company]'s record of every nonconformity and of what is done about it, in the form that Appendix A gives.
2. Roles and Responsibilities
- The CEO: approves this procedure; is told of nonconformities, and receives the reports on them, under section 8; where the responsible role is the CTO, decides the kind of a nonconformity that no audit has given one of the two kinds, agrees its actions and, where no internal audit raised it, names the person who checks them, under sections 4, 6 and 7; changes the due date of an action where needed under section 6; approves, under section 9, the giving of a record outside [Company]; and approves exceptions under section 10.
- The CTO: keeps this procedure and reviews it under section 10; decides whether what is reported, what a security incident shows, or what any other source shows without raising a nonconformity itself, is a nonconformity, and enters each nonconformity in the nonconformity log, under section 3; decides the kind of each nonconformity that no audit has given one of the two kinds, agrees the actions on each nonconformity and, where no internal audit raised it, names the person who checks them, under sections 4, 6 and 7, other than where the CTO is the responsible role; reports on nonconformities under section 8; and keeps the nonconformity log and the other records under section 9.
- Responsible roles: put right what was found, find the cause, propose the corrective action and complete the actions on each nonconformity in their part of the management system by their due dates, under sections 5 and 6, and give the person who checks them the evidence under section 7.
- People who check actions: check the evidence that the actions on a nonconformity are complete and that its cause has been dealt with, under section 7, and never check actions that they carried out or that are in a part of the management system they are responsible for.
- All staff: report to the CTO anything they believe may be a nonconformity, under section 3, and give the responsible role and the people who check actions the information they ask for.
3. Raising a Nonconformity
- Nonconformities are raised from internal audits, from audits and assessments of [Company] made by others, from checks, tests and measures of controls, from security incidents, from the review of the management system and from reports by staff.
- Staff report to the CTO, as soon as they can, anything they believe may be a nonconformity. Nobody is treated worse for reporting, in good faith, a possible nonconformity, including one that their own mistake caused.
- The CTO decides, within 5 working days of receiving a report from a member of staff, whether it is a nonconformity, records the decision and the reason, and tells the person who reported it.
- Each security incident is handled under [Company]'s incident response plan. Once the incident has been dealt with, the CTO decides whether it showed that a requirement was not met, records the decision and the reason, and raises a nonconformity where it did.
- Where a check, test or measure of a control, an audit or assessment of [Company] made by others or the review of the management system shows that a requirement may not have been met, and does not itself raise a nonconformity, the CTO decides whether it is a nonconformity, records the decision and the reason, and raises a nonconformity where it is one.
- Something that an exception approved under one of [Company]'s policies or procedures allows is not a nonconformity while the exception lasts and its conditions are met.
- A way to do better something that already meets its requirement is not a nonconformity. The CTO puts it before the next review of the management system as an opportunity for improvement.
- The CTO enters each nonconformity in the nonconformity log within 5 working days of learning of it or, for one that an audit raises as a nonconformity, of receiving the report of the audit. Each nonconformity has one entry, whatever raised it, and the entry records what raised it, the date it was raised, the requirement, what was found and the evidence for it, and the responsible role.
- The reference of a nonconformity is the reference that the audit gave it, where an audit raised it and gave it one, and otherwise a reference that is never reused.
- The date a nonconformity is raised is the date the report of the audit was sent, where an audit raised it as a nonconformity, and otherwise the date it is entered in the nonconformity log.
- Each nonconformity that is known before the effective date of this procedure and has not been closed is entered in the nonconformity log within 3 months of the effective date, in place of the 5 working days to enter it. For such a nonconformity, the date it is raised is the date it is entered, whatever raised it, and an action on it that already has a due date keeps that date where it is earlier than the one that section 6 gives.
4. Kinds of Nonconformity
Each nonconformity is one of the two kinds below.
- Major nonconformity: a requirement is not met in a way that shows a part of the management system is not working, such as a requirement that is not met at all or is not met in many cases.
- Minor nonconformity: a requirement is not met in part or in a single case, and the part of the management system it belongs to is still working.
A nonconformity that an audit raises keeps the kind that the audit gave it, where the audit gave it one of these two kinds. The CTO decides the kind of every other nonconformity when it is entered in the nonconformity log, and the CEO decides it instead where the responsible role is the CTO. The nonconformity log records the kind and who decided it.
Where whoever decides the kind of a nonconformity is not sure which kind it is, it is a major nonconformity.
5. Correction and Cause
- Where what was found puts [Company]'s information or systems at risk until it is put right, the responsible role puts it right, or limits the harm it can do, as soon as it is found, without waiting for the nonconformity to be entered in the nonconformity log or for its cause to be found.
- The responsible role finds the cause of each nonconformity. The work done to find it is in proportion to what the nonconformity affects.
- A cause is never recorded as a person's mistake alone. Where a person's mistake led to the nonconformity, the cause records why the mistake could be made and why it was not caught.
- The responsible role also checks whether the same cause has led, or could lead, to the same nonconformity in another part of the management system, and the nonconformity log records the result. Each nonconformity found in this way is raised under section 3.
- Where a nonconformity is the same as one closed in the 12 months before it was raised, the nonconformity log names the earlier one, and the cause is found again, including why the earlier corrective action did not stop it.
6. Corrective Action
- For each nonconformity, the responsible role agrees with the CTO the correction, unless it has already been made, and a corrective action, each with a due date. Where the responsible role is the CTO, the CEO agrees them instead.
- The due date of each action on a major nonconformity is no later than 3 months after the date it was raised, and of each action on a minor nonconformity no later than 6 months after the date it was raised.
- Where a contract or the law sets an earlier date for an action, or the person outside [Company] who raised the nonconformity sets one, its due date is no later than that date.
- Only the CEO changes the due date of an action, never to a date later than one that a contract, the law or the person outside [Company] who raised the nonconformity sets, and the nonconformity log records the reason.
- A corrective action deals with the cause that section 5 finds. Telling or training staff again is a corrective action only where the cause is that they did not know what the requirement asks of them.
- Where a corrective action changes a policy or a procedure, that document is changed and approved in the way it sets for its own changes.
- Where a nonconformity shows a risk that the risk register does not record, or records as less likely or less harmful than the nonconformity shows it to be, the CTO has that risk assessed again and the risk register changed.
- The nonconformity log records the correction and the date it was made, the cause, the corrective action, the due date of each action, who agreed the actions and when, and each document and each risk that a corrective action changed.
7. Checking and Closing
- When the actions on a nonconformity are complete, the responsible role gives the evidence to a person who checks that they are complete and that the cause has been dealt with.
- For a nonconformity that an internal audit raised, the person who checks is the auditor who raised it or another auditor. For every other nonconformity, the CTO names a person who did not carry out the actions and is not responsible for the part of the management system where it was found, and the CEO names that person instead where the responsible role is the CTO.
- The nonconformity log records who checked, the date and the result.
- A nonconformity is closed only when that check finds the actions complete and the cause dealt with. Until then it stays open.
- The nonconformity log records against each nonconformity whether it is Open or Closed and, once it is closed, the date.
- No sooner than 3 months and no later than 6 months after a major nonconformity is closed, a person who may check its actions under this section checks that its corrective action is still working and that the nonconformity has not happened again, and the nonconformity log records who checked, the date and the result. Where it has happened again, a new nonconformity is raised under section 3.
- The next internal audit of the part where a nonconformity was found checks that its corrective action is still working.
8. Reporting
- The CTO tells the CEO of each major nonconformity, and of each nonconformity in a part of the management system that the CTO is responsible for, within 5 working days of the date it is entered in the nonconformity log.
- At least every 3 months, the CTO tells the CEO which nonconformities are open, which are past their due date and which have happened again since they were closed, and each decision under section 3 that something in a part of the management system that the CTO is responsible for was not a nonconformity.
- The CTO puts before the next review of the management system the nonconformities raised and closed since the last review, their kinds and causes, those that are past their due date, those that have happened again, and the results of the checks made under section 7.
- Where a contract requires [Company] to tell someone outside [Company] of a nonconformity or of what is done about it, the CTO makes sure that they are told as the contract requires, and the nonconformity log records who was told and when.
9. Records
- [Company] keeps the nonconformity log, the evidence for each correction, cause, corrective action and check, and the record of each decision under section 3 that something was not a nonconformity.
- [Company] keeps each entry in the nonconformity log, and the evidence for it, for at least 3 years after the nonconformity is closed, and the record of each decision that something was not a nonconformity for at least 3 years after the decision.
- The CTO keeps these records where the CEO, the responsible roles and the people who check actions can read them, and protects them from being changed, lost or seen by people who have no need to see them.
- An entry in the nonconformity log is brought up to date as the nonconformity moves through this procedure. What it already records is not deleted, and an amendment is added to it with the date and the name of the person who made it.
- No entry in the nonconformity log, or evidence for it, is given to a person outside [Company] without the approval of the CEO, other than to an auditor, as section 8 requires or where the law requires it.
10. Exceptions, Breaches and Review
An exception to this procedure is approved in writing by the CEO, with the reason and any conditions recorded, and lasts no longer than 12 months. No exception lets a nonconformity be closed without the check that section 7 gives, or removes an entry from the nonconformity log.
Recording in the nonconformity log something that the person recording it knows to be untrue, closing a nonconformity without the check that section 7 gives, and hiding from the CTO a nonconformity that the person knows of are breaches of this procedure. A breach may lead to disciplinary action up to dismissal, in line with [Company]'s disciplinary process and the employment law of the country where the person works; for contractors and other non-employees it may lead to the engagement ending.
The CTO reviews this procedure at least every 12 months and after any significant change to [Company]'s work, systems or obligations, and each change is approved by the CEO.
11. Appendix A: Nonconformity Log
The nonconformity log has one entry for each nonconformity. The table gives what each entry holds.
| Field | What it holds |
|---|---|
| Reference | The reference that the audit gave it, where an audit raised it and gave it one, and otherwise a reference that is never reused |
| Raised by | What raised it, with the reference of the audit, the report or the security incident |
| Date raised | The date it was raised, as section 3 sets it |
| Requirement | The requirement that was not met, and where it is written |
| What was found | What was found, and the evidence for it |
| Responsible role | The role responsible for the part of the management system where it was found |
| Kind | Major nonconformity or Minor nonconformity, and who decided it |
| Correction | What was done to put right what was found, and the date it was made |
| Cause | The cause and, where a person's mistake led to the nonconformity, why the mistake could be made and why it was not caught |
| Elsewhere | Whether the same cause has led, or could lead, to the same nonconformity in another part of the management system, and the reference of each nonconformity raised as a result |
| Earlier nonconformity | The reference of an earlier nonconformity that this one is the same as, and why its corrective action did not stop this one |
| Corrective action | The corrective action, and who agreed the actions and when |
| Due dates | The due date of each action, and the reason for any change to a due date |
| Changes made | Each document and each risk that a corrective action changed |
| Others told | Who outside [Company] was told of it under a contract, and when |
| Check | Who checked that the actions are complete and the cause dealt with, the date and the result |
| Status | Open or Closed, and the date closed |
| Later check | For a major nonconformity, who checked that the corrective action is still working, the date and the result |
Disclaimer
This document is provided for informational purposes only and does not constitute legal advice. It is provided "as is", without warranty of any kind, express or implied, and no liability is accepted for any loss or damage arising from its use. It is used at your own discretion. Review it with a qualified adviser before adopting it.