top of page

September 29 Release – FAQs

This page answers common questions about the new Campus and Academic Year model and other changes released on 29 September

  • Yes, when you need to create your next Daily Organiser dataset, you will need to create a campus and academic year.


    We introduced Campuses, replacing published timetable groups, to provide schools with a clearer, more sustainable structure for managing timetables and daily operations. 

    Previously, schools created several Daily Organiser datasets in the same group, with different, yet very similar names, e.g. Daily Organiser 2025, Daily Organiser New, 2025 Daily Organiser.  This often led to errors, duplication, and significant processing delays when publishing timetables to groups.
     

    Campuses now form the required structure for publishing timetables and syncing with portals or administration systems.


    What this means for you

     

    • When creating your next Daily Organiser dataset, before publishing timetables, you must create at least one Campus | Academic Year in the Management Portal.  Ask your Global or School Administrator to go to [2A] Manage School to set them up.
       

    • Once campuses are established, all publishing (to Daily Organiser, portals, or LISS integrations) is then tied to a campus, rather than to published timetable groups.
       

  • We introduced Campuses, replacing published timetable groups, to provide schools with a clearer, more sustainable structure for managing timetables and daily operations.
     

    Why Campuses?
     

    • Eliminates Confusion with Multiple Daily Organiser Files
      Previously, schools created several Daily Organiser datasets in the same group, with different yet very similar names, e.g. Daily Organiser 2025, Daily Organiser New, 2025 Daily Organiser.  This often led to errors, duplication, and significant processing delays when publishing timetables to groups.
       

    • Reflects Real-World School Structures
      A campus represents a physical school location. By tying timetables, academic years, and daily data to campuses, the system now mirrors how schools actually operate across single-site and multi-site environments.
       

    • Simplifies Publishing and Integrations
      Instead of managing timetabling groups, which often did not reflect the correct year, campuses provide a consistent anchor point for publishing timetables, sharing data to portals, and syncing with external systems (e.g., Student Administration via LISS).

    ​

  • You can no longer create new Published Timetable Groups.  

    Publish Timetable Groups is replaced with Campus | Academic year for new Daily Organiser datasets.

    Existing Publish Groups remain active and can only have timetables published to them from the desktop.

    Opening Daily Organiser datasets from Published Timetable Groups is done by clicking the 'Open Legacy' folder on the Daily Organiser home page.

    Users with the role of Global or School Administrator create Campus |Academic year in the Management Portal, [2A] Manage School.  Read more...
     

  • The term dates recorded under each campus define the school’s overall academic structure and are used across our applications, for example, to display correct start and end points in portals, reports, and integrations.

    The Daily Organiser cannot open the dates between terms.

    ​

    In a scenario where the term dates are entered incorrectly and the Daily Organiser enters changes on those dates, changing them will not erase the Daily Organiser data; they won't be able to open on those dates.  Editing the term dates back will allow the Daily Organiser to view those dates again, and the data will be preserved.  (Closure dates created by the Daily Organiser do remove any edits added to those dates)


    While closure days and exceptions are still managed in the Daily Organiser | Timetable Days, the campus-level term dates provide the framework for ensuring that all systems reference the same academic calendar.
     

  • Each school will now define up to three campuses, set their academic year and term dates, and use one Daily Organiser file per campus per year. This removes the need for multiple files (per term or semester) and improves publishing speed.

    A campus can be the same physical site, such as defining the junior, middle, and senior schools, or it could be separate physical sites, such as primary and secondary.

    A separate campus will have a separate timetable and daily organiser data for each academic year.  The term dates cannot overlap.

    If your timetable structure changes mid-year (e.g. between terms or semesters), you will enable a 'Period Realignment' change option in the Management Portal, task [2B] Settings, Daily Organiser. When you next publish your timetable, it will replace the future dates with the new timetable and remove any no longer relevant changes that you had made to those dates.  Click here to purchase another campus

    ​

    ​

  • Datasets now run for the full academic year to simplify management and improve reliability.

    Previously, when datasets were created for terms or semesters, schools often ended up with multiple overlapping datasets, leading to confusion, duplicated work, and slower processing when publishing timetables.

    By standardising on the academic year, each school has a single, consistent dataset that can support timetable changes across terms or semesters without the overhead of managing multiple files.
     

  • Daily Organiser datasets can no longer be copied. Each Campus and Academic Year has a single dataset to keep data simple, accurate, and fast to publish.

    This change removes the complications caused by multiple file copies in the same timetable group, which often led to confusion and slower publishing. Allowing copy would introduce the problem we are trying to solve.
     

  • Each campus requires a physical address. This ensures campuses can be clearly identified and supports future enhancements. For example, the address may be used when notifying a casual relief teacher of a replacement class at a particular campus, allowing them to get directions via a map app. It also provides accurate information for reporting, integrations, and communications where campus location matters, aligning with attendance, duty, or scheduling systems that require site-based data

  • The LISS integration allows you to select a campus and year so you can sync more than one timetable | daily organiser data set and sync next year's data while still in the current year.

    To publish a timetable to your admin system for next year requires a new LISS integration (academic year/term dates/Daily Organiser dataset to be created). Then a manual sync can be performed.

  • To publish a future timetable (such as Semester Two) while still operating in Semester One:
     

    1. Open your LISS Integration settings.

    2. Tick Sync future date.

    3. Select the start date for Semester Two.

    4. Click Synchronise.
       

    The Sync future date option ensures your Semester Two timetable can be published to your administration system in advance, without interrupting your Semester One operations.

  • Schools can continue using their current setup without creating campuses until a new Daily Organiser dataset is created.

    Existing integrations with legacy files remain supported. They will continue to work and do not require the user to change anything.

    The Daily Organiser dataset that is marked published will continue to be marked published.

    The new SIF/LISS Integrations support Campus and Academic Year, so you can sync more than one timetable | daily organiser data set and sync next year's data while still in the current year.

    We have also included the option to create users for Teachers and Students added via the get calls.

    Additionally, when a school adds a new LISS, we check if the third party supports Timetable Structure calls (common with TASS). If they do, we retrieve the timetable values and populate our database. Then, we display the data, allowing the user to select the Timetable Structure to associate with.

    ​

  • With the new Campus | Academic Year model, the Daily Organiser dataset runs for a full year. There are two ways to manage a headstart program:
     

    1. Within the Same Dataset (Recommended)

    Use a Period Realignment publish for the headstart program. (Recommended)
    ​

    • Talk to your Daily Organiser and check whether they have applied any changes to the headstart program dates.  Publishing the headstart program, which changes the periods that the Daily Organiser edits have been made on, will be lost.
       

    • In the Management Portal, go to [2B] Settings and open the Daily Organiser tab, and enable Period Realignment.
       

    • Open your Timetable, publish the headstart program for the Campus|Academic year and enter the start date. This approach keeps all records together, avoids duplication, and ensures cleaner long-term data management.
       

    2. As a Separate Campus (Available, Not Recommended)

    If your school prefers to keep the headstart timetable completely separate, you may create a dedicated campus for it. Go to [2A] Manage School to create a new campus for the headstart program.
     

    This allows both the main timetable and the Headstart timetable to exist in the same academic year, but in separate datasets. We don't recommend it as this option mirrors how some schools previously managed multiple Daily Organiser files, which often led to errors and confusion as to which dataset to use.

     

  • If the headstart or early start wasn’t planned when setting up the year, you can edit term 4 of the current year to end earlier, making room for the next year’s timetable to begin.
     

    • Talk to your Daily Organiser, any edits they have made to the end of term 4 will need to be redone, if the 2026 term 1 will now replace the end of term 4
       

    • Go to [2A] Manage school and edit the term 4 end date
       

    • In the same campus, create a new set of term dates, select the 2026 academic year, and this will automatically create the terms for 2026
       

    • Edit the start of term one date to begin after term 4 of 2025.  Note:  the term dates cannot overlap.  Your academic year will now show as 2025/2026, as it combines both years
       

    • Open your next year's timetable and publish it to the new academic year, with the relevant start date


       

  • On Monday, September 15th, our sign-in page displayed a maintenance message notice with a link to an article detailing the changes.
     

    Mass emails have been sent to subscribers, with the role of Global Administrator or Software Maintenance main contact.

    You can update your email preferences here, select 'Software/Application Updates Email' to be included in future announcements.
     

bottom of page