Benefits Realization Plan Template
Benefits map, benefit profiles with measure, baseline, target, timing and owner, tracking schedule, dependencies and dis-benefits
使い方: Use with the business case, before delivery starts, to plan how benefits will be proven. Fill the benefits register and measure baselines first. Main pitfall: benefit owners inside the project team instead of in the business that realises them.
プレビュー
Benefits Realization Plan: [Project name]
Plan for how and when the benefits that justify the project will be realised, measured and reported: benefits map, benefit profiles, tracking schedule, dependencies, dis-benefits and review. Based on common project and programme management practice. Replace every
[bracketed]value and every row marked Example.
| Field | Value |
|---|---|
| Document ID | [BRP-PROJECT-001] |
| Project | [Project name] |
| Business case | [BC-001 version x.y] |
| Version | [0.1] |
| Owner | [@sponsor] |
| Prepared by | [@project-manager] |
| Last updated | YYYY-MM-DD |
1. Purpose and scope
This plan covers the benefits of [Project name] claimed in business case [BC-001] and sets out how they will be measured from the baseline date [YYYY-MM-DD] until [24] months after go-live, when responsibility for tracking passes fully to the business.
2. Benefits map
The benefits map traces each project output through the business change it enables to the benefit and strategic objective.
3. Benefits register
The register summarises all benefits; profiles follow in section 4.
| ID | Benefit | Type | Measure | Baseline | Target | Expected by | Owner |
|---|---|---|---|---|---|---|---|
| B1 | Example: Shorter onboarding time | Non-financial | Median days application to active account | 11 days | 3 days | Go-live + 3 months | Head of operations |
| B2 | Example: Lower cost per onboarding | Financial, cashable | Fully loaded cost per completed onboarding | 64 EUR | 28 EUR | Go-live + 6 months | Finance director |
| B3 | Example: Fewer abandoned applications | Non-financial | Abandoned / started applications | 18% | Below 8% | Go-live + 6 months | Head of digital |
| B4 | Example: More products per new customer | Financial, non-cashable | Products held at 90 days | 1.4 | 1.8 | Go-live + 12 months | Head of retail |
| [B-n] | [Benefit] | [Type] | [Measure] | [Baseline] | [Target] | [Date] | [Owner] |
4. Benefit profiles
Each benefit is described in a profile so that it can be measured consistently.
4.1 Profile B2: Lower cost per onboarding
| Attribute | Value |
|---|---|
| Description | Example: Reduce the cost of onboarding a retail customer by removing manual document checks and paper handling |
| Measure | Total onboarding operating cost per month divided by completed onboardings that month |
| Data source | Finance cost centre 4410 and onboarding system completion report |
| Baseline | 64 EUR (average of 12 months to YYYY-MM-DD) |
| Target | 28 EUR by go-live + 6 months |
| Interim targets | 50 EUR at +2 months, 35 EUR at +4 months |
| Value | Approximately 432,000 EUR per year at 12,000 onboardings |
| Enablers | Outputs O2 and O3; staff reallocation agreed by HR |
| Owner | Finance director |
| Measured by | Finance business partner, monthly |
The annual value is calculated as:
4.2 Profile [B-n]: [Benefit name]
| Attribute | Value |
|---|---|
| Description | [What improves and for whom] |
| Measure | [Precise definition] |
| Data source | [System or report] |
| Baseline | [Value and date] |
| Target | [Value and date] |
| Owner | [@name] |
5. Tracking schedule
Benefits are measured and reported on the schedule below.
| Benefit | Baseline measured | First measurement | Frequency | Reported to | Final review |
|---|---|---|---|---|---|
| B1 | YYYY-MM-DD | Go-live + 1 month | Monthly | Steering committee, then operations board | Go-live + 12 months |
| B2 | YYYY-MM-DD | Go-live + 2 months | Monthly | Finance committee | Go-live + 12 months |
| B3 | YYYY-MM-DD | Go-live + 1 month | Monthly | Digital board | Go-live + 12 months |
| B4 | YYYY-MM-DD | Go-live + 3 months | Quarterly | Retail board | Go-live + 24 months |
6. Dependencies and enablers
Benefits depend on the following enablers.
| Benefit | Dependency | Type | Owner | Status |
|---|---|---|---|---|
| B2 | Example: 6 FTE of back-office capacity reallocated to customer advice | Business change | HR director | Agreed in principle |
| B3 | Example: Marketing campaign directs customers to the online channel | Other initiative | Head of marketing | Planned |
| B4 | Example: Branch sales incentive scheme updated | Policy | Head of retail | Not started |
| [B-n] | [Dependency] | [Type] | [@owner] | [Status] |
7. Dis-benefits
The following dis-benefits are expected and managed.
| ID | Dis-benefit | Who is affected | Measure | Mitigation | Owner |
|---|---|---|---|---|---|
| DB1 | Example: Higher licence cost for identity verification | Finance | Annual subscription cost (48,000 EUR) | Included in B2 net value | Finance director |
| DB2 | Example: Fewer face-to-face contacts with new customers | Branch staff | Share of onboardings with branch contact | Follow-up call offer within 30 days | Head of retail |
| [DB-n] | [Dis-benefit] | [Affected] | [Measure] | [Mitigation] | [@owner] |
8. Risks to benefits
Key risks to realisation:
| Risk | Benefits affected | Response | Owner |
|---|---|---|---|
| Example: Staff savings not released because volumes grow | B2 | Measure cost per onboarding, not headcount; agree reallocation plan | Finance director |
| Example: Customers keep using paper forms out of habit | B1, B3 | Paper form retired after 3 months; assisted digital in branches | Head of digital |
| [Risk] | [IDs] | [Response] | [@owner] |
9. Reporting and review
Benefit status is reported in the steering committee report until project closure, then in the [operations board] pack. A formal benefits review takes place at go-live + 6 and + 12 months. Where a benefit is more than [20%] below its interim target, the benefit owner presents a recovery plan.
| Benefit | Target | Latest actual | Date | Status | Comment |
|---|---|---|---|---|---|
| B1 | 3 days | [n] | YYYY-MM-DD | [On track / At risk / Off track] | [Comment] |
| B2 | 28 EUR | [n] | YYYY-MM-DD | [Status] | [Comment] |
10. Handover of benefits ownership
At project closure the benefit owners confirm in writing that they accept responsibility for continued measurement and reporting. Open benefit actions are transferred with the closure report.
Standard and licence note
Based on common project and programme management practice for benefits management, benefits mapping and benefit profiles. This template is original text written for this collection. Template licence: MIT.
関連テンプレート
Procurement Management Plan Template
Make-or-buy analysis, procurement items, contract types, weighted supplier evaluation, timeline, supplier management, approvals
プロジェクト管理Project Management Plan Template
Integrated plan: objectives, governance, scope, schedule, cost and EVM, quality, risk, procurement, change control, baselines
プロジェクト管理Project Quality Management Plan Template
Quality policy, objectives, acceptance criteria, roles, QA audits, QC metrics, nonconformance and corrective action, improvement, records