For institutions

Run a real challenge programme with your own cohort.

Your students work in small teams on questions organisations have actually posted. You see every team, every submission and every score for your own institution, and nobody else sees yours.

What you do here

01
Set up campuses and cohorts
Each cohort gets a join code. That code is all a student needs to sign up under your institution.
02
Bring in your faculty
Invite faculty by email. They follow the teams and read what is submitted.
03
Follow the work
See who has formed a team, which challenge each team chose, and what they submitted in each round.
04
Arrange the review
Assign evaluators to teams and link mentors. Scores and feedback go back to the teams.

How it looks inside

What your admin, faculty and jury see.

01
Your institution in one place
Each cycle and where its rounds stand, with your campuses, cohorts and their join codes.
02
Every team, and where it stands
Who is in which team, who leads it, and whether it is still competing. Move a participant when a team needs it.
03
Assign the jury
Choose who scores which team, and watch scoring fill in.
04
Scored against a rubric
A juror sees the team's name and its work, never who is in it, and gives a score and a note on each criterion.
05
Results you can stand behind
Standings come from the scores, round by round and criterion by criterion, for your own institution only.

These are real screens from CoBuild. The names, teams and scores in them are invented for the demonstration.

Worth knowing

What stays inside your institution.

Your institution is its own space: People at one institution cannot see participants or work at another.
Judging is blind: Evaluators are shown a team's name and its work, not who is in the team.

What you do here

Set up campuses and cohorts

Each cohort gets a join code. That code is all a student needs to sign up under your institution.

Bring in your faculty

Invite faculty by email. They follow the teams and read what is submitted.

Follow the work

See who has formed a team, which challenge each team chose, and what they submitted in each round.

Arrange the review

Assign evaluators to teams and link mentors. Scores and feedback go back to the teams.

What your admin, faculty and jury see.

Your institution in one place

Each cycle and where its rounds stand, with your campuses, cohorts and their join codes.

The institution admin page showing a cycle with one round complete and one in evaluation, and a campus with its join code.

Every team, and where it stands

Who is in which team, who leads it, and whether it is still competing. Move a participant when a team needs it.

The teams list for one cohort, with each team's standing and its members.

Assign the jury

Choose who scores which team, and watch scoring fill in.

The evaluation desk for a round in evaluation: six teams submitted, twelve of twenty assignments fully scored, and a form to assign an evaluator.

Scored against a rubric

A juror sees the team's name and its work, never who is in it, and gives a score and a note on each criterion.

A juror's scoring form for one team: the submitted work, then a score out of ten and a note for each criterion.

Results you can stand behind

Standings come from the scores, round by round and criterion by criterion, for your own institution only.

The leaderboard for one cohort, each team with its score in every round and on every criterion.

These are real screens from CoBuild. The names, teams and scores in them are invented for the demonstration.