Project Proposal Template
The situation, what you propose, what it produces and what it costs.
Details
project proposal templateUploads
Your logo
A photo or picture
Goes on this page only. Drag it anywhere and pull its corner to resize it.
Your signature
Draw it with a finger, a mouse or a trackpad, and it goes on the page like a picture.
Pictures and signatures stay on this device. Nothing is uploaded to a server.
Red highlights mark what is still blank. Click anything on the page to change it. Your draft is kept on this device as you work.
Once it is filled in it still has to be signed. An e-signature service gets it signed and timestamped without anyone printing or scanning.
| Prepared for | [client] |
| Project | [project name] |
| Date | October 14, 2026 |
1. The situation
[what is happening now, in their terms — this should be recognisable to them]
2. What we propose
[the approach, plainly]
3. What you get
| Deliverable | When |
|---|---|
| [add one deliverable per line] |
4. Who does the work
| Name | Role | Time |
|---|---|---|
| [add one person per line] |
5. Cost
| Item | Amount |
|---|---|
| [add one cost per line] |
6. To proceed
Sign below and return one copy. This proposal is open for 30 days from the date above. Anything outside the deliverables listed is quoted separately before it is started.
What is a Project Proposal?
A project proposal sets out the situation, what you propose to do about it, what will be produced, what it costs, how long it takes and what happens next. It matters because it is the document the decision is made from, and anything not in it gets argued about later. Without one, a project starts on the strength of a conversation, and the scope each side remembers turns out to be different.
Agencies, consultants and freelancers write them for clients. Internal teams write them for a budget holder or a steering group. Charities and research groups write them for funders, contractors write them in response to tenders, and suppliers write them to convert an enquiry into work. The document does two jobs at once: it persuades someone to say yes, and it defines what they are saying yes to. Proposals that do the first well and neglect the second are where delivery disputes come from.
When you are responding to a formal tender or a grant call, the format is not yours to choose. Public procurement rules set the process and the buyer's invitation to tender sets the structure, the word limits, the scoring and the deadline: procurement regulations in the UK, the Federal Acquisition Regulation for US federal buyers, GeM and the general financial rules in India, AusTender in Australia, and the EU directives as implemented in each member state. Late or non-compliant submissions are commonly excluded without being read, so follow the instructions exactly.
A proposal is a document you send, not a project plan — it should not carry the detailed schedule, resource plan or risk register, which come after acceptance. It is also not automatically a contract. Whether a signed acceptance forms a binding agreement, and on whose terms, depends on the wording, on what else has been exchanged and on the law that applies, so for anything of significant value have the terms reviewed rather than relying on a signature line at the end of a document.
What to put in a Project Proposal
These are the details this template asks for. Anything left blank is marked in red on the preview so you can see what is still missing.
| Field | What goes in it |
|---|---|
| Business name | For example: Barton Supply Co. |
| Your address | For example: Unit 7, Barton Road, Columbus, OH 43212 |
| Customer name | For example: Halliwell Interiors Inc. |
| Customer address | For example: 44 High Street, Columbus, OH 43215 |
| Project name | For example: Barton Road trade counter fit-out |
| The situation | For example: Your trade counter closes at 4pm, which is when your customers finish on site. Around a… |
| What we propose to do | For example: Run a six-week evening counter trial with two staff, an after-hours order line, and a… |
| What you get | One per line: Deliverable | When |
| Who does the work | One per line: Name | Role | Time |
| Costs | One per line: Item | Amount |
| Why us optional | For example: We have run this trial at two other sites and both times the answer was different from… |
How to write a Project Proposal
Open with their problem in their words
The first section should describe the situation the reader already recognises, in the language they used: the sales team rekeys orders from email into two systems, the grant reporting takes a fortnight each quarter. Quote their own figures back where you have them. A proposal that opens with your company history is asking to be skimmed. One that opens with an accurate description of their problem has already earned attention.
Define deliverables as countable things
Write what the client will have, in objects they can count and check: 'six page templates, two rounds of revisions on each, delivered as source files with a style guide' rather than 'website refresh'. Say what format, how many, and when each arrives. Every uncountable deliverable becomes an argument at the end about whether the work was actually finished.
Price the work and say what changes it
Give the price in the structure you will actually invoice: fixed fee, day rate with an estimated range and a cap, or a retainer with defined inclusions. State what is excluded — travel, third-party licences, hosting, printing — and whether tax is included, since VAT, GST and sales tax presentation differ. Then state the change mechanism: what counts as a variation, how it is quoted, and who may authorise it.
Put their dependencies on your timeline
A schedule showing only your work implies you are the only possible cause of delay. Put the client's obligations on the same timeline: content supplied by a date, access granted, one named approver, feedback consolidated within a stated number of working days. Add the consequence — the end date moves by the same period — so slippage becomes a shared fact rather than a negotiation held later.
Close with validity, assumptions and how to accept
State how long the price holds, the assumptions the estimate rests on, and exactly what the reader does next: sign here, return by this date, raise a purchase order to this reference. Name one contact on each side. A proposal that ends with 'let us know your thoughts' sits in an inbox. One that ends with a dated action and a named person gets a decision.
Common mistakes
- Leading with company credentials instead of the client's problem, so the reader reaches the price without ever seeing evidence that you understood the brief.
- Describing deliverables as activities rather than objects, which leaves no way to tell when the work is finished and delays the final invoice.
- Quoting a fixed price with no exclusions and no change mechanism, so every extra request has to be absorbed or fought over.
- Leaving the client's own dependencies off the timeline, which makes their delays look like your overrun.
- Ignoring a tender's stated format, word limits or deadline, which in formal procurement usually means exclusion no matter how good the proposal is.
Frequently asked questions
What is the difference between a project proposal and a quotation?
A quotation is a price for defined work, often a single page. A proposal explains the problem, the approach, the deliverables and the timeline, then prices them. Use a quote when the buyer already knows exactly what they want, and a proposal when part of your value is defining the work. Both should state exclusions and how long the price is valid.
How long should a project proposal be?
As short as the decision allows. Five to ten pages covers most commercial work: problem, approach, deliverables, timeline, price, terms, next step. Tenders run to whatever the buyer's format requires and no further. Detailed methodology and case studies belong in appendices, so the decision-maker can read the argument without wading through supporting material.
Is a signed proposal legally binding?
It can be, which is exactly why the terms matter. Whether a signature creates a contract, and which terms govern it, depends on the wording, on what else has been exchanged and on the law that applies. If the value or the risk is meaningful, attach your terms and have them reviewed by a qualified adviser rather than assuming a signature block settles the question.
Should I include the price in the proposal or send it separately?
Include it. A proposal without a price forces a second exchange and lets the reader anchor on a number you did not choose. If the scope is genuinely uncertain, price it in phases: a fixed fee for a short discovery stage, then an estimated range for delivery to be confirmed at the end of it. Say plainly which parts are firm.
How do I follow up on a proposal without being pushy?
Put the follow-up in the document: state the validity date and say you will check in on a specific day, then do it once. Refer to the decision they said they had to make rather than asking whether they have had a chance to look. If the answer is no, ask what changed — silence is usually a scope or budget problem you can still fix.
This page explains general practice and is not legal advice. Requirements differ between countries and, in some cases, between states — check what applies where the document will be used.