---
name: competency-based-education-design
description: Use when asked to design a curriculum structured around demonstrated mastery of defined competencies rather than seat time or fixed pacing, as distinct from [[curriculum-design]], whose general sequence-and-pacing model assumes a fixed calendar that this is a specific alternative structural approach to.
---

# Competency-Based Education Design

Competency-based education design structures a curriculum around
demonstrated mastery of explicitly defined competencies, where students
advance to the next competency upon proof of mastery rather than after
a fixed number of weeks or a fixed calendar date. It's a specific
alternative to the pacing model [[curriculum-design]] generally assumes
— that model still applies to sequencing and dependencies between
competencies, but the pacing axis is replaced: time becomes the
variable, and mastery becomes the fixed requirement.

## Key components

- **Competency definitions** — precise, demonstrable statements of what
  a student must be able to do to be considered proficient, specific
  enough that mastery can be judged consistently — see
  [[smart-criteria]] for writing them measurably rather than
  aspirationally.
- **Mastery threshold** — the specific bar a student must clear to be
  considered proficient in a competency, set before any student
  attempts it, not adjusted after seeing results.
- **Assessment for advancement** — a way to demonstrate mastery that a
  student can attempt when ready, potentially more than once, rather
  than a single scheduled test everyone takes on the same day.
- **Pathway and sequencing** — which competencies depend on which
  others, so a student can be allowed to move at their own pace within
  a structure that still enforces real prerequisites.
- **Pacing supports** — structures for students moving faster or slower
  than average (acceleration paths, additional instructional time,
  reteaching cycles) so self-paced advancement doesn't just leave
  slower students permanently behind an entire cohort.

## The logistics problem pacing models don't have

The part of competency-based design that a fixed-calendar curriculum
never has to solve is what to do with a room full of students who are
each at a different competency at the same time. A traditional
course can plan one lesson for one day because everyone is assumed to
be in the same place in the sequence; a competency-based course has to
plan for simultaneous instruction, practice, and assessment across
several different competencies in the same room, which changes what a
"lesson plan" even looks like — often shifting toward stations,
independent or small-group work with the teacher circulating, and
on-demand reassessment rather than a single whole-class activity.

This logistics problem is also why competency-based design fails when
it's adopted only as a grading philosophy — declaring that grades now
reflect mastery, while instruction continues to run on a fixed weekly
schedule — without redesigning how instructional time actually gets
allocated to support students at different points simultaneously. The
structural commitment (multiple competencies running in the room at
once, reassessment available on demand) is what makes the model work;
without it, "competency-based" describes only how the report card is
computed, not how learning actually happens.

## Common pitfalls

- **Vague competency definitions** — statements too broad to judge
  mastery against consistently, which reintroduces the grader
  inconsistency the model is supposed to eliminate.
- **Adopted as grading policy only** — changing how grades are computed
  without redesigning instructional time to actually support students
  progressing at different rates.
- **No reassessment path** — treating the mastery check as a
  single-attempt event defeats the purpose of a model built around
  demonstrating mastery when ready, not on a fixed date.
- **Sequencing that ignores real dependencies** — allowing students to
  attempt a competency before its actual prerequisites are mastered,
  because the pathway wasn't checked for dependency order.
- **No support for students moving slower than average** — a model that
  works well for advancing quickly but has no structured reteaching or
  additional time for students who need more of it just relocates the
  original pacing problem rather than solving it.

## Learn more

- [[curriculum-design]] for the sequencing and dependency logic this
  model still relies on, with pacing replaced by mastery.
- [[rubric-design]] for building a mastery-threshold scoring instrument
  precise enough to judge consistently.
- [[unit-plan]] for how a single competency's instruction and practice
  gets structured within this model.