Why Most Opportunities for Improvement Get Ignored
Ask any quality manager what happens to the opportunities for improvement section of an audit report and you will get a familiar answer. They read them once, nod politely, and file the report. Nothing changes. The OFI sits there until the next audit cycle, when a different auditor writes almost the same thing.
On this page
This is not a management problem. It is a writing problem. Most opportunities for improvement are written in a way that makes them easy to dismiss. They are vague, they lack context, and they do not give the reader a clear reason to act. If you want your OFIs to drive genuine improvement, you need to write them differently.
This article is about how to do exactly that. It covers what an OFI actually is, why so many of them fail, and how to write opportunities for improvement that organisations take seriously and act on.
What an Opportunity for Improvement Actually Is
Before getting into the writing, it is worth being precise about what an OFI is and what it is not.
An opportunity for improvement is a finding where the auditor has observed something that does not rise to the level of a nonconformity but where the current approach is less effective than it could be. The system is compliant. The requirement is met. But there is a gap between where the organisation is and where it could reasonably be.
OFIs are sometimes confused with observations, and different certification bodies use different terminology. Some use the terms interchangeably. Others treat an observation as a statement of fact and an OFI as a specific suggestion. For the purposes of this article, an OFI is a finding that points toward a realistic improvement the organisation could make, without mandating that they make it.
That last point matters. You cannot compel an organisation to act on an OFI. They are not required to respond the way they are with a nonconformity. This is precisely why the writing has to do the persuading that the classification cannot.
For a broader look at how findings are classified, the article on classifying findings: NC, OFI and observation explained covers the distinctions in detail.
Exemplar Global Certified Training ProviderRTP No. 310970
The Common Failures in OFI Writing
Most weak OFIs share the same problems. Identifying them helps you avoid them.
Too Vague to Be Actionable
The most common failure is vagueness. An OFI that says consider enhancing your supplier evaluation process tells the reader almost nothing. Enhance how? Which part of the process? Based on what evidence? The reader cannot act on it because they do not know what specifically needs to change.
Vague OFIs often come from auditors who spotted something but did not dig deep enough to understand it. If you cannot explain specifically what you observed and why it matters, you have not finished the audit yet.
No Evidence Base
An OFI without evidence is an opinion. Auditors who write OFIs based on general impressions rather than specific observations leave themselves exposed to challenge and give the auditee no foundation to work from. If the finding is not grounded in what you actually saw, heard, or reviewed, it should not be in the report.
Moralising or Prescribing
Some auditors write OFIs as though they are telling the organisation what to do. This creates defensiveness and resistance. Your role is to observe and report, not to redesign the system. An OFI that reads like a consulting recommendation will be treated like one: noted and set aside.
Disconnected from Business Impact
If the reader cannot see why the improvement matters to their organisation, they will not prioritise it. OFIs that are written purely in terms of standard compliance, without connecting to operational outcomes, customer impact, or risk, are easy to deprioritise.
The Structure of a Well Written OFI
A well written opportunity for improvement has three components: what was observed, why it matters, and what a potential improvement might look like. You do not need to be prescriptive about the third element, but giving the reader a direction is more useful than leaving them to figure it out alone.
Component One: The Observation
Start with what you actually found. Be specific. Name the process, the area, the document, or the activity. Reference the evidence you reviewed. This grounds the OFI in fact and makes it harder to dismiss.
For example, rather than writing the training records could be improved, write something like: During review of training records for the production team, three of seven sampled operators had no documented evidence of competency evaluation following induction. Records confirmed completion of training attendance but did not include assessment results or sign off by a supervisor.
That is a specific, evidence based observation. The reader knows exactly what was reviewed and what was found.
Component Two: The Significance
Once you have stated the observation, explain why it matters. Connect it to something the organisation cares about. This might be risk, customer outcomes, regulatory exposure, efficiency, or the intent of the standard.
Continuing the example above: Without documented evidence of competency evaluation, the organisation cannot demonstrate that operators are capable of performing their tasks to the required standard. This creates exposure in the event of a product quality issue or an external audit.
Now the reader understands the stakes. The OFI has moved from being a paperwork observation to something with real operational implications.
Component Three: The Direction
Suggest a direction without being prescriptive. You are pointing toward a possibility, not writing a corrective action plan.
Completing the example: The organisation may wish to consider whether the current training record template captures sufficient evidence of competency evaluation, and whether a supervisor sign off step could be incorporated into the induction process.
Notice the language. May wish to consider and could be incorporated are deliberate. They invite action without demanding it. The organisation retains ownership of the solution.
Calibrating the Language
The language you use in an OFI shapes how it is received. There is a spectrum between too soft and too directive, and most well written OFIs sit in the middle.
Phrases that work well include: the organisation may wish to consider, it could be beneficial to, there may be value in reviewing, and the evidence suggests an opportunity to strengthen. These are constructive without being prescriptive.
Phrases to avoid include anything that sounds like a command (the organisation should implement), anything that implies a deficiency when one does not exist (the current approach is inadequate), and anything vague enough to be meaningless (further improvement is possible in this area).
Tone matters too. An OFI written with genuine interest in the organisation's success reads differently from one that feels like a box being ticked. Auditees can tell the difference, and it affects how seriously they take the finding.
Connecting OFIs to the Right Clause or Process
Every OFI should be anchored to something: a clause of the standard, a process, or a stated objective of the organisation. This gives the finding credibility and helps the organisation understand where it fits within their management system.
An OFI that floats without context is harder to assign to an owner and easier to ignore. If you can say this relates to Clause 7.2 competence requirements or this connects to the organisation's stated objective of reducing customer complaints, you give the reader a hook to hang the finding on.
This also makes OFIs more useful at management review. When the quality manager is presenting audit findings to leadership, an OFI that is linked to a specific process or objective is far easier to discuss than one that is written in isolation.
For context on how audit findings feed into the broader audit process, the article on what are audit findings: a plain English guide for ISO auditors and quality managers provides a useful foundation.
Real World Examples Across Different Standards
To make this concrete, here are examples of weak OFIs rewritten as strong ones across different standards.
ISO 9001: Customer Feedback
Weak: The organisation could do more to capture customer feedback.
Strong: Review of the customer satisfaction process identified that feedback is collected via post delivery survey, with a current response rate of approximately 12 percent. The low response rate limits the organisation's ability to identify trends or act on emerging issues. The organisation may wish to consider whether the current survey method is reaching customers effectively, and whether alternative channels could increase response rates and the quality of data captured.
ISO 45001: Hazard Identification
Weak: Hazard identification could be more thorough.
Strong: During a walkthrough of the warehouse, three areas of pedestrian and forklift interaction were observed that were not reflected in the current hazard register. The register was last reviewed eight months ago. Given the dynamic nature of warehouse operations, there may be value in reviewing the frequency of hazard identification reviews to ensure the register remains current and reflects actual site conditions.
ISO 14001: Environmental Objectives
Weak: Environmental objectives could be more measurable.
Strong: Two of the four documented environmental objectives reviewed did not include defined targets or timelines. While the objectives identify areas of focus, the absence of measurable targets makes it difficult to assess progress or report meaningfully at management review. The organisation may wish to consider adding specific, time bound targets to these objectives to support more effective monitoring and reporting.
In each case, the rewritten version is longer, but it earns that length. Every sentence adds information the reader can use.
How Many OFIs Should an Audit Report Include
There is no rule about the number of OFIs an audit report should contain, but there are practical limits. Too few and you may appear to have missed things. Too many and the report becomes overwhelming, which has the same practical effect as writing nothing at all.
A useful guide is to include OFIs only where you have a specific, evidence based observation and a genuine sense that acting on it would benefit the organisation. If you are writing an OFI because you feel you need to fill space, or because you want to appear thorough, the quality of the finding will show it.
In a typical internal audit of a single process area, two to four well written OFIs is a reasonable number. In a full system audit, you might have more, but each one should still meet the same standard: specific observation, clear significance, suggested direction.
OFIs in Internal vs External Audits
The principles of good OFI writing are the same regardless of audit type, but the context differs in ways that affect how you write them.
In an internal audit, you often have deeper knowledge of the organisation and its history. This can be an advantage because you can connect OFIs to known challenges or previous findings. It can also be a risk if familiarity leads you to soften findings that deserve to be stated clearly. The article on writing nonconformity reports that stand up to scrutiny explores the discipline of evidence based finding writing in more depth.
In an external audit, you are writing for an audience that may include people who were not present during the audit. Your OFIs need to be self contained. A reader who was not in the room should be able to understand exactly what was observed, why it matters, and what the direction of improvement might be, without needing to ask you questions.
Exemplar Global Certified Training ProviderRTP No. 310970Getting OFIs Taken Seriously After the Audit
Even a well written OFI can be ignored if the organisation has no process for reviewing and acting on them. As an internal auditor, you have some influence over this. As an external auditor, you have less, but you can still structure your report in a way that makes action more likely.
One approach is to group OFIs thematically. If you have three OFIs that all relate to documented information, grouping them together makes the pattern visible. Patterns are harder to ignore than isolated findings.
Another approach is to connect OFIs explicitly to the organisation's own objectives. If the organisation has stated that reducing customer complaints is a priority, and your OFI relates to the feedback process, make that connection explicit in the finding. This shifts the OFI from being an auditor's suggestion to being aligned with what the organisation already says it wants to achieve.
For those developing their audit report writing skills more broadly, the article on audit report writing that people read: how to communicate findings that drive action covers the full picture of effective audit reporting.
Building This Skill Through Practice
Writing good OFIs is a skill, and like any skill it improves with deliberate practice. After each audit, review your OFIs against the three component structure: observation, significance, direction. Ask yourself whether a reader who was not present could understand each finding completely. Ask whether the language invites action without demanding it. Ask whether every finding is grounded in specific evidence.
If you are working through an auditor training programme, practise rewriting weak OFIs as part of your preparation. The ability to write findings that drive genuine improvement is one of the things that separates competent auditors from exceptional ones.
At Audit Workshop, audit reporting and finding writing are embedded throughout our Internal Auditor and Lead Auditor courses across ISO 9001, ISO 14001, ISO 45001, ISO 27001, and other standards. Our courses are built on real audit practice, not theory, and they give you the tools to write findings that organisations actually act on. If you want to develop this skill in a structured way, explore our training options at auditworkshop.com.
