Group Project Flagged for AI When You Didn't Use AI: What to Know
You wrote your portion by hand. The AI flag covers the whole document. Here is what the documentation actually says, and what it does not say.
HumanPen Team
· 16 min read
The flag covers the whole document, not individual authors
Group projects create a specific problem with AI detection. The submission is one document, and the detector evaluates the full text. It does not separate contributions by author.
Turnitin describes the mechanism this way: "When a paper is submitted to Turnitin, sentences from the submission are extracted and segmented into overlapping sections for prediction analysis. Each segment is classified by the AI detection model and given a value between 0 and 1, denoting the probability of the text being likely human or AI-generated."
This means the model scans every segment of the document. If one group member used an AI tool for their section, those segments will carry a high probability score. The overall percentage reflects the entire submission, not just your part. You could have written every word of your section yourself, and the document still shows an AI percentage because the score is aggregated.
The score is not the sole basis for action
If you see an AI percentage on a group project, it is natural to worry about what happens next. The documentation is explicit about how the score should be used.
Turnitin states: "Hence, we must emphasize that the percentage on the AI writing indicator should not be used as the sole basis for action or a definitive grading measure by instructors."
This is a direct statement from the documentation. The percentage is one piece of information. It is not a verdict. The documentation also says: "It is not meant to provide definitive answers in isolation. More important than any tool is the educator who sees the score and makes decisions balancing this information with their personal knowledge of their students, their work, and institutional policy."
For a group project, this matters. Your instructor is expected to weigh the score alongside their knowledge of the students, the assignment, and the institution's policies. The score alone does not determine the outcome.
The score is a single data point
The documentation reinforces this idea with specific language about how educators should interpret the percentage.
"When educators look at the AI writing score and utilize it as a single data point rather than a definitive response, then it is being used as intended."
A single data point. That is how Turnitin describes its own indicator. In a group project scenario, this is important context. The flag does not prove who used AI. It does not prove that you used AI. It signals that some portions of the document resemble AI-generated text, and the educator is expected to investigate further. What your instructor is told to do when your AI percentage is high sets out what that is supposed to look like.
Some texts are more prone to false positives
If your section was flagged and you know you wrote it yourself, there is a documented explanation. Turnitin acknowledges that certain types of writing are more likely to produce false positives.
"Sometimes false positives (incorrectly flagging human-written text as AI-generated), can include content without a lot of structural variation, text that literally repeats itself, or text that has been paraphrased without developing new ideas."
Group projects can produce exactly these patterns. If multiple group members write in a similar style, the text may lack structural variation. If someone paraphrased source material without adding original analysis, that section may trigger a flag. If your own section uses repetitive phrasing because of the topic, it could be caught.
The documentation continues: "If our indicator shows a higher amount of AI writing in such text, we advise you to take that into consideration when looking at the percentage indicated."
In other words, a high percentage on text with these characteristics deserves extra scrutiny rather than immediate conclusions. Flagged, but you wrote it yourself covers how to make that case for your own section.
You may not see the score at all
There is another layer to this. As a student, you might not have direct access to the AI report.
"Please note, only instructors and administrators are able to see the indicator."
And: "The AI writing detection indicator and report are not visible to students."
This means you might hear about an AI flag from your instructor without seeing the actual percentage or the report yourself. The documentation does offer one path for sharing: "However, with the PDF download feature, instructors can download and share the AI report with students."
If your instructor shares the PDF report with you, look at which sections are highlighted. In a group project, this can help you and your group understand which parts of the document triggered the flag. If the highlighted sections correspond to a specific group member's contribution, that is relevant context for a conversation with your instructor. How to read a Turnitin AI writing report covers what the highlights on that PDF actually mean.
What to do if your group project gets flagged
Here are practical steps based on what the documentation says.
First, remember that the score is one data point, not a definitive answer. The documentation says instructors should balance the score with their knowledge of students and institutional policy.
Second, look at the false positive features. If your section lacks structural variation, repeats phrases, or paraphrases without new ideas, the documentation acknowledges these can trigger false positives. This is worth discussing with your instructor.
Third, ask your instructor to share the PDF report if you have not seen it. The documentation confirms instructors can download and share the AI report. Seeing which sections are flagged can help you understand the situation.
Fourth, talk to your group. The flag covers the whole document, and the mechanism analyzes segments across the entire submission. Understanding which sections triggered the flag is a group conversation, not an individual one.
Finally, remember that the documentation itself advises caution. The percentage is not the sole basis for action. If you wrote your section yourself, the documentation supports a conversation about context rather than a rush to judgment. Per-member drafts help there, and how to keep version history in Word, Google Docs and Overleaf covers turning that on.
KEEP READING