A one-page brief for an internal application states the problem, who encounters it and what the first release must achieve. You can write it before speaking to a provider. Start from a recent example, such as a service request that had to be found across several spreadsheets. Record the time spent and the information that was missing so you can compare the effect of the change later.

Describe the current workflow in a few lines
In this illustrative example, a service company receives enquiries by phone and email. Colleagues enter cases into a spreadsheet, and the coordinator assigns jobs. Technicians learn about changes through messages, while customer confirmation happens separately. A request can be assigned twice if two colleagues work from different copies of the spreadsheet. A new form only solves this problem if there is a shared record and a clear assignment rule.
Record volume from actual activity. How many requests arrive in an ordinary week? What happens during a busy period? How many colleagues work at the same time? Attach a sample stripped of personal or commercially confidential data. A representative row often shows what needs to happen better than a long list of field names from the old spreadsheet.
| Item | What to write | Service company example |
|---|---|---|
| Objective | The specific outcome you want | The team can see the current state of each request |
| Users | Who uses the system and with what rights | Dispatcher records, coordinator assigns, technician updates |
| Normal case | What should happen in sequence | Request, assignment, job and closure |
| Exception | A situation that changes the workflow | Technician becomes unavailable and the case is reassigned |
| First release | What is essential and what can wait | Tracking and assignment first, customer portal later |
| Acceptance | How to show the workflow works | Reassignment is visible immediately and retains its history |
Set the boundaries of the first release
Specify what each role needs. A dispatcher has to record an enquiry and find a case. A coordinator needs the team's status and can reassign a job. A technician views assigned jobs and records the outcome. State who approves a change to the rules and whether the application needs to exchange data with existing tools.
Include at least one common exception. If a technician falls ill, the coordinator reassigns the job and the business needs to know who made the change and when. If a request arrives without an address, it might stay pending until the address is provided. Your acceptance criteria then cover a normal working day, including the exceptions that take time.
Specify what happens to the old records
Record which fields to retain and for how long, who can correct values and what happens to duplicate rows. In the service example, the company could import open jobs and keep the other records in an accessible archive. Confirm the rule with the team before sharing it with the provider. Migrating all records can take different work from importing active cases, even if the application looks the same after launch.
Try the criteria before requesting a quote
Write each acceptance criterion as a starting situation, a user action and an observable outcome. For example, when the coordinator reassigns an existing job, the new technician sees it in their list and the history records who made the change and when. Also check what happens when two colleagues try to assign the same enquiry. When discussing development of your business application, ask the provider to estimate the tests and identify the dependencies.
Appoint someone to confirm the process and one or two users to check the first release. If a feature is out of scope, record who decides when it will be reconsidered. Send the same brief to every provider you are comparing. That lets you evaluate quotes against the same situations and refer back to the document when new requirements arise.
In the quote, check who delivers the import, who validates the data and who measures results during the first few weeks. Time to job assignment and the number of cases assigned twice are two possible measures for this company. Compare them with the situation recorded in the brief.