Clinic Inventory Variance Audit Workflow (2026 Guide)

Clinic Inventory Variance Audit Workflow: Detection and Resolution

Inventory variance — the difference between what the system says you have and what physical count shows — is not primarily a counting problem. Counting reveals the variance; the cause is usually upstream: delayed transaction posting, untracked wastage, unauthorised use, or supplier delivery discrepancies that weren't reconciled at receipt.

A structured inventory variance audit workflow addresses all of these systematically. This guide covers how to design the workflow, what root-cause categories to track, and how to measure process improvement over time.

Why Variance Audits Fail Without Structure

The unstructured approach is common: a stock count is done, a discrepancy is found, the count is corrected in the system, and no further action is taken. The correction is made, but the cause is unknown, so the same variance appears in the next count. Over months, the stock count correction becomes a routine entry with no investigation — effectively accepting a chronic loss without understanding it.

Structured audit workflow requires three things the unstructured approach skips:

1. Root-cause assignment: Every variance above threshold has a documented cause
2. Ownership: A named person responsible for investigating and resolving the discrepancy
3. Prevention action: A specific process change to prevent the same variance recurring

Without all three, the audit is a reconciliation exercise, not a process improvement tool.

Variance Audit Workflow Design

Stage 1: Variance detection

Continuous monitoring (daily/transactional):

• Set stock-level alerts: when a counted item falls below minimum threshold unexpectedly, flag for investigation
• Flag unusual consumption rates: if an item is being used 2× faster than the historical average, investigate before the next scheduled count

Cycle count schedule (planned):

• Assign cycle count frequency by item category and criticality:

Category	Frequency	Rationale
High-value controlled medications	Weekly	High theft/misuse risk
High-cost consumables (sutures, implants)	Monthly	High unit value
Standard clinical supplies	Monthly	Moderate value, high volume
Administrative supplies	Quarterly	Low risk, low value
Capital equipment	Annually	Low frequency of movement

• Count should be done by a person other than whoever manages day-to-day inventory when possible (segregation of duties)
• Count results entered before the inventory system is checked — blind count, then compare, reduces the tendency to adjust counts toward expected numbers

Formal reconciliation (monthly close):

• Full system vs. count reconciliation at month-end
• All unresolved variances from the cycle count period reviewed
• Financial impact calculated (unit cost × variance quantity)

Stage 2: Variance classification

Not all variances have the same cause or the same fix. Classify every variance above the minimum investigation threshold into one of the standard cause categories:

Cause code	Description	Typical trigger
POSTING-DELAY	Transaction occurred but wasn't posted until after count	Staff didn't post immediately; batch posting workflows
MISCOUNT	Physical count error	Training gap; poor count conditions; labelling confusion
WASTAGE-UNTRACKED	Product used and discarded without logging	No wastage log process; no consequence for skipping
UNAUTHORISED-USE	Product used without proper requisition	Weak access controls; informal requisition practice
DELIVERY-DISCREPANCY	Received quantity differed from invoice, not caught at receipt	Receipt matching process not followed
THEFT-SUSPECTED	No legitimate explanation; security review warranted	Access logs, CCTV review
SYSTEM-ERROR	Software posting or calculation error	Needs vendor investigation
OTHER	Explained but not in above categories	Requires manual documentation

Classification is done by the investigation owner, not by whoever discovered the variance.

Stage 3: Investigation and owner assignment

Each variance above threshold gets an investigation record:

• Variance quantity and value (system vs. count)
• Date of discovery and expected date of occurrence (if different)
• Investigation owner (named staff member, not a team)
• Investigation deadline (48 hours for high-value items; 7 days for low-value)
• Cause code assigned (after investigation)
• Supporting evidence (delivery note, wastage log, access log)

Investigation owners should be empowered to check transaction logs, delivery records, and usage logs. If they don't have access to investigate, the ownership assignment is meaningless.

Stage 4: Correction and approval

Stock corrections require two-person oversight:

• Entry: The investigation owner proposes the correction quantity and cause code
• Approval: Manager or inventory controller (independent from the investigation) approves the correction before posting

Corrections posted without approval create an audit trail problem: if the same person who manages day-to-day inventory also approves their own stock corrections, variance manipulation becomes undetectable.

Correction posting includes:

• Variance quantity and direction (positive adjustment = we found more than expected; negative = we have less)
• Cause code
• Supporting evidence reference
• Approved by (name and timestamp)

Stage 5: Prevention action

The most important stage — and the most commonly skipped.

For every cause code, there is a standard prevention action:

Cause code	Prevention action
POSTING-DELAY	Enforce same-day posting policy; add posting to workflow checklist
MISCOUNT	Recount training; improve storage labelling; improve count documentation form
WASTAGE-UNTRACKED	Implement mandatory wastage log; add wastage logging to clinical workflow
UNAUTHORISED-USE	Review access permissions; add requisition step to clinical process
DELIVERY-DISCREPANCY	Retrain on receipt matching; add sign-off requirement on deliveries

Prevention actions are assigned to owners with deadlines. If the action is not completed, the cause will appear again in the next count cycle. The monthly variance review should include a check on whether previously assigned prevention actions have been completed.

Setting Up in Tregovia

Tregovia's Pharmacy module (EUR 15/month) supports inventory management with variance audit workflows:

• Item master: Minimum stock levels, reorder points, unit costs
• Transaction log: All stock movements recorded (receipt, usage, wastage, adjustment) with timestamps and user
• Cycle count workflow: Count entry form, blind count mode, immediate variance display on submission
• Variance queue: All variances above configured threshold appear in investigation queue with owner assignment
• Correction approval: Two-step correction workflow (entry + approval, different users)
• Cause code taxonomy: Standard cause codes with custom additions
• Prevention action tracking: Action record linked to variance, with deadline and completion confirmation
• Variance trend report: Variance rate by category, by cause code, by time period

Privacy controls: Configure access roles, consent records, exports, deletion requests, and retention rules before publishing this workflow.

Key Performance Metrics

Metric	Definition	Target
Variance rate by category	(Variance quantity / total counted quantity) per category	Declining trend month-on-month
Investigation completion rate	Variances investigated on time / total variances triggered	100%
Cause code distribution	Variance frequency by cause code	Informs which process gaps need most attention
Correction approval latency	Days from correction entry to approval	<2 days for standard; same day for high-value
Prevention action completion rate	Prevention actions completed by deadline / total assigned	90%+
Unresolved variance aging	Variances in queue > 7 days	Should approach zero

FAQ

How often should full inventory counts be conducted?

Fully counting every item in the inventory at once (a wall-to-wall count) is disruptive and should be reserved for annual audit purposes. Cycle counting — counting a subset of items on a defined schedule — is more effective for ongoing control. Count the highest-risk, highest-value categories most frequently. A structured cycle count program that counts every item at least once per quarter provides adequate control without the disruption of monthly wall-to-wall counts.

What threshold should trigger a formal investigation?

Set category-based thresholds rather than a single value. For controlled medications: any variance above zero should trigger investigation. For high-cost surgical supplies: any variance with a value above EUR 50. For general consumables: variances above 5% of counted quantity or EUR 100 in value. Thresholds should be reviewed annually — a threshold that made sense for last year's purchase volumes may be too high or too low as the practice grows.

Who should approve stock count corrections?

The approver must be independent of the person who entered the count and the person who manages day-to-day inventory. In a small clinic, this is typically the practice manager or owner. The independence requirement is not bureaucracy — it is the control that makes variance correction trustworthy. Without it, systematic under-reporting of variance to avoid investigation is undetectable.

What is the most common cause of persistent inventory variance in clinics?

Untracked wastage is consistently the most common cause in clinical environments. Clinical staff open and partially use consumables — medications drawn but not fully administered, sutures used and the remainder discarded — without logging the usage or wastage. The system shows the item checked out from inventory but the usage quantity doesn't match because the remaining product was wasted. Mandatory wastage logging with a no-judgment policy (staff are not penalised for logging waste, only for not logging it) is the most effective fix.

Can inventory variance audits reduce controlled medication losses?

Yes, but controlled medications require additional controls beyond what standard inventory audit provides. Controlled substance registers (required by pharmaceutical regulation in most EU member states) must record individual administration — patient, dose, practitioner, date, and time — at the unit level, not just at the stock level. Reconciling the controlled substance register against inventory movements provides much stronger assurance than a quantity variance check alone. Ensure your inventory software supports controlled substance register-level logging if your practice handles scheduled medications.