Course content decays: prices drift, tools change, regulations move, examples go stale. This doc sets the schedule that keeps it current — quarterly content updates, one major annual overhaul, and continuous feedback triage — plus the timestamping rule that makes staleness visible.
Last reviewed: 2026-07.
The cadence at a glance
- Quarterly — plan and ship new content, plus a minor patch release (errata, refreshed examples, small mission improvements).
- Annually — a full curriculum review followed by a major relaunch.
- Continuously — community feedback and error reports are collected year-round and triaged into the next release; factual errors in legal/finance content are fixed immediately, out-of-band.
Schedule diagram
The PRD's example schedule (a Mermaid Gantt chart — shown here as source; see the table below for the same information):
gantt
title Content Review & Update Schedule
dateFormat YYYY-MM-DD
section Quarterly Updates
Plan New Content :q1, 2024-01-01, 30d
Release Patch (minor) :after q1, 14d
section Annual Review
Full Curriculum Review:2024-07-01, 21d
Major Relaunch :2024-09-01, 14d
section Continuous
Community Feedback :2024-01-01, 365d
Same schedule as a table
Dates below use the PRD's example year; in practice the pattern repeats every year, offset to our launch date. Outputs per workstream: planning yields the prioritized list of new missions and simulator cases; the patch ships errata fixes and the quarter's new content; the curriculum review audits every category against the ontology, competitor landscape, and learner analytics; the relaunch implements the review's findings; community feedback keeps a standing triage queue feeding both cycles.
| Workstream | Section | Example start | Duration | Repeats |
|-----------------------|-------------------|---------------|----------|-------------|
| Plan New Content | Quarterly Updates | Jan 1 | 30 days | Every quarter |
| Release Patch (minor) | Quarterly Updates | after planning| 14 days | Every quarter |
| Full Curriculum Review| Annual Review | Jul 1 | 21 days | Yearly |
| Major Relaunch | Annual Review | Sep 1 | 14 days | Yearly |
| Community Feedback | Continuous | Jan 1 | 365 days | Always on |
What each cycle covers
Quarterly patch
- Fix all triaged errata and learner-reported errors.
- Refresh time-sensitive facts: pricing benchmarks, tool names, market figures, anything flagged time-sensitive at authoring time.
- Ship the quarter's planned new content (new missions, simulator variants, calculator improvements).
- Re-run
pnpm verify— every formula and content file must still validate.
Annual review
- Audit the full curriculum against the concept ontology: are all concepts still covered, correctly related, and sequenced sensibly?
- Re-run the competitor scan and pedagogy review from the Research Appendix; fold findings into the relaunch plan.
- Retire or rewrite the weakest content, judged by mission completion and quiz-accuracy analytics.
- Re-verify every learner-facing citation still resolves and still says what we claim (per the Content Governance Policy).
Continuous triage
- Community flags, tutor-conversation spot checks, and support reports land in one queue.
- Each item is classified: factual error in legal/finance content (fix now), other factual error (next patch), quality/clarity (next patch or annual review), idea (quarterly planning input).
Timestamping rule
All content is timestamped. Concretely:
- Every doc and content file carries a last reviewed date, updated whenever a human reviews it (not merely when a typo is fixed).
- Learner-facing pages surface the timestamp so learners can judge freshness themselves.
- Any fact likely to drift (prices, rates, named tools, regulations) is flagged at authoring time; flagged items are the first checklist in every quarterly patch.
- A file whose last-reviewed date is older than one year is overdue by definition and goes to the top of the next review queue.