Student success & retention
Spot the students who are slipping in week two, while there is still time to help.

At a glance
See it early
Check-ins add up to trends by campus and program, so a dip shows in week two.
Act on it
Help requests reach an inbox your staff answer, and support routes get each student to the right place.
Stand behind it
Decisions rest on what students told you, read in aggregate.
The signs show up early, in places nobody joins up
By the time a withdrawal form lands, the moment to help has usually passed. The signs were there in week two: a quiet check-in, a missed start, an unanswered request. They sat in systems nobody had time to join up, and a predictive risk score is hard to explain to a student, let alone act on.
A weekly picture, and a short list of who to contact
Weekly check-ins add up to trends across campuses and programs, so your team knows where its hours count. The Needs attention list shows who might need a hello, by three published rules. Help requests go to an inbox your staff answer, and every look at a student's record is logged.
- WobblingTheir check-in says it's hard
- Not startedNever answered a check-in
- Gone quietQuiet for three weeks
What your team does each week
A weekly briefing tells each student what matters this week, so fewer drift away in the first place.
Weekly briefingsCheck-ins add up to trends by campus and program, and Needs attention shows who might need a hello.
Cohort insightsWhen a student asks for help, the request lands in an inbox your staff answer and reaches the right person.
Help inboxTrends give your team a basis for where support goes, ready for leadership.
Cohort insightsWhat you can expect
Earlier sight of who is struggling
You see which campus or program is slipping in week two, while there is still time to act.
Support hours where they count
Your team spends its limited hours on the groups that need them most.
A privacy-safe basis for decisions
Trends you can put in front of a retention committee. Printed reports withhold any group under five.
Help offered early, while it is still light
Built so the first contact is a hello or a reply, long before a crisis.
FAQs
Can't see your question? Ask us and we'll reply.
Does this mean monitoring individual students?
Insights shows group figures, with no names or risk scores. The Needs attention list uses three published rules that read check-in answers only, and every look at a student's record is audit-logged.
How quickly can we get started?
First Six connects to your single sign-on and roster, and a pilot can run with a single intake. We plan for six to eight weeks from kick-off to launch.
How is this different from an early alert system?
Many early alert systems score students on logins, submissions and grades. First Six gives your team a picture of how all your students are going, plus a short list built from what students chose to say in a check-in.
Where is our student data stored?
The data of record is hosted in Australia on AWS in Sydney, with each institution's records kept apart by row-level security. Every subprocessor is listed on our Knowledge Base.
Where to go next
The features behind it
Further reading
Research and practical guides on the same question.
- Why the first six weeks decide first-year retentionA look at why the opening weeks of first year matter so much for retention, and what to do inside that window.Read article
- Support without surveillance: a privacy-first approach to student analyticsWhy student analytics so often feels like surveillance, and how to get the insight without crossing the line.Read article
See it with your students
Book a walkthrough built around your own first-year intake.





