How to assign students to groups in a large class
Hari B · Founder · July 2026 · Updated October 2026
To assign students to groups in a large class, collect availability, skills and preferences once through a short survey and form every team from that data with the same rules. A class list alone does not show who can meet or work together.
A process for a large class
- Open the survey early with a clear close date, and send one reminder before it shuts.
- Before it closes, fix the team size and decide how you will handle the remainder.
- Place non-responders deliberately instead of leaving them to the end.
- Form every team in one pass with the same rules.
- Review the flagged teams: no shared time, a lopsided skill mix, or one student on their own.
- Publish, then rework only the affected team when someone drops or swaps.
Why the spreadsheet breaks down
As a class grows, sorting teams by hand gets harder: you can lose track of who is placed or miss a team with no shared availability. A late enrolment adds another decision to make.
It is also hard to hold many criteria in your head at once. Layton and colleagues (2010) observe that instructors find it very difficult to consider more than a few criteria when assigning teams, particularly in large classes, so most end up letting students self-select, assigning at random, or balancing on very few criteria.
Collect the inputs once, up front
The step that makes large-class grouping tractable is a short formation survey. Ask for the few things that change who ends up with whom, when students are free, what they can do, who they want to work with, and gather it in one place instead of chasing it later.
Structured inputs are what make it fast. Oakley, Felder, Brent and Elhajj (2004) collect a short form on the first day of class, and one of the authors reports forming teams for classes of 120 and more in two hours or less that way.
Form on the data, then review
With structured inputs in hand, forming balanced teams across two hundred students is a matter of applying the same rules consistently: spread skills, keep sizes even, honour a reasonable number of preferences. The part that still needs a human is the review, checking the handful of teams that look off before students see them.
Consistency is where software helps most. When Layton and colleagues compared teams formed by their Team-Maker tool with teams formed by experienced faculty using the same criteria, the software consistently met the criteria more closely.
Plan for churn
In a large cohort, students drop, add, and swap tutorials for weeks. Assume it. Whatever process you use should let you rework one affected team without rebuilding the whole arrangement, and keep a record of what changed.
Sources
- Layton, R. A., Loughry, M. L., Ohland, M. W. & Ricco, G. D. (2010). Design and validation of a web-based system for assigning members to teams using instructor-specified criteria. Advances in Engineering Education, 2(1), 1 to 28. https://advances.asee.org/wp-content/uploads/vol02/issue01/papers/aee-vol02-issue01-p09.pdf, accessed 18 October 2026.
- Oakley, B., Felder, R. M., Brent, R. & Elhajj, I. (2004). Turning student groups into effective teams. Journal of Student Centered Learning, 2(1), 9 to 34. https://engr.ncsu.edu/wp-content/uploads/drive/1ofGhdOciEwloA2zofffqkr7jG3SeKRq3/2004-Oakley-paper%28JSCL%29.pdf, accessed 18 October 2026.
This is exactly what Teamer is built for: collect the survey once, generate balanced draft teams across the whole cohort in one pass, review the ones that need it, and handle drop-ins and swaps without starting over. No spreadsheet, no re-keying.
If you are running group work in a large course and want to see how it would fit, get in touch.
Start a pilotJust have a question? Email hello@teamer.university