Step 01
Students complete a working-style survey.
Students answer a short instrument about how they work, communicate, solve problems, and contribute. Designed to take under ten minutes.
Faculty Access · Beta
For faculty teaching team-based courses.
Cohort forms balanced student teams from your roster — then shows you how each team is configured to work, where they’re drifting, and where one student may be carrying the load.
Approved faculty can use Cohort free during our beta.
Why this exists
You can’t fix what you can’t see inside the team.
You assign the teams. You watch them. By week three, you can usually tell something’s off — a quiet drift, an uneven load, a student you suspect is carrying more than their share. By the time you can name it, the deadline is close enough that the team can’t recover. Cohort gives faculty a team-level view of fit, friction, and balance — without reducing students to personality labels or individual scores.
What faculty get
A team-level read on every team in your class.
01
Team formation that’s actually balanced.
Upload your class roster. Cohort uses configuration fit — not personality types — to build teams that complement across strengths, working style, rhythm, and load.
02
A Team Configuration Report™ for every team you form.
Once teams are set, each gets a report: where they’re strong, where load may concentrate, and what to do about it.
03
An overview of every team in your class.
Catch the team that’s drifting before the deadline gets close.
04
Direct support during the beta.
Office hours with Jessica and the Cohort team. Your feedback shapes what ships next.
How teams are formed
Formation is the first lever.
Before students start a project, Cohort helps instructors form teams from a short working-style survey — so groups are balanced for the work, not just based on who already knows each other or happens to sit nearby.
Step 02
Mapped across 15 working-style roles.
Cohort maps each student across 15 working-style roles — not personality types or skill labels, but patterns in how they tend to contribute, communicate, and coordinate.
Step 03
Teams are formed for coordination balance.
Cohort compares possible team configurations and recommends groups balanced across working styles, contribution patterns, and workload risk — not random assignment or self-selection.
Step 04
You review and adjust before teams go live.
Every formation is a draft. Instructors can approve, swap, hold, or override suggested teams. Cohort shows how each change affects the balance, so final decisions stay in your hands.
As the work unfolds
Step 05 · ongoing
Check-ins show whether the configuration is holding.
Once the project starts, brief team-level check-ins show whether the configuration is working as intended — and surface drift while there is still time to act.
What your class will see
Once a team is formed, this is what you’ll see.
A Team Configuration Report for each project team — plus a pattern label that names what the configuration tells you.
Sample Team Configuration Report
The Tentpole Pattern
The team is moving, but the load is uneven.
One member is absorbing too much of the coordination burden. The team may perform well early, but pressure is concentrating around a single point.
What to do
Clarify ownership before the strongest contributor becomes the bottleneck.
Sample shown: The Tentpole Pattern. You’ll also see patterns like Parallel Play, Harmony, and Spark across your class.
Early classroom use
Mid-term survey results from the Spring 2026 beta showed strong student response: 96% reported clear team roles, 4.83/5 average psychological safety, 4.82/5 average team goal clarity. Seven university sections measured.
Why this exists
Why Cohort exists
Cohort is built by working professors and technologists who kept watching faculty assign team projects without a clear way to see what was happening inside those teams. By the time the issues surfaced — the load imbalance, the quiet drift, the disengaged member — the deadline was too close.
Cohort is what they wished they had. A way to see how each team is configured, not just who’s on it. Where the load is concentrating. Where coordination is breaking down. Whether the pattern of work is set up to actually deliver.
Faculty Access applications are reviewed by the Cohort team. If you teach team-based courses, we’d like to hear from you.
Approval process
Reviewed by hand. No automated approvals.
Applications are reviewed by the Cohort team. Most qualified faculty hear back within a few days. If you’re approved, we’ll send a short onboarding call link to get your class wired up.
Apply
Tell us about your course.
FAQ
Before you commit.
What does it cost?
Free for approved faculty during our beta.
Who’s eligible?
Faculty teaching team-based courses at accredited colleges and universities.
How long does setup take?
About 15 minutes to onboard a class. Students complete a 10-minute assessment on their own time.
What if my class is already underway?
Cohort works mid-stream. You can configure existing teams or form new ones.
Does it integrate with my LMS?
Not yet. Cohort is web-based and works alongside Canvas, Blackboard, or whatever you use. No IT setup required.
What happens to individual student data?
Individual responses stay private. You see team-level patterns only — never raw individual answers.
Do I need IRB approval?
Using Cohort as a teaching tool typically doesn’t require IRB. If you’d like to use the data for published research, that’s a separate conversation.