Free tool

Requirements Builder

Capture what's actually needed before anyone builds or buys anything. Work through guided sections for new software, a business problem, a project, a process change, or a purchase — then check the quality of what you wrote and print a clean requirements document.

🔒 Everything stays in this browser — nothing is uploaded. Back up to a file if you want to keep or share it.

🔒 Saved only in this browser.

Turn requirements into a delivered project — Affinity PM tracks scope, tasks, timeline, testing, and status reports. Get early access

Tips for good requirements

Be specific. "Search results appear within 2 seconds" beats "search should be fast". Replace adjectives with numbers, names, and examples.
Make it testable. If nobody could check whether it's been met, it isn't a requirement yet. Acceptance criteria say how you'll know.
One idea each. Split anything with "and/or" or a list of features into separate requirements so each can be prioritized and tested.
Say why it matters. Record who asked for it and what problem it solves. It helps when trade-offs come up later.
Describe the need, not the solution. "Managers can approve from a phone" leaves room for good options; "build an iPhone app" doesn't.
Prioritize with MoSCoW. Must — without it, the result fails. Should — important, but there's a workaround. Could — nice to have if time allows. Won't this time — agreed to leave out for now, so it stops coming back up.

Walk the finished document through with your decision-makers and get their agreement before work or buying starts. Requirements change — keep this updated as questions get answered.