How far before the IB submission date should a school set its internal TOK and EE deadlines?

The IB requires schools to meet the submission dates it communicates, but it does not prescribe one universal internal buffer for every school. Coordinators should work backwards from the current session’s official dates and allow time for authentication, documentation, file checks, absences, and technical problems. A final school deadline several weeks before upload is often safer than a last-minute cutoff, although the exact interval depends on the calendar and cohort size. Earlier developmental deadlines should cover research, reflection, drafting, feedback, and revision rather than concentrating everything near submission. The published calendar should clearly identify which dates are school deadlines and which are external IB deadlines.

Should Year 1 and Year 2 students appear in the same TOK and EE tracker?

Yes, provided the tracker supports filtered cohort views and appropriate access permissions. One system allows the coordinator to identify staff overload, room conflicts, and deadline clustering across the whole programme. Every record should include the student’s examination session, applicable guide, component, owner, status, and evidence link. Staff members can then view only the students or milestones relevant to their responsibilities. Sensitive pastoral information should be stored separately in the school’s approved confidential system.

How should a coordinator track students who are behind on the Extended Essay?

Track missed deliverables rather than subjective estimates of how much of the essay is complete. Record the last evidence produced, the reason for concern, the next required action, the responsible adult, and a review date. A student who misses one minor checkpoint may need a supervisor reminder, while repeated missed meetings may require coordinator and pastoral intervention. Red status should trigger a documented recovery plan with smaller, time-bound outputs. The student should remain responsible for the work even when the school increases monitoring and support.

Can the younger cohort begin the TOK essay before its prescribed titles are released?

Students can develop TOK essay skills before their session’s titles are available, but they should not draft the assessed essay using another session’s prescribed titles. Useful preparation includes analysing claims, evaluating examples, comparing perspectives, and responding precisely to practice questions. Once the correct titles are issued, the tracker should record title selection and verify the exact wording. This prevents work from being developed for an invalid title or examination session. The exhibition can follow a separate timeline because it uses the official exhibition prompts rather than session-specific essay titles.

What should happen when an EE supervisor repeatedly fails to update progress?

The coordinator should first clarify the reporting expectation and request the missing evidence by a specific date. If updates remain absent, the case should be escalated to the EE lead or relevant line manager because weak reporting can conceal risks to several students. The coordinator should check students directly rather than assuming that no report means satisfactory progress. If necessary, supervision responsibilities or additional support should be reassigned according to school policy. The incident should also inform future workload allocation and supervisor training.

What is the best way to prevent TOK and EE deadlines from colliding with other IB assessments?

Maintain a programme-wide assessment calendar containing major internal assessments, oral work, mock examinations, university deadlines, TOK, EE, and CAS checkpoints. Review the calendar with subject leaders before dates are published to students. Move developmental milestones where possible, while protecting non-negotiable submission and moderation requirements. Limit the number of major deliverables assigned to one cohort in the same seven-day period and monitor staff workload as well as student workload. A termly calendar review should be supplemented by a short weekly check because school events and assessment plans often change.

Back to all posts

Coordinator’s Guide to TOK and EE Deadlines

IB Coordinators Program Management IB TOK

• 6 Oct 2026•11

Coordinator’s Guide to TOK and EE Deadlines

Join 650k+ students breezing through the IBReady to breeze through the IB?

Coordinator’s Guide to TOK and EE Deadlines | RevisionDojo

Back to all posts

Coordinator’s Guide to TOK and EE Deadlines

IB Coordinators Program Management IB TOK

• 6 Oct 2026•11

Managing TOK and EE deadlines across two overlapping IB cohorts requires one programme-wide system, not separate calendars maintained by individual teachers and supervisors. The most reliable model combines a master assessment calendar, cohort-specific milestones, named owners, evidence of completion, and a weekly exception report.

The central principle is simple: coordinators should monitor deliverables and risks, not merely dates. Every deadline needs a defined submission, a responsible person, recorded evidence, and an agreed response when progress slips.

Start with the official deadline hierarchy

The IB communicates submission dates for TOK and the Extended Essay to schools, which are responsible for submitting candidate work and required documentation on time. The IB recommends setting earlier internal deadlines for each component, as explained on its official TOK deadline page and Extended Essay deadline page.

Coordinators should distinguish three types of date:

Deadline level	Purpose	Typical owner
IB submission date	Final external deadline communicated to the school	DP coordinator
School final deadline	Approved final work reaches the coordinator for checking	Student and assigned staff
Development milestone	Research, planning, drafting, reflection, or authentication checkpoint	Student and assigned staff

The school deadline should leave time for file checks, missing documentation, authenticity concerns, technical problems, and absences. The precise buffer is a school decision, but the IB submission date should not become the ordinary student deadline.

Build one tracker with two cohort views

A single source of truth is essential when managing overlapping IB cohorts. Use one protected spreadsheet, database, or school platform, then create filtered views for each cohort, TOK teachers, EE supervisors, and senior leadership.

Each student record should include:

Candidate name, identifier, and examination session
Applicable subject guide or assessment model
TOK class and teacher
EE subject, working research question, and supervisor
Milestone, due date, completion date, and evidence link
Status: not started, on track, at risk, overdue, or complete
Date of the last substantive staff contact
Required intervention, owner, and review date
Authentication, documentation, and upload status

Organise records by examination session, not only Year 1 and Year 2. Session labels prevent students from using the wrong TOK prescribed titles and help schools manage curriculum transitions. This matters because the revised Extended Essay has its first assessment in May 2027, according to the IB’s Extended Essay curriculum update.

Students should see only their own milestones, while supervisors see assigned candidates and the coordinator retains the complete view. Store sensitive welfare information in the school’s approved confidential system, not a widely shared tracker.

Use measurable milestones for each component

Both cohorts should follow the same milestone architecture, although their dates and current stages will differ. Common milestone definitions make reports comparable and prevent supervisors from applying inconsistent expectations.

Extended Essay milestones

The IB’s Extended Essay overview describes the EE as independent research supported by a supervisor. It includes three mandatory reflection sessions, with the final session known as the viva voce.

A practical tracker can include:

Subject, topic, and supervisor confirmed
Preliminary research and feasibility check completed
Working research question approved
First formal reflection recorded
Research base or data collection reviewed
Interim reflection completed
Detailed outline submitted
Complete draft submitted by the permitted school deadline
Feedback acknowledged and revision plan recorded
Final essay submitted
Viva voce and final reflection completed
Authentication, documentation, file, and upload checks completed

Every milestone should require observable evidence. “Continue research” is too vague; “submit an annotated list of eight relevant academic sources” can be checked consistently.

TOK milestones

TOK has two assessment tasks: the TOK exhibition, which is internally assessed and externally moderated, and the 1,600-word TOK essay, which is externally assessed. The official TOK subject brief explains that the essay responds to one of six prescribed titles for the relevant examination session.

Useful TOK checkpoints include:

Exhibition prompt and three specific objects checked
Commentary plan reviewed and final commentary submitted
Internal marking, standardisation, and moderation records completed
Session-specific essay titles introduced
Prescribed title selected and exact wording verified
Planning conference and outline completed
Permitted draft feedback completed
Final essay and required planning documentation submitted
Authentication, file, and upload checks completed

The younger cohort may practise argumentation and evaluation, but it should not draft an assessed essay using another session’s prescribed titles.

Stagger cohorts through a rolling calendar

Treat the programme as a continuous 24-month cycle. The graduating cohort will normally be completing, authenticating, or uploading work while the younger cohort explores topics, develops research skills, and establishes routines.

School-cycle period	Graduating cohort	Younger cohort
Start of academic year	EE draft review and TOK essay planning	EE orientation and topic exploration
First reporting point	Final EE revision and checks	Supervisor allocation and feasibility review
Middle of year	TOK essay completion and upload preparation	First EE reflection and early research
Before examination preparation	Audit TOK and EE submissions	Research checkpoint or exhibition development
End of cycle	Archive records and evaluate procedures	Interim reflection and next-stage planning

Adapt the sequence for the school calendar and May or November session. Avoid major core deadlines for both cohorts in the same week because coordinators, librarians, TOK teachers, and EE supervisors often support both groups.

Run a weekly traffic-light review

The tracker should generate a short weekly exception report. Coordinators do not need to read every draft; they need to identify unsafe progress, missing supervision, and incomplete documentation.

Green: completed or more than 14 days away with evidence of progress
Amber: due within 14 days, incomplete evidence, missed meeting, or delayed feedback
Red: overdue, repeated non-response, absent supervisor, authenticity concern, or final deadline at risk

Every amber or red record needs an action, owner, and review date. “Coordinator aware” is not an intervention. “Supervisor meets student Thursday; revised research question uploaded Friday; coordinator reviews Monday” is actionable.

Hold a short weekly meeting with the TOK and EE leads. Review status changes, red cases, staff capacity, deadline collisions, and required escalation; complete a fuller cohort audit monthly.

Define accountability and audit completion

Publish a simple responsibility structure before problems appear:

Role	Core responsibility
DP coordinator	Owns the calendar, confirms dates, monitors risk, and verifies readiness
TOK lead	Sequences assessment, coordinates standardisation, and reports missing evidence
EE lead	Oversees supervision, reflection checkpoints, and completion reporting
Supervisor	Monitors research, conducts required sessions, and raises concerns
Student	Produces work, attends meetings, keeps evidence, and communicates obstacles

Before submission, check the candidate, component, subject, session, prescribed title or prompt, required documentation, file accessibility, citations, authentication, and upload confirmation. Record who completed each check and when.

Common mistakes include publishing the IB date as the student deadline, tracking drafts without feedback, using the wrong TOK titles, accepting silence as evidence of progress, and recording vague percentages instead of deliverables. Coordinators should also avoid clustering TOK, EE, internal assessment, mock examination, and university deadlines.

For student-facing guidance, schools can share RevisionDojo’s explanation of what happens when an EE or TOK deadline is missed, its Extended Essay guide hub, and its TOK support guide. School instructions and current official IB documentation remain authoritative.

Conclusion

Effective management of TOK and EE deadlines depends on one tracker, examination-session labels, measurable milestones, weekly risk review, clear ownership, and protected submission buffers. Both cohorts should share one framework while following timelines suited to their stage.

RevisionDojo can complement the system through structured EE guidance, TOK resources, Jojo AI, and Coursework Review between formal teacher checkpoints. These tools can support independent progress, while deadline control, authentication, and official decisions remain with the school.

Sources and referenced URLs

Add as a preferred source on Google