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). Double-check the targeting in the new cohort. Publish week one.

Run this after creating the new cohort with a source picked in Start from, or after filling an existing one with Copy content in. It does not appear on Home: the Home banner is the first-launch checklist, and a cohort that was created from a source does not get it. This guide lives in Guides & Articles and in the floating guide companion, which is what tracks your progress through it.

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 & Student Import → 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.

Picking a source cohort seeds the new cohort with last term's week blocks and events, with audience tags carried across. Blocks arrive complete: their tick-off flag, any per-student gate, and any day-of-week deadline come with them. (The weekly check-in is standard on every cohort and comes across automatically.) Library entries are institution-wide and already apply to the new cohort, no clone needed. This step ticks automatically when the new cohort has at least one week block.

If it doesn't tick, open Cohorts & Student Import, find the new cohort and press Copy content in, then pick the cohort you are rolling over from. Everything arrives as a draft, and it is safe to press more than once: only weeks that are still empty get filled, so it tops up what is missing rather than doubling anything you have already written. The audit log records the run.

Walk through it

• Open the new cohort.
• Verify week blocks and events are present.
• If empty, press Copy content in and pick last term's cohort.

In the console: Open Cohorts.

Tune for this cohort

Re-target, check the targeting.

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 the right program, campus and group tags exist for the new intake (the page lists tags, not student counts); spot-check a targeted item in Briefings and verify student counts in the cohort browser. 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 tags read sensibly for the new intake.

Walk through it

• Open Audiences and confirm the right program, campus and group tags exist for the new intake (the page lists tags, not student counts).
• Spot-check a targeted item in Briefings and verify student counts in the cohort browser.
• Check the first-in-family / international tags are switched on if you target them.

In the console: Open Audiences.

Double-check the targeting

Needs: confirm content cloned across first.

Same load-bearing check as the first-launch journey. Read week 1 back in the new cohort and confirm each item's audience label resolves against the new student data. The tags cloned across, but the students behind them changed.

Catch the wrong-cohort-link mistakes here too. Cloned resource links sometimes carry forward URLs that are stale; cloned help-route copy sometimes references staff who've left, so click into each one.

Walk through it

• Open Briefings → Week 1 in the new cohort.
• Read it top to bottom.
• Confirm each item's audience targeting matches the new students.
• Click every cloned link and help route.

In the console: Open Briefings.

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 published. The companion ticks this step off and the guide completes.

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 the week-1 blocks and events.
• Watch the guide companion tick the last step off.

In the console: Open week 1.

Related guides