How do I map practicum activities to competencies?

Mapping is easiest when it happens as you work, not at the end of the semester. If every log entry already names the competency it supports, your final mapping becomes an exercise in selecting your best examples rather than hunting for any examples at all.

Tag as you go

When you log an activity, note which of your selected competencies it relates to. Not every entry needs one; meetings and admin tasks may not map to anything. Over a few weeks you will see which competencies are well covered and which are thin, while there is still time to ask your preceptor for work that fills the gap.

What makes a mapping credible

A competency label attached to a task is not evidence. A strong mapping connects:

• The specific activity: what you did, for whom, and with what tools or methods
• Your role: what you personally contributed, especially on team projects
• The result: a deliverable, a decision it informed, or what you learned
• The link: why this activity shows the competency, in your own words

A useful test: could this description only have been written by someone who did the work? If it could apply to any student at any site, add specifics. Writing authentic competency evidence has more examples.

One activity, several competencies

Real public health work often uses several skills at once. You can use one project for more than one competency if you write a distinct narrative for each, focused on a different aspect. A community assessment might show data analysis in one narrative and communicating findings to partners in another.

Quality over quantity

One well-documented example usually beats several shallow ones. Save work products as you create them, where your site allows, and check your program handbook for how much evidence each competency needs.