K
Knowles Training Institute
Guest
- Thread Author
- #1
Knowles Knowledge Centre•Diagnosis
A diagnostic method for working out whether a compliance finding is a drafting error, an approval-route problem or a resourcing one — before you commission any training.
A procedure writing gap exists when a document fails to describe a method that could be performed, even where the named roles still exist, a departure can be authorised within the working day, logging one carries no disciplinary consequence, and there is time to do the work. That is a narrower condition than it sounds. Most procedures that are not followed name a form that was withdrawn, a team that was dissolved, or a step that takes longer than the shift allows.
This guide sets out a three-step diagnostic method, the evidence sources that support it, sample questions for separating a document problem from a governance one, and thresholds for deciding when revision is the right response.
Practical guide•For HR and L&D teams•Updated September 2026
1 A step is not followed
2 Walk it as written
3 Find the cause
Resourcing gapRewriting will not help Document gapRevision is the answer
About this guide
Published byKnowles Training Institute
AudienceQuality, risk and anybody about to run a compliance campaign
Use beforeActing on an audit finding that a procedure is not being followed
The common failure is starting from the behaviour. An auditor finds a step not performed, and the finding enters the pipeline as a discipline problem rather than as a question about whether the step could have been performed at all.
Three things go wrong when the finding is accepted at face value.
Non-compliance is inferred from a gap“The team is not following the procedure” describes a difference between a document and some behaviour, and says nothing about which of the two is wrong. A retired form and a careless shift produce the identical finding, and the two call for opposite responses.
A review is mistaken for a testA document reviewed and approved every year is convincing to everybody who signed it. The reviewers all know the work, and every reader silently supplies the steps the document has lost. Nobody has attempted it in the live environment, which is the only act that distinguishes a current procedure from a plausible one.
No alternative explanation is testedIf a compliance campaign is the only option considered, it will be the option chosen — whether the step was performable, whether the doer still exists, or whether departing from it could be authorised by anybody.
An impossible step and a careless team produce the same audit finding. Only one of them responds to a reminder.
The method works backwards from the step that is not being performed to what happens when somebody tries, then tests whether the document is the cause.
1
State which step is not performed and what is done instead. “Step five requires a sign-off in a system module, and the line has been using a paper form for nine months” is usable. “The release procedure is not being followed’ is not.
If the finding cannot be stated as one step and one substitute behaviour, the diagnosis stops here until it can, because a document-level finding has no cause and no remedy.
2
Have somebody who did not write the procedure perform it, in order, in the live environment, with the document in hand and somebody watching. Record every point at which it was wrong, every point at which it was silent, and how long each step actually took.
For one release procedure the walk may stop at step five, where the module named in the document was switched off during an upgrade. The staff’s paper form turns out to meet the underlying obligation perfectly well and to be documented nowhere, which is a finding about the organisation’s records rather than about its people.
This is the step most organisations skip. Without it, everything downstream is an assessment of the team.
3
Ask the question that separates a drafting error from everything else: could somebody in the named role perform this step today, exactly as written?
If they could not, the finding is about the document and no reminder will change anything. Revise the method, tell the people who were working around it, and close the finding as a drafting error rather than as non-compliance.
If they could, establish whether the step takes longer than the available time, whether departing from it can be authorised by anybody within the day, and whether logging a departure carries a disciplinary consequence. Those three point at capacity, at the approval route and at governance, and the remedies differ.
A diagnosis is only as good as what it is built on. Most of this can be settled by one walk and a look at the approval route, and organisations reach instead for the source that cannot tell a current procedure from a plausible one.
Evidence source
What it shows well
What it cannot show
One walk through the live environment
Every point at which the document is wrong or silent
Why people chose the workaround they chose
What people actually do, observed once
The method genuinely in use, including its substitutes
Whether that method meets the obligation
The exception register, where one exists
Which departures recur, and how often
Anything, where logging is tied to discipline
The document’s own approval route
Whether the method can be revised without reopening the policy
Whether anybody has ever tried to
Staffing and volumes for the step
Whether the step is performable in the time available
Whether the document is also wrong
A signed compliance attestation
That somebody has confirmed they are compliant
Whether the procedure describes the work — a current document and a plausible one are signed identically
Note the pattern: the source most organisations lead with — a signed attestation — is the only one on this list that cannot establish whether the document describes the work, because it is signed by people who are doing the work correctly by means the document does not mention.
Use at least two independent sources before concluding that behaviour is the problem. One walk supported by the step’s volumes and timings is evidence. An attestation is a hypothesis.
Ask these in sequence. The first “no” usually identifies the constraint.
PerformabilityCould somebody in the named role perform the step today, exactly as written? A step naming a withdrawn form cannot be complied with by anybody, however willing.
DoerDoes the step name one role that still exists? Steps belonging to a dissolved team are performed as a favour by somebody, and nobody finds out until they leave.
RouteCan a departure be authorised by somebody within the working day? Where the only route is a quarterly committee, departures will happen without authorisation.
SeparationIs logging a departure from the method separate from the process for breaching the obligation? Where it is not, the register will stay empty by construction.
CapacityIs there time and staffing to perform the step at current volumes? A step that takes eleven minutes in a nine-minute cycle is departed from for reasons no drafting reaches.
CapabilityWith the step performable, a doer who exists, a route that works within the day, logging separated from discipline and the capacity to do it — is the step still not being performed?
Only the last question identifies a behaviour problem. The first five identify drafting, structural, approval, governance and resourcing problems that no campaign will resolve — and that will still be there afterwards.
A diagnosis should end in a decision, not a report. These thresholds keep that decision defensible.
Finding
Threshold
Response
The step cannot be performed as written
A withdrawn form, a decommissioned screen, a dissolved team
A drafting error. Revise the method; nobody needs reminding.
No step names a doer
Passive voice throughout, across several documents
A drafting error, and the cheapest of them to fix.
Departures cannot be authorised within the day
The only route is the committee that owns the policy
An approval-route problem. The method is sharing the obligation’s gate.
Logging a departure carries a disciplinary consequence
One document covers both the obligation and the method
A governance problem. The register will stay empty however it is written.
Performable, routed, separated, resourced
One team departs where comparable teams do not
Now it is local, and supervision or training is appropriate. Scope it to the step.
The threshold that matters most
If the step cannot be performed as written, there is no evidence about anybody’s compliance and no basis for a finding against them. That single check prevents more pointless compliance activity than any other step in this method.
A Singapore food manufacturer’s quality team receives an audit finding that a batch release procedure is not being followed on one line. A compliance campaign across three lines is proposed.
1
One step is at issue: step five requires a release sign-off recorded in a named system module. The line has been recording it on a paper form, countersigned by a supervisor, for about nine months.
2
A quality officer who did not write the procedure attempts the steps in order on the line. Step five cannot be completed: the module was switched off during a platform upgrade and was never reinstated. The paper form the line uses was devised by a supervisor at the time, meets the underlying obligation of an independent recorded check, and appears in no document anywhere.
3
The document is examined. Obligation and method sit in one combined document approved by a quality committee that meets quarterly, so the only route to changing the system name was the route for changing the release obligation. The exception register is empty, and logging a departure is routed through the same process as a breach of release.
Diagnosis: this is not a compliance problem and the campaign would have been aimed at the wrong thing. The obligation was met throughout by a sensible substitute; the document named a module that does not exist; and the two structural reasons nobody reported it were an approval route four times a year and a register that reads as a confession.
Response: a campaign across three lines would have instructed people to use a module that is switched off. What is needed is the method split from the obligation so the system name can be changed by the procedure’s owner, the paper form documented or the module reinstated, and logging separated from the release breach process. The walk also established that the three steps protecting allergen segregation were followed exactly, which is worth recording as a finding in its own right.
What is a procedure writing gap?It exists when the document fails to describe a performable method, despite the named roles existing, a departure being authorisable within the day, logging carrying no disciplinary consequence, and there being time to do the work. If any of those is absent, what you have is a structural, approval, governance or resourcing problem rather than a drafting one.
?
How do you measure it objectively?By one walk, which takes an hour and produces a list of points at which the document was wrong or silent. Attestations cannot do it, because they are signed truthfully by people who are meeting the obligation using a method the document does not mention.
?
Should we audit every procedure?Usually not as a first step, and walking beats auditing in any case. Walk the three procedures attached to the obligations you would least like to breach. That produces a short list of drafting errors and a reliable estimate of how stale the rest of the manual is, in considerably less time than an audit programme.
?
What if the team insists the procedure is unworkable?They are usually describing one step and are usually right about it. The disagreement is settled by walking that step rather than by discussion, and the result is frequently a surprise to the document’s owner, who has reviewed and approved it for several years without attempting it.
?
How often should this be repeated?Tie it to the work rather than the calendar. Walk a procedure after any system change, because a decommissioned screen is the most common single cause of a stale step; after any reorganisation, since dissolved teams leave steps with no doer; and whenever the same departure appears in a register more than twice, which is the document telling you where it is wrong. Annual reviews tend to produce ritual rather than insight.
Identifying a procedure writing gap is mostly an exercise in attempting the thing. The method is not complicated:
1Name the one step and the substitute behaviour
2Walk it in the live environment, with somebody new
3Ask whether the named role could perform it today, as written
The discipline it requires is the willingness to conclude that nobody’s compliance is the problem.
A diagnosis that recommends a reminder every time it is run has not been a diagnosis; it has been an administrative reflex.
Where the diagnosis does point to the document rather than to the route or the resourcing, the next question is which stage — covered in what separates a policy from a procedure. Organisations that decide facilitated development is appropriate can review the Writing Policy and Procedure Documents Course in Singapore, evaluating scope and expected workplace application against the diagnosis rather than against the course description.
Published by Knowles Training Institute.
The post How to Identify Whether Your Procedures Are Being Followed appeared first on Corporate Training Courses in Singapore.
How to Identify Whether Your Procedures Are Being Followed
A diagnostic method for working out whether a compliance finding is a drafting error, an approval-route problem or a resourcing one — before you commission any training.
A procedure writing gap exists when a document fails to describe a method that could be performed, even where the named roles still exist, a departure can be authorised within the working day, logging one carries no disciplinary consequence, and there is time to do the work. That is a narrower condition than it sounds. Most procedures that are not followed name a form that was withdrawn, a team that was dissolved, or a step that takes longer than the shift allows.
This guide sets out a three-step diagnostic method, the evidence sources that support it, sample questions for separating a document problem from a governance one, and thresholds for deciding when revision is the right response.
Practical guide•For HR and L&D teams•Updated September 2026
1 A step is not followed
2 Walk it as written
3 Find the cause
Resourcing gapRewriting will not help Document gapRevision is the answer
About this guide
Published byKnowles Training Institute
AudienceQuality, risk and anybody about to run a compliance campaign
Use beforeActing on an audit finding that a procedure is not being followed
Why compliance findings are misdiagnosed
The common failure is starting from the behaviour. An auditor finds a step not performed, and the finding enters the pipeline as a discipline problem rather than as a question about whether the step could have been performed at all.
Three things go wrong when the finding is accepted at face value.
Non-compliance is inferred from a gap“The team is not following the procedure” describes a difference between a document and some behaviour, and says nothing about which of the two is wrong. A retired form and a careless shift produce the identical finding, and the two call for opposite responses.
A review is mistaken for a testA document reviewed and approved every year is convincing to everybody who signed it. The reviewers all know the work, and every reader silently supplies the steps the document has lost. Nobody has attempted it in the live environment, which is the only act that distinguishes a current procedure from a plausible one.
No alternative explanation is testedIf a compliance campaign is the only option considered, it will be the option chosen — whether the step was performable, whether the doer still exists, or whether departing from it could be authorised by anybody.
An impossible step and a careless team produce the same audit finding. Only one of them responds to a reminder.
The step–walk–cause method
The method works backwards from the step that is not being performed to what happens when somebody tries, then tests whether the document is the cause.
1
Name the step, not the procedure
State which step is not performed and what is done instead. “Step five requires a sign-off in a system module, and the line has been using a paper form for nine months” is usable. “The release procedure is not being followed’ is not.
If the finding cannot be stated as one step and one substitute behaviour, the diagnosis stops here until it can, because a document-level finding has no cause and no remedy.
2
Walk it as written
Have somebody who did not write the procedure perform it, in order, in the live environment, with the document in hand and somebody watching. Record every point at which it was wrong, every point at which it was silent, and how long each step actually took.
For one release procedure the walk may stop at step five, where the module named in the document was switched off during an upgrade. The staff’s paper form turns out to meet the underlying obligation perfectly well and to be documented nowhere, which is a finding about the organisation’s records rather than about its people.
This is the step most organisations skip. Without it, everything downstream is an assessment of the team.
3
Test whether the document is the cause
Ask the question that separates a drafting error from everything else: could somebody in the named role perform this step today, exactly as written?
If they could not, the finding is about the document and no reminder will change anything. Revise the method, tell the people who were working around it, and close the finding as a drafting error rather than as non-compliance.
If they could, establish whether the step takes longer than the available time, whether departing from it can be authorised by anybody within the day, and whether logging a departure carries a disciplinary consequence. Those three point at capacity, at the approval route and at governance, and the remedies differ.
Where the evidence comes from
A diagnosis is only as good as what it is built on. Most of this can be settled by one walk and a look at the approval route, and organisations reach instead for the source that cannot tell a current procedure from a plausible one.
Evidence source
What it shows well
What it cannot show
One walk through the live environment
Every point at which the document is wrong or silent
Why people chose the workaround they chose
What people actually do, observed once
The method genuinely in use, including its substitutes
Whether that method meets the obligation
The exception register, where one exists
Which departures recur, and how often
Anything, where logging is tied to discipline
The document’s own approval route
Whether the method can be revised without reopening the policy
Whether anybody has ever tried to
Staffing and volumes for the step
Whether the step is performable in the time available
Whether the document is also wrong
A signed compliance attestation
That somebody has confirmed they are compliant
Whether the procedure describes the work — a current document and a plausible one are signed identically
Note the pattern: the source most organisations lead with — a signed attestation — is the only one on this list that cannot establish whether the document describes the work, because it is signed by people who are doing the work correctly by means the document does not mention.
Use at least two independent sources before concluding that behaviour is the problem. One walk supported by the step’s volumes and timings is evidence. An attestation is a hypothesis.
Diagnostic questions that separate cause from symptom
Ask these in sequence. The first “no” usually identifies the constraint.
PerformabilityCould somebody in the named role perform the step today, exactly as written? A step naming a withdrawn form cannot be complied with by anybody, however willing.
DoerDoes the step name one role that still exists? Steps belonging to a dissolved team are performed as a favour by somebody, and nobody finds out until they leave.
RouteCan a departure be authorised by somebody within the working day? Where the only route is a quarterly committee, departures will happen without authorisation.
SeparationIs logging a departure from the method separate from the process for breaching the obligation? Where it is not, the register will stay empty by construction.
CapacityIs there time and staffing to perform the step at current volumes? A step that takes eleven minutes in a nine-minute cycle is departed from for reasons no drafting reaches.
CapabilityWith the step performable, a doer who exists, a route that works within the day, logging separated from discipline and the capacity to do it — is the step still not being performed?
Only the last question identifies a behaviour problem. The first five identify drafting, structural, approval, governance and resourcing problems that no campaign will resolve — and that will still be there afterwards.
Decision thresholds
A diagnosis should end in a decision, not a report. These thresholds keep that decision defensible.
Finding
Threshold
Response
The step cannot be performed as written
A withdrawn form, a decommissioned screen, a dissolved team
A drafting error. Revise the method; nobody needs reminding.
No step names a doer
Passive voice throughout, across several documents
A drafting error, and the cheapest of them to fix.
Departures cannot be authorised within the day
The only route is the committee that owns the policy
An approval-route problem. The method is sharing the obligation’s gate.
Logging a departure carries a disciplinary consequence
One document covers both the obligation and the method
A governance problem. The register will stay empty however it is written.
Performable, routed, separated, resourced
One team departs where comparable teams do not
Now it is local, and supervision or training is appropriate. Scope it to the step.
The threshold that matters most
If the step cannot be performed as written, there is no evidence about anybody’s compliance and no basis for a finding against them. That single check prevents more pointless compliance activity than any other step in this method.
A worked example
A Singapore food manufacturer’s quality team receives an audit finding that a batch release procedure is not being followed on one line. A compliance campaign across three lines is proposed.
1
Name the step
One step is at issue: step five requires a release sign-off recorded in a named system module. The line has been recording it on a paper form, countersigned by a supervisor, for about nine months.
2
Walk it as written
A quality officer who did not write the procedure attempts the steps in order on the line. Step five cannot be completed: the module was switched off during a platform upgrade and was never reinstated. The paper form the line uses was devised by a supervisor at the time, meets the underlying obligation of an independent recorded check, and appears in no document anywhere.
3
Find the cause
The document is examined. Obligation and method sit in one combined document approved by a quality committee that meets quarterly, so the only route to changing the system name was the route for changing the release obligation. The exception register is empty, and logging a departure is routed through the same process as a breach of release.
Diagnosis: this is not a compliance problem and the campaign would have been aimed at the wrong thing. The obligation was met throughout by a sensible substitute; the document named a module that does not exist; and the two structural reasons nobody reported it were an approval route four times a year and a register that reads as a confession.
Response: a campaign across three lines would have instructed people to use a module that is switched off. What is needed is the method split from the obligation so the system name can be changed by the procedure’s owner, the paper form documented or the module reinstated, and logging separated from the release breach process. The walk also established that the three steps protecting allergen segregation were followed exactly, which is worth recording as a finding in its own right.
Frequently asked questions
?What is a procedure writing gap?It exists when the document fails to describe a performable method, despite the named roles existing, a departure being authorisable within the day, logging carrying no disciplinary consequence, and there being time to do the work. If any of those is absent, what you have is a structural, approval, governance or resourcing problem rather than a drafting one.
?
How do you measure it objectively?By one walk, which takes an hour and produces a list of points at which the document was wrong or silent. Attestations cannot do it, because they are signed truthfully by people who are meeting the obligation using a method the document does not mention.
?
Should we audit every procedure?Usually not as a first step, and walking beats auditing in any case. Walk the three procedures attached to the obligations you would least like to breach. That produces a short list of drafting errors and a reliable estimate of how stale the rest of the manual is, in considerably less time than an audit programme.
?
What if the team insists the procedure is unworkable?They are usually describing one step and are usually right about it. The disagreement is settled by walking that step rather than by discussion, and the result is frequently a surprise to the document’s owner, who has reviewed and approved it for several years without attempting it.
?
How often should this be repeated?Tie it to the work rather than the calendar. Walk a procedure after any system change, because a decommissioned screen is the most common single cause of a stale step; after any reorganisation, since dissolved teams leave steps with no doer; and whenever the same departure appears in a register more than twice, which is the document telling you where it is wrong. Annual reviews tend to produce ritual rather than insight.
Conclusion
Identifying a procedure writing gap is mostly an exercise in attempting the thing. The method is not complicated:
1Name the one step and the substitute behaviour
2Walk it in the live environment, with somebody new
3Ask whether the named role could perform it today, as written
The discipline it requires is the willingness to conclude that nobody’s compliance is the problem.
A diagnosis that recommends a reminder every time it is run has not been a diagnosis; it has been an administrative reflex.
Where the diagnosis does point to the document rather than to the route or the resourcing, the next question is which stage — covered in what separates a policy from a procedure. Organisations that decide facilitated development is appropriate can review the Writing Policy and Procedure Documents Course in Singapore, evaluating scope and expected workplace application against the diagnosis rather than against the course description.
Published by Knowles Training Institute.
The post How to Identify Whether Your Procedures Are Being Followed appeared first on Corporate Training Courses in Singapore.
Last edited: