Requirements checklist: what to write before asking for offers
How to turn a generic need into requirements a vendor can price and you can verify.

A useful requirement states who must be able to do what, with which result, and how it is verified. "The system must be fast" cannot be tested; "a warehouse operator records a goods receipt in fewer than 3 scanner steps" can.
1. Start from roles, not features
List who will use the system and for which task. Features follow from tasks.
- Role (e.g. accounting, warehouse, sales)
- Recurring task and frequency
- Data read and data changed
2. Separate mandatory, desired, excluded
Without this split offers cannot be compared: one vendor prices everything, another only the essentials. Exclusions prevent disputes later.

3. Add a verification criterion
For every mandatory requirement, write how you will prove it is met. This becomes the basis for acceptance.
4. What to prepare
Before a structured assessment it helps to have:
- List of current systems and owners
- Two or three anonymised samples of the main flow
- Known constraints: indicative budget, deadlines, critical periods
Example
Sample requirement row
| ID | Role | Requirement | Priority | Verification |
|---|---|---|---|---|
| R-07 | Accounting | Issue an invoice from a confirmed order without re-keying data | Mandatory | From a test order, the invoice shows identical customer, lines and amounts |
| R-12 | Sales | View the customer's order history on mobile | Desired | Access from a smartphone with a sales account |


