Every ODL programme that misses its cohort start date misses it for the same reason. Three workstreams that are independent of each other, regulatory paperwork, content production and platform configuration, were run in series instead of in parallel. By the time the first finishes, the second is starting cold and the third is being asked to compress eight weeks into two.
The three workstreams, and their real dependencies
- Regulatory paperwork. Depends on programme design, not on content or LMS.
- Content production (SLM, video, question banks). Depends on syllabus and outcomes, not on approvals.
- Platform configuration (LMS, CRM, ERP, examinations). Depends on roles, programmes and reporting needs, not on content or approvals.
The bottleneck is therefore always Step Zero: locking the programme design and outcomes. Once that is done, three teams can run in parallel for ten to twelve weeks without blocking each other.
What the parallel calendar actually looks like
- Weeks 1 to 2: Programme design and outcomes locked, success criteria signed off.
- Weeks 2 to 10: Regulatory paperwork drafted and submitted; reviewer queries handled.
- Weeks 2 to 12: SLM, video and question banks produced unit by unit, with ongoing faculty sign-off.
- Weeks 2 to 10: LMS, CRM and ERP configured; integrations and dry runs completed.
- Weeks 10 to 12: User-acceptance, internal mock cohort, faculty and registrar training.
- Week 13: Cohort go-live with a defined support runbook.
Where Yatharth fits
Our University Operations Support engagement is built around exactly this playbook. One delivery lead owns the parallel calendar, escalates blocked workstreams early and keeps the cohort start date as the single non-negotiable. If you have a 2026 cohort that has to start on time, write to info@yatharthedu.com.