Planning: From Needs Assessment to Blueprint
What this domain tests
Planning converts evidence and stakeholder priorities into a feasible design. Candidates should be able to conduct and interpret a needs assessment (surveys, focus groups, administrative data, key-informant interviews), separate documented need from expressed demand, and set priorities using explicit criteria-magnitude, severity, feasibility, cost, equity, and community readiness.
Know the logic model chain: inputs → activities → outputs → short-term outcomes → intermediate outcomes → long-term impact. Most errors occur at the output/outcome boundary: a training session delivered is an output; changed staff practice is an outcome.
Objectives must be SMART-specific, measurable, achievable, relevant, time-bound-and must state who, what, how much, and by when. Distinguish a goal (broad aspiration) from an objective (measurable commitment), and a process objective (what we will do) from an outcome objective (what will change). Tie each objective to a mechanism or theory, such as social cognitive theory or the stages-of-change model, so activities are justified rather than habitual.
Also plan stakeholder roles, timeline, budget with realistic unit costs, and sustainability from the outset. Cultural adaptation should be planned, documented, and reviewed with community partners rather than improvised.
Traps
Look for objectives using vague verbs ("understand," "be aware of") with no measure; plans listing activities with no outcome; budgets missing indirect or in-kind costs; and sustainability answers resting on a single grant renewal.
Rule of thumb
If you cannot write the data source next to an objective, rewrite the objective.
Worked example
"Reduce waiting time" fails SMART. Better: "By June 30, reduce median intake-to-first-appointment time from 21 to 10 days, measured monthly from scheduling-system records."