Every intake
Mid-year, monthly, pathway or rolling admissions — every student gets their first six weeks from their own start date, not one shared calendar.
Fit your intake pattern
One switch per cohort, one start date per student.
Late, mid-year and rolling starters each get a real first six weeks from their own start date, instead of being dropped into the middle of someone else's.
A first six weeks that starts when the student does
Not every student starts in February. Mid-year intakes, monthly pathway starts, and rolling admissions mean students arrive on different days — and a platform pinned to one shared calendar drops a late starter into 'week four' on day one, having missed the welcome entirely.
First Six can run each student's six weeks from their own start date. A student who joins in March gets week one in March. Orientation content lands when it's actually their orientation. Campus events and real deadlines still sit on the true calendar — only the guided arc follows the student.
Every intake, not just the main one
One switch per cohort, one start date per student.
01
Choose the cohort's clock
Run a cohort on one shared timeline, or switch it to an individual clock for rolling and staggered intakes.
02
Set each start date
Add a start date on the student import, and each student's six-week arc is measured from their own day one.
03
Content follows the student
Week-one content lands on their week one, not the cohort's. A March starter gets the welcome in March.
04
Campus events and deadlines like census stay on the true calendar for everyone — only the guided arc is individual.
Fit your intake pattern
See how a rolling or staggered intake runs in First Six, with each student on their own clock.
What we never do. The line between support and surveillance, drawn clear.
Support means seeing the pattern, not the person. We built the line between helping and watching into the product itself.
Support, not surveillance
Support staff can see individual check-in responses so they can reach out. Access is scoped to your institution and audit-logged.
Logged and reviewable
Every time a staff member opens a student's record, it's written to a tamper-resistant audit log.
Never sold or mined
We do not sell or mine student data. Subprocessors are disclosed, and the data of record is hosted in Australia.
No silent exposure
Small groups are suppressed, so no individual can be singled out from an aggregate.
Plugs into the systems you already run
SSO, roster sync, calendar integration. Your stack stays yours, and your students see only your university.
SSO, no new passwords
Sign in with Microsoft Entra or any OIDC provider (SAML on the roadmap). Students sign in as themselves.
Roster sync keeps cohorts current
Idempotent SIS sync keeps your cohorts in step with your source system.
Calendar stays theirs
iCal export to Apple, Google, or Outlook, kept current automatically.
FAQ
Questions about how First Six works and what it does for your students.
A cohort setting. Instead of everyone moving through the six weeks on one shared calendar, each student's arc runs from their own start date — so a late starter still gets week one on their week one.
Yes — that's exactly what it's for. Monthly pathway starts, mid-year intakes, and rolling admissions all work, with each student anchored to their own day one.
Those stay on the real calendar for everyone. A campus event or a census deadline is a fixed date — only the guided content arc follows each student's clock.
No. It's one switch on the cohort, and a start-date column on the student import. Anyone without a start date simply follows the cohort's shared clock.
Yes, at any time, and it's non-destructive. Students without a start date follow the cohort clock either way.
Fit your intake pattern
Currently meeting with universities.