Mapping Competencies to Program Learning Outcomes Without Fudging It

Mapping competencies to program learning outcomes is defensible only when the table reflects the real relationship between the two. If a competency is only addressed in one assignment, or is introduced in a course but not assessed until later, mark it that way. A partial mapping is not a weakness. It shows the program understands the evidence it has, the evidence it does not have, and where additional assessment is needed.

Start with the smallest honest unit of evidence

A curriculum map becomes unreliable when it treats every course as if it teaches every outcome equally. The safer approach is to map only what can be supported by a syllabus, rubric, assignment prompt, or clinical experience. If an outcome appears in discussion but is not assessed, that is not the same as an outcome that is evaluated with a score.

For competency mapping, use a simple distinction:

• Introduced: students encounter the concept or skill
• Developed: students practice it with guidance and feedback
• Assessed: students are evaluated on it using a criterion-based measure

This gives reviewers a clearer picture than an all-or-nothing table. It also prevents the common problem of claiming that a program “covers” a competency because it mentions it in multiple courses, even though no assignment actually measures student performance.

Build the table from assignments, not from aspiration

A strong mapping table starts with actual program artifacts. Review course learning outcomes, major assignments, rubric criteria, internship or practicum expectations, and any direct assessment instruments. Then ask a narrow question for each cell in the table: does this assignment produce evidence for this competency, and if so, what kind of evidence?

A useful table often has columns like these:

• Program learning outcome
• Related competency
• Course or experience
• Evidence type, such as introduced, developed, assessed, or not addressed
• Source of evidence, such as rubric criterion or supervisor rating
• Notes on limitations

The last column matters. If a capstone project assesses written communication but only in a team report, say so. If the employer feedback is based on a single internship site with inconsistent supervision, note that too. Accreditation reviewers are usually more comfortable with a table that names limitations than one that looks tidy but overclaims.

Why partial mapping is stronger than forced equivalence

A partial mapping says, in effect, “This program contributes to the competency, but not all parts of the competency are measured here.” That is often the correct answer. Many competencies are broader than any one course or assignment can capture.

Take critical thinking. A program may assess it in a senior research project, but only infer it in earlier labs or case studies. Marking the early courses as partial avoids pretending that a quiz on terminology is the same as an evaluated argument or decision-making task. The mapping is stronger because it preserves the distinction between exposure and assessment.

This matters for two reasons. First, it makes the table credible to external reviewers who know the difference between content coverage and student performance. Second, it helps the program identify gaps. If a competency is only assessed once, the table shows concentration risk. One assignment can fail, one supervisor can be lenient, or one faculty member can score differently from the rest. A partial map makes that vulnerability visible.

Use a rubric language that matches the competency language

Misalignment often starts with wording. A program outcome might say “communicate effectively in professional settings,” while the competency language asks for “articulate ideas clearly in writing and speaking.” Those are related, but not interchangeable unless the rubric actually measures both forms.

To avoid fuzzy mapping:

1. Break broad outcomes into observable behaviors.
2. Match each behavior to a specific rubric criterion.
3. Avoid mapping a competency to a course simply because the course is important.
4. Separate communication mode, context, and audience when relevant.

If a faculty rubric only has a global “professionalism” score, that may support a broad claim but not a precise mapping. “Professionalism” can include punctuality, dress, responsiveness, judgment, and teamwork. Without subcriteria, the table may overstate what the program can actually evidence.

Decide in advance what counts as a full, partial, or no match

The fastest way to make a defensible table is to set rules before anyone fills it in. For example:

• Full match: the assignment directly assesses the competency with a criterion tied to student performance
• Partial match: the assignment addresses part of the competency, or provides indirect evidence only
• No match: the competency is not meaningfully addressed or assessed

Write those definitions into the mapping instructions. Otherwise, different faculty members will use the same label for very different situations. One person’s “full” may mean “mentioned in class,” while another’s means “scored on a rubric.” That inconsistency weakens the final report more than any honest partial marking ever would.

Treat internships and employer ratings carefully

Work-based learning often produces strong evidence, but it is not automatically complete evidence. An internship supervisor may rate teamwork and professionalism well, yet have little visibility into writing quality, quantitative reasoning, or ethical decision-making in complex situations.

That is why the mapping should specify what the supervisor could actually observe. A 360-degree evaluation can be useful for competencies such as teamwork, communication, and professionalism, but the mapping should not claim it measures technical skill unless the rubric includes that skill and the supervisor had a chance to observe it. In the Career Readiness Report, this is one reason combining student self-assessment with supervisor and faculty feedback gives a more defensible picture than relying on a single rater.

Expect disagreement, and document how you resolve it

Faculty members will not map every outcome the same way. That is normal. The solution is not to force consensus by softening the criteria. The solution is to document the logic.

When disagreement appears, ask:

• What evidence was used?
• Was the evidence direct or indirect?
• Did the assignment measure the whole competency or only part of it?
• Was the competency demonstrated once or repeatedly?

If the program can answer those questions consistently, the table will hold up under review. If it cannot, the problem is usually not the labels, it is the underlying assessment design.

A clean table is not the goal, a truthful table is

A perfect-looking map can hide the most important information, which is often where the assessment is thin. Marking partial mappings honestly is better for accreditation, better for internal improvement, and better for students. It tells the program where it has direct evidence, where it has inference, and where it needs another assignment, another rubric criterion, or another data source.

If the map is meant to support reporting on career readiness, use a platform or process that preserves those distinctions rather than flattening them into yes-no cells. The value is not in claiming every competency everywhere. The value is in showing exactly how each competency is supported, and where it still is not.