All frameworks and cheat sheets

Process

Evaluating a module disrupted by strike action

Five steps for running and reporting course evaluation after a disrupted term

Process diagram with five steps for evaluating a module disrupted by strikes, from flagging it early to acting on what students lost.
Flag the term, ask about the disruption directly, and keep the results apart from staff reviews

A five-step process for quality teams evaluating a module that lost teaching or marking to industrial action or other major disruption. It keeps the standard questions for comparability, adds questions about missed content and catch-up, reports flagged results separately from trends and staff reviews, and closes the loop with students. Koji can add the open disruption questions as short AI-led interviews with thematic analysis.

What's in this process

  1. Flag the module before results arrive: Record which weeks, sessions and assessments were affected, while the facts are fresh.
  2. Keep the standard questions: Ask the usual items so results stay comparable, and mark the term as disrupted.
  3. Ask about the disruption itself: Missed content, whether catch-up helped, and how delayed marks affected next steps.
  4. Report flagged results separately: Keep them out of trend charts and staff reviews, or show them with the disruption named.
  5. Act on what students lost: Tell the next module what was missed, and tell students what changed.

Use this image

Free to use in your docs, decks and posts under CC BY 4.0, as long as you credit Koji with a link to this page. To embed it, paste this into your page:

html
<a href="https://www.koji.so/visuals/evaluating-strike-disrupted-module-process"><img src="https://www.koji.so/visuals/evaluating-strike-disrupted-module-process/evaluating-strike-disrupted-module-process.png" alt="Process diagram with five steps for evaluating a module disrupted by strikes, from flagging it early to acting on what students lost." width="1200" height="792" /></a>
<p>Source: <a href="https://www.koji.so/visuals/evaluating-strike-disrupted-module-process">Evaluating a module disrupted by strike action</a>, Koji</p>