# BRD Evaluation Checklist

Answer each question Yes or No. If any answer is No, revise before proceeding.

- [ ] Does every functional requirement trace back to a VOC quote or business goal?
- [ ] Is every requirement testable — can you definitively say "built" or "not built"?
- [ ] Are there any vague words like "user-friendly," "fast," or "intuitive" that need measurable replacements?
- [ ] Does each requirement specify WHO it's for (which user role)?
- [ ] Are the requirements numbered consistently (FR-001, FR-002)?
- [ ] Is there a clear priority on each requirement (Must Have / Should Have)?
- [ ] Are edge cases covered — what happens on errors, empty states, and invalid input?
- [ ] Is the scope section clear — can you point to a requirement and say "that's Phase 2, not MVP"?
- [ ] Does the system architecture section specify exact technologies, not just categories?
- [ ] Would a developer reading this document be able to start building without asking clarifying questions?