Home › Course Management
Course updating, maintenance & retained value
Building a Course Is a Project.
Keeping It Is the Whole Job.
A course is built once and maintained for as long as it is taught, and its record is held after it is retired. Institutions budget carefully for the first and often not for the second, which is why currency work arrives as an emergency, gets absorbed out of hide, and so often shows up on no line item. This page is about that work: what sets it off, what it costs today, what CMP does with it, and what your courses are worth once they stop decaying quietly.
The premise
Your Courses Are Depreciating Right Now.
A course does not fail on a particular Tuesday. It drifts. The standard it was written against is revised, the text it was built around goes out of print, the practice it teaches moves on, and each of those is small enough to survive on its own. Together, over a few years, they are the difference between an asset and a liability that still enrolls students.
Schematic, with no scale on either axis and no measurement behind it. The shape is the argument, not the slope: maintenance is not a cost you avoid by skipping it, it is a cost you defer at interest. The institution pays either in scheduled review hours or in licensure pass rates, employer confidence, monitoring reports, and eventually a rebuild.
What sets it off
Little About This Is Unpredictable. It Is Mostly Unowned.
Each of these is known in advance, arrives regularly, and touches more than one course. What makes currency work feel like an emergency is not that the triggers are surprising. It is that few people own the space between reviews.
A standard or requirement is revised
TodaySomeone forwards an email. Whoever notices decides what it touches, usually from memory.
In CMPRequirements are held once and inherited.
A textbook or material changes
TodayThe course was built around the old text. It is treated as a rebuild because few can see what was actually load-bearing.
In CMPYour faculty revise the course against its outcomes, and the earlier version stays on the record.
The field moves and the course does not
TodayDiscovered by a student, an employer, or a transfer partner. Usually after the damage.
In CMPReview dates are on the record, so drift becomes a scheduled question rather than an incident.
Term length or module count changes
TodayFifteen weeks becomes eight, sixteen modules become twelve, and outcome coverage is preserved by hope.
In CMPYour faculty reshape the modules against the outcomes, and the earlier version stays on the record.
A modality is added
TodayA parallel copy is made for online, and from that day the two versions drift apart.
In CMPOne master, deployed to the modalities you offer, with no parallel copy to keep in step.
An accreditor issues a finding
TodayA remediation project, staffed out of hide, on someone else's deadline.
In CMPThe evidence is already on the record, kept as the work happened.
The author leaves
TodayWhat the course was built against leaves with them. The next revision starts with archaeology.
In CMPAuthorship, sources, and design intent are on the record. The work survives the person.
The LMS changes
TodayA rebuild billed as a migration, and the institution pays twice for content it already owns.
In CMPA redeploy from the record you already hold, and the version deployed is the version that was approved.
Note the pattern in the left column: in these cases the institution finds out from a person rather than from a system, and the cost of finding out late is carried by whoever happened to be standing there. That is not a discipline problem. It is a missing record.
The update loop
When Something Changes, Your Experts Decide.
This is what an update looks like once a review date comes due. It repeats for as long as the course is taught.
A review comes due
The report shows which courses are coming due for review, so the question is scheduled rather than discovered.
Your people revise
Faculty and instructional designers revise the course in CMP, and the earlier version stays on the record.
Your reviewer decides
The designated reviewer edits, rejects, or approves, and the decision carries a name and a date.
It redeploys
To your LMS by the path it supports. The version that is live is the version that was approved.
The judgment stays with your people. CMP records the decision. It does not make it for your faculty. If no change is needed, that answer goes on the record too, with a name and a date.
CMP holds the design and governance record. Delivery, grades, and student records stay in your LMS and SIS.
The value argument
The Cost the Institution Has Rarely Been Asked to Size.
Ask any institution what a course costs to build and someone will produce a figure. Ask what the courses cost to keep and the room goes quiet, because the work is real, recurring, and distributed across so many people's evenings that it has rarely been added up. It is not a hard sum. It is an unowned one, and these are the four things it turns on.
Driver 01
The number of courses
The courses you are responsible for keeping current, not only the academic ones. Compliance, onboarding, and professional development content ages on the same clock.
Driver 02
The review window in your policy
How often policy says each course should be looked at. A shorter window commits the institution to more work each year, whether or not that work is staffed.
Driver 03
The effort one review honestly takes
Faculty, designer, and reviewer time combined, including the reconstruction that has to happen before the review can start.
Driver 04
What that time is worth
Fully loaded. This is the driver that turns an academic obligation into a financial one, and it is the reason the total surprises people.
These four do not add. They multiply. Which is why the total often differs from what anyone expects when they estimate it a driver at a time, and why few at the institution have volunteered the figure: it is not that the arithmetic is hard, it is that the question has no clear owner.
Before and after
The Institution Stops Discovering Drift and Starts Scheduling It.
Maintenance without a record
- Drift is found by a person, usually a student, an employer, or an auditor
- The work is unbudgeted and absorbed out of hide under someone else's deadline
- Prior versions are overwritten, so what was taught when cannot be reconstructed
- Compliance and onboarding content is maintained three separate times
- Currency is asserted in the self-study and defended in the visit
- The condition of the courses is unknown until someone commissions a project to find out
Maintenance on a record
- Review dates are on the record, so drift becomes a scheduled question
- The work is forecastable, so it appears in a plan rather than in an emergency
- Versions are kept, so what was taught when is a lookup, not an excavation
- All content types are kept in one place, on one review cycle
- Currency is reported: the share of courses inside their own review window
- The condition of the courses is visible in one report
Scheduled
Currency work moves from crisis response to a forecastable operating line.
Visible
Review dates for your courses are in one report.
Attributable
Each re-version carries its trigger, its author, its reviewer, and its date.
Your call
Approval stays with the people your institution designates.
Who feels it
Maintenance Is Paid for in One Budget and Felt in Six.
Provost · CAO
Currency becomes reportable
The share of courses reviewed inside their own review window, course by course, on demand. It stops being a claim that has to be defended and becomes a number that can be managed.
Foundation: currency
Deans · Faculty · Designers
The reconstruction shrinks, the judgment stays
Less reconstructing what a course was built against, and less rebuilding a course because the textbook changed. What remains is the part that needed a person.
Foundation: institutional capacity
CFO · CBO
A recurring cost becomes visible and then forecastable
The maintenance obligation can be stated, attributed by institutional area, and planned against, instead of surfacing as overtime, stipends, and emergency vendor contracts.
Foundation: hard costs
Accreditation · IE
Evidence of review, not evidence of intent
Dated, versioned proof that each course was reviewed, by whom, against what, and what changed. Accumulated as the work happened rather than assembled the semester before a visit.
Foundation: risk mitigation
Board of Trustees
Condition of the asset, in writing
What we own, when it was last reviewed, when it is next due, and what our exposure is if that date passes. The same questions the board already asks about the other assets it governs.
Foundation: risk mitigation
Next step
Bring Us the Course You Suspect Has Drifted.
A working session on a real course of yours. We work on it as it stands, review it against the outcomes and requirements you supply, and show you what the record and the reports look like on your own material. If it turns out the course is fine, that is a useful answer too.