Product
Solutions
Trust
ResourcesDocs
Live previewBook a demo

Rolling and staggered intakes

First weeks that start when each student does

An intake in the console: Semester 2 2026, six weeks, 120 students, with Import students and ClockA student who joined after week one is welcomed at week 3, with See all six weeks and Start with week one
Clock
Shared or individual
Anchored to
Each student's start
Fits
Rolling and staggered intakes
Real dates
Stay on the calendar

Week one starts on their day one

Late, mid-year and rolling starters get their own first weeks instead of joining partway through.

Mid-year, monthly pathway and rolling intakes mean students start on different days. On a shared calendar, a late starter lands in week four after the welcome has passed. First Six can run each student's guided weeks from their own start date, while events and census stay on the real calendar. How cohort clocks work.

A proper start for every intake

One setting for each group of students, and one start date for each student.

  1. Run a cohort on one shared timeline, or switch it to an individual clock for rolling and staggered intakes.

  2. Add a start date on the import, your SIS feed or a student's profile, and their weeks run from it.

  3. Week-one content lands in their week one. A March starter gets the welcome in March.

  4. Campus events and deadlines like census stay on the true calendar for everyone. Only the guided arc is individual.

How student data is looked after

How First Six handles student data

  • Seen by the staff who support them

    Support staff can open a student's check-in answers to reach out. Every look is audit-logged.

  • Every look is recorded

    Each time a staff member opens a student's record, it is written to a tamper-resistant audit log.

  • Never sold or mined

    We do not sell or mine student data. Every subprocessor is disclosed, and the data of record is hosted in Australia.

  • Wellbeing figures stay with your team

    Only staff with the insights permission see wellbeing figures, for the students they support. Nobody outside your team does, First Six included.

Fits what you already run

  • Your sign-in, no new passwords

    Students and staff sign in with your identity provider over OpenID Connect, including Microsoft Entra ID. There is no new password.

  • Rosters that stay current

    Import a roster CSV with no IT work, or push rosters and enrolments over HTTPS from any SIS.

  • Their own calendar

    An iCal feed puts it into Apple, Google or Outlook and keeps itself up to date.

FAQs

Can't see your question? Ask us and we'll reply.

What is an individual clock?

A cohort setting. Each student's guided weeks run from their own start date instead of one shared calendar, so a late starter still gets week one on their week one.

Does this suit mid-year and rolling intakes?

Yes, that is what it is for. Monthly pathway starts, mid-year intakes and rolling admissions all work, with each student anchored to their own day one.

What about events and census dates?

Those stay on the real calendar for everyone. A campus event or a census deadline is a fixed date. Only the guided weeks follow each student's clock.

Is it hard to set up?

No. It is one switch on the cohort, and a start-date column on the student import. Anyone without a start date follows the cohort's shared clock.

Can a cohort switch back to a shared clock?

Yes, at any time, and nothing is lost. Students without a start date follow the shared clock either way.

Fit your intake pattern

See how a rolling or staggered intake runs in First Six, with each student on their own clock.