Skip to main content
bthebigclass
All help topics

For creators

Cohort start + end dates

Time-box a community to a cohort window — opens on a date, wraps on a date, with the right countdown / archive banner on the batch page. Leave both dates empty for an always-on group.

Last updated May 22, 2026

Setting the window

Open /dashboard/batches/<id> → Community settings → Edit community. Two date pickers — 'Cohort starts' and 'Cohort ends'. Both optional.

  • Both set — a time-boxed cohort. Opens on the start date, wraps on the end date.
  • Only starts set — a rolling cohort with a launch date. No end.
  • Only ends set — an always-on community that wraps on a fixed date.
  • Both empty — the default. The community is always-on and never archives.

What the banner says

A single chip strip on the batch hero, with three states. No reconfiguration needed — the chip just reads the dates and computes.

  • Pre-launch (amber) — 'Cohort begins in N days · <date>'.
  • Live (primary) — 'Cohort live · wraps in N days (<date>)'.
  • Past (muted) — 'Cohort wrapped on <date>'.

Pairing with a course

Cohorts make the most sense when paired with a course that has drip-unlocked modules. Set the cohort start date, then on the course set per-module unlock days (Module 2 = 7 days, Module 3 = 14, etc.). The cohort opens, modules unlock on schedule, the cohort wraps — that's a complete 'program' without renaming anything.

The dates are display + scheduling hints — they don't hide the common room from members. If you want the room hidden before the cohort opens, switch visibility to 'closed' until launch day, then flip it back to 'open' / 'tag-gated'.

Related