
Group Project Writing: Fixing the One AI Paragraph Everyone Notices
One ChatGPT paragraph in a shared Google Doc stands out against three human voices. Who edits last, how to match voice, and how to disclose team AI use.
Group papers fail in a specific way when AI enters the shared Google Doc: three sections sound like your teammates. One sounds like a press release.
That paragraph is usually the night-before ChatGPT paste. It is grammatically cleaner than the rest. It cites "studies" with no page numbers. It never mentions the interview you actually ran.
Humanizing group writing is not a full-document rewrite. It is voice consistency, a last editor who owns seams, and disclosure the whole team can stand behind.
Short Canvas replies: How to Humanize AI Discussion Posts. Solo essays: How to Humanize a ChatGPT Essay. Team ethics: Checklist for Ethical AI Use in Academia.
Why one AI paragraph stands out
| Tell | What the instructor sees |
|---|---|
| Register jump | Section 2 hedges; section 3 is textbook-smooth |
| Missing project facts | No quote from your survey, lab, or site visit |
| Citation style drift | One author used real sources; the AI block invented two |
| Pronoun / we mismatch | "This paper argues" vs "we found on Tuesday" |
| Length and rhythm | Even sentences in a sea of messy student prose |
Detectors may flag the block. Peers and TAs often notice first. The rest of the paper becomes evidence.
Agree before anyone opens ChatGPT
Write this in the shared doc, even if it is four bullets:
- Allowed uses for this assignment (outline only, grammar only, banned)
- Who verifies every citation
- Who does the voice pass (one last editor, not four competing rewrites)
- Disclosure sentence you will all sign if the course requires it
If one member cannot afford a paid tool, do not make paid AI a requirement for their section. Fair split of work is an integrity issue, not a niceness issue.
Workflow that keeps four voices honest
1. Outline together, draft apart
The group owns the thesis and the evidence list. Individuals write from that list. Do not let a model invent a finding nobody collected.
2. Paste only your own notes into any draft prompt
Ban "write section 3." Require named data: interview initials, table numbers, assigned readings. Mark gaps [NEED FROM TEAM] instead of guessing.
3. Merge, then hunt seams
Read the compiled draft aloud. Circle every paragraph that could belong to a different course. Those are the AI or copy-paste blocks.
4. One Human Writes pass on stiff seams only
Paste the mismatched paragraphs into Human Writes, not the methods table and not the quotes. Humanize once. Then put back a detail only your group has: the failed recording, the store that would not talk, the lab that ran late.
5. Last editor owns pronouns and tense
Pick one person to make "we" / "the team" / "this study" consistent. That person also re-checks citations. They are not rewriting everyone else's argument.
Before and after (the obvious section)
AI paste in a four-person paper:
It is important to note that consumer behavior is a complex phenomenon influenced by a variety of socioeconomic factors. Furthermore, this study contributes to the existing literature.
After the team's facts + one voice pass:
Shoppers in our three-store sample mentioned price first, then wait time. We only got usable interviews at Store B; the manager at Store A declined. That gap is why we do not claim a city-wide pattern.
Same assignment. Second version survives "who wrote this?" in the presentation.
What not to do
- Do not humanize the entire compilation so it all sounds like one chatbot.
- Do not "fix" a teammate's ESL grammar into generic academic English without their OK; that can look like ghostwriting and can false-positive.
- Do not leave invented sources because "the rest of the paper is fine."
- Do not hide AI use if the syllabus requires disclosure. The group, not the person who clicked paste, usually owns the file.
Detector notes
A mixed human-AI paper can flag and a fully human paper with one over-edited section can flag. Treat scores as a review signal. See Can Professors Detect AI Writing?.
The fix is still the seam: add the project-specific sentence, then one polish pass.
Bottom line
In a group doc, the tell is contrast. Match evidence first. Then use Human Writes on the paragraph that does not sound like anyone on the team. One last editor. One disclosure line if required.
Paste the stiff section on Human Writes after the shared facts are locked.