Student team charter for a course group project https://ai-essay.com/guides/student-team-charter-template Use this as a discussion aid, not a contract that overrides the course rules. Complete the reflection prompts individually first, then write only agreements the whole team accepts. Adapt every section to the assignment and instructor’s requirements. PROJECT AND SHARED OUTCOME Course / project: Team name (optional): Assignment or rubric location: Final deliverable and due date: What must the whole team understand or be able to explain? What does the instructor assess individually and as a group? INDIVIDUAL WORK PREFERENCES (SHARE VOLUNTARILY) What strengths, interests or experience would you like the team to know about? What kind of task helps you contribute? What availability or access constraint should the team plan around? Share only what you are comfortable sharing. What helped or hindered you in a previous group project? ROLES, TASKS AND LEARNING Task / deliverable: Responsible person or pair (only by agreement): Backup or reviewer, if the team agrees: Expected output and where it will be shared: Due date or checkpoint: Who will review or connect this work to the whole project? How will tasks or roles rotate so each person practises the learning goals? COMMUNICATION AND MEETINGS Agreed channel and backup: Usual response window (allow for class, work and access needs): Meeting/check-in cadence and accessible format: How will members propose an agenda item or flag a blocker? How will the team document a decision and who agreed to it? DECISIONS, MISSED COMMITMENTS AND DISAGREEMENTS How will the team make routine decisions (for example: discuss, record options, agree on a next step)? If the team cannot agree, what is the next respectful step? How can a member raise a concern privately or ask for support? What should happen when a task is at risk: contact the owner, adjust scope, redistribute by agreement, or ask the instructor? When and how should the instructor or course support be contacted? CARE AND ACCESS (OPTIONAL TEAM AGREEMENTS) What formats or participation routes should be available so everyone can contribute? How can someone flag a workload or access problem without sharing private details? Would naming a backup for a time-sensitive task help? If so, agree who and what they cover. PROJECT CHECK-IN LOG (make one copy per meeting) Date / milestone: What is complete? Link, file, page, or other evidence: What changed since the last check-in? Next task and owner, if agreed: Expected checkpoint: What is blocked or needs a decision? What support is requested, and from whom? Decision made, who agreed, and any course question to ask: Does the team need to revise this charter? REVISIT THE AGREEMENT Next review date: What is working for the project and for participation? What should change, and does everyone agree? Keep this record factual and proportionate. Do not use it to assign grades, diagnose a teammate, keep private personal information, or punish someone for an unexpected constraint. Follow the instructor’s process for serious or unresolved problems. Keep individual work separate when the assignment requires it.