# Everything to decide before development starts

Changes are cheap on paper and expensive in code. This checklist covers the decisions that most often get missed until a project is half built: who can see and change what, what happens when something goes wrong in a workflow, which data comes in and in what state, which systems must be connected, how each feature will be checked, and who looks after the system after launch. Use it with your team before you ask for quotes, or with the development team in the first workshop. Each item is a question to answer, not a feature to buy.

## How to use it

1. Go through one section at a time with the people who know that part of the work.
2. Tick an item only when the answer is written down somewhere the team can find it.
3. Leave "we don't know yet" as an answer where it is true; it is better than a guess.
4. Share the result with every team you ask for a quote, so they price the same thing.

## Users and roles

- [ ] Every kind of user is listed.
- [ ] What each role can see, add, change and delete.
- [ ] Who approves what, and what happens when they are away.
- [ ] Whether customers or suppliers log in too.

## Workflows

- [ ] Each main process is written as numbered steps.
- [ ] What starts each process: a customer, a date, a person.
- [ ] What happens on exceptions: cancel, return, reject, change.
  - Tip: Exceptions are where most hidden work is. List the ones that happen every week.
- [ ] Who gets notified, how, and when.

## Data

- [ ] The main records: customers, orders, products, cases, staff.
- [ ] Which fields are required and which are optional.
- [ ] Existing data to import, and how clean it is.
  - Tip: Duplicates and different spellings in old sheets take real time to clean. Say if you know they exist.
- [ ] Reports and exports people need, and how often.

## Connections to other systems

- [ ] Every system to connect, and who owns its account.
- [ ] Direction of each connection: send, receive or both.
- [ ] E-invoicing, if you issue invoices from the system.
  - Tip: For example Egypt's ETA or Saudi Arabia's ZATCA. Confirm the rules with your accountant.
- [ ] Payments, messaging and email providers you already use.

## Quality, security and access

- [ ] Languages, and whether Arabic needs a right-to-left layout.
- [ ] Devices, and whether anything must work with a weak connection.
- [ ] How many people use it at the same time at busy hours.
- [ ] Logins, permissions, a history of changes, and backups.

## Acceptance

- [ ] How each feature will be checked before it counts as done.
- [ ] Who signs off each milestone on your side.
- [ ] Test data and test accounts the team can use.

## After launch

- [ ] Training for each group of users.
- [ ] Who to call when something breaks, and how fast they answer.
- [ ] Hosting, updates and running costs over time.
- [ ] Who owns the code and the data.

---

From NOVA Solutions · novasolutions.bassemhazem.com
https://www.nova-solutions.co/en/resources/requirements-checklist
