Every team is a draft until you say otherwise.
Teamer never publishes a team on its own. Draft teams land in front of staff first, where you can inspect them, move students, explain a choice, and release them only when they are right.
Teamer never publishes a team on its own. Draft teams land in front of staff first, where you can inspect them, move students, explain a choice, and release them only when they are right.
See the full set of proposed teams for the cohort in one place, not one group at a time.
Look at who is in each team and the survey answers that shaped it, so you can judge whether it works.
Move a student, rebalance a group, or reform a team. Your changes hold, and the draft stays yours until you publish.
Release the teams when you are happy with them, and students see the result straight away.
A draft is a starting point. Change anything about it before it becomes real.
Move a student
Shift someone into a team that suits them better.
Rebalance a team
Even out a group that is too heavy or too light in one area.
Reform a team
Break up and rebuild an arrangement that is not working.
Leave a note
Explain a decision so other staff have the context.
Drafts, edits, and published teams are stored in Australia on AWS in Sydney. Only staff with the right course role can see or change a draft.
Read how Teamer handles dataSee how reviewing and publishing feel on your own course. Start a pilot and we will help you form and release your first set of teams.
Start a pilot© 2026 Teamer™. All rights reserved.
Teamer