Editorial dates are assigned for this collection; they do not represent original publication or author approval dates. The update date records this site revision.
Name the operating event
A product description is not an acceptance criterion. Describe the event, such as a denied credential at the receiving door or a vehicle entering a lane after dark, and identify what an authorized operator should see.
Set the test conditions
Agree on the door, camera, time of day, user role, network state and permitted access. Include who supplies test credentials and who can approve an exception. This lets competing proposals answer the same question.
Record pass, fail and retest
A complete record notes the expected result, observed result, witness and unresolved item. Corrected issues should be retested against the original scenario before final acceptance.
Working example: The scenario below is illustrative. It describes a practical design and review method, not a completed customer project or a guaranteed result.
A working scenario
A proposal says “fully integrated” but never defines what an operator sees when an access event occurs. The acceptance scenario belongs in the purchasing conversation.
The decision to make before buying
Write the people, event, expected action, timing assumptions, fault state and exclusions before finalizing a bill of materials. Include who witnesses and what counts as evidence.
A useful acceptance test
During review, ask bidders to describe the same normal, denied and outage event with actual product versions. At completion, observe those scenarios with operators rather than only installers.
What the owner should receive
Keep a signed test matrix, responsibilities, assumptions, pass criteria and exception log linked to the proposal. This reduces ambiguous change orders.
Questions owners ask
Why define acceptance before signing?
The parties otherwise may mean different things by “complete.” A camera vendor may mean video appears, while the owner needs a retrievable nighttime incident clip. A door supplier may mean the badge grants access, while facilities needs a tested latch and exit. Put those outcomes into the scope while changes are still affordable to evaluate.
What should a test line contain?
State location, starting condition, action, expected physical and software behavior, observer, evidence and exception rule. Include at least one relevant fault condition. Identify third-party witnesses and prerequisites before work begins. A sample test can also expose missing power or IT responsibilities in the bid.