Business Requirements Document

Project Name Here

a close up of a clock

Company Name

By John Smith

Feb 1, 2021

Executive Summary


Use this space to give a high-level overview of the project. This Business Requirements Document (BRD) outlines the goals and expectations of a project. It contains both functional and non-functional requirements including the user’s needs and expectations, the purpose behind this solution, and any high-level constraints that could impact a successful deployment.

Project Objective

This section describes the desired results of the project, which often includes a tangible deliverable.


  • Specific: Who? What? Where? Why? When?
  • Measurable: What are the metrics? Any numbers or percentages to reach?
  • Achievable: Do you have resources and skills to reach the goal you are setting?  
  • Realistic: Does it match your organization's overall goals?  
  • Timely: When will you finalize this project?

Needs Statement

It's a good idea to explain why you're tackling this project. Explain why the project is needed for the business and how the project will meet these needs. It should present facts and evidence to support the need for the proposed project.

Project Scope


This section describes the scope of the project at a high level.  Summarize the business requirements for this project. What should be included in the scope and what should not?

In Scope

The following areas are in scope for this project:

  • Point 1
  • Point 2
  • Point 3
  • Point 4
  • Point 5

Out of Scope

The following areas are out of scope for this project:

  • Point 1
  • Point 2
  • Point 3
  • Point 4
  • Point 5

Functional Requirements


This section should detail the functional requirements of the project. Outline, in detail, the functional requirements and corresponding features including diagrams, charts, and timelines.

Non-Functional Requirements


Also include non-functional requirements, such as processing time, concurrent users, availability, etc. These criteria will be used to assess the system operation, rather than specific behaviors.

ID

Requirement

Priority

FRAQ1

Functional Requirement 1

High

FRQ2

Functional Requirement2

High

FRQ3

Functional Requirement 3

Medium

FRQ4

Functional Requirement 4

Low

FRQ5

Functional Requirement 5

Low

ID

Requirement

Priority

NFRQ1

Non-Functional Requirement 1

High

NFRQ2

Non-Functional Requirement 2

High

NFRQ3

Non-Functional Requirement 3

Medium

NFRQ4

Non-Functional Requirement 4

Low

NFRQ5

Non-Functional Requirement 5

Low

Schedule, Timeline and Deadline

Outline a project timeline to ensure that all stakeholders are aware of the deadline and important milestones along the way.  What is the final deadline? What is the timeline for delivering specific requirements? 

Milestone 1 (Feb. 20)


  1. Point 1
  2. Point 2
  3. Point 3
  4. Point 4

Milestone 2 (Feb. 28)


  1. Point 1
  2. Point 2
  3. Point 3
  4. Point 4

Milestone 3 (Mar. 15)


  1. Point 1
  2. Point 2
  3. Point 3
  4. Point 4

Milestone 4 (Mar. 28)


  1. Point 1
  2. Point 2
  3. Point 3
  4. Point 4

Risks

Every project has inherent risks that may cause delays or even failure of a project. Use this section to outline the risks to show you know what they are, and also identify ways in which you would mitigate those risks.

Glossary of Terms

If needed, add a glossary of terms used in the document for clarification. These could be terms that are unique to the organization, the technology being used in the project or the standards in use.

Exit