← All postsHow-to

Project proposal template: the sections a decision actually needs

A project proposal template is judged on two sections: what will be delivered, and what it costs. Here is a structure that gets those decided instead of deferred.

How-toP

A project proposal template exists to get a decision. Not to demonstrate effort, not to describe your methodology, and not to look impressive in a PDF — to let somebody say yes, or say what would have to change for a yes. Most proposals fail because the reader cannot find the two things they need to decide on: the scope and the number.

This structure works for an internal project seeking budget and for an external bid, with one difference noted at the end.

The project proposal template

  • Summary — problem, approach, cost and timeline in four sentences at the top. Many decisions are made from this box alone.
  • Problem or opportunity — the situation in the reader's terms, with whatever evidence exists. If you cannot state it without adjectives, the proposal is early.
  • Objectives — what will be true when the project is done, phrased so anyone can tell whether it happened.
  • Scope — deliverables as things a person can point at, plus an explicit list of what is out of scope.
  • Approach and phases — how the work runs, with what you need from them at each phase.
  • Timeline — dates or durations, dependencies named, and the assumptions the dates rest on.
  • Cost — the number, what it covers, the payment or budget schedule, and what would change it.
  • Risks — the three that actually matter, each with what you would do about it. Naming risks makes a proposal more credible, not less.
  • Team — who does the work, briefly.
  • Decision — what you are asking for and by when.

The out-of-scope list is the highest-value section per line in the whole document. Two lines naming what is excluded prevents the conversation six weeks in where both sides remember the agreement differently.

Writing it so it gets read

  1. Write the summary last, then move it to the top.
  2. State the problem in the words the client or sponsor used. Recognition is what earns you the second page.
  3. Give one number, not a range. If the scope is genuinely uncertain, propose a small paid discovery phase and price the rest afterwards.
  4. Put assumptions where they can be seen — dependencies on their data, their approvals, their availability — rather than in a footnote.
  5. Keep it to five pages. Detail that matters to specialists goes in an appendix.
  6. End with a dated next step and follow up on that date, not a week later.

Internal proposals differ in one way

An external proposal argues that you are the right supplier. An internal one argues that this project beats the other things the same money and people could do. That means the comparison section — what happens if we do nothing, and what we are not doing instead — carries the weight that "why us" carries externally.

Both benefit from naming the decision-maker's actual constraint. A sponsor with a fixed budget and flexible dates needs a different shape of proposal from one with a hard deadline and a flexible budget, and the proposal that ignores this gets deferred rather than refused.

In Ettex, proposals are one of the document templates in Write, alongside briefs and reports: rich formatting with headings, tables and images, reusable text styles so every proposal looks the same, an outline view for navigating long documents, comments and @mentions for an internal review pass, version history to compare drafts and restore any of them, and export to PDF, DOCX, ODT or Markdown. When the proposal is agreed, Ettex Sign turns it into a signature request with reminders and an audit trail — an accepted proposal is a contract and should be signed like one.

What gets proposals deferred

  • No summary, so the decision-maker has to read five pages to find the number.
  • Deliverables described as activities — "workshops", "analysis" — rather than outputs.
  • A price range, which is read as the top of the range plus uncertainty.
  • No risks section, which reads as either naivety or concealment.
  • Ending with "let us know your thoughts", which asks the reader to invent the next step.

Frequently asked

How long should a project proposal be?

Five pages or fewer, with a one-paragraph summary at the top and any depth in an appendix.

What is the difference between a project proposal and a business proposal?

A business proposal offers your services generally; a project proposal defines one specific piece of work with its own scope, timeline and cost.

Should a proposal include a price range?

Prefer one number for a defined scope. Where scope is genuinely unknown, price a discovery phase firmly and quote the rest once it is known.

How detailed should the timeline be?

Phase level, with dependencies and the assumptions the dates rest on. Task-level plans belong in the project, not the proposal.

Do internal proposals need a risks section?

Especially internal ones. Sponsors approve projects they believe are understood, and naming three real risks with responses is the cheapest way to show that.

A project proposal template earns its place when the reader can find the scope and the cost in under a minute and knows exactly what to do next. Everything else is supporting material.

IP
Written by Ivan P.

Part of the Ettex team — writing about product, engineering and the future of work.

More posts
Get the best of the Ettex blogProduct news, guides and tips — straight to your inbox, no spam.