Open Coaching → Cohorts and select October Builders to inspect the cohort cockpit. It shows the intake's operating state: phase position, capacity and member counts, and collective signals such as work needing attention. Phase position is an explicit delivery fact; it is not simply the calendar week. Capacity can be unlimited or a hard limit. A cohort signal tells Mike Academy where to look, while Maya's member record supplies her own timeline, submission and interventions.
| Question | Use this surface | Scope of the answer |
|---|---|---|
| Is October Builders on track? | Coaching → Cohorts, then its cockpit | Cohort phase, capacity, enrollments and aggregate signals |
| Why is Maya stuck? | Coaching → Member monitoring, then Maya's enrollment | Individual evidence and follow-up history |
| When is the cohort workshop and who attended? | Management → Lives | A scheduled cohort live and attendance per enrollment |
If several October Builders members struggle with their demos, Mike can inspect the cohort pattern and schedule a workshop from Management → Lives. A live targets the cohort and can be moved or cancelled; attendance is recorded against the participating enrollments. Mike, as organization owner, may schedule, change or cancel it; an organization admin may do the same. Nina's coach assignment and a reviewer's assignment do not grant this write permission. A member, including a coach acting only as a member, reads only lives that target their own enrollments.
Information
The Cohorts API documents authorized cohort reads, cockpit and configuration operations. The Live sessions API documents scheduling, moving, cancelling, listing and attendance; its read and write permissions differ. Delivery analytics is a separate aggregate view. Return to sessions and interventions for Maya's individual follow-up.