8.3 — The Group Project Survival Kit | AI for Real Life

Templates and scripts for group projects.

The logistics of working with 3–5 humans on a deadline can be awful.

Claude can't make your teammates reply faster. Claude can't make Drew do his half. What Claude can do is take the worst three jobs off your plate: writing the awkward kickoff message, drafting the polite-but-firm nudge to the disappeared teammate, and translating "this is a disaster" into a calm message to the prof.

The integrity frame for group work

This lesson is about coordination, not content. Using AI to draft the kickoff message, build the timeline, and word the difficult conversations is fine. Using AI to write your half of the actual project deliverable falls under Modules 4 and 5:same rules, no special exemption because "it's a group thing."

The Day-One Kickoff Pack.

The day you get the assignment, before anyone has decided who's doing what, run these three prompts in sequence. Don't wait for the group chat to "figure it out." Show up to the first meeting with a draft and your group will love you.

1 · The Role-Split Prompt

Here's the assignment: [paste the assignment description, the rubric, and any prof notes]. We're a group of [N] students. Due in [X] weeks. Break the project into [N] roughly-equal roles. For each role: - A clear name ("Research Lead" / "Writing Lead" / "Slides & Visuals" / "Coordinator & Edits") - 3–5 specific deliverables that role owns - An estimated time investment over the [X] weeks - What this role hands off to the others, and when Make the roles distinct so two people can't accidentally do the same thing. Flag any deliverable that doesn't fit cleanly into one role: those are the ones the group needs to talk about. End with a 3-sentence "how this fits together" paragraph I can use to pitch the split to the group.

2 · The 3-Week Timeline Prompt

Take the role split above. The deadline is [date]. Today is [date]. Build a week-by-week timeline. Format as a table: | Week | Dates | What each role does | Group meeting? | Handoff/check-in | Rules: - Front-load research and outline. Don't leave them for week 3. - Hard deadline for "first full draft of all sections" should be at least 4 days before the final due date. - Build in ONE catch-up day before the deadline for the inevitable last-minute fix. - Suggest 2 group meetings: kickoff (this week) and mid-project check-in. Anything more is overhead. End with a "Risks" section: 3 things most likely to go wrong on this timeline, and the early sign for each so we catch it in week 1, not week 3.

3 · The Kickoff Message Prompt

Draft a kickoff message I can post in our group chat / email thread. Tone: friendly but organized. I'm not the elected leader, just the one who showed up first. Include: - One-sentence summary of the assignment. - The role split from above (4 roles, here's what each owns). - The timeline at a high level (3 milestones, not the full table). - A specific ask: "Reply with which role you want by [day], or pick one in the doc." (Avoid "let me know your thoughts":too vague.) - Suggest one specific time for the kickoff meeting. - Close with: "I drafted this so we'd have a starting point: happy to swap roles, change anything, push back." Length: under 200 words. Friendly. Not corporate. We're [students], not consultants.

The Polite-But-Firm Nudge.

It's week 2 and one teammate hasn't responded in 5 days. Their part of the project is the bottleneck.

The right move: a calibrated nudge. Three levels, depending on how late and how much is at stake. Each one Claude can draft for you on demand.

👋

Level 1 · Gentle check-in (Day 3 of silence)

"Hey [name]:just checking in. Saw you haven't been able to post the [thing] yet, no stress. Are you good for the [Friday] handoff or do we need to swap things around? Let me know either way and we'll figure it out."

Goal: open the door without accusation. Most of the time, this gets a "sorry, busy week, I'm on it" reply within hours.

⏰

Level 2 · Specific deadline (Day 5–7)

"Hey [name]:circling back on this. We're tight on the timeline and the rest of us are blocked on your section. Can you have [specific deliverable] up by [specific day/time]? If something's going on and you can't, that's okay too: just need to know so we can re-plan. Either way, can you confirm by [tomorrow EOD]?"

Goal: name the impact, give a real deadline, give an honest out. The "if something's going on" line is the empathy that keeps the relationship intact.

📨

Level 3 · Loop in the prof (when nothing else worked)

This isn't a teammate message: it's an email to the professor or TA. Document what happened, ask for guidance, don't ask for the teammate to be punished.

"Hi Professor [X], wanted to give you a heads-up about my group project. [Teammate] hasn't responded to [N] messages over [N] days, and we're [%] from the deadline. We're going to cover their section so the project lands on time, but I wanted you to know in case it affects how you're thinking about [grading / participation / etc.]. We've still got their parts of the timeline saved if you'd like to see what was missed."

The Nudge Prompt: pick a level, get a personalized draft

My group project teammate [first name only] has been silent for [N] days. Their part is [specific deliverable]. We're [N] days from the deadline. Context I want you to know but NOT include in the message: [1–2 sentences: busy with another class, going through something hard, I just don't know, etc.] Draft a Level [1 / 2 / 3] nudge per the survival kit. Tone: warm but real. Under 100 words. Do not include passive-aggressive phrases ("just wondering...", "not sure if you got my last...", "obviously..."). Don't make me sound like a manager. End with a specific ask, not "let me know your thoughts."

The four hardest group-project conversations.

Scenario 1 · The dominant member

One teammate is making every decision and dismissing pushback. The work is getting done, but the project is becoming theirs alone.

Prompt: "Draft a message I can send in the group chat that names one specific decision I disagreed with and proposes we vote rather than have it decided unilaterally. Tone: not confrontational, not whiny. The goal is making the group function better, not winning."

Scenario 2 · Scope creep

The project is getting bigger every meeting. Someone keeps adding "wouldn't it be cool if we also..." and now we're way past the rubric.

Prompt: "Draft a 2-paragraph 'pump the brakes' message. Reference the rubric explicitly. List what we have. List what's been added. Ask the group to vote: cut the extras and finish on time, or push everything by [N] days. Be respectful but real."

Scenario 3 · Last-minute panic (T-minus 24 hours, half is missing)

It's the day before. Two sections aren't done. The teammate responsible is unreachable. Group chat is silent.

Prompt: "Triage. Here's what we have: [list]. Here's what's missing: [list]. Here's the rubric: [paste]. Tell me: what's the minimum viable submission that still passes? What's the one thing I should personally do in the next 6 hours? Draft a message I can send to the group at 8pm telling them I'm pushing through on [specific parts] tonight, and giving them until [time tomorrow morning] to add anything else before I submit."

Scenario 4 · The post-mortem (after grades come back)

Grade was lower than expected because of one teammate. You're considering reporting it. Or just venting forever. Both are bad.

Prompt: "I'm thinking about whether to email my prof about the group project grade. Walk me through the decision. Ask me 4 clarifying questions before suggesting anything. I want help thinking, not a pre-written email yet. After my answers, give me an honest read on whether it's worth doing: and if yes, draft something measured. If no, tell me why and help me let it go."

The pattern across all four scenarios

Notice what every prompt does: it asks for a specific deliverable (a message, a triage plan, a draft email), gives real context, and explicitly rules out things you don't want (passive-aggression, manager-speak, dramatic escalation).

The shared-doc setup + your "save these for next semester" pack.

Last move: set up a shared workspace.

The Shared Doc Setup Prompt

We just split the work as [4 roles, here are the names]. We need a single Google Doc / Notion page that the group will use as the project hub. Draft the structure of that doc, ready for me to paste into Google Docs as section headers. Include: - A "Quick Status" table at the top: each role, current status (Not started / In progress / Drafted / Done), last update date. - A linked "What we're building" section restating the assignment in our own words (1 short paragraph), so we don't drift. - One section per role with a 1-sentence "what this person is building" lead. - A "Decisions" log at the bottom: every time we vote on something or change direction, one line goes here. - A "Questions for the prof" section we add to as they come up. Output as plain Markdown I can paste in. Don't include the actual content: just the structure with placeholder text where my group will fill it in.

What you carry out of this lesson: the survival kit, in one place

Day 1: Role-Split prompt + 3-Week Timeline prompt + Kickoff Message prompt + Shared Doc Setup prompt. 30 minutes total.
When someone goes quiet: Three levels of the Polite-But-Firm Nudge: gentle (Day 3), specific deadline (Day 5–7), prof email (last resort).
When the group dynamic breaks: Four scripts: dominant member, scope creep, last-minute panic, post-mortem decision.
Save them in your Coach. Drop these prompts into your Coach Project (Module 7) under group_projects.md. Next semester's group project starts with you already armed.

Honest Work Code · all three rules apply to group work too

Rule 1 (learn with it, not instead of it): AI helps you coordinate; the actual research, writing, and analysis still has to be yours and your teammates'. Rule 2 (your work survives scrutiny): if a teammate says "I had AI write this section," that section gets the same treatment as your own AI-assisted writing: Module 4 rules apply across the whole submission. Rule 3 (respect the rules of the room): some profs explicitly disallow AI on group projects. Read the assignment. Ask. Don't assume "everyone uses it" is a defense: it isn't, and group projects are exactly where one person's AI use becomes the whole group's grade problem.

Up next: 8.4: Money Basics, Budgets & the "Not Financial Advice" Guardrails

You're caught up on schedules and group projects. Next: money. Building a basic dorm/college budget, tracking what you actually spend, and the bright line that runs through the whole lesson: AI is good at organizing money, not at deciding it.

Continue to 8.4:Money Basics →