Group Projects With ADHD: Roles, Check-Ins and Not Being Flaky

The group chat has 212 unread messages. Someone made a shared document you have not opened. Your section is due to the group on Friday, you have not started, and the thing you dread is not the work. It is the moment you have to say so. Group projects with ADHD have a specific shape: your lateness is public, your part sits on someone else's path, and the group remembers.

This is a practical guide for college and university group work. Which role to take and which to avoid. How to set the group up so the structure does the remembering. What to say when you are behind. And whether to tell anyone about the ADHD, a question most students answer by saying nothing, which is usually the worst of the options.

Why group work exposes ADHD differently than solo work

On a solo assignment, the deadline crunch is private. You can start at 11 p.m. the night before, hyperfocus until 4 a.m., and hand in something decent. Nobody sees the method. In a group, your section is due days before the real deadline so someone can merge it, which removes the one strategy that has always worked for you. There is no last-minute rescue, because the last minute belongs to someone else.

Group work also leans on exactly the skills ADHD affects most. Meetings happen out loud, so decisions live in working memory unless somebody writes them down. Tasks are assigned verbally and half-remembered. The group chat competes with every other notification. And there is a social performance running the whole time: tracking who said what, reading the room, not interrupting. Many students with ADHD respond in one of two ways. They over-function and quietly take on half the project because that feels safer than depending on their own follow-through. Or they go quiet, miss a check-in, and become the person the group talks about. Neither is a character flaw. Both are predictable, and both can be designed around.

Picking the role that fits (and the one that doesn't)

Roles get handed out in the first ten minutes and nobody thinks hard about them. You should. The best roles for ADHD share three features: they are front-loaded, they have a clear definition of done, and they do not depend on everyone else finishing first.

• Good fits: the opening research sprint, the first draft of a section, the slide design, the presenter. These are bounded, interesting at the start when your energy is highest, and due early so a slip has room to recover.
• The one to avoid: the final integrator. The person who merges everyone's parts, fixes the formatting and submits. That job starts only when the last teammate delivers, usually late, so it lands on the final night with zero buffer. It is the highest-risk role in the project and it is routinely volunteered for by the most conscientious person in the room.
• A tempting trap: project manager. You can see everything that needs doing, which makes this feel like your job. It is only a good fit if the shared board tracks the tasks, not your memory.

If you are stuck with the integrator role, split it. One person merges, another proofreads, and the internal deadline for all sections moves three days earlier. Breaking the work into small pieces with their own dates is the same approach that works for large solo assignments; it just needs to be agreed out loud in a group.

A shared board and a 48-hour check-in rule

Propose this in the first meeting, before anyone has had the chance to be late. It is two things.

A shared board, wherever the group already lives: a table in the shared document, a Trello or Notion board, a Teams planner if the course uses it. Every task has an owner and a date. Decisions made in meetings go on the board within the hour, by whoever is typing. If it is not on the board, it was not decided. This is good practice for every group and it quietly removes the working-memory tax for you.

And a 48-hour check-in rule: nobody goes more than two days without posting one line in the group chat. 'Draft half done, finishing Thursday.' 'Nothing yet, blocked on the data, will ask the TA tomorrow.' 'Done, it's in the doc.' The rule is for everyone, so it does not single you out. For a brain prone to waiting mode and avoidance, it makes a small, frequent, low-stakes report the default instead of a big, late, high-stakes confession. Set a repeating reminder for your own check-in, and pin the group chat so it is not buried under everything else.

Communicating a delay before it becomes a problem

You will be behind at some point. The difference between a schedule change and a reputation is timing. A delay announced when you are halfway through is logistics. A delay announced at 11 p.m. the night it was due is something the group has to absorb. The ADHD trap is the guilt-silence loop: you are behind, you feel bad, you avoid the chat because of the feeling, and the silence makes it worse. Break it with a script you can send without thinking.

1. State it plainly. 'I'm behind on the methods section.'
2. Show what exists. 'I have the outline and two paragraphs in the doc.'
3. Give a new time, with a clock time, not a day. 'I can have the full draft in by Thursday at 6 p.m.'
4. Offer a trade. 'If that's too late, I can hand the second half to someone and take the references list instead.'

Four lines. Send it the moment you know, not when you have fixed it. Groups forgive delays. What they do not forgive is finding out at the merge. If time blindness means you genuinely do not notice you are behind until it is late, that is what the 48-hour rule is for: the check-in forces the comparison between where you are and where you said you would be.

Disclosure: what to tell the group, if anything

You do not owe your group a diagnosis. There are three options, and the right one depends on the group and on you.

• Say nothing about ADHD, but say how you work. 'I'm much more reliable with written tasks and clock-time deadlines, so can we keep everything on the board?' This gets you most of the structure with none of the disclosure.
• Partial disclosure. 'I have ADHD, so I'll be asking for things in writing and doing check-ins. It's not a big deal, it just helps.' Works well in a group you trust, and it makes your check-ins read as a system rather than anxiety.
• Full disclosure plus formal accommodations. If you are registered with the accessibility office, some accommodations can extend to group work, but a shared deadline is harder to move than an individual one. Talk to the instructor early, not the group.

If you have not yet registered, the process is covered in our answer on how ADHD accommodations work at Canadian universities and colleges. Accommodations are rarely a solution to group dynamics on their own, but a letter on file gives you and the instructor a starting point if a project goes badly for reasons connected to ADHD.

What to try at the first meeting

1. Ask for a front-loaded role with a clear finish line, and decline the final integrator job unless it is split.
2. Propose the shared board and the 48-hour check-in rule before roles are even finished. Frame it as good for everyone, because it is.
3. Move the internal deadline for all sections to three days before the real one.
4. Save the four-line delay script in your notes app so it is ready the day you need it.
5. Decide now which disclosure option you are using, so you are not deciding it at 11 p.m. under stress.

Group projects will never be the format ADHD was built for. But most of what makes them go wrong is the absence of structure, and structure is something you can bring to the first meeting, regardless of whether anyone else in the room needs it as much as you do.