Technical Demo Pass-Fail Criteria: A Scorecard
Published October 21, 2026 · By Kate Steinmeyer · Presales

A technical demo scorecard prevents “That looked good” from standing in for a verified result. Define the test and evidence before the session, then record exactly what the environment showed.
Choose observable criteria
A criterion should name the condition, action, and expected result. “Supports permissions” is too broad. “A requester cannot see the approve action for a manager-owned request in the configured test account” can be observed. Record the product version, role, data, and relevant setting.
Mark which criteria are must-pass and which are exploratory. This helps the team avoid celebrating a polished secondary feature while a central requirement remains untested.
Score what happened
Use pass, fail, partial, or not tested. Attach a screenshot, log, recording, or written observation as appropriate. A prepared capture may explain a workflow but should not be scored as a live test of the buyer’s environment.
For a hypothetical API demo, the request may be accepted but the downstream update may not appear. That is a partial result with a specific follow-up, not a pass because one screen looked correct.
Review disagreements immediately
Ask the buyer whether the evidence answers their requirement. Record alternative interpretations and assign an owner to resolve them. Keep the scorecard with the session notes so a later summary cannot silently strengthen the result.
A POC scope covers a longer validation program. This scorecard works for one focused technical demo.
Try a filled scorecard
This fictional example shows how to separate observed behavior from an untested requirement. Use pass, fail, partial, or not tested based on what happened in the agreed setup.
| Criterion | Observation | Result |
|---|---|---|
| Manager can approve assigned item | Action and final state shown in the test account | Pass |
| Requester cannot approve own item | Attempt blocked in the test account | Pass |
| Expired request cannot be approved | Approval still worked after the test request expired | Fail |
| Decision notification reaches the requester | In-app notice appeared; email delivery was not checked | Partial |
| Decision history is retained | Record opened after the action | Pass |
| Buyer identity mapping | No live connection shown | Not tested |
Agree on the criteria and environment before the session. If a step fails, record the starting state and whether a retry changed the outcome; do not quietly mark it as pass after switching environments. Share screenshots or logs only through a channel appropriate for the data they contain.