Application Requirements Checklist
A requirements checklist for deciding what a web application actually needs before design and development begin.
Working record
| Check | What to do | Evidence to retain |
|---|---|---|
| Users | Define the user roles and tasks. State which records and actions each role needs to access. | The users record, its source and the person responsible for resolving missing evidence. |
| Core workflow | Describe the trigger, inputs, sequence, handoffs and exceptions. Check the current process before specifying a replacement. | One real source record, process steps and an exception case. |
| Inputs | Retain the original source and state its format, unit and period. Mark assumptions separately from measured values. | Source values, conventions and missing details. |
| Rules | Write the conditions that control the workflow. Include approval and exception cases. | The rules record, its source and the person responsible for resolving missing evidence. |
| Acceptance criteria | Describe a testable result for each essential requirement, including failure or missing-input cases. | The acceptance criteria record, its source and the person responsible for resolving missing evidence. |
Review the decision
A requirements checklist for deciding what a web application actually needs before design and development begin. Keep users, core workflow, inputs attached to the conclusion so the next owner can challenge the assumptions. Resolve missing evidence before treating this record as approval.
Continue the decision
How to Write Requirements Developers Can Actually Use · ROAS: What the Number Means and How to Use It.
Calculation and source notes
Keep the displayed formula, input units and model scope with the result. Corrections or questions can be sent through the request section on this page.
Content updated: October 11, 2026