Your Cart
Loading
Consultant reviewing a printed proposal beside a laptop and taking notes at a desk.

How to Write a Public Health Consulting Proposal: Moving Beyond Technical Expertise

You find a consulting opportunity that fits your experience. You understand the public health issue, have worked in similar settings, and can see how you would approach the assignment.


Then you sit down to write the proposal.


How much detail should you include? How do you demonstrate your expertise without simply repeating your CV? And how do you explain your approach when important information is still missing?


Writing a public health consulting proposal requires more than describing what you know. It requires helping a prospective client understand how your expertise relates to their need and why your proposed approach makes sense.


A Proposal Is More Than a Description of Your Services

It is tempting to treat a proposal as an opportunity to showcase your qualifications, experience, and technical knowledge.


While these cartainly matter, it is important to keep in mind that the client is also trying to make a decision.

They need to understand whether you grasp what the assignment entails, whether your approach is appropriate, and whether they can trust you to deliver within the available time and resources.


A strong proposal connects your experience to those concerns. Rather than leaving the reader to work out why your background is relevant, it makes that relevance clear.


For example, having experience in programme evaluation is useful. Explaining how that experience will help you address a particular evaluation challenge is more persuasive.


The shift is from “Here is what I have done” to “Here is how my experience can help with this assignment.”


Start with the Assignment, Not Your Biography

Before writing, spend time understanding what the client is asking for.


A terms of reference document may describe activities and deliverables, but the purpose behind them deserves equal attention. What decision will the work inform? What problem is the organisation trying to address? How will the findings or recommendations be used?


Consider an assignment to review a public health programme. A technically thorough review could still fall short if it does not help the client make the decision that prompted the work.


Perhaps they need to decide whether to expand the programme. Perhaps they need to understand implementation barriers. Perhaps they need evidence to inform the next funding cycle.


Each objective can lead to a different approach.


Where clarification is possible, ask focused questions. Where it is not, distinguish between what the brief establishes and what you are assuming.


Make Your Approach Specific to the Context

Public health consulting takes place across varied institutional, geographic, and operational settings.


Therefore, an approach that worked well for one organisation may need substantial adaptation for another. Access to data, stakeholder availability, local capacity, and decision-making processes can all affect what is feasible.


Your proposal should show that you have considered those realities.


For example, proposing extensive stakeholder consultations may sound thorough. But if the assignment has a short timeline or stakeholders are difficult to reach, the client needs to understand how your approach will remain workable.


Specificity does not mean writing the longest possible methodology. It means explaining the choices that matter and connecting them to the assignment.


Demonstrate Relevant Experience Selectively

You do not need to include every project you have worked on.


A few well-chosen examples can tell the client more than a long list of assignments with little explanation. The most useful examples help the reader understand the connection between your previous work and the current opportunity. That connection might concern the technical subject, the type of organisation, the stakeholder environment, or a delivery challenge.


Be clear about your own contribution, particularly when describing work completed as part of a team.


For professionals transitioning into consulting, relevant experience may come from employment, research, programme management, or other roles. The task is to explain how that experience prepares you for the work being proposed.


Keep the Promise Realistic

A proposal creates expectations that will carry into delivery. This makes it important to distinguish between what you can commit to producing and what depends on factors outside your control.


You may be able to deliver an analysis, facilitate a planning process, or develop recommendations. Whether those recommendations are adopted may depend on funding, leadership decisions, or organisational capacity.


Similarly, a timeline that looks competitive on paper can become a problem if it relies on immediate access to information or unusually fast feedback.


A credible proposal shows ambition alongside an honest understanding of the conditions needed to deliver.


Treat the Budget as Part of the Approach

The financial proposal and technical proposal should tell a consistent story.


If the proposed work involves substantial consultation, analysis, or coordination, the budget needs to reflect that effort. If resources are constrained, the approach may need to be adjusted.


Pricing is therefore more than choosing a daily rate. It involves understanding the work you are committing to and the resources required to carry it out.


A mismatch between the approach and the budget can create difficulties even when the proposal is accepted. Underestimating effort may leave too little time for important activities or make the assignment difficult to sustain financially.


The aim is to propose work that is both valuable to the client and feasible for you to deliver.


Make the Proposal Easy to Assess

Your reader may be reviewing several submissions alongside other responsibilities.


Clear writing helps them understand your proposal and locate the information they need. Follow the requested format, respect any length limits, and make the relationship between the client’s requirements and your response easy to follow.


Technical language has its place, but it should support understanding. Broad claims about quality or impact are less useful than a clear explanation of what you intend to do and why.


Before submitting, consider the proposal from the client’s perspective: does it give them a coherent basis for assessing your suitability?


A Strong Proposal Cannot Guarantee Selection

Consulting decisions depend on more than the quality of a written submission. Competition, budget, eligibility requirements, and organisational priorities may all influence the outcome.


An unsuccessful proposal does not automatically mean your approach was poor or your experience insufficient.


Where feedback is available, use it to identify what you can improve. Over time, proposal writing becomes a way to sharpen how you communicate your value and assess which opportunities are worth pursuing.


Looking for a Structured Approach?

Understanding these principles is one thing. Applying them when a submission deadline is approaching can be another.


My Proposal Writing Guide for Public Health Consultants provides a practical framework for developing proposals, alongside a reusable proposal draft template, budget template, and review checklist. It is designed for public health consulting contexts, including formal requests for proposals and direct client pitches.


Explore More Consulting Resources

For tools and guidance covering the transition into consulting, proposal writing, and starting assignments, explore my Public Health Consulting Resources library.