Needs assessment outline: health status and population

The audience is stated and it changes everything: the purpose is to help reviewers understand the community or organisation the project will serve. Reviewers are deciding whether to fund something, so they are reading for whether a real need exists, whether you can document it, and whether you understand your own service area well enough to be trusted with the work. That is a different register from an academic paper. Every claim needs a source and a number, hedging reads as weakness rather than as scholarly caution, and anything you assert without evidence will be read as something you did not check. Write it as a case rather than as a description, and remember that the outline is establishing the premise on which everything else in the proposal rests. Assume the reader is comparing your document against several others and has limited time. Reviewers reward documents that are easy to verify.

The document has a required logical order and skipping a step is visible. First the health status issue itself, with baseline prevalence data for your proposed locale rather than national figures. Then the demographic characteristics of the targeted population, with supporting racial and ethnic data as the brief specifies. Then the prevalence of health indicators in the geographic area, which is broader than the single issue and situates it. Then the current availability of preventive services addressing that issue in that group. Then the barriers. Then the gaps, which the brief splits into three separate kinds. Notice that services come before gaps for a reason: a gap is defined against what exists, so a document that describes gaps without first establishing current provision has asserted rather than demonstrated them. Say at the outset which order you are following so a reviewer can navigate it. The order is itself an argument.

Baseline data is the requirement that most often goes wrong and it repays care. Baseline means the level before your project starts, and it is what everything afterwards will be measured against, so specify the year, the source and the geography precisely. National prevalence in place of local prevalence is the commonest substitution and it will be spotted by anyone who knows the area. Where local data genuinely does not exist at the level you need, say so explicitly and explain what you used instead and why it is a reasonable proxy, since a stated limitation is far stronger than a silent substitution. The requirement for supporting racial and ethnic data is not decorative either; it is how a reviewer judges whether the project reaches the people carrying the burden, so present it disaggregated rather than as a single population figure. Present the figures in a small table if that makes them easier to check.

The three kinds of gap the brief names are genuinely different and collapsing them wastes the section that most distinguishes a strong document. A gap in provision means the service does not exist or does not reach far enough. A gap in knowledge means nobody knows something that would need to be known, which may be about the population, about what works locally, or about why an existing service is underused. A gap in capacity is about what providers and agencies can actually do, and the brief unpacks it into four verbs: screen, routinely assess, effectively intervene, and coordinate within a comprehensive network. Coordination is the one most often omitted and it is frequently the real problem, since services can each exist and still fail a patient who has to navigate between them unaided. Coordination gaps are the ones a funder is most often willing to pay to close.

On execution, the brief supplies a suggested structure beginning with Health Status and Community Description, so follow it and use headings that a reviewer can navigate rather than continuous prose. Three to five pages is tight for this much content, which means the writing has to be dense with specifics and free of general statements about the importance of prevention. Barriers should be concrete and local, meaning transport, clinic hours, language, cost, documentation requirements and distance, not abstractions about access. Cite data sources properly, since a reviewer may check them, and prefer public health surveillance, census and agency data over secondary summaries. Finally, keep the project itself mostly out of this document: the needs assessment establishes that a need exists, and arguing for your particular solution belongs in the sections that follow. Keep the tone factual and let the numbers make the case for you.