feasibility report Template

Feasibility report Template (Word Version, 366KB)

Project Name

Branch Name

National Project Management System
Business Projects-information technology-Enabled
Feasibility Phase

Instructions

This document is your template to producing a feasibility report, a key requirement for the definition of any project.

Document Purpose

A feasibility report is a document that assesses potential solutions to the business problem or opportunity, and determines which of these are viable for further analysis.

The purpose of the feasibility report is to present the project parameters and define the potential solutions to the defined problem, need, or opportunity. Having brainstormed a variety of potential solutions, the project team expands on each of these potential solutions, providing sufficient detail, including very high-level costing information, to permit the project leader to recommend to the approving authority all of the viable potential solutions that should be further analyzed in the next phase (Business Case). Project constraints and limitations of expenditure are among the various factors that will determine viability.

Using this Template

To create a feasibility report from this template, simply:

  1. Replace the title on the cover page with the name of your project and the organization information
  2. Replace the <bracketed text> in the document header with your project name and information
  3. Save your document with a file name that is in accordance with current branch document naming standards
  4. Update the file name in the document footer by right-clicking and selecting “edit footer”
  5. Complete the entire template. Each section contains abbreviated instructions, shown in italics, which can be removed once your document is finalized. Tables are also provided as a suggested layout for some of the information required
  6. Update the table of contents by right-clicking and selecting Update Field, then Update entire table
  7. Delete this page when the feasibility report is complete

Revision History

Note: This table is only for example and contains no data.

Version Number Description Date Modified Author
       
       
       
       
       
       
       

Authority Signatures

Prepared by:

(PSPC) / Signature

Please print:

Name:

Position:

Date:

Prepared by:

(PSPC) / Signature

Please print:

Name:

Project Analyst:

Date:

Recommended by:

(PSPC) / Signature

Please print:

Name:

Title:

Date:

Approved by:

(PSPC) / Signature

Please print:

Name:

Title:

Date:

On this page

List of Appendices

1. Executive Summary

The purpose of the Executive Summary is to provide a very brief overview of the most essential and decision-relevant information concerning the project.

Suggested Content

2. Problem Statement

Briefly identify the main problem, opportunity, or key issue that the proposed project is seeking to address. The problem or opportunity statement should be taken from the Statement of Requirement document.

3. Project Business Requirement

This section provides pertinent details regarding the context for undertaking the proposed project. This information should be based on the Problem Definition Section of the Statement of Requirement document.

This is the section where information relevant to the initial analysis can be noted, such as the findings of an environmental scan (whether pertaining to technology or to what other organizations have done to support a similar business problem or opportunity), key parameters/constraints from relevant policy and legislation, key references to the conceptual version of the Architecture Solution document, and key points arising from the initial Concept of Operations document.

4. Assessment of Options

The purpose of this section is to list the possible options for satisfying the client requirements and to document the results of the feasibility assessment of each of the options. This may be done in a table format. Documentation will include the rationale to support viable options and to reject non-viable options. Project constraints and limitations of expenditure are among the various factors that will determine viability.

In table format, such as the sample table below, assess each option against common high-level criteria. There should be one table for each option.

Note: The evaluation criteria provided below are for illustration purposes. Add or remove criteria to suit the specific option.

Note: This table is only for example and contains no data.

Option 1
Name 		Notes / Comments
Description of Option  
Option Evaluation Criteria
Alignment with Desired Business Objectives  
Technical Fit to Target Enterprise Architecture  
Costs  
Cost Benefit  
Legal / Regulatory Fit  
Impact  
Potential Risks that impact the ability to Deliver Desired Business Outcomes   
Fit to Project Constraint 1  
Fit to Project Constraint 2  
etc  
Rationale for Rejection or for Recommending further Analysis  
Overall Viability State Whether “Viable” or “Non-Viable”
Note: Viable Options are un-ranked at this stage

5. Risk Assessment of Viable Options

List the top three to five risks for each of the viable options. Use a high-level, standard risk assessment process.

Note: A more substantive risk assessment will be conducted for the business case. For the feasibility report, identify the results of the preliminary risk assessment of each option in terms of scope, time, cost or other considerations surrounding the problem/opportunity. These other considerations could relate to physical plant and installations, environment, infrastructure, and technical, political, legal, organizational or social factors, which may be derived from assumptions and constraints discussed in the preliminary project plan, and pertain to the project being able to attain its objectives.

6. Recommended Options for Further Analysis

Summarize the key findings of the option assessment. Identify which options will carry forward into the analysis phase and the business case.

Appendix 1—References

Note: This table is only for example and contains no data.

No. Reference Document Name Location
for example File No.: E-DRM No. Web Address etc 		File Volume No.
1      
2      
3      
Etc      

Appendix 2—Glossary

Note: This table is only for example and contains no data.

Term Definition
   
Acronym Name in Full
   
Date modified: