Cross-Sector Partnerships and Stakeholder Engagement

Quick Answer: Cross-sector partnerships unite public health with non-health sectors—education, housing, transportation, criminal justice, agriculture, and labor—because the social determinants of health are largely shaped outside clinics and health departments. Stakeholder engagement identifies who matters, maps their influence and interest, and brings them into planning, implementation, and evaluation at the intensity each phase requires.

Why Cross-Sector Partnerships Matter

Health outcomes are driven an estimated 80% by non-clinical factors: housing quality, school environments, transportation access, food availability, income, and neighborhood safety. No single health department can move those levers alone. The NBPHE task "identify opportunities to partner across sectors and related disciplines" asks candidates to recognize where the authority, data, or resources to change a determinant actually live. A housing authority controls lead remediation code; a school district controls nutrition standards and health education; a transit agency controls walkability and commute exposure; a criminal justice agency shapes overdose response and reentry health. Public health's contribution is often epidemiologic data, evidence-based interventions, and evaluation capacity, while the partner sector contributes the implementation channel and regulatory authority.

Health in All Policies (HiAP) is the flagship cross-sector framework tested on the CPH. HiAP is a collaborative approach that integrates health considerations into policymaking across all sectors, using structured health-impact appraisal of non-health decisions. It is not a single program but a governance stance: every policy decision is screened for health co-benefits and harms. The CDC and NACCHO endorse HiAP as the standard mechanism for systematic intersectoral action. A HiAP partnership typically includes a cross-agency steering committee, a health-impact screening checklist applied to proposed policies, and joint work plans that name each agency's contribution. A health department implementing HiAP with a transportation department might co-develop street design standards that prioritize pedestrian safety and air quality, rather than merely commenting on completed plans.

Stakeholder Mapping Methods

The companion task—identify and engage key stakeholders for planning, implementation, and evaluation—requires a systematic mapping step before outreach. Two frameworks dominate CPH items.

The power-interest grid plots stakeholders on two axes: their influence over the issue (high or low power) and their concern about it (high or low interest). The four quadrants dictate engagement intensity: high-power/high-interest stakeholders are manage closely (co-design partners); high-power/low-interest are keep satisfied (briefed so they do not block); low-power/high-interest are keep informed (their support builds legitimacy); low-power/low-interest are monitor (lightest touch). The grid is fast, transparent, and the most commonly tested mapping tool. It should be revisited at each phase transition because power and interest shift as a program matures and as political conditions change.

Mitchell's salience model adds a third dimension. A stakeholder's salience rises with the number of attributes they hold: power (ability to impose will), legitimacy (properness of involvement), and urgency (time-criticality of their claim). Stakeholders with all three are "definitive" and demand immediate engagement; those with two are "expectant" and should be actively managed; those with one are "latent" and warrant monitoring. Salience is more nuanced than the grid but slower to apply—use it for complex, contested issues where legitimacy disputes are real.

Phase-Specific Engagement

Stakeholder roles shift across the program cycle. Planning demands the widest net: affected residents, frontline service providers, sector partners, and critics of the status quo all belong at the table so the needs assessment reflects lived reality and the intervention design is feasible across sectors. Implementation narrows to operational gatekeepers—the people who sign off on staffing, budgets, referrals, and data sharing. A resident advocate who shaped the plan may not run the program, but should still receive progress briefings. Evaluation needs data holders (who can release claims or surveillance records), methodologists, and the affected community itself, because community-validated findings are more credible and more likely to be acted on.

A common exam trap is assuming the highest-power stakeholder should always be placed in the "collaborate" quadrant. Engagement intensity is task-dependent: a powerful hospital CEO may only need to be "consulted" for a school-based intervention, while a community-based organization with modest power but high interest may be a true co-implementation partner. Another trap is conflating sector partners (institutional actors with regulatory authority) with community members (individuals with lived experience). Both matter, but they are distinct stakeholder categories that map to different engagement strategies. Sector partners are engaged through formal MOUs and data-sharing agreements; community members are engaged through trust-building, flexible meeting times, childcare, stipends, and shared decision-making power. A third trap is treating the stakeholder map as static—the map should be updated at each phase transition because who holds urgency and who holds implementation authority are not the same at month one and month twelve.