The Ops Community ⚙️

Victoria Hodgson
Victoria Hodgson

Posted on

Why a green compliance dashboard is not proof of a clean audit

The dashboard shows green, but a stock count finds a package in the wrong room and another quantity that does not match the records. Before treating either finding as a software failure, establish what the green indicator actually checked. A successful system operation and verified physical inventory answer different questions.

When reviewing information through a dispensary owner mobile app, ask how to move from the summary to the records behind it. A convenient owner view can help direct attention, but readiness for an audit requires evidence tied to the review’s scope. Start by separating connection status, recorded transactions, physical stock, and the procedures used to investigate exceptions.

A green status answers a limited question

Ask the provider to define the indicator in plain language. It might describe an available connection, a completed submission, or the absence of detected errors in a particular queue. Those are possible meanings to investigate, not definitions that apply to every dispensary platform. A status is useful only when you know what was checked.

Ask what the indicator actually checks

Write down the data source, last evaluation time, included locations, and exclusions. Ask whether the system confirms delivery, acceptance, or a comparison between records. Also ask what would make the status change and where exceptions appear.

Save the answer with the operating procedure so managers do not assign different meanings to the same display. Include the account role used to view the status. If the owner and inventory manager see different information, verify whether permissions or filters explain the difference before concluding that either screen is inaccurate.

Matching digital records does not verify physical stock

A comparison between recorded quantities can show agreement without establishing what is on the shelf. If a physical movement was never entered, the records being compared may lack the same event. Agreement therefore needs a defined boundary: which systems, which products, which locations, and which point in time were examined?

Compare the same inventory at the same point in time

Dutchie’s guidance on physical inventory reconciliation describes comparing physical on-hand inventory, POS quantities, and traceability quantities. It recommends ensuring that inventory-affecting events are recorded before counting. Use that documented workflow as an example, rather than assuming another platform performs the same checks automatically.

For your review, identify the packages and locations included, record the count time, and account for movements during the comparison. Where the store remains active, agree how sales, transfers, and returns during the count will be tracked. Otherwise, a later quantity may be compared with an earlier observation without anyone recognizing the timing difference.

No visible errors does not mean every event was recorded

Consider an exchange that happened at the counter but was not entered into the system. A review limited to submitted records cannot establish the details of that missing event. Staff observations, receipts, and related inventory movements may be needed to explain the difference. The absence of a visible error is not evidence that every event was captured.

Investigate the event before adjusting the balance

Dutchie identifies unrecorded exchanges as a cause of discrepancies and explains that quantity adjustments do not always resolve the issue after synchronization. Its guidance recommends checking for pending or failed transactions that might later succeed.
Before authorizing a correction, determine whether a sale, exchange, movement, or count error explains the result. Do not create a replacement transaction unless the underlying event is supported by evidence and the appropriate workflow has been confirmed.

A completed correction still needs supporting evidence

Changing a recorded quantity, explaining a discrepancy, and confirming the outcome are separate steps. A balance that now agrees with the count does not describe why the original difference existed. For an internal review, preserve the initial finding and its explanation alongside the authorized correction. This is a recommended evidence practice, not a universal legal retention rule.

Keep the explanation attached to the record

Build a short chain that another reviewer can follow: what was found, which source records supported the explanation, what changed, and who checked the result. Include identifiers and relevant times instead of relying on a screenshot alone. Closing an exception should preserve the reason it was closed. If the cause remains unknown, record that uncertainty rather than presenting an adjustment as a completed investigation.

One dashboard cannot establish the scope of an audit

Clarify whether the review concerns inventory reconciliation, a particular operational process, or a broader compliance inspection. Then identify the evidence requested for that scope. Inventory quantities do not automatically answer questions about staff actions, supporting documents, or access decisions. Avoid treating a general dashboard label as a complete statement about areas it was never designed to examine.

Separate software coverage from review coverage

Map each review question to a record, observation, or procedure that can support an answer. Ask the reviewer or responsible compliance lead to confirm the applicable requirements rather than importing a checklist from another jurisdiction. A system’s feature list describes its capabilities; your evidence map should describe what was actually examined. Keep unresolved questions visible even when the main dashboard status is green.

Turn the status into a verification routine

Use the dashboard as a starting point for a repeatable review. For each selected indicator, record its meaning and follow it through to the supporting evidence. A compact checklist can help:

  • Confirm the indicator’s definition and last evaluation time.
  • Identify the stores, packages, and reporting period covered.
  • Compare the relevant digital records with physical observations.
  • Review open exceptions and transactions awaiting resolution.
  • Verify authorized corrections against their supporting records.
  • Assign an owner and next action to every unresolved finding.

Keep the result specific. “No submission errors found in the reviewed records” communicates something different from “physical inventory reconciled for the selected packages.” State the period and coverage with the finding. If a location, room, or transaction category was excluded, make that visible. Report the evidence and its limits, so the owner can distinguish completed checks from work still pending.

Retest the procedure after a change to an integration, reporting filter, or staff responsibility. Confirm that the supporting record is still available and that the assigned person can reach it. A previously successful review should remain reproducible under the current configuration, with any changed assumptions recorded.

Choose a green indicator used in your daily review and ask its assigned manager to trace it to the underlying records. Have another person follow the same evidence and explain what the check establishes. If they cannot identify the scope, source, and unresolved exceptions, revise the procedure before using that status to support an audit-readiness report.

Top comments (0)