A business requirements document (BRD) is written for the people who approve the change. Its order follows their questions: why, what, for whom, and only then the detail.
A typical structure:
- Executive summary: the problem and the proposed change in a few lines.
- Business objectives: the goals and how success is measured.
- Scope: what is in and what is out.
- Stakeholders: who is affected and who decides.
- Current state and future state: how work is done today and how it will be done, often with process maps.
- Business requirements, then stakeholder requirements, each traced to an objective.
- Business rules, assumptions, constraints and dependencies.
- Risks and open issues.
- Glossary and sign-off.
The classic mistake is jumping to the requirements before scope is agreed: pages of detail for something that turns out to be out of scope. Keep solution design out; it belongs in later documents.