Some professors resist using teamwork in their classes because they mistakenly believe that team projects are too difficult to grade. One issue is that, as educators, we often only evaluate the team presentation, project or paper with a grade based on how well the team has met our learning objectives.

However, a single project evaluation at the end allows some members to potentially free ride on harder-working teammates, or enables one aggressive or dominating member to take over the entire project to ensure the team gets an A. If we simply grade team projects at the end, it is too late for our student teams to adapt or adjust and learn how to be better at working in teams, a key skill that employers look for in our graduates.

The key to effectively grading teamwork is to set up the grading process systematically at the start of the project. In this article, we offer four ways that you can grade team projects effectively to meet your learning objectives and help students become better team members.

1. Share your grading rubric at the start of the assignment. Students need to know at the outset of the team project how they will be graded. Many good students tell us they hate team projects because they know they will have to deal with “social loafers” who rely on one or two others to do the work. However, by sharing a rubric that highlights the expectations for each team member and how you will be combining individual and team grading, you can help students make more intentional decisions regarding how they distribute the assignment’s requirements. We not only distribute the rubric at the start of the project, but we post it on our course management system and frequently review it with the class so our expectations are clear.
2. Include peer evaluation as a part of the evaluation process. Students are sometimes asked to rate their fellow team members, but they are seldom taught how to do it well. As a result, they tend to only give positive feedback to avoid conflict or hurting another student’s feelings. Teaching peer feedback takes only a little class time, as few as 15 minutes. It starts with clarifying your expectations about how you will use peer feedback. You can use or create a form that allows students to provide quantitative and qualitative feedback, and then you should use this same form multiple times during the project. The first time you collect peer feedback should be a low-stakes or practice situation early during the project so that students have a psychologically safe opportunity to learn how to use it. Your students should begin with self-evaluation and then evaluate their peers.
   Next, you need to summarize the peer feedback and give results to individual students so they know how they are doing. Finally, have groups reflect on how well the group is doing without naming or shaming others. There are times when students will have to give feedback to a person who is free riding or loafing. When they do, make sure they know to first ask that person for permission before they give feedback, then praise in public, and finally provide any negative feedback in private. Finally, we have a YouTube video that instructors can show during class to help students learn about how to give and receive feedback.

3. Incorporate ongoing feedback from the instructor. We know of faculty who give out a team assignment and never mention it again until the week before the project is due. This is setting up the student teams for failure. Faculty need to check in frequently with their teams to be sure they are making progress on their work and any questions or concerns are answered. Taking just five minutes at the end of class for teams to meet can pay great dividends in a better project product. This instructor feedback can include a way to hold individual team members accountable for the work they are doing. For example, we have set up a separate Google folder for each team with instructor access. Each team member needed to post their contributions to the team project weekly. In this way, we could keep an eye on any social loafers, and provide feedback to those who were working independently instead of with the team. Instructors can also schedule a brief time to sit in on team meetings so that they get a more comprehensive update about the project and who is working toward each of the outcomes.
4. Carefully consider the weight you give to each phase of the project. It is essential to incorporate peer assessments and the instructor evaluation about how well the project met the learning objectives into any final grade; both are important. However, the weight of these different evaluations tells students the importance of each. More weight on the individual peer assessments stresses the individual work, while more weight on the instructor grade of the project shows the team efforts are more important. At a minimum, use the 80/20 rule: At least 20 percent of the student’s grade should be based on each.
   Also, be sure to check the peer evaluations to verify that they result from real behaviors rather than personal biases. We accomplish this by looking for consistency across the times of evaluation, across team members and between peer and self-evaluations. In most cases, we find that the evaluations show consistency in all three areas (though self-evaluations are often inflated). In the rare cases when they don’t align, we always refer to supporting documentation, such as agendas, meeting minutes and information that resulted from our ongoing check-ins to help make sense of the reasons underlying any inconsistencies.

Grading a team project may seem like a daunting challenge, but grading is by no means a reason to avoid giving students the experience of working with a team. By following these four principles for evaluating teamwork, instructors can account for the team’s achievement of the learning objectives as well as provide students with valuable teamwork experiences that they can take to future classes, internships, co-ops and employment.