Table of Contents
- What Is a Feasibility Report?
- Why the Feasibility Report Matters
- Feasibility Report Format: Standard Structure
- How to Write a Feasibility Report in 6 Steps
- Feasibility Report Example
- Checklist Before You Submit the Report
Show more ▾Show less ▴
A feasibility report, also called a feasibility study report (FSR), is the document that turns months of analysis into one decision: go ahead with the project, drop it, or go ahead with conditions. The feasibility study is the analysis; the report is what the sponsor and senior management actually read before they commit budget.
This guide explains what a feasibility report is, what it looks like, the standard format most organizations expect, and how to write one in six steps. It ends with a condensed example report and a pre-submission checklist.
Key Takeaways
- A feasibility report is the formal output of a feasibility study: it summarizes the analysis and recommends whether the project should proceed.
- The standard format has three parts: front matter (title page, contents), the report body (summary, background, method, alternatives, findings, costs and benefits, recommendation), and back matter (references, appendices).
- Evaluate every option against the same weighted criteria, and say clearly which option wins and why.
- When scores are close, test how the result changes if the weights change, and report it. A recommendation that flips with a small change in weights needs conditions attached.
- A “not feasible” conclusion is a valid, useful result: it saves the sponsor money and time.
What Is a Feasibility Report?
Definition
Feasibility Study Report (FSR)
In project management, a Feasibility Study Report (FSR) is a formally documented output of the feasibility study that summarizes the results of the analysis and evaluations conducted to review the proposed solution and investigate project alternatives, for the purpose of identifying whether the project in question is feasible, cost-effective and profitable or not. It describes and supports the most feasible solution applicable to the project.
In simpler terms: the study is the work, the report is the evidence. The report gives a brief description of the project and its background, shows how the options were evaluated, and ends with a clear recommendation. Formally, it is the starting point for the pre-charter sub-phase of project initiation. In practice, an approved report means the sponsor can decide on the investment and assign a project manager.
The project manager usually coordinates the reporting process, with input from finance, the technical team, and the business units affected by the project. The readers are decision makers: the project sponsor, a steering committee, investors, or a funding body.
The name on the cover is not always “FSR.” In software and product development, the feasibility study usually happens inside a discovery phase, and the final document is more often called a discovery report, a product discovery summary, or a solution assessment. The content is the same: options, feasibility findings, a budget range, risks, and a recommendation.
Why the Feasibility Report Matters
A feasibility study that is never written up properly rarely influences a decision. The report gives senior management documented technical, financial, and legal evidence in one place, so budgeting and investment decisions are made on facts rather than on whoever argues loudest. A well-written report also supports:
- Project analysis: it links the expected results of the project to its budgeted costs.
- Risk planning: the risks identified in the report become the starting point for contingency planning and risk treatment.
- Resource planning: management can see early what skills, staff, and training the project will need.
- The business case: the report’s findings underpin the business case, which states why the organization should invest and formally secures funding.
Feasibility Report Format: Standard Structure
Formatting rules vary between organizations, universities, and funding bodies, so always check whether your sponsor or supervisor has a required format first. If not, this is the structure most feasibility reports follow:
| Part | Section | What it contains |
|---|---|---|
| Front matter | Title page | Descriptive title, author’s name and role, organization, date, version |
| Contents | Headings and sub-headings in report order, plus a list of tables, figures, and appendices | |
| Report body | Executive summary | The problem or opportunity, the options considered, the recommendation, and the key numbers, on one page |
| Background | Project description, why the study was done, and any relevant history | |
| Method and criteria | How the study was carried out and which criteria were used to evaluate options | |
| Alternatives evaluated | Each option considered, compared against the same criteria | |
| Findings | Results for each feasibility area: economic, technical, operational, schedule, legal | |
| Cost-benefit evaluation | Costs, benefits, NPV, ROI, and payback period for the main options | |
| Conclusions and recommendations | The verdict, the preferred option, conditions, and next steps | |
| Back matter | References and appendices | Sources cited, detailed calculations, survey data, technical specifications |
Formatting tips that apply to almost any feasibility report:
- Keep the front matter short, no more than 4-5 pages, and leave the title page unnumbered.
- Add a running header with a short report title and page numbers.
- Use one consistent heading style and a readable 10-12 point font throughout.
- Put numbers in tables, not paragraphs: decision makers compare options faster when they can scan a row.
- Use one citation style (APA, Harvard, or your organization’s standard) for all sources.
If you have not written up the analysis yet, start from our free feasibility study template (Word and PDF). Its eight sections map directly onto the report body above.
How to Write a Feasibility Report in 6 Steps
Regardless of the size and type of project, the writing process follows the same six steps. The examples below come from one project: a retailer that wants to start selling its products online.
Step 1. Describe the project and the decision needed
Collect background information and write a short project description. State the business goal and what decision the report should support. Keep it to one or two paragraphs.
Example: “This project aims to start direct online sales of the company’s products and grow online revenue to 15% of total sales within two years. The report evaluates the available sales channels and recommends one for launch.”
Step 2. Describe the possible solutions
Run an alternatives analysis and describe each realistic option in a few sentences. Include options you expect to reject: showing why they lose is part of the evidence.
Example: “Three solutions were analyzed: (1) a dedicated online shop on the company’s own domain; (2) a corporate website with a product catalog and order requests by phone or email; (3) a branded storefront on an existing online marketplace.”
Step 3. Define the evaluation criteria
Set the criteria every option will be judged against, and give each a weight that reflects its importance to the organization. Agree the weights with the sponsor before scoring, not after; otherwise the weights tend to drift toward the option someone already prefers.
Example: “Options were scored from 1 (poor) to 5 (excellent) against five weighted criteria: revenue potential (30%), total three-year cost (25%), time to launch (15%), in-house capability to run the channel (15%), and control over brand and customer data (15%).”
Step 4. Evaluate and compare the options
Score each option, show the scores in a comparison matrix, and summarize the findings for each feasibility area: economic, technical, operational, schedule, and legal. Back the scores with evidence (quotes from vendors, cost estimates, staff interviews), and put detailed calculations in an appendix.
Step 5. Propose the most feasible solution
Identify the option that makes the best use of resources and delivers the most benefit, and explain why it beats the others. If the scores are close, check how sensitive the result is to the weights and say so in the report.
Step 6. Write the conclusion, recommendations, and executive summary
Summarize the project’s aim, state the verdict (go, no-go, or go with conditions), and list the next steps with owners. Write the executive summary last, once every other section is final, and place it at the front of the report.
Feasibility Report Example
What does a feasibility report look like in practice? Below are the three sections decision makers read first, condensed from a report for the online sales project used in the steps above.
Executive summary (extract): “The company wants online sales to reach 15% of total revenue within two years. Three sales channels were evaluated against five weighted criteria. A marketplace storefront scored highest (3.70 out of 5) thanks to low cost and a launch time of six weeks, but it gives the company little control over customer data. We recommend launching on a marketplace now and re-assessing a dedicated online shop after 12 months, once online demand is proven.”
Comparison of alternatives:
| Criterion (weight) | Online shop | Corporate website | Marketplace storefront |
|---|---|---|---|
| Revenue potential (30%) | 5 | 2 | 4 |
| Total 3-year cost (25%) | 2 | 4 | 4 |
| Time to launch (15%) | 2 | 4 | 5 |
| In-house capability (15%) | 3 | 5 | 4 |
| Control over brand and customer data (15%) | 5 | 4 | 1 |
| Weighted score | 3.50 | 3.55 | 3.70 |
Sensitivity check: “The scores are close. If control over brand and customer data is weighted at 25% instead of 15% (with revenue potential reduced to 25% and cost to 20%), the online shop and the corporate website both score 3.65 and the marketplace drops to 3.40. The recommendation therefore depends on how much the company values owning its customer relationships in the first year.”
Recommendation: “Go with conditions. Launch a branded marketplace storefront within six weeks (owner: E-commerce Lead). Track online revenue, margin after marketplace fees, and repeat-customer rate monthly. Re-run the evaluation for a dedicated online shop in month 12 (owner: Commercial Director).”
This is a composite illustration, not a real company. A full report would also include the background, method, findings for each feasibility area, and the cost-benefit evaluation described in the format section above.
From the field
The Fitness App That Started With a Report, Not Code
A few years ago I worked on a project for a chain of fitness clubs. They wanted a mobile app where members could book classes, buy memberships, see their visit history, and get personal recommendations. The brief fit in one sentence: “build us an app.” Before anyone signed a development contract, though, we had harder questions to answer. Do members really need a separate app? Can it work with the CRM the clubs already use? What will it cost, and will it pay for itself?
So instead of sending a quick estimate, we ran a short discovery phase. We talked to club owners, front-desk managers, trainers, and a handful of regular members, and we went through every system already in place: the CRM, the loyalty program, the payment provider, and the class scheduling tool. What we delivered at the end was, in textbook terms, a feasibility study report: business goals, solution options, technical and operational feasibility, a budget range, risks, and a recommendation. Nobody on the team called it an FSR, though. For us it was just the discovery report.
We put three options in front of the client:
| Option | What it offered | Main conclusion |
|---|---|---|
| Custom app | A fully bespoke product with deep integrations | Most control, but the most expensive and the slowest to launch |
| White-label platform | A ready-made solution under the client’s brand | Fast launch, but limited customization |
| Hybrid MVP | A ready-made core plus custom booking and loyalty modules | The best balance of speed, cost, and differentiation |
We compared the three on cost, time to launch, integrations, scalability, data security, and likely effect on member retention. The surprise was where the real risk sat. It wasn’t the development. It was keeping class schedules and memberships in sync between the app, the CRM, and the point-of-sale system. If we had skipped discovery, we would have found that out halfway through the build.
Our recommendation was go with conditions: launch the hybrid MVP in three clubs first, with booking, membership purchase, a user profile, and a basic loyalty program. Personal recommendations, challenges, and advanced analytics would wait until we knew members actually used the app. The client agreed, the MVP went live in the pilot clubs four months later, and we judged it by three numbers: the share of bookings made in the app, repeat membership purchases, and how many requests still ended up at the front desk.
Daniel Linman
IT Software Consultant, Canada
Checklist Before You Submit the Report
- The executive summary fits on one page and states the recommendation in the first paragraph.
- At least two real alternatives are evaluated, using the same criteria, time horizon, and assumptions.
- The criteria weights were agreed with the sponsor before the options were scored.
- Every number in the summary can be traced to a table or an appendix.
- Assumptions and risks are listed explicitly, not buried in the text.
- The verdict is unambiguous: go, no-go, or go with named conditions, owners, and dates.
- Someone outside the project team has read the report and could explain the recommendation back to you.
Feasibility Report vs. Feasibility Study vs. Business Case
All three are produced early in a project and often by the same people, which is why they get mixed up:
| Document | Main question | Output |
|---|---|---|
| Feasibility study | Can this project work? | Analysis of the options across the five feasibility areas |
| Feasibility report (FSR) | What did the study find, and what do we recommend? | A formal document for decision makers, with a verdict |
| Business case | Should we invest in this rather than something else? | The funding justification, built partly on the report’s findings |
A feasibility report and a business case are designed to dovetail: the first proves the project is viable, the second proves it is worth the money.
Frequently Asked Questions
The feasibility study is the process: researching, analyzing, and comparing options. The feasibility report is the document that presents the results of that process to decision makers. In everyday use the two terms are often swapped, but if someone asks you for “the feasibility report,” they want the written deliverable with a recommendation.
For an internal business project, the report body is often 10-20 pages, plus appendices. Student and academic feasibility reports usually follow the length set by the course or supervisor. Large infrastructure or investor-funded projects can run to hundreds of pages, but even then the executive summary should stay at one or two pages.
A financial (or economic) feasibility report focuses only on the money side: investment required, operating costs, revenue or savings forecasts, funding sources, and indicators such as NPV, ROI, and payback period. It is common when a lender or investor is involved. In a full feasibility report, the same content appears as the cost-benefit evaluation section, alongside the technical, operational, schedule, and legal findings.
Usually the project sponsor, sometimes together with a steering committee, an investment board, or an external funding body. The approver’s decision (go, no-go, or go with conditions) is often recorded on a sign-off page at the end of the report.
No. A report that concludes a project is not viable is a positive result: it stops the sponsor from spending money and time on a project that would not deliver. What makes a report a failure is a vague conclusion that leaves the decision makers no better informed than before.
Yes. Our feasibility study template is free in Word and PDF, with no email required. It covers the full report body, from the executive summary to the recommendation and sign-off, with guidance prompts in every section.