Roll your cohort over

When you're carrying last term's cohort across to a new intake, most of the content clones. What's left is making sure the spine fits the new term and the targeting still matches the new students. That's what this guide walks.

Five steps. Set the new term's dates first — the cloned weeks recompute around them. Confirm the content actually came across. Re-target the audiences (programs and campuses might be the same, but the students they map to are not). Preview as a student in the new cohort. Publish week one.

Run this after creating the new cohort via clone-from-previous in /cohorts. The Home card switches to this guide automatically for cohorts created that way.

About 30 min · Setup checklist.

Set the new term up

Dates and the clone.

Set the new term's dates

Open the new cohort and set semester_start, semester_end, and census_date. The clone flow may have copied these from the source cohort — confirm they're right for the new intake before anything else, because the cloned weeks recompute their date ranges off these.

If your new term starts on a different day-of-week than the source cohort, all the cloned events will need their starts_at re-anchored. The clone flow handles that with a date-shift offset — check the audit log to confirm the events came across with their times intact.

Walk through it

• Open Cohorts → the new cohort.
• Confirm or set semester_start, semester_end, census_date.
• Check the cloned events shifted to the new term's days correctly.

In the console: Open Cohorts.

Confirm content cloned across

Needs: set the new term's dates first.

The clone-from-previous flow seeds the new cohort with last term's week_blocks, todos, events, library entries, and quick links. This step ticks automatically when the new cohort has at least one week_block.

If it doesn't tick, open Cohorts → the new cohort → Clone from previous and pick the source cohort. The clone runs as a bulk job; large cohorts can take 30-60 seconds. The audit log shows progress.

Walk through it

• Open the new cohort.
• Verify week_blocks, todos, events are present.
• If empty, run Clone from previous.

In the console: Open Cohorts.

Tune for this cohort

Re-target, check the preview.

Re-target the audiences

Needs: confirm content cloned across first.

Audience tags (program codes, campus names, year level, first-in-family) clone across with the content. The students they target, however, are entirely new — last term's commerce cohort isn't this term's commerce cohort.

Open Audiences and confirm each tag still resolves to the right student count for the NEW cohort. If a program rename, campus closure, or first-in-family flag drift has happened between terms, fix it here before anything goes live.

Tick this once the tag counts read sensibly for the new intake.

Walk through it

• Open Audiences.
• Filter to the new cohort.
• Confirm each program tag has the expected student count.
• Check first-in-family / international flags resolve correctly.

In the console: Open Audiences.

Preview as a student

Needs: confirm content cloned across first.

Same load-bearing preview as the first-launch journey. Pick a persona from the new cohort, walk week 1 top to bottom, click into the help routes, confirm the audience targeting matches the new student data.

Catch the wrong-cohort-link mistakes here. Cloned quick links sometimes carry forward URLs that are stale; cloned help-route copy sometimes references staff who've left.

Walk through it

• Open Preview.
• Switch to the new cohort.
• Pick a persona.
• Walk week 1 and click every cloned link.

In the console: Open Preview.

Go live

Flip week one.

Publish week one and go live

Needs: confirm content cloned across first.

Same go-live trigger as the first-launch journey: open Briefings → Week 1 in the new cohort and confirm at least one week_block is status='published'. The Home card retires the moment the cohort goes live.

If anything's still in draft that you wanted live, publish it now. The audit log captures the cutover so you've got a timestamp if a regulator or auditor asks when the new cohort went live.

Walk through it

• Open Briefings → Week 1.
• Publish what-matters, top to-do, week-1 events.
• Watch the Home card retire 4/5 → 5/5 → gone.

In the console: Open week 1.

Related guides