HomeInstitution Programs
Institution programs

What you would actually run.

Four flagship programmes and five things that run alongside them. Every one of them is a cohort — a fixed group, a fixed calendar, facilitated rooms and marked work.

Flagship programmes

Four programmes, chosen by the outcome you need

Pick by what you are trying to change, not by what sounds most comprehensive. The second is the most common mistake in this list.

Placement Readiness

For a pre-final or final year batch heading into a placement season. Case discussion, technical depth and interview reasoning run as one track, with the readiness distribution visible to the placement cell from the first month rather than after the season.

One or two terms, by department
Readiness distribution refreshed from marked work
Mock panels run as facilitated rooms, not as one-off events
Who this is for

A placement cell that knows its December outcome and wants to know its August position, while there is still a term in which to move it.

Foundation Reasoning

For senior school. Structured argument, evidence handling and written reasoning, run in an existing period against the board calendar rather than on top of it. The skills the board exam does not assess and the years after school depend on.

Grades 9–12, weekly cadence, one existing slot
Shorter, scaffolded cases for grades 6–8
Written submissions usable as internal assessment
Who this is for

A school that can see its students can recall a syllabus and cannot defend a position, and has one free period a week to do something about it.

Faculty Development & Facilitator Certification

Your staff trained and certified to run the rooms themselves, with calibration so two facilitators mark the same submission the same way. This is the programme that decides whether everything else survives a change of coordinator.

Shadow, co-run, then run — certified at the end
Rubric calibration sessions each term
Runs alongside a live cohort, not as a separate workshop
Who this is for

An institution that intends to own the programme rather than renew a service, which in practice is the only kind that still runs it in year three.

Corporate Capability

For teams rather than classes. Cohorts by level or function on a working-hours cadence, with capability movement reported to managers instead of course completions, and the same rubric-marked submissions underneath.

Cohorts by team, level or function
Evening or in-hours cadence, set per cohort
Manager view of capability movement, not seat time
Who this is for

An L&D team tired of reporting a completion percentage that nobody in the business believes measures anything.

Runs alongside

Five things that attach to a programme

None of these is a programme on its own. Each one is added to a cohort that is already running.

Capstone Support

A term-long project run as a cohort: scoped, reviewed at checkpoints, defended in a facilitated room and marked against the same rubric.

Campus Hackathons

Your own hackathon on our infrastructure — registration, teams, submissions, judging and a public leaderboard — run as an institution event.

Co-Branded Certification

Any programme above can issue certificates carrying both names on the same public verification path students can put on a CV.

Custom Case Development

Your own material converted into cases with rubrics and moderator notes. Usually the hardest part of running your own content, so we do it with you.

The common structure

Every programme is a cohort

The content differs. The mechanic does not: one group, one calendar, a facilitator in every room, and written work marked against a rubric by a person.

20–40
Learners per room
1 term
Typical programme length
8–12
Modules and submissions
100%
Rubric-marked, by a person

The mechanic is set out in full on Cohort Learning.

How a programme starts

Outcome first, programme second

Five steps. Institutions that start at step two usually cannot answer, at the end, whether it worked.

01

Say what you want to change

Not which programme you want. The programme follows from the outcome, and occasionally the honest answer is that none of these fit.

02

Scope a pilot

One cohort, one track, one term — sized so the result is readable rather than impressive.

03

Certify your facilitators

Alongside the pilot, so by the end of it your staff can run the next one.

04

Review against a baseline

The pilot cohort read against the group that did not run it. Without the comparison the review is a testimonial.

05

Roll out

Widen by grade, department or function on what the pilot showed.

Questions

About the programmes

Yes, and most partners do — Faculty Development almost always runs alongside whichever programme is being piloted, because the point of the pilot is to end with staff who can run the next one. Combining two content-heavy programmes in a first term is usually a mistake and we will push back on it.
The structure is fixed — cohorts, facilitated rooms, rubric-marked submissions. What goes through it is adaptable: track scope, case selection, cadence, and your own material converted into cases.
One discussion room, so 20 to 40 learners. Below that a discussion does not have enough positions in it to be worth facilitating, and the outcome data is too small to read.
Participation data from week one, rubric marks from the end of week two, and something worth calling a trend by week five or six. A full readiness comparison needs a term.
Per-cohort pricing that falls with size, and pilots priced to be easy to approve, because an expensive pilot never happens. The number depends on programme, cohort size and track count — the conversation starts on the contact page.
Yes, though the calendar and the case library are strongest for Indian school boards and Indian placement seasons. We will say plainly when a cohort would be better served by material we do not yet have.
Pilots start each term

Tell us the outcome.
We will tell you the programme.

Occasionally we will tell you none of them fits, which is a cheaper conversation to have now than a term from now.