Write Acceptance Criteria for an Equipment Tracking Pilot

A pilot should end with a decision the operator can explain: accept the agreed scope, accept it with specific conditions, extend a defined test, or stop. That is difficult when success was never written down. A memorable demonstration can then outweigh unresolved identity problems, while one unusual exception can overshadow useful performance elsewhere.

Write acceptance criteria for the asset tracking pilot before installation and testing. The criteria should say what will be tested, who will verify it, what counts as a usable result and what happens when evidence is missing. The single-facility pilot guide explains the case for starting small; acceptance criteria make that small start reviewable.

Define the scope in equipment and places

Name the building, included equipment categories and the spaces in scope. Identify exclusions such as equipment not enrolled in the pilot or locations awaiting setup. A result cannot be interpreted fairly if the tested population keeps changing without a record.

A hypothetical operator pilots visibility for a defined set of mobile equipment across two wings and a storage area. The operator records which units belong to the test and which room names staff will see. When an additional unit appears during the pilot, it is either formally added with a date or kept outside the original sample. It does not silently change the denominator.

Choose a sample that represents the operating questions. Include ordinary storage, equipment that changes rooms and situations where staff must distinguish similar units. Avoid selecting only convenient equipment that everyone already knows how to find.

Separate four acceptance questions

Identity asks whether the record describes the exact physical unit. Location asks whether the reported place is useful and current enough for the agreed search task. Workflow asks whether staff can act on that information. Exception handling asks whether a mismatch reaches someone who can resolve it.

Acceptance area	Example evidence to agree in advance
Identity	Reviewer matches physical identifiers to the intended records
Location	Reviewer checks a defined sample against an independently recorded location
Search workflow	Staff use the agreed view to find a specified unit and record the outcome
Exception route	A mismatch receives an owner, response and documented resolution or limitation

Set operator-approved thresholds for the actual test rather than borrowing a generic percentage. Define what an acceptable room match means, how observation times are recorded and how excluded cases are handled. The vendor and operator should understand the same test before seeing the result.

Test an ordinary operating task

Ask a staff member to work through a realistic equipment search without coaching that would be unavailable on a normal shift. Record the starting request, the information shown, whether the correct equipment was found and what uncertainty remained.

For the hypothetical two-wing pilot, a search might reveal that staff recognize a room by a different name than the pilot view uses. That can be a fixable naming issue rather than a failed location result. Preserve the distinction, correct the name through the agreed process and repeat the affected test.

Do not ask a location test to establish readiness, suitability or lending permission. Those remain staff decisions. A useful search may end with “equipment located, availability requires confirmation.” That is a legitimate operational outcome if the workflow routes the remaining question clearly.

Define the treatment of failures and retests

An exception record should include the exact unit, observation time, expected result, observed result and reviewer. Add the investigation owner and the scope of any corrective action. Keep the original result when a retest is run.

Avoid repeating only failed cases until they succeed and then reporting the final attempts as the entire pilot. Show the original test, the change and the retest separately. If a setup change affects the wider population, agree whether a broader sample must be checked again.

Also record cases that could not be tested. Equipment unavailable for verification is different from equipment that failed the test. Both matter, but they answer different questions.

Make the final decision proportional to the evidence

At acceptance review, compare results with the original criteria and list unresolved issues. A conditional acceptance needs an owner, completion date and affected scope for each condition. An extension needs a focused question that more testing can answer, not simply more time.

Room-level equipment visibility is the relevant product capability for a Norra visibility pilot. Norra is an AI equipment manager using proprietary smart tags. Its cross-building visibility can support future sharing decisions, while humans retain permission and readiness responsibilities. Keep financial outcomes and clinical utilization claims outside the location acceptance result unless they have their own defined evidence. The pilot becomes useful when its conclusion says exactly what the operator has learned and what remains unproven.