Project proposal example with objectives, milestones and budget

Both documents try to win approval, but they answer different questions. A business proposal sells a service or a relationship. A project proposal sells a plan. The reader wants to know that the work is well defined, the risks are understood and the budget is realistic.

• It is built around one project with a clear finish line
• It explains the method, not just the outcome
• It lists milestones and who is responsible for each
• It names risks openly and says how they will be handled
• It defines success criteria the approver can check afterward

Project proposals are written by vendors for clients, and also internally, by a manager asking leadership for budget. The structure is the same in both cases.

Use this order and the approver can follow your reasoning from the problem to the decision without jumping around the document.

• Project title and summary
• Background and the problem to solve
• Objectives and success criteria
• Approach and methodology
• Milestones and timeline
• Team, roles and responsibilities
• Budget
• Risks and mitigation
• Approval and next steps

Our project proposal template contains all of these sections, ready for your own project.

In this example, Keystone Workflow Consulting proposes a central scheduling project to Northfield Dental Group, which runs six clinics. Here is the opening of the proposal as the operations director reads it.

Project title: Central patient scheduling for Northfield Dental Group

Summary: Each Northfield clinic books appointments separately, so patients who call the wrong clinic are often asked to call back, and open chair time at one clinic goes unused while another is fully booked. We propose a fourteen week project to set up a central scheduling team, shared booking rules and one phone number for new patients, delivered in three phases with a pilot at two clinics before rollout. The project budget is $64,500.

Background: Northfield grew from two to six clinics over several years. Scheduling practices grew with each clinic rather than being designed together, so each location uses its own booking rules, its own templates in the practice management system and its own phone greeting. Clinic managers report that front desk staff spend much of the morning on the phone instead of with patients in the office.

Objectives tell the approver what will be different when the project ends. Good objectives are specific and can be checked, and they use the client's own baseline rather than borrowed industry numbers.

Objectives:

• One phone number and one online booking path for all new patients
• Shared booking rules and appointment templates across all six clinics
• A central scheduling team of existing staff, trained and working from one queue
• A weekly report showing open chair time by clinic

Success criteria, measured against the four weeks before the project starts:

• Fewer callers asked to call another clinic, tracked through the new phone system
• Less unused chair time across the group, measured from the practice management reports
• Front desk staff at the pilot clinics spend less time on scheduling calls, measured by a two week time log before and after

Northfield will confirm the baseline figures with Keystone during the first two weeks.

The approach section explains how the work will be done. The milestone table turns it into dates the approver can plan around.

Approach: We start by mapping how each clinic schedules today and agreeing on one set of booking rules with the clinic managers. We then pilot central scheduling at two clinics for four weeks, adjust the rules and staffing based on what we learn and roll out to the remaining four clinics in two waves.

Approvers want to know who is doing the work and what they are paying for. Break the budget down by phase, and keep anything the client pays to third parties separate.

Team: a Keystone project lead (part time across all fourteen weeks), a scheduling process specialist (weeks 1 to 9) and a training lead (weeks 7 to 14). Northfield provides the operations director as sponsor, one manager per clinic for workshops and a staff member from IT for phone system changes.

Not included: phone system licenses or hardware, changes made by the practice management software vendor and staff wages during training. Fees are invoiced at the end of each phase.

Naming risks builds trust. An approver who sees that you have thought about what could go wrong is more likely to believe the rest of the plan.

Approval and next steps: once this proposal is signed, Keystone schedules the discovery workshops within ten business days and sends a detailed week one plan to the operations director.

The example above works because it is concrete. These habits make any project proposal easier to approve.

• Write the summary last, after the plan is clear, and keep it to one paragraph
• Tie every objective to something the approver already cares about
• Use the client's baseline instead of industry averages you cannot source
• Put owners next to milestones, including the client's own people
• Separate your fees from third party costs and from the client's internal time
• Make approval easy with an electronic signature in the same document
• Keep the proposal short enough that the approver can read it before the meeting where the decision is made
• Offer a smaller first phase when the budget is a concern, so the approver can say yes to part of the plan

A project proposal is also a promise about how you will work. If the plan is clear on paper, the approver assumes the project will be run the same way.

When the project itself is agreed and you need a contract level description of the work, follow up with a statement of work. Our statement of work example shows how.