|
Video | Introduction | At a Glance | Project Information | Methodology / Approach | Assumptions | Key Deliverables | Timeline | Costs | Acceptance & Acknowledgement | Conclusion | Sources |
In this video, project management consultant Adriana Girdler walks through the seven sections she includes in every project proposal she writes for clients.
Introduction
A project proposal is a document that presents an idea to a decision-maker, who decides whether that idea becomes a project.
At work, ideas need approval before anyone spends time or money on them. A proposal gives the decision-maker what they need to answer one question: should this move forward?
Proposals usually grow out of an organization’s strategy: a company wants to cut costs, serve customers faster, or reach a new market, and someone proposes a project that would help. A proposal that connects to what the organization already cares about is easier to approve.
Section 2.4 of Open Technical Communication, “Proposals,” distinguishes two kinds. A solicited proposal answers a request, such as a call for bids. An unsolicited proposal is one you start on your own, so it first has to convince the reader that a problem or need exists. The section also notes that a proposal sells two things: the project, and you as the right person to carry it out.
A proposal is persuasive, but it isn’t a sales pitch. Decision-makers approve projects when they understand exactly what they’re agreeing to: what the project will do and produce, how long it will take, and what it will cost. Suzan Last recommends relying mainly on logic and credibility, and using emotional appeals sparingly. Section 7.2 of her textbook Technical Writing Essentials quotes engineers Irish and Weiss: “An engineering proposal is not an advertisement.”
|
In practice: The decision-maker reading your proposal is often comparing it to other ideas competing for the same budget and people. A proposal that answers their questions before they ask them has a real advantage. |
|
ABOUT THESE NOTES The seven sections below are what a typical professional proposal includes. Some, such as resources, costs, and the sign-off, matter most when a business is deciding whether to commit money and staff. Your final project proposal will use an adapted version, but you should know the full list, because it’s what you’ll see on the job. |
At a Glance
A typical project proposal has seven sections. Each one is explained below.
- Project Information: The project’s name, background, objective, scope, and resources.
- Methodology / Approach: How you plan to carry out the project.
- Assumptions: What you’re taking for granted that could change the plan.
- Key Deliverables: What the decision-maker will get at the end.
- Timeline: High-level milestones and how long the project will take.
- Costs: What the project will cost.
- Acceptance & Acknowledgement: A sign-off showing everyone agrees.
1. Project Information
This section sets up what you’re proposing and why it’s on the table.
Think of this section as a snapshot of the whole proposal. In a few short paragraphs, it tells the decision-maker what the project is, why it matters, and what it involves. Some of these points come back in more detail later, such as how you’ll do the work, what you’ll deliver, and what it will cost. Here, the goal is a quick, clear preview, so the reader understands the idea before they get to the details.
▸ Project Name
The project name is a short working title that everyone uses to refer to the project.
Choose something descriptive and easy to say, such as “New Volunteer Onboarding Guide” rather than “Project 1.” It doesn’t need to be final; it just keeps everyone talking about the same thing.
▸ Background
The background explains why this idea is coming up now.
Describe the situation as it stands today: what’s wrong, or what opportunity is being missed. Is the idea tied to the organization’s strategy, a problem that needs fixing, or an opportunity worth taking? Support it with evidence where you can, such as complaints, error rates, or time lost. The background is your justification, the reason the proposal exists. Suzan Last adds that a strong justification also shows what happens if nobody acts. The cost of doing nothing is often what gets a yes.
▸ Objective
The objective states, in a sentence or two, what the project will accomplish.
It grows directly out of the background: if the background describes a problem, the objective describes what solving it looks like. You’ll describe the specific things you’ll hand over later, under Key Deliverables. Write one or two sentences that name the result, not the activities: “New volunteers will be able to complete their first shift without a trainer present,” not “We will write a guide.” Put the justification first, so the reader sees why before what.
▸ Scope
The scope defines the boundaries of the project: what’s included and what isn’t.
Make two short lists: what’s in and what’s out. Decision-makers bring their own assumptions about what a project covers, and they often don’t match yours. Stating the scope up front puts everyone on the same page from day one.
Northeastern University’s guide to scope statements suggests a test for the “out” list: name the things a decision-maker might reasonably assume are included but aren’t. Clear exclusions also guard against scope creep, when work that was never part of the original agreement gets added partway through.
|
In practice: Scope is where many projects go wrong. “Redesign the website” can mean new colors to one person and a complete rebuild to another. Writing down what’s in and out prevents that argument later. |
▸ Resources
Resources gives a quick overview of the people, skills, and time the project needs.
This part identifies the roles involved (such as a writer, subject-matter expert, designer, or reviewer), how many people fill each, roughly how much of their time the project will take, and whether they come from inside the organization or outside. Name roles rather than individuals if assignments aren’t settled. Approving a project means committing people who already have other work, so the decision-maker needs to know what it will take from their team. The Costs section puts a price on these later.
2. Methodology / Approach
The methodology describes the major activities you’ll use to get from the idea to the finished deliverable, in the order you’ll do them.
To write it, walk through the project from start to finish and name each major stage and what happens in it. Projects often begin with research or discovery, move into workshops, interviews, or drafting, and end with testing and revision. For each stage, say briefly what you’ll do and why. You can also note checkpoints, sometimes called go/no-go points, where the decision-maker approves whether the project continues.
The methodology shows the decision-maker that the plan is realistic; a good idea with no believable path to completion is hard to approve. Checkpoints add confidence, because the reader won’t be locked in if something changes. Keep it high level: show you’ve thought the path through, without planning every step.
3. Assumptions
Assumptions are the conditions you’re treating as true in order to plan the project.
Debra Patterson’s Strategic Project Management defines an assumption as something you aren’t sure of but can confirm later, or accept as true so the project can move forward. Constraints are different: limits you already know about, such as a fixed deadline, a small budget, or a short-staffed team. Many proposals list both.
Assumptions come after the methodology because they come from both the project information and your approach. To find them, reread everything you’ve written and ask of each statement, “What has to be true for this to work?” List those conditions plainly, one per line.
Small assumptions can change a lot. Are your workshops in person or online? In-person workshops change the cost, the schedule, and who can attend. If you don’t say, the reader will assume, and may assume differently than you.
|
In practice: Stating an assumption protects both sides. If it turns out to be wrong, everyone can see why the plan needs to change, and nobody is caught off guard. |
4. Key Deliverables
Deliverables are the tangible results the decision-maker will receive when the project is finished.
This section is often short, sometimes a single line. A project may involve dozens of activities, but the deliverable is the result: a report, a piece of equipment, an installed system, a finished manual. For a process improvement project, it might simply be a report mapping the improved process and what needs to change to get there. Name each deliverable and describe it in a sentence: what it is, what form it takes, and who it’s for.
A clear deliverable tells everyone what “done” looks like. Northeastern’s scope guide offers a quick check: deliverables are usually nouns (a manual, a report, a training video), while the work that produces them is verbs (research, draft, test). If your deliverable starts with a verb, you’ve described an activity, not a result.
5. Timeline
The timeline lays out the project’s major milestones and how long the whole project will take.
Take the stages from your methodology and give each a target date or duration. Milestones are the points where something is finished or decided, such as “research complete” or “first draft ready for review.” Stick to the major stages, not a detailed schedule.
Decision-makers need to know whether a project will take two weeks, three months, or two years, and whether it fits around other deadlines. A proposal is not a project plan; detailed planning comes after approval. Suzan Last suggests showing the timeline visually, such as a simple Gantt chart (a bar chart of each stage across time), so the reader sees the whole schedule at a glance.
6. Costs
The costs section estimates what the project will cost, and it’s often the deciding factor.
A decision-maker may love an idea and still say no if it doesn’t fit the budget. To write this section, estimate what each part of your resources and methodology will cost, grouped into the main types:
- Resource costs: Staff time, whether people come from inside the organization or are hired from outside.
- Fixed costs: One-time purchases, such as software or equipment.
- Direct costs: Expenses tied to specific project activities, such as travel, lodging, or food for a workshop.
You don’t need a line-by-line budget yet; that comes during detailed planning. But the reader needs a realistic sense of the total.
|
In practice: An honest cost estimate builds more trust than an optimistic one. A project that runs far over its proposed cost makes the writer’s next proposal harder to approve. |
7. Acceptance & Acknowledgement
The acceptance section is the formal sign-off that turns the proposal into an agreement.
Provide a space for the writer and each decision-maker (the client, project owner, or senior leader) to sign and date the document, confirming that they agree with the proposal and that the project will move forward. Patterson’s sample project charter, a closely related document, ends the same way, listing the name, title, and signature line of each person who signs off.
It works like a contract: everyone agrees on the same scope, deliverables, timeline, and costs, with written proof. If questions come up later about what was promised, the signed proposal is the answer.
Conclusion
A proposal gets an idea approved. It isn’t the plan for carrying it out.
A strong proposal answers a decision-maker’s questions in a logical order: why the idea matters, what it will accomplish, how it will happen, what you’re assuming, what they’ll get, how long it will take, and what it will cost. Once it’s accepted, the real work begins with initiation and detailed planning. The proposal’s job is to get the idea to that starting line, with everyone agreeing on what they’ve said yes to.
Sources & Further Reading
- Adriana Girdler, “How to Write a Winning Project Proposal” (video)
- David McMurrey and Jonathan Arnett, Open Technical Communication, Section 2.4, “Proposals” (CC BY 4.0)
- Suzan Last, Technical Writing Essentials, Section 7.2, “Proposals” (CC BY 4.0)
- Debra Patterson, Strategic Project Management, Section 5.11, “Example of a Simple Project Charter” (CC BY-NC-SA 4.0)
- Northeastern University Graduate Programs, “How to Develop a Project Scope Statement in 8 Steps”