A Programme Learning Objective is not a permanent declaration. It is a working contract between the institution and the world it sends graduates into — and the world keeps moving.
When BoS minutes from five years ago and BoS minutes from this year recommend the same revisions, the question is no longer the recommendation. The question is the loop that was supposed to close it.
Most institutions have a loop on paper: the BoS recommends, the curriculum committee acts, the faculty revise, the outcomes are reassessed. The paper loop is closed. The institutional loop — the one that changes what a student actually encounters in Week 7 — is not.
The gap between the two is not laziness. It is architecture. The loop fails because it was designed for compliance, not for learning. Its feedback signal is a committee recommendation, not a learning outcome measurement. Its trigger is the academic calendar, not evidence of drift.
What to look for. Pull your PLO documentation from three years ago. Read it alongside the current version. If the language is nearly identical, you have a question to answer — not about the PLOs, but about the feedback mechanism that was supposed to update them.
What to do. Assign a Course Anchor to each PLO. That person’s job is not to write the PLO. It is to produce, once per cycle, a one-page evidence note: what changed in industry or society that is relevant to this objective, and whether the objective still holds. The BoS then reads evidence, not opinions.
The loop closes when someone is accountable for the evidence, not just the recommendation.