Assess teamwork fairly with criteria for contribution, collaboration, responsibility, and communication, then export the rubric to PDF.
Every teacher who assigns group work meets the same complaint: “I did everything and we all got the same grade.” This rubric exists to make that complaint untrue. Its four criteria — Contribution, Collaboration, Responsibility, and Communication — describe how an individual worked within the team, so you can give four students on one project four different, defensible scores.
The core move is to separate the product from the process. The poster, the slide deck, the model — those can earn a shared group grade for quality. But this rubric grades the process, and process is individual: Contribution is the share and quality of the work a student actually did; Collaboration is how well they worked with others rather than around them; Responsibility is reliability — meeting commitments and deadlines the team depended on; and Communication is whether they kept the group informed and listened as much as they talked. Scored per student, these rows let the diligent student and the free-rider land where they belong.
The most common way to use this rubric is one half of a two-part grade: a shared group score for the final product, plus each student’s individual process score from these four rows. A common split is 60 percent group, 40 percent individual, but the ratio matters less than telling students the split beforethey start — the whole deterrent effect of individual accountability evaporates if it’s a surprise at the end. When they know their own contribution is graded separately, the social math of coasting changes.
Scoring individuals fairly means you need to see individual work, which a finished product hides. Three sources help: brief peer- and self-assessments (students rating their own and teammates’ process against these rows), a shared task log or role assignment that records who owned what, and your own observation during work time. Treat peer ratings as evidence, not verdicts — a single teammate’s low score is a prompt to look closer, not an automatic penalty. Triangulating these keeps one loud voice from deciding a quiet student’s grade.
A student did a solid, reliable share of the work and always hit deadlines — but worked in a silo, never checked in, and rewrote a teammate’s section without telling them. Contribution is a 4 and Responsibility a 4, but Collaboration is a 2 and Communication a 2. The grade correctly says: you are dependable, and you are not yet a teammate — which is a far more useful message than the shared A the group product might otherwise have handed them.
Every so often a student simply doesn’t show up for the team. Decide the policy in advance: a student who contributes nothing earns low Contribution and Responsibility scores regardless of the group’s product, and the rubric gives you the dated documentation to defend that grade if a parent questions it. Just as important, scoring process individually protects the teammates who carried the work from being dragged down with the absent member.
Grading group work fairly is a genuinely hard problem with more approaches than one rubric can hold — peer assessment designs, contribution weighting, and handling the truly absent member. Our guide to grading group projects fairly without punishing the team works through those options in depth. Edit the rows in the builder above to match how your teams actually operate, then export a copy each student can be assessed against.