1. Templates
  2. Contracts
  3. Business Requirements Document Template (BRD)
POPULAR
Image 5

Business Requirements Document Template

Prepared by:[Sender.Company]

Prepared for:[Client.Company]

Image 3
Image 4
Image 20

Executive summary

Attached you'll find the business requirements document that covers the work required by ​[Client.Company] . Sections contained within the document include Business Objectives, Background, Scope, Features, Functional Requirements, Personnel Requirements, Reporting and Quality Assurance, Delivery Schedule, Other Requirements, Assumptions, Limitations, Risks. One of the issues faced by [Client.Company] is (client issue) The goal of [project name] is to allow [Client.Company] to (client objective). By bringing on [Sender.Company] to assist with the project, ​[Client.Company] gets the benefit of [Sender.Company] 's years of experience in services to [client's industry] . ​[Sender.Company] appreciates the faith that [Client.Company] has placed in us. Our company's mission is to (Company mission). We understand the intricacies of services to the (client's industry).[Sender.Company] will work hard to ensure that [Client.Company] receives everything necessary to accomplish their business goals upon the successful delivery of [project name] .

Image 21

Business objectives

2.1 Project Solution

The new (project solution) will help [Client.Company] accomplish its goal of [business deliverable] . [Sender.Company] will oversee quality control at each step of the process to avoid issues during deployment.

2.2 Value

Thanks to [project name] , [Client.Company] can move further toward their goal of [client objective] . By doing so, [Client.Company] puts itself in a position to (overall business strategy).

2.3 Next Steps

The success of [project name] will impact [Client.Company] positively by [positive business impacts] . In addition, there will be established metrics to gauge the impacts of the [project solution] release. By implementing [project name] , [Client.Company] can put itself into a position to accomplish the following business goals:

2.3.1 [Client.Company] should have the ability to (business objective 1). 2.3.2 [Client.Company] should have the ability to (business objective 2). 2.3.3 [Client.Company] should have the ability to (business objective 3). 2.3.4 [Client.Company] should have the ability to (business objective 4). 2.3.5 [Client.Company] should have the ability to (business objective 5).

The stakeholders involved in the project include: (Stakeholder 1)(stakeholder title)(stakeholder department) (Stakeholder 2)(stakeholder title)(stakeholder department) (Stakeholder 3)(stakeholder title)(stakeholder department) (Stakeholder 4)(stakeholder title)(stakeholder department) (Stakeholder 5)(stakeholder title)(stakeholder department)[Client.Company] decided to pursue [project name] because (description of business drivers) .

2.4 Functionality

The new functionality provided by [project name] will allow [Client.Company] to accomplish their goal of (business goal) . Changes will include modifications to (systems modified) and (business processes modified) . (Additional functionality of new process)

2.5 Process diagrams

(Original process diagram) (Current process diagram)

Image 22

Background

Currently, [Client.Company] handles (business process) by (description of current process). Because of changing business needs caused by (reason for change) , the business must now (new process) . As a result, [Client.Company] is initiating [project name] to allow [Sender.Company] to (new business process) .[Sender.Company] is the ideal partner to assist [Client.Company] pursue their desired business strategy because (Company services/experience). (Additional background description of issues) (Additional background text)

Scope

The scope of the [project name] initiated by [Client.Company]​ should cover the following changes to business procesess:

4.1 Project objective

[Client.Company] (PROJECT DESCRIPTION (IF ANY)) Prepared by: ​[Client.FirstName][Client.LastName][Client.Company] MM / DD / YYYY The primary objective of [project name] is to (project objective) . (Additional description of overall project objective)

Image 23

4.2 Project deliverables

4.2.1 [Sender.Company] must provide [Client.Company] with the ability to (deliverable 1). 4.2.2 [Sender.Company] must provide [Client.Company] with the ability to (deliverable 2). 4.2.3 [Sender.Company] must provide [Client.Company] with the ability to (deliverable 3) . 4.2.4 [Sender.Company] must provide [Client.Company] with the ability to (deliverable 4) . 4.2.5 [Sender.Company] must provide [Client.Company] with the ability to (deliverable 5) . 4.2.6 [Sender.Company] must provide [Client.Company] with the ability to (deliverable 6) .

4.2.7 [Sender.Company] must provide [Client.Company] with the ability to (deliverable 7) .

4.3 Project milestones

The following milestones must be hit by [Sender.Company] on the dates indicated below: 4.3.1 Milestone 1 – (MM.DD.YYYY) 4.3.2 Milestone 2 – (MM.DD.YYYY) 4.3.3 Milestone 3 – (MM.DD.YYYY) 4.3.4 Milestone 4 – (MM.DD.YYYY) 4.3.5 Milestone 5 – (MM.DD.YYYY)

4.4 High-level requirements

[Sender.Company] must adhere to each of [Client.Company] ’s requirements as listed below: 4.4.1 [Sender.Company] must (requirements description 1) to meet the client’s need for [business need 1] . 4.4.2 [Sender.Company] must (requirements description 2) to meet the client’s need for [business need 2] . 4.4.3 [Sender.Company] must (requirements description 3) to meet the client’s need for [business need 3] . 4.4.4 [Sender.Company] must (requirements description 4) to meet the client’s need for [business need 4] . 4.4.5 [Sender.Company] must (requirements description 5) to meet the client’s need for [business need 5] .

4.4.6 [Sender.Company] must (requirements description 6) to meet the client’s need for [business need 6] . 4.4.7 [Sender.Company] must (requirements description 7) to meet the client’s need for [business need 7] . 4.4.8 [Sender.Company] must (requirements description 8) to meet the client’s need for [business need 8] .

4.5 Assumptions

[Sender.Company] should keep the following assumptions in mind when performing the work required by [Client.Company] : 4.5.1 [Sender.Company] should assume that [Client.Company] (assumptions description 1) . 4.5.2 [Sender.Company] should assume that [Client.Company] (assumptions description 2) . 4.5.3 [Sender.Company] should assume that [Client.Company] (assumptions description 3) . 4.5.4 [Sender.Company] should assume that [Client.Company] (assumptions description 4) . 4.5.5 [Sender.Company] should assume that [Client.Company] (assumptions description 5) .

4.6 Acceptance criteria

[Sender.Company] must adhere to the following acceptance criteria that define success for [project name] , as outlined by [Client.Company] : 4.6.1 The user must be able to (acceptance criteria description). 4.6.2 The system must allow the user to (acceptance criteria description). 4.6.3 The user must be required to (acceptance criteria description). 4.6.4 The system must validate (acceptance criteria description) before proceeding with (system process). 4.6.5 The system must prompt the user to (acceptance criteria description) before allowing the user to (user process) .

Image 24

4.7 Constraints

[Sender.Company] must take the following constraints into consideration when mapping out the technical details of [project name] : 4.7.1 The (business system) currently does not allow for (constraints description). 4.7.2 Users of (business system) are currently limited to functions that include [constraints description] . 4.7.3 There is currently a data storage limit of (data storage limit) that limits the system to (constraints description) . 4.7.4 Reporting and other system insights are currently limited to (constraints description) because of (additional constraint description) . 4.7.5 Users can only process up to (constraints description) within (business system).

Features

[Sender.Company] will introduce the following features upon completion of [project name] :

5.1 [Sender.Company] must add (feature name) to (business system). The feature should give the user the ability to (feature description) .

The feature should give the user the ability to (feature description) . 5.3 [Sender.Company] must add (feature name) to (business system). The feature should give the user the ability to (feature description) . 5.4 [Sender.Company] must add (feature name) to (business system). The feature should give the user the ability to (feature description) . 5.5 [Sender.Company] must add (feature name) to (business system). The feature should give the user the ability to (feature description) . 5.6 [Sender.Company] must add (feature name) to (business system). The feature should give the user the ability to (feature description) .

Image 26

Functional requirements

6.1 Context

[Sender.Company] must provide [Client.Company] with the following system updates and expand the functionality available to users as outlined in the context diagrams below: Exhibit 1: context diagram Exhibit 2: context diagram

6.2 Methodology

[Sender.Company] will adhere to an (Agile/Waterfall/Scrum/Kanban) framework when planning out the different phases of [project name]. That will afford the development team and all project stakeholders the best chance of identifying potential risks to ensure they don’t disrupt the delivery of [project name].

6.2 User requirements

6.2.1 System use cases The following diagrams provide a visualization of what [Client.Company] requires from the system: 6.2.1.1 (system use case diagram 1) 6.2.1.2 (system use case diagram 2) 6.2.1.3 (system use case diagram 3) 6.2.1.4 (system use case diagram 4) 6.2.1.5 (system use case diagram 5) 6.2.2 System use case descriptions The following system use cases provide a text description of what [Client.Company] requires from the system through changes put in place by [project name] : 6.2.2.1 The system must (system use case description 1). 6.2.2.2 The system must (system use case description 2). 6.2.2.3 The system must (system use case description 3).

6.2.2.4 The system must (system use case description 4). 6.2.2.5 The system must (system use case description 5).

6.3 Data flow diagrams

The following data flow diagrams outline the flow of information through different systems affected by the changes brought about as a result of [project name] : 6.3.1 (data flow diagram 1) 6.3.2 (data flow diagram 2) 6.3.3 (data flow diagram 3)

6.4 Logical data model

The following logical data model showcases the information captured and processed based on the system changes implemented by [project name] :

[Client.Company] will require the following personnel in place to ensure the timely completion of ​[project name] by [Sender.Company] :

Personnel requirements

Name

Price

QTY

Subtotal

Item 1

Description of first item

$35.00

5

$175.00

Item 2

Description of second item

$55.00

1

$55.00

Item 3

Description of third item

$200.00

1

$200.00

Image 27

Reporting and quality assurance

[Client.Company] requires that [Sender.Company] enables the reporting of the following metrics to measure the successful delivery of each project milestone: 8.1 (QA Metric 1)[Sender.Company]must provide a metric that measures the success of (project deliverable) by (reporting metric description) . 8.2 (QA Metric 2)[Sender.Company] must provide a metric that measures the success of (project deliverable) by (reporting metric description) . 8.3 (QA Metric 3)[Sender.Company] must provide a metric that measures the success of (project deliverable) by (reporting metric description) . 8.4 (QA Metric 4)[Sender.Company] must provide a metric that measures the success of (project deliverable) by (reporting metric description) . 8.5 (QA Metric 5) [Sender.Company] must provide a metric that measures the success of (project deliverable) by (reporting metric description) .

Delivery schedule

[Sender.Company] must adhere to [Client.Company] ’s delivery schedule for each project phase. Include both final deadlines and detail around milestones.

Image 28

9.1 (Project phase 1)[Sender.Company] must deliver (project phase) of [project name] by (MM.DD.YYYY) . 9.2 (Project phase 2)[Sender.Company] must deliver (project phase) of [project name] by (MM.DD.YYYY) . 9.3 (Project phase 3)[Sender.Company] must deliver (project phase) of [project name] by (MM.DD.YYYY) . 9.4 (Project phase 4)[Sender.Company] must deliver (project phase) of [project name] by (MM.DD.YYYY) . 9.5 (Project phase 5)[Sender.Company] must deliver (project phase) of [project name] by (MM.DD.YYYY) . 9.6 (Project phase 6)[Sender.Company] must deliver (project phase) of [project name] by (MM.DD.YYYY) .

Other requirements

[Sender.Company] must adhere to the following requirements per the needs of [Client.Company] : 10.1 The company must provide [Client.Company] with the ability to (additional requirement 1) . 10.2 The company must provide [Client.Company] with the ability to (additional requirement 2). 10.3 The company must provide [Client.Company] with the ability to (additional requirement 3) . 10.4 The company must provide [Client.Company] with the ability to (additional requirement 4) . 10.5 The company must provide [Client.Company] with the ability to (additional requirement 5) .

Image 29

Limitations

The following limitations may impact [Sender.Company] ’s ability to comply with specific project deliverables by [Client.Company] 's outlined milestone dates:

11.1 The (business system) prevents [Sender.Company] from (limitation 1). 11.2 Current company policy prohibits users from (limitation 2). 11.3 A lack of reporting resources limits the ability of upper management from (limitation 3). 11.4 A need to comply with (regulatory policy) prohibits users from (limitation 4). 11.5 Data that comes from (limitation 5). must be kept in a separate business system. The company currently lacks the data storage resources to support that business requirement.

Risks

12.1 Technology Risks

12.1.1 If (business system) does not (business process), then the users will not be able to (business function) . 12.1.2 If the data team fails to perform information backups every night, then the system will not have the ability to (system process). 12.1.3 If the change management team fails to update the system on the scheduled date, then the user will not be able to (business process). 12.1.4 If the system does not properly save user updates, then that will affect the integrity of information stored in (database/datastore).

Image 30

12.2 Skills Risks

The following risks might arise due to not having personnel in place to perform the necessary system or business functions: 12.2.1 If the developer does not possess knowledge of (technology/programming language), they will not be capable of making the necessary updates to (business process/application) . 12.2.2 If the user does not understand how to (business capability) , then they will not have the ability to take full advantage of the changes put in place by (system change) .

12.3 Environmental/political risks

The following environment or political risks might impact [Sender.Company] ’s ability to provide the changes required by [Client.Company] for [project name] : 12.3.1 If [Client.Company] is unable to obtain buy-in from (stakeholder) , then that impacts the ability to deliver on (project milestone) . 12.3.2 If (local/state/federal law title) becomes implemented, [Sender.Company] will be unable to proceed with (project milestone) . 12.3.3 If [Client.Company] fails to win approval to proceed with (business change) , then that impacts [Sender.Company] ’s ability to provide client with (project milestone) .

12.4 Business risks

The following business risks might hinder the ability of [Sender.Company] to deliver on the goals of ​[project name] for [Client.Company] : 12.4.1 If [Client.Company] fails to provide [Sender.Company] with all information pertaining to [business process] , then that may impact [Sender.Company] ’s ability to deliver on (project milestone). 12.4.2 If [Client.Company] fails to provide [Sender.Company] with all information pertaining to [user process] , then that may impact [Sender.Company] ’s ability to deliver on (project milestone). 12.4.3 If [Client.Company] fails to provide [Sender.Company] with all information pertaining to [system process] , then that may impact [Sender.Company] ’s ability to deliver on (project milestone).

Image 31

12.5 Requirements risks

12.5.1 If [Sender.Company] and fail to account for all systems impacted by the changes caused by [project name] , then that may impact the ability to deliver on some or all project milestones. 12.5.2 If [Sender.Company] and [Client.Company] fail to account for all constraints around various aspects of [project name] , then that may impact the ability to deliver on some or all project milestones. 12.5.3 If [Sender.Company] and [Client.Company] fail to account for all user needs when outlining the scope of [project name] , then that may impact the ability to achieve [Client.Company] business objectives.

12.6 Additional risks

The following additional risks must be accounted for by [Sender.Company] when considering the scope of the project: 12.6.1 The potential of (additional risk) occurring during the project development phase could impact [Sender.Company] ’s ability to deliver on (company milestone) . 12.6.2 The potential of (additional risk) occurring during the project testing phase could impact ​[Sender.Company] ’s ability to deliver on (company milestone) . 12.6.3 The potential of (additional risk) occurring during the project release phase could impact [Sender.Company] ’s ability to deliver on (company milestone) .

Appendix A – Glossary of Terms

(Glossary term) — (glossary definition) (Glossary term) — (glossary definition) (Glossary term) — (glossary definition) (Glossary term) — (glossary definition) (Glossary term)(glossary definition)

Image 32

Business Requirements Document Template (BRD)

Used 6,443 times

Use this template — free