When publishing a timetable, you will see a red message asking you to select a Campus and Academic Year.

This change replaces the old file-based approach and ensures timetables are correctly linked to your school’s structure. It also prevents duplicate or unnecessary datasets.

What are Campus and Academic Year?

  • Campus - This represents your school site(s). A school can be set up to be on three campuses (e.g., Primary, Junior, Senior).

  • Academic Year – This represents the year of study (e.g., 2025, 2026). Timetables are always tied to an Academic Year to keep data separated and consistent.

Note: You can continue publishing to the Legacy Published Timetable Group, when creating a new Daily Organiser datsaet will require a Campus and Academic Year going forward.



You can continue to publish timetables to your existing Daily Organiser datasets by selecting "Publish To: Legacy Published Timetable Group".

Campuses are required when creating new Daily Organiser data sets.

How to Add a Campus and Academic Year

STEP 1: Sign in to the Management Portal on https://timetabling.edcuation




STEP 2: Click [2A] Manage School.

If the task is not visible, you will need the Global Administrator or School Administrator role.

Click +Add Campus




STEP 3: Add an Academic Year.

  • Select the correct year (e.g. 2026) and the start month.
  • Select either terms or trimesters.


  • Edit the term dates relevant for your campus. These can be edited at any time.

    The holidays will create 'closure days' in the Daily Organiser.



STEP 4: Publish your timetable.

  • When publishing, select the Campus and Academic Year from the drop-down list.
  • If your school has multiple campuses, they will appear in the drop-down list.

 

Why did Timetabling Solutions remove the option to create multiple Daily Organiser data sets?

The primary reason for this change is to improve reliability, performance, and consistency in the Daily Organiser. In the past, allowing multiple files for the same year led to duplication, confusion, and slower publishing times, as every timetable update had to be associated with each file. By moving to a single dataset per year, we eliminate the inefficiencies and risks created by multiple copies, ensure that schools are always working with the correct version, and align Daily Organiser with the modern approach used across our other cloud applications, which no longer use file-based structures. This simplifies the user experience, reduces errors, and provides a more streamlined and scalable platform for schools.

A common sight of multiple Daily Organiser files, with confusing names, is shown below: