How many students should be in a group project team?
Hari B · Founder · July 2026 · Updated October 2026
For most university group projects, aim for teams of three to five students, and keep sizes even across the cohort. Fewer than three leaves the project exposed if one person drops out, and more than five makes it easy for someone to go passive.
Team size at a glance
| Team size | When it fits |
|---|---|
| Two | Lab-style work at shared stations, where the setup dictates pairs. |
| Three | A short or tightly coupled brief that does not split into parts. |
| Four | The default for most projects, and the safer choice when early dropouts are common. |
| Five | A larger deliverable with five clearly separable parts. |
| Six or more | Only when the project genuinely has that many distinct roles. |
Where three to five comes from
The research lands in the same place. Oakley, Felder, Brent and Elhajj (2004) note there is no consensus on an optimal size, but most authors agree the minimum for most team assignments is three and the maximum five. In a pair there may not be enough variety of ideas, and the dominant partner wins most arguments. Above five, at least one member is likely to be relatively passive unless the project has six or more distinct roles. Their own recommendation is teams of three and four, with more fours if early dropouts are common.
University guidance sets a similar ceiling. For tutor-selected groups early in first year, the University of Bath's group work guide (2025) says groups should ideally be no larger than six.
The right number inside that range depends on the project. Bigger deliverables with clearly separable parts can carry five; a tight, fast-moving brief is usually better at three or four.
Why bigger teams get worse, not better
Adding people adds communication links faster than it adds hands. A team of four has six pairs to keep in sync; a team of six has fifteen. That overhead is exactly where free-riding and missed handoffs creep in, because it gets easier for one person's absence to go unnoticed.
Match the size to the assessment
Before you fix a number, look at what you are asking teams to produce. If the deliverable cannot keep five people meaningfully busy, five is too many, and you are designing in a passenger. Size the team to the work, not the other way around.
Keep sizes even across the cohort
Uneven teams create a fairness problem: a group of three doing the same brief as a group of five is not being marked on equal footing. When you form teams, aim to keep sizes consistent, and decide in advance how you will handle the remainder when the cohort does not divide evenly.
Sources
- 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.
- Centre for Learning and Teaching, University of Bath (2025). Group work guide: recommendations and resources to support effective practice, version 1.0. https://teachinghub.bath.ac.uk/wp-content/uploads/2025/03/Group-Work-Guide-Version-1.0-March-2025.pdf, accessed 18 October 2026.
Keeping team sizes even across a whole cohort, while still balancing skills, availability, and preferences, is the fiddly part. Teamer handles it: you set the team size, and it generates balanced draft teams that fit, which you review before publishing.
If you want a second opinion on the right team size for your particular project, get in touch and I am happy to talk it through.
Start a pilotJust have a question? Email hello@teamer.university