BRD Block
Document business requirements with objectives, drivers, stakeholders, scope, and success criteria. Bridge the gap between business needs and technical solutions.
The BRD (Business Requirements Document) block captures business-level requirements and objectives. It focuses on the why behind initiatives, documenting business drivers, stakeholder interests, scope boundaries, and success criteria.
When to Use
Block Properties
| Property | Required | Description |
|---|---|---|
| Title | Yes | BRD document title |
| Version | No | Document version number |
| Status | No | Draft, In Review, Approved, or Obsolete |
| Author | No | Document author |
| Date | No | Creation or last update date |
| Executive Summary | No | High-level overview for stakeholders |
| Business Objectives | No | What the business aims to achieve |
| Business Drivers | No | Why this initiative is needed now |
| Stakeholders | No | Key people with name, role, and interest |
| In Scope | No | What is included in this initiative |
| Out of Scope | No | What is explicitly excluded |
| Success Criteria | No | How success will be measured |
| Risks | No | Business risks with impact and mitigation |
| Assumptions | No | Conditions assumed to be true |
| Constraints | No | Business limitations |
| Timeline | No | Expected delivery timeframe |
Risk Impact Levels
Example: Digital Transformation BRD
A complete BRD for a customer portal modernisation initiative.
Example: Early Stage BRD
A draft BRD for initial stakeholder discussion.
Best Practices
| Practice | Description |
|---|---|
| Executive Summary Last | Write the executive summary last, after all details are complete |
| Measurable Objectives | Make business objectives measurable and time-bound |
| Early Stakeholder Identification | Identify all stakeholders early and document their interests |
| Explicit Scope Boundaries | Be explicit about scope boundaries to prevent scope creep |
| Quantified Risks | Quantify risks where possible (cost, time, probability) |
| Regular Assumption Review | Review assumptions regularly as the project progresses |
| Linked Success Criteria | Link business requirements to specific success criteria |