Collaboration learning should count.
The collaboration activities are designed as part of students' learning, not as optional additions to the project. Giving them a place in the course grade signals that completing this work matters.
Grades for these activities are based on completing the required learning processes, not on how well students are judged to collaborate. Peer feedback, self-assessment, and reflection remain sources of perspective and learning rather than measures of collaboration performance.
How the Activities Are Graded
Completion means more than submitting the activity. The activities use requirements-based completion grading. Each activity has specific requirements that establish what must be present or completed for credit.
Students receive credit for completing the required parts of the learning process. This grading approach does not require instructors to evaluate students' collaboration performance or judge the quality of their feedback or reflection to award that credit.
| Activity | For completion credit, verify... |
|---|---|
| Team Charter | All required sections are addressed, including 3–5 specific and observable Team Success Commitments. |
| Pulse Check | All five ratings and both required short responses are completed. |
| Feedback in Progress | The required developmental feedback process is completed. |
| Feedback Forward | The required feedback-and-reflection process is completed. |
What Completion Emphasizes in Each Activity
Team Charter — Create usable shared expectations. Completion requires the full Team Charter, including 3–5 specific and observable Team Success Commitments, because the Charter is intended to function as working infrastructure for the team's collaboration rather than simply as a document submitted at the beginning of the project.
Pulse Check — Pause, notice, and prepare for team discussion. Completion includes both the ratings and short responses because the ratings help students step back across several aspects of collaboration while the short responses give them observations they can bring into the team's follow-up conversation. The subsequent discussion and action remain team-owned rather than instructor-graded.
Feedback in Progress — Provide developmental coaching while there is still time to use it. Giving feedback receives the greatest grading emphasis because much of the learning depends on students giving teammates access to perspectives they cannot generate for themselves. Reading and reflecting on feedback remain required, while students retain agency over what they ultimately take from it and use during the remainder of the project.
Feedback Forward — Turn the completed experience into learning that can transfer. Giving feedback remains a major reciprocal responsibility, but completing reflection becomes substantially more central because students use the completed collaboration and teammates' perspectives to determine what they have learned and what they want to carry into future teamwork.
Completion grading does not mean the substance of the activities is unimportant. The requirements protect different parts of the learning process in each activity. Instructors can respond when what students produce reveals an opportunity for additional support without turning that response into a quality-based activity grade.
Grade What Students Had the Opportunity to Complete
Students should not lose completion credit for a required interaction they could not complete because another participant did not make that interaction available.
For example, if receiving or responding to peer feedback depends on a teammate first providing that feedback, grade the student only on the required interactions they had a reasonable opportunity to complete.
Decide How the Activities Count Toward the Course Grade
Give the activities a proportionate place in the course grade. Their weight should be enough to make completion consequential without implying that the activity grades measure how effectively students collaborated.
The activities do not need to occupy a particular type of grading category. Consider where they fit in relation to the learning already represented in your course grade, then determine an appropriate weight within that structure.
Possible Ways to Fit the Activities Into Your Course Grade
| Possible fit | Example |
|---|---|
| Within an existing course component | If Participation represents 5% of the course grade, you might allocate 2% to the collaboration activities and retain 3% for other participation activities. |
| Within the collaborative project | If a collaborative project carries a substantial portion of the course grade, you might designate part of that project grade for completing the adopted collaboration activities. |
| Within a related project assignment | If you adopt only Team Charter and already use a 15-point Project Proposal, you might make completion of the Team Charter worth 5 of those 15 points rather than create a separate collaboration category. |
These are starting examples, not recommended weights or placements for every course. The aim is to give the adopted activities a proportionate place in the grading structure without requiring a particular course-grading model.
If You Are Using Canvas
The distributed activities are placed in a Collaboration Assignment Group so they have a ready-made location in the course grading structure. The group is not assigned a course weight because the appropriate weight depends on the grading structure of the course receiving the activities.
If you use Canvas Assignment Groups, use the Collaboration Assignment Group as provided or place the activities elsewhere when that better fits your course grading structure. For example, you could assign 2% to Collaboration and reduce an existing 5% Participation group to 3%, or move Team Charter to the Assignment Group containing the Project Proposal.
After changing Assignment Group weights, check the total course weighting. Canvas allows weighted Assignment Groups to total more or less than 100%. If that is not intentional, adjust the weights so the course grade still reflects the total and relative weighting you intend.
Keep Peer Ratings Separate From Grades
Peer ratings give students access to teammates' perspectives on their collaboration. They can also help instructors notice experiences and patterns that may otherwise be difficult to see. Peer ratings and rating averages should not determine students' collaboration grades.
Keeping peer ratings separate from grades preserves their developmental purpose. Students can make evidence-based judgments and exchange developmental feedback without being placed in the role of assigning one another's grades.
This separation does not mean peer feedback is inconsequential. Feedback can include specific observations about project responsibilities and contribution that the instructor was not present to observe. When those observations raise a possible project-contribution concern, use them as information to look more closely rather than treating the rating itself as the basis for a grading conclusion.
When Peer Feedback Raises a Project Contribution Concern
Peer feedback can make project contribution visible in ways the final team product may not. It gives instructors access to observations from people who experienced the collaboration directly, including information about responsibilities, follow-through, and work absorbed by others that may otherwise be difficult to see.
This visibility does not make peer feedback a grade. It gives the instructor additional information that can be considered alongside relevant course and project information when a contribution concern may affect grading.
Separate Project Contribution From Collaboration Quality
A substantial contribution shortfall is not the same as ineffective collaboration.
A student might miss meetings, create additional coordination work, or receive strongly negative feedback from teammates while still completing the project responsibilities reasonably expected of them. Those experiences may matter for the student's development or warrant instructional attention, but they do not by themselves establish a shortfall in project contribution.
The reverse is also possible: a student may be supportive and well regarded while failing to complete project responsibilities.
For grading purposes, focus on whether the student had a reasonable and sufficiently established responsibility and opportunity to contribute to the shared project work but substantially did not carry that responsibility, leaving required project work unfulfilled or requiring others to carry work that reasonably belonged to that student.
Determine What the Available Information Supports
A low rating, rating average, missed meeting, uneven workload, unmet Team Charter commitment, or work completed by another teammate does not establish a substantial contribution shortfall on its own.
When the information may affect a project-grade decision, consider:
| Consider | Ask |
|---|---|
| Responsibility | What project work was the student reasonably responsible for? |
| Opportunity | Did the student have a reasonable opportunity to carry that responsibility? |
| Contribution | What required project work did the student substantially not complete? |
| Effect | Was that work left unfulfilled or carried by someone else? |
Consider peer observations alongside other relevant course and project information. Multiple peer reports can strengthen the available information, but they are not required; one teammate may have absorbed most of another student's unfinished work.
If the available information does not sufficiently support the conclusion that a substantial contribution shortfall occurred, do not use it to change the student's project grade on that basis.
Apply Your Existing Expectations for Project Work
When the available information sufficiently supports the conclusion that a substantial contribution shortfall occurred, use the same grading expectations you would ordinarily apply if the student's completed and uncompleted project work were directly visible.
Ask:
If this were not hidden inside a shared submission, how would I ordinarily grade what this student completed?
If the student completed the project responsibilities reasonably expected of them, a difficult collaboration experience does not itself change the project grade through this guidance.
If required project work was partially or entirely uncompleted, apply the course or project's usual approach to partial, missing, incomplete, excused, or otherwise uncompleted work as appropriate. If a student completed none of the required project work, for example, use the same course policies and grading judgment you would ordinarily use when a student completes no required work.
The Collaboration Development Activity Chain does not add a separate free-riding penalty or prescribe how much to deduct. It provides additional visibility into individual project contribution that a shared submission can otherwise obscure.
Tell Students What Grading Means
Students should understand that peer feedback makes parts of the project work more visible without making teammates responsible for one another's grades. Keep the message focused on what peer feedback can and cannot do.
When explaining how peer feedback relates to project grades, make clear that:
- Teammates do not assign one another's grades.
- High or low collaboration ratings do not determine a student's grade.
- Peer feedback gives you visibility into project contribution you may not otherwise have.
- When that information warrants a closer look, consider what happened and apply your existing expectations for required project work.
When Adapting the Grading Approach
Grading decisions such as where the activities fit and how much they count will necessarily vary across courses, but not every change has the same effect. Changes to what earns activity credit or how parts of an activity are emphasized can change what students understand as important and the learning conditions the activities were designed to create.
Before making a change, be clear about what you want the grading approach to accomplish, how that compares with what the provided approach is designed to accomplish, and what the change may alter for students.
| If you change... | What changes with it |
|---|---|
| What earns completion credit | A required component that no longer affects completion credit may become effectively optional to students and therefore be treated as unimportant or simply not done. |
| Emphasis within Feedback in Progress | Giving feedback carries the greatest emphasis because teammates depend on one another for perspectives they cannot generate themselves. Reducing that emphasis weakens the responsibility to provide that learning opportunity to others. |
| Emphasis within Feedback Forward | Giving feedback remains an important responsibility to teammates, while reflection becomes much more central because Feedback Forward prepares learning for transfer. |
| Grade peer collaboration ratings | Ratings move from providing perspectives on collaboration to directly affecting a teammate's grade. That can change what students are willing to say and how openly they rate one another. |
| Grade feedback for quality | Feedback becomes something students are writing for both their teammate and the instructor who will evaluate it, which can shift attention away from giving the teammate useful information. |
| Grade reflection for quality | Reflection becomes an instructor-evaluated performance rather than a space for students to make sense of the experience and decide what they take from it. |
| Increase the weight of feedback-usefulness ratings | One recipient's experience of the feedback has more influence over another student's grade. |