How do I write good practicum activity descriptions?

Most weak activity descriptions have the same problem: they say where you were, not what you did. "Attended meeting" or "worked on data" tells a reviewer almost nothing. A simple three-part formula fixes that.

Action, context, competency

• Action: What did you actually do? Name your role. Did you facilitate, take notes, draft, analyze, present, or observe?
• Context: Why did it matter for public health? Name the population, program, or problem.
• Competency: What skill did it demonstrate or develop? Tie it to one of your selected competencies or learning objectives.

Compare "Attended coalition meeting" with: "Took minutes and summarized action items at the county tobacco prevention coalition meeting, where partners set priorities for youth vaping outreach. Practiced communicating with community partners and learned how coalitions negotiate shared goals." The second version could only have been written by someone who was there.

Adjust for the type of activity

• Meetings: your role, the purpose, and what you contributed or learned
• Independent work: the task, your approach, and what you produced
• Learning conversations: the topic, the key insight, and how you will apply it
• Observations: what you learned about practice, organizations, or community needs

Keep it sustainable

Two to four sentences per activity is enough. For tasks that repeat weekly, a template is fine, but change the details each time: new topics, new contributions, or growing responsibility. Identical entries week after week look copied, and they hide the progression reviewers want to see.

Routine tasks count too. Answering calls at a clinic can show client communication; filing reports can show data management. If you are staring at a blank entry, these strategies for activity description writer's block can help you get started.