coordinate-a-student-research-team

# coordinate-a-student-research-team Make ownership and contribution visible without concentrating authority in one person. ## When to use - Use for group studies, laboratory teams, capstones, field projects, or collaborative papers. - Do not assign unsafe, inaccessible, or inappropriate work based on status, availability, or stereotypes. ## Procedure 1. Confirm scope, rubric, academic-integrity rules, supervision, deadlines, approvals, and shared outputs. 2. Inventory skills, access needs, time constraints, learning goals, and required training privately and respectfully. 3. Assign accountable owners and reviewers for protocol, recruitment, data, analysis, writing, safety, and submission. 4. Define decision rights, meeting cadence, response expectations, file structure, naming, version control, and change approval. 5. Train and calibrate members on methods, coding, equipment, consent, privacy, safety, and quality checks. 6. Use a task board and decision log that records dependencies, evidence, status, and blockers. 7. Review workload and contribution regularly; redistribute through transparent criteria without rewriting history. 8. Resolve disagreements through evidence, small tests, supervisor escalation, and documented decisions. 9. Audit data, analysis, references, permissions, authorship, and contribution statements before submission. 10. Archive the final package and conduct a learning and fairness retrospective. ## Worked example One student becomes the only person able to run the analysis. The team pairs another member, documents the environment, and adds review checks. When results change, the decision log shows which transformation caused it and who verified the rerun. ## Done - A team charter and task board record roles, permissions, training, decisions, dependencies, workload, and contribution - A final audit verifies source evidence, analysis, authorship, approvals, reproducibility, and fair acknowledgment