For the program lead at leadership academies and fellowship programs — the people who run leadership and fellowship cohorts: CohortOps runs a 6–12-month cohort end to end after selection — the cohort set up with its dates, its graduation rules, and its tuition; sessions and deliverables scheduled; participants enrolled with tuition status tracked; attendance recorded against the graduation rules; every participant's standing read as Meets rules, At risk, or Not meeting; and the cohort closed out into its graduation list and alumni rollover — so at-risk participants surface early, not at graduation. CohortOps tracks and surfaces; it sends no participant notifications, and tuition is tracked in it, never collected, as the sections below state plainly.
How it works
- Set up the cohort after selection — the dates, the graduation rules (the attendance floor and the required deliverables), and the tuition
- Schedule the sessions and the deliverables for the season
- Enroll the participants, with tuition status tracked for each one — who owes and who has paid, as your team records it; the amount outstanding is computed per participant and per cohort. Tuition is tracked in CohortOps, never collected: no participant can pay tuition through CohortOps, and no payment handling exists
- Record attendance per session against the graduation rules — excused absences are excluded from the denominator, as the rule states — and track deliverables against the required list
- Read every participant's standing — Meets rules, At risk (with the reason named), or Not meeting — on the at-risk board, so a participant falling behind surfaces early, not at graduation; CohortOps surfaces the standing to your team and sends no notification to any participant — your team notifies participants its own way
- Close the cohort out — the graduation list, printable completion records, and alumni rollover that persists across cohorts
Cohort setup — the rules are set once, after selection
A cohort begins after selection. At setup, the program sets the cohort's dates, its graduation rules — the attendance floor a participant must hold and the deliverables a participant must complete — and its tuition. Those rules are the program's own; CohortOps holds them and measures the season against them.
Sessions and deliverables are then scheduled for the season, and participants are enrolled with their tuition status tracked. From that point, the season runs against the setup: attendance against the floor, deliverables against the required list, tuition against the ledger.
- Cohort dates
- Graduation rules — the attendance floor and the required deliverables
- Tuition
- Sessions and deliverables scheduled
- Participants enrolled, with tuition status tracked
Attendance and standing — at-risk surfaces early
Attendance is recorded per session, against the graduation rules. Excused absences are excluded from the denominator, as the rule states — an excused absence does not count against a participant's attendance. Deliverables are tracked against the required list the same way.
Each participant's standing is read from that record against the graduation rules:
The at-risk board gathers the participants whose standing is At risk or Not meeting, each with the reason named, while there is still season left to act on it. That is the point of the product: at-risk participants surface early, not at graduation.
CohortOps surfaces standing to your team. It sends no notification to any participant: real participant notifications do not exist in CohortOps today. Your program team notifies participants its own way, as it does today — CohortOps tracks and surfaces; the notifying stays yours.
- Meets rules
- At risk — with the reason named
- Not meeting
Tuition — tracked as a ledger, never collected
Tuition lives in CohortOps as a ledger. Each enrolled participant carries a tuition status — who owes and who has paid, as your team records it — and the amount outstanding is computed per participant and for the cohort as a whole, so what is still owed is a number on the record, not a memory.
The ledger is tracking only. Tuition payment handling does not exist in CohortOps: no participant can pay tuition through CohortOps, and no payment is taken or processed here. Your program handles tuition its own way, as it does today, and records the result in the ledger.
Closeout — graduation and alumni rollover
At the end of the season, the cohort closes out: the graduation list is drawn from the standings against the graduation rules, and completion records are printable for the graduates.
Graduates then roll into alumni, and the alumni rollover persists across cohorts — the alumni record carries from season to season, so a program's graduates stay on the record as new cohorts are set up and run.
- Graduation list
- Printable completion records
- Alumni rollover that persists across cohorts
Where it stands — the honest state
CohortOps is forming its first organization pilot group now. The door below is an organization pilot application — applying starts a pilot conversation; it does not create an account, and it is not a sign-up for a running service.
CohortOps sends no participant notifications. Real participant notifications do not exist in the product today: CohortOps tracks and surfaces — attendance, deliverables, standing, the at-risk board, the tuition ledger — and your program team notifies participants its own way, as it does today.
Tuition is tracked, never collected. Tuition payment handling does not exist in CohortOps — no participant can pay tuition through CohortOps, and no payment is taken here. The product's own billing is likewise not armed: there is no checkout on this page.
No price has been set. A price range exists in our market research as a hypothesis; it has not been validated and it has not been decided, so no price is shown here and there is nothing to buy on this page.
Organization pilot application
This is an organization pilot application — an application to join CohortOps' first organization pilot group, not an account sign-up and not a purchase. Tell us who to reach, your organization, and how many participants each cohort carries. If you like, tell us how many cohorts you run per year, and how you run cohorts today. We will be in touch about the pilot group.