Ask for a response against each task
| Task | Required result | Evidence requested | Supplier response field |
|---|---|---|---|
| Prevent booking conflicts | One confirmed booking per room/slot | Run supplied conflict scenario | Included / change / unavailable + explanation |
| Export agreed records | IDs, dates and statuses retain meaning | Export and inspect synthetic sample | Format, limits and exclusions |
| Handover operation | Named receiver can run a test release | Rehearsal plus access inventory | Deliverables and customer dependencies |
Use this after the project brief has established the goal and scope. Give each row a feature reference in your working copy, and keep required results separate from preferred implementation. If a particular platform is mandatory, explain its dependency. Add quantity assumptions such as users, records and peak simultaneous tasks; “unlimited” is not a useful substitute for a tested workload.
Decide how evidence will be assessed
For the conflict task, a supplier saying “booking module included” leaves the failure behaviour unresolved. Ask for the scenario result and any configuration or custom work needed. Agree mandatory conditions before assigning scores; a polished demonstration should not compensate for a missing essential requirement.
Two suppliers quote different record-migration quantities. What should the next comparison do?
Show the worked answer
Request both responses against the same stated quantity and data condition. Preserve the original offers and record any revised exclusions rather than comparing headline totals directly.