The BBAI template library gives business analysts everything they need to deliver professional, consistent work — from requirements gathering through to solution validation. All templates are free. Use them as-is or adapt them to your project context.
Jump to section: Requirements · Analysis & Assessment · Stakeholder Management · Process & Workflow · Business Case & Planning · Testing & Quality · BA Project Management · Agile & Product
Requirements Templates
The most-used templates in a BA’s toolkit. Requirements templates help you capture, document, and manage what the business needs from a solution.
Business Requirements Document (BRD)
The BRD captures what the business needs to achieve, independent of how the solution will be built. Use at the start of a project to align stakeholders before solution design begins.
| Section | Content to Include |
|---|---|
| 1. Executive Summary | Problem statement, business opportunity, and recommended approach (1 page) |
| 2. Business Objectives | SMART goals the solution must achieve, linked to strategic objectives |
| 3. Current State | As-is process description, pain points, and root causes |
| 4. Scope | In-scope processes, systems, and stakeholder groups. Explicit out-of-scope list. |
| 5. Stakeholders | Key stakeholders, roles, and approval authorities |
| 6. Business Requirements | Numbered list: BR-001, BR-002… Each with priority (MoSCoW) and owner |
| 7. Assumptions & Constraints | Known limitations, dependencies, regulatory requirements |
| 8. Success Criteria | How the business will measure whether the solution delivered value |
| 9. Glossary | Business terms and definitions used in this document |
Functional Requirements Specification (FRS)
Translates business requirements into specific, testable functional behaviours. Used by development teams to understand what the system must do. Write this after the BRD is approved.
| Field | Description | Example |
|---|---|---|
| FR-ID | Unique reference number | FR-001 |
| Title | Short name for the requirement | User Login |
| Description | What the system must do | The system shall allow registered users to log in using email and password |
| Source | Business requirement it traces to | BR-003 |
| Priority | MoSCoW classification | Must Have |
| Acceptance Criteria | How to confirm it works | Given [context], When [action], Then [expected outcome] |
| Owner | Stakeholder responsible | Product Owner |
| Status | Draft / Approved / Implemented / Tested | Draft |
Requirements Traceability Matrix (RTM)
Maps each business requirement through to functional requirements, test cases, and implementation. Ensures nothing is missed and every requirement can be tested. Essential for projects with regulatory compliance requirements.
| BR-ID | Business Requirement | FR-ID | Functional Requirement | Test Case ID | Test Status | Sign-off |
|---|---|---|---|---|---|---|
| BR-001 | Users must authenticate securely | FR-001, FR-002 | Login, Password Reset | TC-001, TC-002 | Pass | ✓ |
| BR-002 | [Requirement text] | [FR-IDs] | [FR titles] | [TC-IDs] | Pending |
User Story Template
Captures requirements from the user’s perspective in agile projects. Each story should be independently deliverable and testable. Use the INVEST criteria (Independent, Negotiable, Valuable, Estimable, Small, Testable) to validate stories before sprint planning.
| Field | Format / Example |
|---|---|
| Story ID | US-001 |
| As a… | [Type of user / role] |
| I want to… | [Goal or action] |
| So that… | [Business value or outcome] |
| Acceptance Criteria | Given [context], When [action], Then [result]. Add one row per criterion. |
| Story Points | [Effort estimate] |
| Priority | Must Have / Should Have / Could Have |
| Dependencies | [Other story IDs] |
| Notes | Edge cases, exclusions, open questions |
Use Case Template
Describes a system interaction from the actor’s perspective. Use cases are more detailed than user stories and are better suited to complex workflows or compliance-heavy projects.
| Field | Content |
|---|---|
| Use Case ID | UC-001 |
| Title | Descriptive name (verb + noun: “Submit Expense Claim”) |
| Primary Actor | Who initiates the use case |
| Secondary Actors | Other systems or roles involved |
| Preconditions | What must be true before this can start |
| Main Success Scenario | Step-by-step numbered list of the happy path |
| Alternative Flows | Valid variations of the main flow (Alt-1, Alt-2…) |
| Exception Flows | Error conditions and how the system handles them |
| Postconditions | System state after successful completion |
| Business Rules | Rules that govern this use case (link to BR-IDs) |
Business Rules Template
Documents the operational policies, regulations, and constraints that govern how the business works. Business rules are separate from functional requirements — they define the boundaries of acceptable system behaviour.
| Rule ID | Rule Statement | Category | Source | Impact | Owner |
|---|---|---|---|---|---|
| BR-001 | All purchase orders above $10,000 must have two approvals | Approval | Finance Policy v3.1 | High | CFO |
| BR-002 | [Write rule as: Entity must/shall/must not verb condition] | Validation / Approval / Calculation / Restriction | [Policy, regulation, or SME] | High / Medium / Low | [Name] |
Data Dictionary Template
Defines every data element used in a system or process — its name, format, valid values, and business meaning. Essential for integration projects, data migration, and anywhere multiple systems exchange data.
| Field Name | Business Definition | Data Type | Format | Valid Values | Mandatory? | Source System |
|---|---|---|---|---|---|---|
| CustomerID | Unique identifier for a customer account | String | CUST-NNNNNN | CUST-000001 to CUST-999999 | Yes | CRM |
| [Field name] | [Plain English meaning] | String / Integer / Date / Boolean / Decimal | [Pattern or example] | [List or range] | Yes / No | [System name] |
Analysis & Assessment Templates
Gap Analysis Template
Compares the current state to the desired future state to identify what needs to change. Use early in a project to scope the work and justify investment.
| Dimension | Current State (As-Is) | Desired State (To-Be) | Gap | Priority | Recommended Action |
|---|---|---|---|---|---|
| Process | Manual data entry, 3-day cycle | Automated, same-day processing | No automation; manual errors | High | Implement workflow automation |
| Technology | [Current tools] | [Target tools] | [Difference] | High / Med / Low | [Action] |
| People / Skills | [Current capability] | [Required capability] | [Skills gap] | [Training / hiring] | |
| Data | [Current data state] | [Required data state] | [Data gap] | [Migration / cleanse] |
Root Cause Analysis — 5 Whys Template
Traces a problem back to its root cause by asking “why” repeatedly. Works best for process failures where human or system factors compound. Use before defining requirements so you solve the actual problem, not just the symptom.
| Level | Question | Answer |
|---|---|---|
| Problem Statement | What is the observable problem? | [Describe the symptom clearly] |
| Why 1 | Why does this problem occur? | [First cause] |
| Why 2 | Why does [Why 1 answer] happen? | [Second cause] |
| Why 3 | Why does [Why 2 answer] happen? | [Third cause] |
| Why 4 | Why does [Why 3 answer] happen? | [Fourth cause] |
| Why 5 | Why does [Why 4 answer] happen? | [Root cause] |
| Corrective Action | What addresses the root cause? | [Recommended action] |
SWOT Analysis Template
Evaluates a business, product, or initiative across four dimensions. Use in enterprise analysis, feasibility studies, and strategic planning workshops. Facilitating a SWOT session is a core BA skill — include it in your stakeholder workshop plan.
| Strengths (Internal, Positive) | Weaknesses (Internal, Negative) |
|---|---|
| What advantages does the organisation/product have? What does it do well? What unique resources does it have? | What could be improved? What is done poorly? What should be avoided? |
| Opportunities (External, Positive) | Threats (External, Negative) |
| What opportunities exist in the market? What trends could be exploited? What changes in technology/regulation help? | What obstacles exist? What are competitors doing? What regulations or market shifts threaten success? |
Cost-Benefit Analysis Template
Quantifies the financial case for a change initiative. Required for most business cases. Identify both tangible (measurable) and intangible (qualitative) costs and benefits.
| Item | Type | Year 1 | Year 2 | Year 3 | Total | Notes |
|---|---|---|---|---|---|---|
| COSTS | ||||||
| Software licences | One-off | $50,000 | — | — | $50,000 | CRM platform |
| Implementation / development | One-off | $80,000 | — | — | $80,000 | |
| Training | One-off | $15,000 | — | — | $15,000 | |
| Ongoing maintenance | Recurring | $10,000 | $10,000 | $10,000 | $30,000 | Per year |
| Total Costs | $155,000 | $10,000 | $10,000 | $175,000 | ||
| BENEFITS | ||||||
| Labour savings (automation) | Recurring | $40,000 | $40,000 | $40,000 | $120,000 | 2 FTE |
| Revenue uplift | Recurring | $60,000 | $75,000 | $90,000 | $225,000 | 5% conversion lift |
| Total Benefits | $100,000 | $115,000 | $130,000 | $345,000 | ||
| Net Benefit | -$55,000 | $105,000 | $120,000 | $170,000 | ROI: 97% | |
Risk Register Template
| ID | Risk Description | Category | Likelihood (1–5) | Impact (1–5) | Score | Response Strategy | Owner | Status |
|---|---|---|---|---|---|---|---|---|
| R-001 | [What could go wrong] | Technical / People / Process / External | 3 | 4 | 12 | Mitigate / Accept / Transfer / Avoid | [Name] | Open |
Stakeholder Management Templates
Stakeholder Register Template
A living document that records every stakeholder involved in or affected by a change initiative. Build this at project kick-off and update it throughout delivery.
| Name | Role / Title | Organisation | Interest in Project | Influence (H/M/L) | Impact on Them (H/M/L) | Engagement Level | Communication Preference | BA Notes |
|---|---|---|---|---|---|---|---|---|
| [Name] | [Role] | [Dept/Org] | [What they care about] | H | M | Champion / Supporter / Neutral / Critic / Blocker | Email weekly / Meeting bi-weekly | [Key concerns, motivators] |
Power / Interest Stakeholder Matrix
Maps stakeholders by their power to influence the project and their interest in its outcome. Determines your engagement strategy for each group.
| Low Interest | High Interest | |
|---|---|---|
| High Power | Keep Satisfied Manage their concerns. Keep informed at a high level. Avoid surprises. Example: Executive sponsor who isn’t involved day-to-day. | Manage Closely Engage actively. Involve in decisions. Regular detailed communication. Example: Project sponsor, key business owner. |
| Low Power | Monitor Minimal effort. Keep on distribution list. Example: End users not yet in scope. | Keep Informed Provide regular updates. Involve in workshops. Example: End users, subject matter experts. |
RACI Matrix Template
Defines who is Responsible, Accountable, Consulted, and Informed for each activity or deliverable. Use to eliminate confusion about ownership and prevent decisions stalling. Every activity should have exactly one Accountable person.
| Activity / Deliverable | BA | Project Manager | Product Owner | Developer | Business SME | Executive Sponsor |
|---|---|---|---|---|---|---|
| Requirements Elicitation | R | C | A | I | C | I |
| BRD Sign-off | R | C | C | I | C | A |
| UAT Planning | A | C | R | C | R | I |
| [Activity] |
Key: R = Responsible (does the work) · A = Accountable (owns the outcome, approves) · C = Consulted (input needed) · I = Informed (kept updated)
Requirements Elicitation Interview Template
Structure your stakeholder interviews to consistently capture requirements, pain points, and priorities. Adapt these questions to your project context.
| Category | Questions |
|---|---|
| Context Setting | Can you walk me through your current process? What does a typical day/week look like for you in this area? |
| Pain Points | What are the biggest frustrations with how things work today? Where does the process break down most often? What takes longer than it should? |
| Requirements | What would the ideal solution look like for you? What does the new system/process absolutely must do? What would be a nice-to-have but not essential? |
| Constraints | Are there any systems this must integrate with? Are there regulatory or policy requirements we must comply with? What timeline or budget constraints should we be aware of? |
| Success | How will you know this project has been successful? What does “done” look like from your perspective? |
| Wrap-up | Is there anyone else I should speak to? Is there any documentation I should review? Is there anything I haven’t asked that’s important? |
Process & Workflow Templates
SIPOC Template
SIPOC maps a process at a high level before diving into detailed modelling. Use it at the start of any process improvement or requirements project to scope the work and align stakeholders on what the process actually is.
| Suppliers | Inputs | Process (High Level) | Outputs | Customers |
|---|---|---|---|---|
| Who provides the inputs? | What materials, data, or information enter the process? | 5–7 high-level steps only (verb + noun: “Receive order”, “Validate data”) | What does the process produce? | Who receives the outputs? |
| [Supplier 1] [Supplier 2] | [Input 1] [Input 2] | 1. [Step] 2. [Step] 3. [Step] 4. [Step] 5. [Step] | [Output 1] [Output 2] | [Customer 1] [Customer 2] |
As-Is / To-Be Process Comparison Template
| Step | As-Is (Current) | Pain Point | To-Be (Future) | Change Required | Benefit |
|---|---|---|---|---|---|
| 1 | [Current step description] | [What’s wrong with it] | [Improved step description] | Process / Technology / People / Policy | [Quantified benefit if possible] |
Business Case & Planning Templates
Business Case Template
| Section | Content |
|---|---|
| 1. Executive Summary | Problem, proposed solution, key benefits, cost, recommendation. Max 1 page. |
| 2. Problem / Opportunity | Evidence of the problem. Current cost of inaction. Strategic alignment. |
| 3. Options Analysis | At least 3 options including “do nothing”. Pros/cons and costs for each. |
| 4. Recommended Option | Which option and why. Risk-adjusted rationale. |
| 5. Financial Summary | Costs, benefits, NPV, ROI, payback period. Use the cost-benefit template above. |
| 6. Implementation Plan | High-level timeline, milestones, resource requirements. |
| 7. Risks | Top 5 risks with likelihood, impact, and mitigation. Reference risk register. |
| 8. Recommendation | Decision requested from the approving authority. |
Project Scope Statement Template
| Field | Content |
|---|---|
| Project Name | |
| Project Sponsor | |
| Business Objective | One sentence: what the project must achieve for the business |
| In Scope | Bulleted list of what IS included |
| Out of Scope | Explicit list of what is NOT included (prevents scope creep) |
| Deliverables | Tangible outputs the project will produce |
| Milestones | Key dates and decision points |
| Constraints | Fixed budget, deadline, technology, regulatory |
| Assumptions | What you’re assuming to be true (if wrong, replan) |
| Dependencies | What this project depends on / what depends on it |
| Approved by | [Sponsor name and date] |
Testing & Quality Templates
UAT Test Plan Template
The BA typically owns UAT planning. This template ensures every business requirement has at least one test case and that the right stakeholders are doing the testing.
| TC-ID | Requirement (BR/FR ID) | Test Scenario | Test Steps | Test Data | Expected Result | Actual Result | Pass/Fail | Tester | Date |
|---|---|---|---|---|---|---|---|---|---|
| TC-001 | FR-001 | User logs in with valid credentials | 1. Navigate to login page 2. Enter valid email 3. Enter valid password 4. Click Login | Email: test@example.com Password: Test@123 | User lands on dashboard | [Name] |
Defect Log Template
| Defect ID | TC-ID | Description | Steps to Reproduce | Severity | Priority | Assigned To | Status | Resolution |
|---|---|---|---|---|---|---|---|---|
| DEF-001 | TC-003 | [What went wrong] | [How to reproduce it] | Critical / High / Medium / Low | 1–4 | [Developer] | Open / In Progress / Resolved / Closed | [How it was fixed] |
BA Project Management Templates
BA Meeting Minutes Template
| Field | Content |
|---|---|
| Meeting Title | [Project name] – [Meeting type: Requirements Workshop / Review / Sign-off] |
| Date & Time | |
| Location / Platform | |
| Attendees | [Name, Role] for each attendee |
| Apologies | |
| Agenda Items Covered | 1. [Item] — [Summary of discussion] — [Decision reached] 2. [Item] — [Summary] — [Decision] |
| Decisions Made | List each decision clearly with decision owner |
| Action Items | [Action] | [Owner] | [Due date] | [Status] |
| Open Issues / Parking Lot | Items raised but not resolved — carry to next meeting |
| Next Meeting | [Date, time, location] |
BA Status Report Template
| Field | Content |
|---|---|
| Project / Initiative | |
| Reporting Period | |
| Overall Status | 🟢 On Track / 🟡 At Risk / 🔴 Off Track |
| BA Activities This Period | Bulleted list of what was completed |
| Planned Activities Next Period | Bulleted list of what’s coming |
| Requirements Status | Total / Approved / In Progress / Not Started |
| Issues / Blockers | [Issue description] | [Impact] | [Action needed] | [Owner] |
| Risks | [Risk] | [Likelihood] | [Impact] | [Mitigation status] |
| Decisions Needed | List of pending decisions with deadlines |
Agile, Product & Design Templates
These templates are useful for BAs working in agile teams, product discovery, or design-led projects.
| Template | Link |
|---|---|
| Agile Retrospective | Miro Template |
| Business Model Canvas | Miro Template |
| Continuous Product Discovery | Miro Template |
| Customer Discovery | Miro Template |
| Customer Journey Map | Miro Template |
| Design Sprint (5-Day) | Miro Template |
| Design Thinking Process | Miro Template |
| Empathy Map | Miro Template |
| Feature Prioritization Matrix | Miro Template |
| Impact Mapping | Miro Template |
| Impact-Effort Matrix | Miro Template |
| Jobs To Be Done (JTBD) | Miro Template |
| Kano Model | Miro Template |
| Lean Canvas | Miro Template |
| Mind Map | Miro Template |
| Minimum Viable Product (MVP) | Miro Template |
| Persona Template | Miro Template |
| Problem Statement Template | Miro Template |
| Product Backlog Template | Miro Template |
| Product Requirements Document (PRD) | Miro Template |
| Product Roadmap | Miro Template |
| Project Charter | Miro Template |
| Scrum Framework | Miro Template |
| Sprint Retrospective | Miro Template |
| SWOT Analysis (Visual) | Miro Template |
| User Persona | Miro Template |
| User Story Map | Miro Template |
| Value Proposition Canvas | Miro Template |
| KPI Dashboard | Miro Template |
| 4P+ Business Model | BBAI Framework |
Get Certified in Business Analysis
Templates are only as useful as the analyst using them. The Certified Better Business Analyst (CBBA) course teaches you how to apply every template above in real delivery contexts — not just fill in the boxes, but understand what questions to ask, when to use which tool, and how to turn completed templates into decisions and action.
✓ 80+ lessons covering the full BBAI Framework
✓ Practical assignments using real project scenarios
✓ Verifiable digital certificate
✓ Self-paced — complete in 4–8 weeks
Start free → Try the Introduction to Business Analysis course — no payment required.
Get certified → Full CBBA certification. NZD $499.