BUSINESS REQUIREMENTS DOCUMENT

Project: <INSERT PROJECT NAME>

The purpose of this Business Requirements Document (BRD) is to capture, validate and
communicate the business need and requirements for approval

PMO note: When using this template, remove or replace all placeholders (e.g. red text).
Apply the styles from the Style Ribbon to your content to ensure a consistent look and feel.

Revision Date DD Month YYYY

Sign-off Date DD Month YYYY
Version Number x.y
Author <INSERT NAME>
<INSERT PROJECT NAME>
Business Requirement Document
_____________________________________________________________________________________________________________________

Table of Contents

1 DOCUMENT REVISION LOG.......................................................................................................................................3

2 PROJECT OVERVIEW.................................................................................................................................................4
3 IN SCOPE STATEMENTS............................................................................................................................................4
3.1 IN SCOPE STATEMENTS.....................................................................................................................................4
3.2 OUT OF SCOPE STATEMENTS.............................................................................................................................4
4 ASSUMPTIONS , INTERDEPENDENCIES & CONSTRAINTS.................................................................................................5
4.1 ASSUMPTIONS................................................................................................................................................5
4.2 INTERDEPENDENCIES........................................................................................................................................5
4.3 CONSTRAINTS.................................................................................................................................................5
5 CONTRIBUTING RESOURCES......................................................................................................................................5
6 CURRENT STATE PROCESS FLOWS..............................................................................................................................5
7 FUTURE STATE PROCESS FLOWS................................................................................................................................6
8 BUSINESS REQUIREMENTS........................................................................................................................................6
8.1 <INSERT GROUPING TITLE HERE >......................................................................................................................6
8.2 REPORTING.................................................................................................................................................... 7
9 ONE TIME REQUIREMENTS <OPTIONAL>...................................................................................................................7
9.1 <INSERT GROUPING TITLE HERE >......................................................................................................................7
10 DETAILED REQUIREMENTS........................................................................................................................................7
11 APPROVAL ............................................................................................................................................................ 8
12 APPENDIX <O PTIONAL>..........................................................................................................................................9
12.1 APPENDIX A - GLOSSARY <OPTIONAL>................................................................................................................9
12.2 APPENDIX B - SUPPORTING DOCUMENTATION <OPTIONAL>...................................................................................9
<INSERT PROJECT NAME>
Business Requirement Document
_____________________________________________________________________________________________________________________

1 DOCUMENT REVISION LOG

The purpose of the revisions table is to communicate major versions of the document.

Date Version Description Reqt ID # Author

Description must include a high-level,
itemized summary of changes including
DD Month YYYY x.y <INSERT NAME>
what section was edited and a brief
summary of why.

Private & Confidential

Page 3 of 9
<INSERT PROJECT NAME>
Business Requirement Document
_____________________________________________________________________________________________________________________

2 PROJECT OVERVIEW
The Project Charter is the source document for the Background and Objectives. The following is an excerpt from
the Charter from <Date>. To ensure you have the most up-to-date information, please refer back to the Charter
<insert hyperlink to the Charter>.

<INSERT CONTENT>

3 IN SCOPE STATEMENTS
3.1 IN SCOPE STATEMENTS
The following table outlines the scope of the requirements at a high level.

Scope Items Description / Statement

E.g. Individual Client Types E.g. Individual, ITF, Joint with Spouse & Joint without Spouse

3.2 OUT OF SCOPE STATEMENTS

The following table outlines the items explicitly out of scope, including the reason and/or justification for this
decision.

Scope Items Description / Statement

E.g. Individual Client Types E.g. Individual, ITF, Joint with Spouse & Joint without Spouse

Private & Confidential

Page 4 of 9
<INSERT PROJECT NAME>
Business Requirement Document
_____________________________________________________________________________________________________________________

4 ASSUMPTIONS, INTERDEPENDENCIES & CONSTRAINTS

4.1 ASSUMPTIONS
This section contains any assumptions being made that affect the requirements, these are believed to be true, but
have not been confirmed. Include the impact if the assumption is false.

A1. <INSERT CONTENT>

A2. <INSERT CONTENT>

4.2 INTERDEPENDENCIES
This section contains known relationships among project and project-related factors that could impact the
requirements.

I1. <INSERT CONTENT>

I2. <INSERT CONTENT>

4.3 CONSTRAINTS
This section contains any known restrictions or limitations that may be imposed on the solution.

C1. <INSERT CONTENT>

C2. <INSERT CONTENT>

5 CONTRIBUTING RESOURCES
This section identifies the primary stakeholders engaged in gathering the requirements.

<Identify the primary stakeholders engaged in gathering requirements and their general role in that process. A
separate Stakeholder Register captures project stakeholder details in greater detail.>

Name Business Unit/ Department Role

6 CURRENT STATE PROCESS FLOWS

This section identifies current state process flows of automated and non-automated tasks.

<Insert current state process flow diagram, e.g. swimlane>

<Optional>
Process Flow Narrative (supplemental to the process flow)

Private & Confidential

Page 5 of 9
<INSERT PROJECT NAME>
Business Requirement Document
_____________________________________________________________________________________________________________________

# Activity Input/ Output Who What How

7 FUTURE STATE PROCESS FLOWS

This section identifies future state process flows of automated and non-automated tasks.

<Insert future state process flow diagram, e.g. swimlane>

<Optional>
Process Flow Narrative (supplemental to the process flow)

# Activity Input/ Output Who What How

8 BUSINESS REQUIREMENTS
High level business requirements describe what is required, the business need in business language, unrelated to
any system or system functionality. Business priority helps ensure the work is approached in the appropriate order.

Business Priority Legend:

Critical Requirements that deliver the core value without which the product
is not acceptable to stakeholders (no acceptable workaround
available).
High Requirements that are necessary but deferrable making the product
less usable but still functional (acceptable workaround available).
Nice to Have Requirements that add convenience (“Nice to Have”), are considered
if there are sufficient resources but the product functions well
without it.

8.1 <INSERT GROUPING TITLE HERE >

Business Business
Requirement Description Business Rule/Notes
Reqt ID Priority
Capability Title Here (E.g. Online Access)
8.1.1.1
E.g. Clients shall view their account balances online Critical

8.1.1.2

Capability Title Here

Private & Confidential

Page 6 of 9
<INSERT PROJECT NAME>
Business Requirement Document
_____________________________________________________________________________________________________________________

Business Business
Requirement Description Business Rule/Notes
Reqt ID Priority
8.1.1.3

8.1.1.4

8.2 REPORTING
Busines
Business
s Report Name / Description Business Rule/Notes
Priority
Reqt ID

Report Title Here (e.g. ‘User Access List’)

8.2.1.1 Business need can be
Report Description, e .g. ‘A list of users that have High documented here – why is
accessed a specific system within the last <XX> number this report needed?
of days. Ran ad-hoc, for IT InfoSec. e.g. User Access List is
required for audits.
[ EXAMPLE – Delete:
CE Summary for [Branch Name] or [Department Name]
[ Enables the Department
8.2.1.2 A listing of all IIROC Registrants within a Branch or a Heads / Branch Managers
[ High ]
Department, listing their current Continuing Education to view the progress of their
(CE) status. Provides a summary of CE completion for Department/Branch
the Branch/Department ] towards completing the
IIROC CE requirements. ]
8.2.1.3

9 ONE TIME REQUIREMENTS <OPTIONAL>

Temporary and/or one time capabilities, conditions or activities that are necessary in order to deploy the solution.

9.1 <INSERT GROUPING TITLE HERE >

Business Business
Requirement Description Business Rule/Notes
Reqt ID Priority
Capability Title Here
9.1.1.1 E.g. Seven years of transaction history must be
Critical Private Client Group
migrated to new Client Access database.
9.1.1.2

Capability Title Here

9.1.1.3

Private & Confidential

Page 7 of 9
<INSERT PROJECT NAME>
Business Requirement Document
_____________________________________________________________________________________________________________________

Business Business
Requirement Description Business Rule/Notes
Reqt ID Priority
9.1.1.4

10 DETAILED REQUIREMENTS
Detailed business requirements describe what features and functions the solution must provide to meet the
business needs (i.e. BCP, disaster recovery, performance requirements).

<Insert Detailed Requirements Sheet Here>

11 APPROVAL
The Requirements described in this Business Requirements Document are confirmed to be complete and accurate
on this ______ day of __________ by the following people.

Electronic signoff is permitted by attaching an email within this section.

(Project Sponsor - Name)

<INSERT ELECTRONIC SIGN-OFF>

(Project Owner(s) – Name) SME’s assigned to by the Project Sponsor

<INSERT ELECTRONIC SIGN-OFF>

Private & Confidential

Page 8 of 9
<INSERT PROJECT NAME>
Business Requirement Document
_____________________________________________________________________________________________________________________

12 APPENDIX <OPTIONAL>

12.1 APPENDIX A - GLOSSARY <OPTIONAL>

This section captures any industry or line of business terms and acronyms used within the Project and the Business
Requirements Document.

<Use the Glossary introduction and table below as Appendix A, when a glossary needs be included>

Term Acronym Description

12.2 APPENDIX B - SUPPORTING DOCUMENTATION <OPTIONAL>

This section captures any supporting documents that inform the Business Requirements Document.

<Use the Supporting Documentation introduction and table below as Appendix B, when related or supporting
documents need to be included>

Supporting Document Description Supporting Document File

<Insert Supporting Document

E.g. Account Numbering System - RAP Codes vs Sub TypesDocuments
here>

Private & Confidential

Page 9 of 9