The Adjunct Handoff: Teaching a Course You Didn’t Design

It happens every August and every January, in every department: an adjunct — hired three weeks ago, sometimes three days ago — receives a course they didn't design. What they actually receive is an LMS export and a syllabus. The export is the furniture: readings, quizzes, assignment shells, a gradebook schema. The syllabus is the lease: policies, dates, percentages. What's missing is the floor plan — every reason behind every choice. Why is the third paper weighted at 30%? What is the group project actually for? Which reading is loadbearing and which is a leftover from 2019 that nobody dared delete? The person who knew is on sabbatical, or retired, or was themselves an adjunct whose contract ended in May.

So the inheriting instructor does what anyone would do: they teach the artifacts. They administer the quizzes, collect the papers, apply the weights — execution without intent. And when a live decision arrives mid-term, as it always does — a student contests a rubric line, a week runs long, an assignment obviously isn't working — they have no design rationale to reason from. They guess. Multiply by four adjuncts and six semesters and you get the quiet phenomenon departments rarely name: a course that drifts a little every handoff until it no longer teaches what the catalog promises — and no one decided any of it.

The packet is the design made portable

The fix is a handoff packet, and the reason it works is that it's not extra documentation — it's the backward design of the course, written down where it can travel. If the course was ever designed deliberately — outcomes first, evidence second, activities third — the packet is simply those three stages made explicit for the next pair of hands. Six parts:

• The outcomes, with intent. Not the catalog boilerplate — a paragraph per outcome saying what it actually means here and what a student who has it can do. This is the part that lets an instructor improvise safely: change activities freely, as long as they still aim at this.
• The assessment plan, with its reasoning. Which assignments measure which outcomes, and why the weights sit where they sit. “The third paper is 30% because it's the only place outcome four gets measured” is one sentence — and it's the sentence that stops the new instructor from casually replacing that paper with a quiz.
• The rubrics, with one scored sample each. A rubric alone still leaves calibration to chance; a single annotated example of real (anonymized) student work at each band is the cheapest inter-rater reliability a department will ever buy.
• The week-zero map. One page: the arc of the term, where the workload spikes, what has to happen by week five for week ten to work.
• The known failure points. The most valuable and least documented part: students always misread this prompt; this week runs long; this reading needs framing or they revolt. The designer knows these cold. The packet is the only place that knowledge survives them.
• The drift log. A dated list of what's been changed and why — which is also where the inheriting instructor writes back, because a handoff is a relay, not a delivery.

What the inheriting instructor owes the packet

The packet buys the adjunct something real — the difference between excavating a course and teaching one — and it asks something in return: teach the design before renovating it, log what you change, and flag what didn't survive contact with your section. An adjunct who notes “the week-six debate died with twelve students; worked as a written forum” has contributed more to the course's future than most curriculum meetings do. Drift isn't the enemy — undocumented drift is. The log converts it from erosion into iteration.

The department's stake

For a chair, the packet is continuity insurance priced at a few hours of the designer's time — almost always cheaper than one semester of a course taught blind. It's also, not incidentally, the evidence an accreditor asks for: outcomes mapped to assessments, rationale on record, a paper trail showing the course as delivered matches the course as promised. Departments tend to reconstruct all of this frantically before a review, from memory, in a summer. The handoff packet is the same artifact, built when it's cheap, kept alive by use. And the alignment work at its center — which assessment measures which outcome, where the gaps are — is exactly the grid a curriculum map maintains at the program level.

The bottom line

An LMS export tells the next instructor what the course contains; only the packet tells them what the course is for. Outcomes with intent, the assessment plan with its reasoning, calibrated rubrics, the term's map, the failure points the designer already paid to learn, and a drift log that turns every handoff into iteration instead of erosion. Courses will keep changing hands every August — that's the adjunct economy we actually have. The only choice is whether each handoff loses the design or compounds it.

TeachingsByDesign keeps the packet from being a heroic one-time document — outcomes, assessment maps, and rubrics live as structured, linked objects that export clean for the next instructor, with the coverage grid always current. See how it works.