Managing TOK and EE deadlines across overlapping Diploma Programme cohorts requires more than a shared calendar. Coordinators need one controlled system that separates IB submission dates from school milestones, assigns responsibility, and reveals delays early enough for intervention.
The most reliable model combines a two-cohort tracker, session-specific milestone templates, weekly exception reviews, and protected submission buffers. This structure helps coordinators manage a graduating DP2 cohort alongside a DP1 cohort without confusing examination sessions, assessment requirements, or guide versions.
Separate IB deadlines from school deadlines
The IB sets submission dates for schools and communicates requirements through current programme documentation and coordinator systems. Its official pages for the Extended Essay submission deadline and TOK submission deadline confirm that schools are responsible for submitting work and associated documentation on time.
Schools should set earlier internal deadlines to allow time for:
- permitted feedback and independent revision
- reflection meetings and required records
- authentication and academic integrity checks
- marking or moderation processes where applicable
- file, candidate, and upload verification
- absences, missing components, or technical problems
Students and parents should receive the school deadline as the actionable final date. Presenting the IB cut-off as extra working time removes the administrative buffer protecting the cohort.
Build one source of truth
Use one master tracker rather than separate spreadsheets maintained by TOK teachers, EE supervisors, and coordinators. Staff can use filtered views, but every view should draw from the same records.
| Field | Why it matters |
|---|---|
| Cohort and examination session | Prevents work being assigned to the wrong graduating group |
| Candidate identifier | Supports accurate submission matching |
| Component | Distinguishes the TOK exhibition, TOK essay, EE, and documentation |
| Guide or criteria version | Prevents staff applying requirements from another assessment cycle |
| Milestone and internal due date | Defines the next observable deliverable |
| Operational cut-off | Reserves time for checking and uploading |
| Responsible owner | Identifies who must take the next action |
| Evidence link | Connects the record to a draft, form, or meeting note |
| Status, risk, and next action | Makes delays visible and actionable |
Use controlled labels such as Not started, In progress, Submitted for feedback, Returned, Final received, Authenticated, and Uploaded and verified. Avoid percentage-complete fields because staff may interpret a figure such as 80% differently.
Create different milestone templates for DP1 and DP2
Both cohorts should use the same data structure, but not the same schedule. DP1 focuses on feasibility and process-building, while DP2 focuses on completion, authentication, and submission control.
DP1 milestones
A practical DP1 sequence includes EE orientation, an initial proposal, preliminary reading, and a feasibility review. Students should then receive supervisor allocation, refine a research question, establish a research plan, and complete the applicable reflection requirements.
TOK exhibition checkpoints should cover prompt selection, object selection, commentary development, final submission, marking, and moderation evidence. By the end of DP1, an EE student should have a viable investigation and documented research progress, not merely a topic idea.
DP2 milestones
Begin DP2 by requesting evidence such as a current draft, bibliography, research log, or data set. A verbal assurance that an essay is nearly complete is not an auditable checkpoint.
Track the complete EE draft, permitted supervisor feedback, revised final essay, applicable reflection or viva voce requirement, authentication, and documentation. For TOK, track the prescribed-title choice, planning interactions, complete draft, permitted feedback, final authenticated essay, exhibition records, uploads, and independent verification.
TOK prescribed titles change by examination session. The IB's TOK subject information explains that students respond to one of six prescribed titles, while the exhibition is internally assessed and externally moderated. Every TOK essay record should therefore display its session.
Manage curriculum transitions explicitly
Overlapping cohorts may follow different documentation. This matters during the Extended Essay transition because the IB identifies May 2027 as the first assessment session for the revised EE on its curriculum update page.
Do not label records simply old guide or new guide. Record the examination session and exact guide or criteria version, then attach the correct checklist, reflection workflow, subject guidance, and staff materials. Review this information before student induction, before substantive supervision, and before final checks.
Plan backwards and protect a submission buffer
Start with the verified IB deadline for the relevant session, not a date copied from another school or previous cohort. Work backwards through four distinct gates:
- Student final deadline: The declared final version is received.
- Quality-control gate: Staff check readability, required elements, citations, and documentation.
- Authentication gate: Responsible staff confirm that the work can be authenticated.
- Upload and verification gate: Files are matched to the correct candidate and checked by a second authorized person.
Where the calendar permits, place the final student deadline at least 7-10 working days before the school's upload cut-off. Increase the buffer around holidays, mock examinations, staff absences, or unusually large cohorts.
Run weekly exception reviews
Coordinators should review exceptions rather than discuss every student equally. A short weekly meeting with TOK and EE leads can focus on three risk categories:
- Green: Current milestone completed with evidence.
- Amber: Evidence is incomplete or one checkpoint has been missed.
- Red: A final-stage deadline, authentication issue, staffing dependency, or submission requirement remains unresolved.
Every amber or red record needs an owner, dated action, and review date. Predetermine escalation steps so repeated missed milestones trigger appropriate student, parent, support, or leadership involvement under school policy.
Protect authentication throughout the process
Authentication is not a final-day signature. The IB's academic integrity policy emphasizes observing work as it develops and ensuring students can explain it.
Retain dated drafts, revision histories, interaction records, source logs, and notes about substantial changes. A polished final submission without a development trail may create an authentication risk even when it is punctual. School rules for AI-assisted work should follow current IB policy and be explained before drafting begins.
Communicate one calendar through different views
Students need milestones and next actions, supervisors need assigned candidates, TOK teachers need class and moderation records, and leaders need cohort-level risks. These views should all come from the same database.
Label each date as a draft checkpoint, final school deadline, or IB administrative deadline. Publish revisions through one named channel and preserve version history. Useful supporting guidance includes RevisionDojo's IB coordinator role guide, coordinator resource guide, and EE supervision workflow.
Common coordination mistakes
Serious errors usually result from weak systems rather than low motivation. Common examples include separate trackers that disagree, missing session labels, incorrect TOK titles or EE criteria, unsupported completion claims, incompatible supervisor timelines, last-minute authentication, and deadline changes without version control.
A strong system cannot prevent every late submission. It ensures that missing work becomes visible while the school still has lawful and practical options.
Conclusion
Effective management of TOK and EE deadlines depends on one source of truth, session-specific milestones, named ownership, and protected submission buffers. DP2 requires completion and verification controls, while DP1 requires feasibility, research, and documented process checkpoints.
RevisionDojo can support academic preparation through EE Guides, the TOK resource hub, Jojo AI, and the Coursework Grader. These resources should supplement official documentation, school supervision, and student authorship rather than replace them.
Sources and referenced URLs
- IB Extended Essay submission deadline
- IB TOK submission deadline
- IB TOK subject information
- IB Extended Essay curriculum update
- IB academic integrity policy
- RevisionDojo IB coordinator role guide
- RevisionDojo coordinator resource guide
- RevisionDojo EE supervision workflow
- RevisionDojo EE Guides
- RevisionDojo TOK resource hub
- RevisionDojo Coursework Grader