![The template open in Strokes: a banner picture of a bridge being built across a calm river at dawn, one span still to go, above the title “Project proposal: [Project name]”.](/_next/image?url=%2F_next%2Fstatic%2Fmedia%2Fhero-light.f829b9af.webp&w=3840&q=75)
![The template open in Strokes: a banner picture of a bridge being built across a calm river at dawn, one span still to go, above the title “Project proposal: [Project name]”.](/_next/image?url=%2F_next%2Fstatic%2Fmedia%2Fhero-dark.c7ebd01f.webp&w=3840&q=75)
When to use it
- Asking leadership for budget, people or time for an internal project
- Making the case for a tool purchase, a migration or a process change
- Pitching a project to a client who has not asked for one yet
- Answering a client's request for proposals, with the sections reordered to match it
- Funding requests to a committee or board that has no form of its own
How to use this template
- Start with the problem, not the solution
Fill in The problem and Objectives before you touch the approach. Describe the problem in the reader's terms: what it costs them and how you know. If you can't state it without naming your fix ("we don't have a CRM"), you have described a purchase, not a problem.
- Show the options, including doing nothing
Approvers trust a proposal more when they can see what you rejected. Put at least two real options in the table, plus "do nothing", and price doing nothing in the same units as the problem. That row often makes the argument for you.
- Build the budget from the timeline
Every cost line should trace back to the scope or the timeline: a role times days times a rate, a license times seats times months. Give contingency its own line and say how you sized it. A buffer hidden inside other lines looks like padding when finance finds it, and finance usually finds it.
- Write the summary last and end with the ask
With everything else in place, write the summary in three to five sentences: problem, proposal, cost, end date, decision. Then make Decision requested specific. Say what a yes unlocks (money, people, a start date) and the date you need it by.
A filled-in summary and objectives
Here is the top of a finished proposal for a small internal project. Each number has a source or a basis, and by the fourth sentence the reader knows what they are being asked to approve.
Summary. Support handled 4,210 tickets in the second quarter, and 1,180 of them (28%) asked how to do something the help center already explains. The articles exist; customers can't find or follow them. We propose rewriting the 40 most-viewed articles over ten weeks with a contract technical writer and two days a week from a support lead, for $20,900 including a 10% contingency. We need a decision by November 3 to start on November 9.
Objectives.
- Cut how-to tickets from 28% of volume to 18% by March 31, counted by ticket tag in the help desk.
- Raise the average "Was this helpful?" score on the 40 articles from 2.9 to 4 out of 5 by the same date.
Budget. Writer, 10 weeks at $1,800: $18,000. Ten usability sessions at $100: $1,000. Contingency, 10% of $19,000: $1,900. Total: $20,900.
Look at what the objectives measure. The 40 rewritten articles are the deliverable and belong in scope; fewer tickets is the result the sponsor is paying for. The usual test for an objective goes back to George T. Doran's 1981 article in Management Review, which introduced SMART goals: specific, measurable, assignable, realistic and time-related. The A deserves its original meaning. Someone has to own the goal.
Objectives
- Cut how-to tickets from 28% to 18% of volume by March 31
- Raise article ratings from 2.9 to 4 out of 5 by March 31
Deliverables dressed as objectives
- Rewrite the help center
- Improve documentation quality
Proposal, brief, charter or SOW?
These documents overlap, and organizations use the names loosely. The useful difference is the question each one answers and when it appears.
| Document | Answers | Comes |
|---|---|---|
| DocumentProject proposal | AnswersShould we do this, and what will it cost? | ComesBefore approval |
| DocumentOne-pager | AnswersIs this worth a longer look? | ComesBefore a proposal, or instead of one for small asks |
| DocumentProject brief | AnswersWhat exactly are we making, and for whom? | ComesAt kickoff |
| DocumentProject charter | AnswersWho has the authority to run it? | ComesWhen the project is formally authorized |
| DocumentStatement of work | AnswersWhat will a supplier deliver, on what terms? | ComesWith the contract |
An approved proposal becomes raw material. The objectives and scope move into the project brief, and if you hire outside help, the deliverables and timeline move into a statement of work. If your ask fits on a single page, use the one-pager template instead.
Writing for a client or an RFP
The template is set up for an internal ask, where the reader already knows you and wants the numbers. A proposal to a client needs a few changes:
- Add a section on why you. Two or three similar projects with their results, and the people who will do the work. Put it after the approach, where the reader is deciding whether you can deliver it.
- Turn the budget into pricing. Say what is included, how you bill (fixed fee, time and materials, or a retainer), the payment terms and how long the price holds.
- Send it as a PDF. The layout and the numbers arrive exactly as you wrote them, and nobody edits your pricing by accident.
When you answer a request for proposals, the request sets the structure. Use its section headings in its order, and answer each requirement where an evaluator will look for it. Many teams keep a compliance matrix: a table that lists every requirement beside the section that answers it. Treat page limits and formatting rules in an RFP as hard rules.
Mistakes reviewers push back on
- Numbers without a source. "Customers are frustrated" invites an argument. "1,180 tickets last quarter, from the help desk report" ends one.
- No out-of-scope list. Whatever you leave unsaid, someone will assume is included. The exclusions protect your budget more than any other line.
- Risks that are someone else's fault. "The vendor may be late" tells the reader nothing new. Name the estimate you are least sure of and the person you can't replace.
- A proposal with no deadline on the decision. Without a date, it waits behind everything that has one.
Frequently asked questions
How long should a project proposal be?
As long as the decision needs. An internal proposal usually fits in one to three pages, with the summary on the first. Responses to a formal request for proposals run longer, but the request sets the page limit, and you should treat it as a hard rule.
What is the difference between a project proposal and a project plan?
A proposal asks for a decision: it argues that the project is worth its cost and shows enough of the plan to be believable. The project plan comes after approval and goes much deeper, with tasks, dependencies, a detailed schedule and who does what each week.
Should a project proposal include contingency?
Yes, as its own line with a sentence on how you sized it. The right amount depends on how uncertain your estimates are and on your organization's rules, so check with finance. A visible contingency reads as honest planning; a buffer hidden inside other lines reads as padding.
What does SMART stand for?
In George T. Doran's 1981 article that introduced it: specific, measurable, assignable, realistic and time-related. Later versions often use achievable and relevant instead. Either way, the test is whether someone can check on a given date that the objective was met, and who answers for it.
