Borrowed Time on the Line: A Controlled Lifecycle for Temporary Standards Deviations
Photo: Joseph Mischyshyn, CC BY-SA 2.0, via Wikimedia Commons
Temporary deviation is a legitimate part of industrial governance. A supplier misses a delivery, a material batch behaves slightly differently, a test rig is unavailable, or a customer asks for a short-run concession. In each case, a controlled departure from the default standard can be the sensible commercial and engineering response. The difficulty begins when the departure is not governed as an exception but gradually acquires the status of normal practice.
For UK SMEs, the risk is rarely a single dramatic failure. It is the accumulation of small, reasonable decisions that were never closed. A signed note sits in a folder, the expiry date passes without comment, and the shop floor continues to work to the concession long after the condition that justified it has gone. BEMSC members have raised this pattern consistently in helpline discussions: the deviation itself is not the problem; the absence of a lifecycle around it is.
A deviation is not a waiver
A waiver usually removes or relaxes a requirement for a defined period or quantity. A deviation is a documented, time-bound permission to depart from a specified requirement while the underlying standard remains in force. The distinction matters because it shapes the evidence. A deviation should identify the clause or requirement concerned, the scope of the departure, the reason, the risk assessment, the conditions attached, the approving authority, and the point at which the permission ends. Without those elements, the organisation is relying on memory and goodwill rather than control.
The standard remains the default. The deviation is the managed exception. That principle should be visible in the register, in the approval route and in the language used on the shop floor.
Three controls: authority, expiry and evidence
The first control is authority. Not every deviation needs board approval, but every deviation needs an approver whose level matches the risk. A useful starting point for an SME is a tiered matrix. Low-risk, short-duration departures with no customer or regulatory implication may be approved by a supervisor together with quality. Medium-risk deviations affecting fit, function or delivery commitments should require engineering and quality management sign-off. High-risk deviations, or those affecting safety, regulatory marking, customer-specific requirements or repeat production, should require an operations director or technical authority, with customer notification where the contract requires it. Critical deviations should be reserved for executive or board review and should be rare.
The second control is expiry. An expiry date is necessary but not sufficient. The register should state whether the deviation ends on a date, after a quantity, on completion of a batch, on receipt of a replacement material, or on implementation of a permanent change. Where a date is used, it should be realistic and linked to a review point before expiry. Where a quantity is used, the remaining balance should be visible. An open-ended deviation is not a temporary exception; it is an uncontrolled change.
The third control is evidence. The register should point to the rationale, the risk assessment, any customer or regulator communication, the verification activity that confirms the departure remains acceptable, and the closure evidence. Evidence does not need to be elaborate, but it must be findable. A register that records only the approval and the expiry date will not satisfy an auditor, an insurer or a customer asking how the organisation knew the exception remained safe.
A register template that earns its place
A workable deviation register for a UK SME should be simple enough to maintain and complete enough to govern. The following fields are a practical minimum:
- Deviation reference and date raised
- Originator and area or production line
- Standard, clause or requirement affected
- Description of the departure and its scope: product, batch, customer, quantity or period
- Reason for the deviation and the risk assessment reference
- Affected functions and any customer, insurer or regulatory notification
- Approval level, approver name and approval date
- Conditions attached to the approval
- Expiry trigger: date, quantity or event
- Review dates and the next review owner
- Evidence location for verification and closure
- Status: proposed, approved, active, expired, closed or rejected
- Closure date, closure evidence and any residual action
Status values matter. An expired deviation should not remain in the active list simply because no one has closed it. The register should make ageing visible. A simple weekly review of active deviations, with a warning at thirty days before expiry, is usually enough for an SME. The review should ask three questions: is the condition still valid, is the evidence still sufficient, and is the closure route on track?
Closing the loop before expiry
Closure should be a deliberate act, not the absence of action. When a deviation reaches its expiry trigger, the organisation has three legitimate routes. It can close the deviation with evidence that the departure is no longer required. It can seek a new approval for an extension, supported by fresh justification and risk assessment. Or it can stop the affected activity until conformity is restored. Renewal should never be automatic. A deviation that is renewed repeatedly without a permanent corrective action is a signal that the standard, the process or the supply route needs attention.
Where a deviation has become embedded in practice, the closure route should include a permanent change. That may mean a drawing revision, a process change, a supplier development action or a standards revision request. The register should link to that action so the exception does not reappear under a new reference number.
A board-level cadence for 2026
For the remainder of 2026, BEMSC recommends that SME boards and senior management teams treat the deviation portfolio as a standing item rather than an operational detail. A quarterly review is usually proportionate. The review should consider the number of active deviations, the age profile, any overdue closures, repeat deviations against the same clause, customer or regulatory exposure, and any deviations affected by standards revisions during the period. Monthly management reviews can handle the active list; the quarterly board review should focus on patterns, resourcing and whether temporary exceptions are becoming a substitute for permanent correction.
A short annual audit of the register, sampling approvals, expiry controls and closure evidence, will help confirm that the routine is working. The aim is not to eliminate deviations. It is to ensure that every departure is authorised, time-bound and evidenced, and that the organisation knows when it has returned to the standard.
BEMSC members can adapt the register fields above to their own quality management system. The discipline is more important than the format: authority at the right level, an expiry that is actually monitored, and evidence that closes the exception before it becomes the norm.