Writing a project report or business case that gets a decision

At some point most growing businesses need to put a proposal in writing for someone else to approve. A bank wants a report before lending for new equipment. An investor wants to understand the expansion plan. A government program requires a project proposal before granting support. A council or regulator needs details before approving a facility. A large customer wants a detailed proposal before awarding a contract.

These documents go by different names, such as project report, business case, project proposal, feasibility report or detailed project report, but they share a purpose: to give a decision-maker enough clear, credible information to say yes. Many small businesses find them intimidating and either avoid them or produce long, unfocused documents. This article explains when you need one, what different audiences look for, a standard structure, and how to make the report persuasive without overstating anything.

Why a project report is worth the effort

A good project report does more than satisfy a requirement. It:

Describes the business clearly: its history, capability, financial position and plans, in one place.
Forces you to think through risks in advance. Writing the report often reveals problems, gaps and assumptions that would otherwise surface later at greater cost.
Builds credibility with lenders, investors, government agencies, customers and staff.
Supports large transactions. Business-to-government and business-to-business deals of significant value usually require formal documentation.

Even when nobody asks for one, writing a short business case before a major investment improves the decision.

Common uses and what each audience wants

1. Raising finance

Lenders and investors both want a report, with different emphases.

Lenders focus on your ability to repay. Expect to provide:

Company profile: when and how the business started, its structure and what it does.
Owners and management: backgrounds, experience and qualifications.
Employees: numbers and key people.
Infrastructure: premises, machinery, tools and processes.
Customers: types of customer, major accounts and significant contracts or pipeline.
Operations: locations and branches.
Funding history: how the business has been financed to date.
Credit history: existing and past borrowing.
Financial statements: profit and loss, balance sheet and cash flow, usually for several years plus current trading.
Use of funds: exactly where the new money will go.
Key ratios: profitability, liquidity, debt service cover and break-even analysis.

Above all, lenders want four things to be clear: how much you need, what it will be used for, how it will be repaid and what security or guarantees support it.

Investors care more about growth potential, market size, competitive advantage, the team and the return on their investment, but they also expect sound financials and a credible use of funds.

2. Grants, incentives and concessions

Government support programs usually require evidence that you meet eligibility criteria and that the project fits the program’s objectives. Typical content includes the business profile, the industry and location, infrastructure and machinery, years of experience in the field, proof of eligibility against the program’s rules, the business plan, existing and proposed investment, and expansion plans. Read the guidelines closely and address each criterion explicitly, because assessors often score against them line by line.

3. Approvals and licences

Establishing a facility, obtaining certain licences, securing land or development approvals, gaining quality certifications or tendering for public projects may all require a structured report describing the project, its impacts and how requirements will be met.

4. Policy submissions

Industry associations and businesses sometimes prepare reports to support submissions on policy changes, providing evidence for why a regulation or program should change.

5. Client proposals

In business-to-business selling, a detailed proposal often decides the contract. For example, an agency pitching a digital marketing contract would set out how it will report results, measure traffic and conversions, run campaigns and improve visibility. An engineering firm would set out its approach, deliverables, timeline, team and price. A clear, specific proposal shows competence before any work begins.

Know your reader: need, interest, concern, expectation

Before writing, analyse the decision-maker. A simple framework is NICE:

Need: what does the reader need from this report to make a decision?
Interest: what outcome are they interested in, such as repayment, growth, public benefit or a solved problem?
Concern: what worries them? These are the risks they will look for.
Expectation: what format, level of detail and evidence do they expect?

A report that addresses the reader’s concerns directly, such as “what if demand is lower than forecast?”, is far more persuasive than one that only presents the upside. Show that you have identified the risks and have a plan for them.

A standard structure

Keep the report as simple as the subject allows. The person reading it is a busy human being who wants to understand the proposal quickly. A standard structure:

1. Cover letter or introduction

A short letter or introduction stating what the report is, who it is from, what is being requested and the key reason to approve it.

2. Executive summary

One to two pages summarising the whole report: the opportunity or problem, the proposed project, the amount requested, expected outcomes and benefits, key risks and mitigations, and the decision sought. Many decision-makers read only the cover letter and executive summary, or form their view there before skimming the rest. Write the summary last, and make it able to stand alone.

3. Body of the report

The body typically covers:

Objectives: what the project will achieve, in measurable terms.
Approach: how it will be done, including technology, methods, suppliers and partners.
Deliverables: what will be produced or delivered.
Budget: total cost broken into categories, with assumptions and contingency.
Resources: people, skills and key roles.
Timeline: phases and milestones.
Market and demand: evidence that the output is needed, such as customers, orders, market research or letters of support.
Risks: the main risks, their likelihood and impact, and how each will be managed.
Company profile: capability, track record and relevant experience.
Financials: historical statements and projections, including cash flow and break-even, with the assumptions stated.

4. Conclusion

Restate the objective, how it will be implemented and the benefits, so the reader finishes with the key points fresh in mind. End with the specific decision or action requested.

5. Appendices

Supporting detail, such as quotations, drawings, CVs, letters of support, certifications and detailed financial models, goes in appendices so the main report stays readable.

Writing a strong executive summary

Because the executive summary carries so much weight, it deserves special care:

Lead with the request and the reason. “We seek a $350,000 equipment loan to install a second CNC machining centre, which will double capacity for existing contracted demand.”
Quantify the benefits: additional revenue, margin, jobs, cost savings or capacity.
Show evidence: contracts, orders, pilot results or market data.
Acknowledge the main risks in a sentence or two, with mitigations.
Keep it short: one page is ideal and two is the maximum.

Making the numbers credible

Financial projections are where many reports lose credibility. Guidelines:

State your assumptions for volumes, prices, costs, timing and growth rates, so readers can judge them.
Base forecasts on evidence: past performance, signed orders, quotes and market data.
Show scenarios, such as base case, downside and upside, especially for lenders.
Reconcile the statements so profit, cash flow and balance sheet projections are consistent with each other.
Use break-even analysis to show how much volume is needed to cover costs.
Get an accountant to review the financial sections for significant applications.

Writing style that persuades

Decision-makers read many reports. Clear writing helps yours stand out:

Use plain language. Explain technical terms briefly, or avoid them. Assessors and bank officers may not be specialists in your field.
Use headings that match the reader’s questions, such as “How the loan will be repaid” or “Evidence of demand”, so they can find answers quickly.
Prefer specifics to adjectives. “Two signed contracts worth $480,000 per year” persuades. “Strong demand” does not.
Use tables and simple charts for numbers, timelines and comparisons.
Keep paragraphs short, and put the conclusion first in each section.
Be consistent in terminology, units and figures throughout.
Proofread. Spelling errors and inconsistent numbers suggest carelessness, and readers may assume the project will be run the same way.

Common mistakes

Too long and unfocused. Length does not equal quality.
Writing for yourself, not the reader. Address their needs and concerns.
Over-optimism. Unrealistic forecasts damage credibility instantly.
Missing the ask. Be explicit about what you want approved.
Ignoring eligibility criteria in grant applications.
Inconsistent numbers across sections.
Exaggerated claims. State capability and results accurately, because decision-makers check.

A worked outline

A small manufacturer seeking a loan for a new machine might structure its report as:

Cover letter: request for an equipment loan, purpose and repayment term.
Executive summary: current capacity constraint, contracted demand, the machine, cost, expected revenue and margin, repayment plan and key risks.
Company profile: eight years trading, owners’ experience, staff, current equipment and key customers.
Market and demand: two contracts and a pipeline that exceed current capacity.
Project: machine specification, supplier quotation, installation and commissioning plan, training and timeline.
Financials: three years of statements, a two-year forecast with and without the machine, a cash flow forecast and debt service cover.
Risks: delivery delays, operator training and the possible loss of a contract, each with a mitigation.
Conclusion and request.
Appendices: quotation, contracts and financial statements.

Presenting the report in person

Many reports are followed by a meeting or presentation, with a bank manager, an investment committee, a program assessor or a customer’s selection panel. Preparation matters as much as the document:

Know the report thoroughly, especially the numbers and assumptions. Hesitation over your own figures undermines confidence.
Lead with the summary. Open with the request, the reason and the main benefits in two or three minutes.
Anticipate questions. List the ten toughest questions a sceptical reader could ask, such as “what if your biggest customer leaves?”, “why will this machine be utilised?” or “what happens if the project runs late?”, and prepare clear answers.
Bring the right people. If technical questions are likely, bring the person who knows the technical detail.
Be honest about uncertainty. Decision-makers respect applicants who acknowledge risks and show how they will manage them.
Confirm next steps before leaving: what additional information is needed, and when a decision will be made.

A pre-submission checklist

Before sending any significant report, check:

The request, meaning amount, approval or decision, is stated clearly on the first page.
The executive summary stands alone and fits on one or two pages.
Every eligibility criterion or tender requirement is addressed explicitly, with page references if helpful.
Financial figures are consistent across the summary, body and appendices.
Assumptions are stated, and forecasts are supported by evidence.
Risks are identified with credible mitigations.
Claims about capability, experience, customers and results are accurate and verifiable.
Supporting documents, such as quotations, statements, certificates and letters, are attached and current.
Someone who did not write the report has read it for clarity.
The document is formatted cleanly, with page numbers, headings and a contents page for longer reports.

Frequently asked questions

How long should a project report be? As long as the decision requires and no longer. A small equipment loan may need ten pages plus attachments. A major grant or development approval may need fifty or more. Many funders and agencies specify formats or page limits, so follow them.

Should I use a consultant to write it? For large or complex applications, an accountant, grant writer or specialist consultant can add value, particularly on financial modelling and on matching the funder’s criteria. You should still own the content, because you will need to answer questions and deliver the project.

Can one report serve several audiences? A core business case can be adapted, but each audience has different priorities. Lenders focus on repayment, investors on return, grant bodies on program objectives and customers on solutions. Tailor the executive summary and emphasis for each.

What if the numbers do not look good? Then the report has done its job by revealing a weak project before money was committed. Revisit the scope, the costs or the timing, or decide not to proceed.

Summary

A project report or business case is a decision document. Know who will read it and what they need, are interested in, worry about and expect. Use a clear structure: introduction, executive summary, objectives, approach, deliverables, budget, resources, timeline, market evidence, risks, company profile, financials and conclusion. Invest most effort in the executive summary, back your numbers with evidence and stated assumptions, and be explicit about the decision you are asking for. A clear, honest report makes it easy for a lender, investor, agency or customer to say yes.

Sources: small-business training notes on preparing project reports for finance, subsidies, approvals and client proposals, together with general business-case practice. This article is general information, not financial advice.