Business Analysis: [Initiative name]

Field	Value
Business sponsor	[Name]
Business analyst	[Name]
Version and status	[Version] / Draft
Review date	[YYYY-MM-DD]
Related documents	[PRD, process maps, research, project links]

Executive summary

[Describe the business problem, the proposed change, and the expected outcome in one paragraph.]

Business objectives

Objective	Current baseline	Desired outcome	Evidence and measurement
[Reduce manual processing]	[Measured effort per request]	[Target reduction by date]	[Source and tracking method]

Stakeholders

Stakeholder or role	Need or concern	Decision responsibility	Engagement
[Sponsor]	[Business value]	[Budget and scope approval]	[Review cadence]
[Operations team]	[Workflow impact]	[Process acceptance]	[Workshops]
[End users]	[Usability and access]	[User validation]	[Interviews and pilot]

Current state (AS-IS)

1. [Trigger and responsible actor]
2. [Manual work, system interaction, or handoff]
3. [Result and how completion is recorded]

Pain points: [Delays, rework, errors, and supporting evidence.]

Systems and data: [Existing applications, data sources, and integrations.]

Future state (TO-BE)

1. [Proposed trigger and responsible actor]
2. [New or changed workflow and automated steps]
3. [Exception path, escalation, and completion criteria]

Gap	Required change	Affected team	Dependency
[Difference between current and future state]	[Process or system change]	[Owner]	[Dependency]

Scope and boundaries

• Included: [Processes, teams, systems, and locations.]
• Excluded: [Items this initiative will not address.]
• Assumptions: [Statements to validate, with owner and deadline.]
• Constraints: [Budget, timeline, contractual, or operational limits.]

Business rules

ID	Rule	Source or owner	Exceptions
BR-01	Requests above [threshold] require approval from [role].	[Policy owner]	[Escalation path]
BR-02	[Rule expressed in business language]	[Source]	[Allowed exceptions]

Requirements and traceability

ID	Requirement	Business objective	Priority	Validation or test	Owner
REQ-01	[Required business capability]	[Objective reference]	Must	[Observable acceptance condition]	[Name]
REQ-02	[Reporting or data requirement]	[Objective reference]	Should	[Observable acceptance condition]	[Name]

Options and recommendation

Option	Benefits	Costs and effort	Risks
Keep current process	[Benefits]	[Ongoing costs]	[Risks]
Improve existing system	[Benefits]	[Estimate and basis]	[Risks]
Introduce a new solution	[Benefits]	[Estimate and basis]	[Risks]

Recommendation: [Preferred option, rationale, assumptions, and confidence in estimates.]

Change readiness and approval

• Process owners accept the future workflow.
• Training, migration, and support needs are assigned.
• Requirements have measurable acceptance conditions.
• Benefits review has an owner and a date.

Approver	Role	Decision	Date	Conditions
[Name]	[Role]	[Pending]	[Date]	[Conditions]