Skip to content
The first pages of the Business Requirements Document template

Business Requirements Document

Document template for Google Docs and Word

Make a copy in Google Docs
Price
Free
Style
Modern
Difficulty
Beginner
Updated
October 31, 2026

Every page (8)

Overview

Requirements go wrong when they describe a design instead of a need, or when every line is marked as essential. This template gives business analysts a clear order: purpose and owner, stakeholders with a RACI matrix, the current process, numbered requirements with priority and tests, then scope, assumptions and sign-off.

The sample follows Sandpiper Works as it replaces phone and spreadsheet bookings with a service booking portal: 64 requirements, 37 of them must-haves, a £480,000 budget and a 99.9% availability target. Replace the sample with your own project, keep each requirement to one testable sentence, and add a measurable acceptance test to every line.

Useful for

  • A business analyst agreeing requirements with an operations owner before a supplier is chosen
  • A procurement team scoring supplier bids against MoSCoW priorities and numbered requirements
  • A delivery lead baselining scope so later change requests can be judged against a signed document

What's included

  • Title block with owner, version and status, key figures and the three outcomes the project must deliver
  • Stakeholder directory with contact details and a RACI matrix for five key activities
  • Current process flow with the pain point highlighted, plus an escalation flow
  • Requirements table grouped by area with MoSCoW priority, owner, status and acceptance test
  • In-scope and out-of-scope comparison, assumptions and an exclusions callout
  • Sign-off page, terms of acceptance and a guide page for replacing the sample

How to use it

  1. 1

    Click Make a copy in Google Docs, then confirm on the Google page. The copy is saved to your own Google Drive.

  2. 2

    Write the purpose in two sentences on page 1 and name the business owner, version and status in the title block.

  3. 3

    Replace the sample requirements with your own, one must or should sentence each, and give every line an owner and a measurable test.

  4. 4

    Assign MoSCoW priorities, keep must items to 60% of the list or fewer, and update the stakeholder and RACI pages.

  5. 5

    Delete the guide page at the end, then share the document with your business owner and delivery lead for sign-off.

What you need

Requirements

  • A Google account with access to Google Drive

Works with

  • Google Docs
  • Microsoft Word (download the .docx)

Questions

How many requirements should a BRD contain?

Most projects land between 30 and 120 numbered requirements. The sample shows 64. Quantity matters less than each line being a single sentence a tester can pass or fail.

Can I use this for a product requirements document?

Yes. Rename the groups to your product areas, keep the priority, owner, status and test columns, and use the stakeholder pages for product, design and engineering leads.

Are the organisation and figures real?

No. Sandpiper Works, its people, email addresses and every figure are fictional sample data. Replace them with your own details before sharing the document.

  • #business-requirements
  • #requirements-document
  • #moscow
  • #raci
  • #brd
  • #project-management
  • #sign-off

More requirements document templates

See all 3

Also in Project management

All project management templates
Get this template

Preparing your template…