How to stop free-riders in group projects

Free-riding starts at formation

It is easy to treat social loafing as a problem with individual students. More often it is baked in at formation: teams that are too big, too lopsided, or thrown together with no shared availability make it easy for someone to disappear and hard for the rest to notice.

Get the team right and a lot of free-riding never starts, because there is nowhere to hide and no one is set up to carry everyone else.

Right-size the team

Bigger teams make free-riding easier. Keep teams to a size where the work cannot be done by a subset, so everyone's contribution is visible and load-bearing. Three to five is the usual sweet spot for university projects.

Balance so no team is set up to fail

A team where one strong student ends up doing everything is a free-riding factory. Spreading skills and experience across teams means no group depends on a single person, which both reduces loafing and protects the students who would otherwise pick up the slack.

Surface it early with check-ins

Even with good formation, some imbalance appears mid-project. Short, regular team health checks let students flag uneven contribution while there is still time to address it, rather than only in a bitter peer review at the end.