How to divide work in a school group project

Why most “fair” splits fall apart

• Roles without deliverables

  "You're research, I'm slides" sounds fair until nobody defines what "done" means. Research becomes a 40-page dump. Slides wait on a draft that never arrives.

• One person becomes the AI tab

  Whoever opens ChatGPT first turns into the unpaid research assistant. Everyone else gets a paste and no shared history of what was asked or wrong.

• Deadlines live in someone's head

  The group agrees verbally. Three people remember different dates. The quiet person finds out the draft was due yesterday.

For the private-AI problem specifically, see AI teammates vs chatbots or ChatGPT vs ateams. If you still need a shared home for the project, start with set up your group stack before fall.

A fair split in four moves

Do this in the first meeting—ideally the same day the assignment drops. About 20 minutes if someone already created the team.

• Name the deliverables, not the vibes

  List what the teacher will grade: outline, draft, slides, demo, peer review. Those become parent tasks. Soft skills like "communication" are not a fair split.

• Assign owners before due dates are perfect

  Put a name on each task even if the date is TBD. Empty boards stay empty. You can tighten dates when the assignment sheet or rubric is clear.

• Match work to strengths, then rotate grunt work

  Let the strong writer own the draft and the design-minded person own slides—but rotate citation cleanup, formatting, and meeting notes so one person isn't always the cleanup crew.

• Keep AI output where the group can see it

  @mention Nola or Cora in the team chat (or assign them a task) so summaries and outlines live with the plan. No private-tab bottlenecks.

Example roles for a four-person team

Adapt these to your rubric. Smaller groups combine roles; larger groups add a QA or demo lead. The pattern stays the same: one human owns the outcome, AI helps in public.

• Research lead

  Owns: Sources, notes, and a short source brief the writers can cite

  AI help: Assign or @mention Nola for comparisons and PDF summaries

• Writing lead

  Owns: Outline → draft → final polish against the rubric

  AI help: Use Nola for structure checks; Cora for alternate phrasings the group edits

• Slides / visuals lead

  Owns: Deck structure, figures, and a practice run outline

  AI help: @mention Cora for a 6-slide skeleton everyone can argue with

• Coordinator

  Owns: Meeting times, status check-ins, and calendar nudges

  AI help: @mention Radar for draft and handoff reminders the whole team sees

Deep dive on @mentions vs assigning AI on tasks: group collaboration with AI and tasks.

Copy-paste prompts for kickoff

Drop these in your ateams group chat after the team exists. Paste the brief or rubric with the first prompt.

What to put on the board this week

• Parent tasks for each graded deliverable (research brief, draft, slides, final)
• One human assignee per task—even if a due date is still TBD
• A short definition of done in the task description (what “research done” means)
• One Radar reminder for the first checkpoint so status updates are a habit

Want the longer lifecycle (kickoff → crunch → handoff)? See ateams for group projects or the group projects page.

Common questions

Do this before week two

Create the team, post the brief once, add four owned tasks, and run one @mention so AI help shows up in the same place as the plan. Fair splits are visible splits—everything else is hope.