Business Impact Analysis

This template is designed to assist in planning for project rollout. It helps identify operational impacts in a number of different areas,
both for the rollout period and ongoing after the project has launched. It should be developed during project planning and revisited
during project execution as needed. There are two distinct impact areas identified--the deployment impact representing the impacts
that may occur during the rollout of the project, and the post-implementation impact for the ongoing needs. For example, during
deployment there may be a systems outage while software is deployed, but that is only an impact for deployment. By contrast, on an
ongoing basis there may be a need for additional software license renewals to support the application now in use, but that won’t
directly impact the deployment window.

Guidelines

 Project Name: The name of the project the analysis is for.

 Project Manager: The manager responsible for the project, who should be the person that completes this analysis.
 Deployment Period: The period of time planned to be reserved for the rollout of the project. This will start with the go-live
date and end when support if handed off to operational areas.
 Category: This is the area where the project may experience impact during or after rollout. A list of areas is included as a
suggestion, but feel free to modify to suit your own organization. For simplicity, I have included the same categories in the two
category tables above, but feel free to modify as needed.
 Item: The specific item within each category that may be impacted. This will differ between the two tables (see the technology
example mentioned in the introductory paragraph).
 Impact: The description of the impact that is expected to occur. This should be detailed enough for anyone with a basic
understanding of the project to be able to gain an overview of the impact.
 Contact: The person managing this impact item. Ideally this should be a link to a contact card/email address to allow anyone
to obtain more details. While the PM is accountable for the overall analysis, the contact is responsible for their specific items.
 Notes: This field should identify any specific risks/issues/concern areas related to this category, along with links to
management plans for controlling the impact.
 Project Name Project Manager
Deployment Period From To

Deployment Impact

Category Item Impact Contact Notes

Technology
Outages
Support
People
Communications
Change Management
Transition Support
Workforce
Management
Operations
Workarounds
Customer
Service
Communications
Support
Post-Implementation Impact

Category Item Impact Contact Notes

Technology
Hardware
Software
Support
People
Staffing Levels
Workforce Transition
Operations
Process Change
Performance
Standards
Customer
Service
Communications
Support