Explain complex public health practitioner matters to populations, communities and partner organisations in plain, honest language.
TRIGGERS - Use when a public health practitioner needs a client explanation & communication guide for populations, communities and partner organisations in public health departments and community settings.
Installs into .claude/skills of the current project.
Sponsors
SSkills DirectorySkills Directory
Is that skill safe to install?
SSkills DirectorySkills Directory
Know which skills are safe — weekly.
Are you the author of Public Health Client Explanation?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/lionelsimai-public-health-client-explanation)
---
name: public-health-client-explanation
description: |
Explain complex public health practitioner matters to populations, communities and partner organisations in plain, honest language.
TRIGGERS - Use when a public health practitioner needs a client explanation & communication guide for populations, communities and partner organisations in public health departments and community settings.
category: Public Health
license: MIT
version: 1.0
---
# Client Explanation & Communication Guide — Public Health
Explain complex public health practitioner matters to populations, communities and partner organisations in plain, honest language. The deliverable is a communication pack: explanation script, FAQs and a written summary.
This skill is written for a public health practitioner working with populations, communities and partner organisations in public health departments and community settings.
## When to use
- You are a public health practitioner preparing, delivering or reviewing this part of your work in public health departments and community settings.
- You need a defensible, repeatable approach that produces a communication pack: explanation script, FAQs and a written summary.
- A colleague, auditor or client asks how this was done and what evidence supports it.
## Key Concepts
| Term | Meaning |
|------|---------|
| Surveillance | ongoing collection and analysis of health data |
| Incidence | the rate of new cases of a condition |
| Intervention | an action intended to improve population health |
## Workflow
1. **Step 1** - Identify what populations, communities and partner organisations actually need to decide or understand, and the misconceptions to clear up first
2. **Step 2** - Translate the technical content — including terms behind needs assessments — into plain language without losing accuracy
3. **Step 3** - Structure the explanation: what we found, what it means, the options, the recommendation and the risks such as health inequalities widened
4. **Step 4** - Check understanding by asking populations, communities and partner organisations to play it back in their own words; correct gaps kindly
5. **Step 5** - Follow up with a written summary the same day and record the conversation in the file
## Profession-Specific Components
| Component | Details for Public Health |
|-----------|-------------------------------|
| Core documentation | needs assessments; programme plans; surveillance reports; evaluation reports |
| Core tools & equipment | surveillance databases; mapping software; survey tools; communication platforms |
| People involved | populations, communities and partner organisations; the public health practitioner; colleagues and other services in public health departments and community settings |
| Primary record | needs assessments — keep it current, dated and attributable |
## Output Format
**Context:** [Situation in public health departments and community settings] | **Objective:** [What this must achieve] | **Audience:** [populations, communities and partner organisations and other stakeholders]
The finished output is a communication pack: explanation script, FAQs and a written summary, structured as:
1. Summary of position and evidence
2. Detail, following the workflow above
3. Decisions, actions, owners and dates
4. Review point and escalation route
### Action Plan
1. **Immediate:** Confirm scope, consent and the evidence available in needs assessments.
2. **Short-term:** Complete the workflow steps and record outcomes against programme coverage.
3. **Medium-term:** Review results, close actions, and update local procedures in public health departments and community settings.
## Success Metrics
| Metric | Target | Method |
|--------|--------|--------|
| programme coverage | Agree a local target and track the trend | Measured from needs assessments and reviewed on a set cycle |
| screening uptake | Agree a local target and track the trend | Measured from needs assessments and reviewed on a set cycle |
| outbreak response times | Agree a local target and track the trend | Measured from needs assessments and reviewed on a set cycle |
| evaluation completion | Agree a local target and track the trend | Measured from needs assessments and reviewed on a set cycle |
## Guardrails & Quality Checks
- Never let this happen: health inequalities widened.
- Never let this happen: outbreak signals missed.
- Never let this happen: misinformation unaddressed.
- Work only within the competence and authority of a public health practitioner; escalate or refer anything beyond it.
- Record facts and observations, not speculation, and keep records confidential to public health departments and community settings's rules.
- Verify names, dates, figures and measurements twice before anything is issued or signed off.
- Use only real, verified information from the case in hand — never invent results, credentials or evidence.
## Example (illustrative)
A public health practitioner in public health departments and community settings applies this workflow for populations, communities and partner organisations: they open
needs assessments, work through the five steps using surveillance databases, and close by recording
the outcome against programme coverage and agreeing the next review date. (Illustrative example only —
replace with the real details of the case in hand.)