Team Contracts¶

Strategy · All strategies
Evidence · 2 claims (2 for) · 5 studies (2 causal, 1 quant-synthesis, 1 review, 1 theoretical), q1–q4 · 1 of 5 report an effect size

Description¶

A team contract (also called a team charter or group agreement) is a document co-authored by members of a collaborative learning team at the outset of a project. It typically specifies individual roles and responsibilities, meeting and communication norms, decision-making procedures, quality standards, and consequences for non-participation. Because members negotiate and sign it themselves, the contract functions as a public commitment device rather than an instructor-imposed rule set.

Design Implications¶

Team contracts address the two most common failure modes of Collaborative Learning: unequal participation (free-riding and social loafing) and unproductive conflict. Making expectations explicit at the start reduces ambiguity about what "good teamwork" means, and public commitments increase follow-through [~M]. Contracts also build psychological safety — the shared belief that the team is safe for interpersonal risk-taking — which is the strongest known predictor of team learning behavior Edmondson's research on team psychological safety. [+S]. The act of negotiating the contract itself activates learner Autonomy, which supports intrinsic motivation for the group task Autonomy supports intrinsic motivation. [+S].

Context¶

Requirements¶

• Time early in the project for genuine negotiation — a contract dictated by the instructor forfeits the commitment and autonomy benefits
• Concrete, behavioral language ("respond to messages within 24 hours") rather than vague aspirations ("communicate well")
• A named process for revisiting and revising the contract mid-project, since norms drift as work becomes real
• Instructor-provided templates or exemplar contracts so teams know what dimensions to cover [~M]

Constraints¶

• Contracts signed but never revisited become dead documents; without scheduled check-ins they have little effect on behavior [-M]
• If teams are formed and dissolved too quickly, the upfront cost of contracting exceeds its benefit [-W]
• Contracts cannot compensate for poorly designed tasks — if the task is divisible into isolated slices, members will contract their way into parallel solo work rather than genuine collaboration [~S]
• Overly detailed contracts can shift attention from learning goals to procedural compliance [-W]

Implementation Variability¶

• Full charter: roles, schedule, communication channels, quality standards, conflict-resolution ladder, and signatures — suited to multi-week projects
• Lightweight norms agreement: a short list of working agreements, revisable at each meeting — suited to short activities
• Instructor-scaffolded version: the instructor supplies categories and non-negotiables (e.g., individual accountability metrics) while teams fill in the rest — useful when teams lack experience collaborating
• Digital contracts: shared documents or wiki pages that serve as a living reference and revision log

Target Learners¶

• Adolescents through adults; especially valuable for learners with limited prior experience in sustained group work [~M]
• Teams in online or hybrid settings, where fewer ambient cues regulate participation and explicit norms matter more [~M]
• Less necessary for small, short-lived, tightly structured activities where roles are already assigned

Target Learning Goals¶

• Collaboration and teamwork competencies: negotiating norms, giving and receiving accountability
• Self-regulation of group processes: planning, monitoring, and adjusting collective work
• Social belonging and inclusion: surfacing expectations reduces the interpersonal risk that silences less confident members Belonging interventions improve outcomes. [+M]

Instructions¶

1. Form teams and present the purpose of a contract, with an exemplar showing typical dimensions (roles, norms, deadlines, conflict process).
2. Have teams draft the contract collaboratively, requiring every member to contribute at least one norm — this distributes ownership.
3. Require behavioral specificity: each commitment should be observable and checkable (see Check-ins for recurring accountability touchpoints).
4. Include an escalation ladder for unmet commitments: private conversation → team discussion → instructor involvement.
5. Schedule at least one mid-project review where teams revise the contract against actual experience.
6. At project close, have teams assess performance against the contract, feeding reflection into future collaborations.

Related Strategies¶

• Check-ins — recurring structured touchpoints that keep contract commitments visible during the project
• Peer assessment — individual accountability ratings that pair with contract consequences
• Role assignment — a contract often operationalizes roles; assigned roles alone are a lighter-weight alternative
• Anti-oppressive co-design meeting practices: land acknowledgements, shared roles, breakout discussions, multiple input modes
• Scaffold the transition into team work with explicit team-level AI norms and coding-inclusive team entry points
• Design AI mediators with negotiable intervention, participant-controlled synthesis, and transparent role transitions that preserve human ownership of team decisions

Examples¶

• Project-based courses (e.g., PBLWorks exemplar projects) — teams draft a "group contract" in week one covering roles, meeting schedules, and conflict resolution; PBLWorks publishes contract templates used across K–12 project-based learning.
• Engineering capstone courses — many programs (e.g., following ABET teamwork outcomes) require team charters with signed individual responsibility agreements, reviewed by faculty at milestone gates.
• Online graduate programs — learning-management-system teams post a shared "team agreement" page in the course wiki, with a revision history that documents norm changes across the term.

Key Sources¶

• Edmondson, A. (1999). Psychological safety and learning behavior in work teams. Administrative Science Quarterly, 44(2), 350–383. doi:10.2307/2666999
• Johnson, D. W., & Johnson, R. T. (2009). An educational psychology success story: Social interdependence theory and cooperative learning. Educational Researcher, 38(5), 365–379. doi:10.3102/0013189X09339057
• Karau, S. J., & Williams, K. D. (1993). Social loafing: A meta-analytic review and theoretical integration. Journal of Personality and Social Psychology, 65(4), 681–706. doi:10.1037/0022-3514.65.4.681
• Oakley, B., Felder, R. M., Brent, R., & Elhajj, I. (2004). Turning student groups into effective teams. Journal of Student Centered Learning, 2(1), 9–34.
• Deci, E. L., & Ryan, R. M. (2000). The "what" and "why" of goal pursuits: Human needs and the self-determination of behavior. Psychological Inquiry, 11(4), 227–268. doi:10.1207/S15327965PLI1104_01