How to divide work in a group project

Split the project into deliverables — finished pieces someone can hand over — and give each one a single owner. Set internal deadlines three or four days before the real one, so there’s time to combine and fix things. Keep one shared list of who owns what and when it’s due, and check it at a short weekly meeting.

Divide by deliverable, not by section

The usual split — "you do the intro, I'll do the method, you do the results" — sounds fair and works badly. Sections depend on each other: the results can't be written before the method is settled, and the intro can't be written before anyone knows what the results are. One slow person blocks everyone.

Split by deliverables instead: pieces that are finished on their own and can be handed over.

  • "The survey, built and sent to 50 people."
  • "The data cleaned and the three charts made."
  • "The slide deck, designed, with placeholders for numbers."
  • "The final report, edited into one voice."

Each one has an obvious "done", which is exactly what a section of an essay doesn't have.

One owner per piece, and say it out loud

Every deliverable gets one name. Two people can work on it, but one person owns it — that's who the group asks about it and who says when it's done.

Let people pick first, based on what they're good at or want to learn, then assign what's left. Write the list down where everyone can see it. A split that only exists in a voice call on Tuesday will be remembered four different ways by Friday.

Someone should also own putting it together: combining the pieces, making the formatting consistent, submitting. That's real work, and it's the job that most often falls on whoever cares most at 11pm the night before.

A worked example

Four students have a marketing research project due on Friday 11 December: a survey, an analysis, a 10-minute presentation and a written report.

A real conversation, and the plan it produced. Tap Plan to see the other half.

MKT201 group project

Leo
Let’s split by what we hand in, not by report section. Four pieces: survey, analysis + charts, slides, final report.
Ema
I’ll take the survey, I did one last semester.
Analysis + charts for me.
Tin
Slides. I’m bad at writing but fine at design.
Leo
Then I’ll do the final report and put everything together.
Ema
Survey goes out Monday the 23rd, closes Sunday the 29th.
So I can have charts by Thursday 3 Dec if the data comes Monday the 30th.
Leo
Everything to me by Monday 7th, I edit till Wednesday, we submit Thursday — one day spare.
Tin
Can we do a 15-min call every Monday to check?
Who’s behind?Add a check-inDraft the survey questions
Type your preferences, or @voko to ask...

Internal deadlines before the real one

Work back from the due date:

  1. Submission — the real deadline.
  2. Final edit done — two days before.
  3. All pieces handed to the person combining them — three or four days before.
  4. Check-in — a week before, where each owner says "done", "on track" or "stuck".

The gap between steps 3 and 1 is what saves the project when someone's part comes in late or turns out to need rewriting.

Keep check-ins short and regular

A fifteen-minute call once a week does more than a long meeting every now and then. Each owner answers three things: done, on track, or stuck — and if stuck, on what. Nothing else. Problems surface while there's still time to fix them, and nobody has to read back through a week of messages to find out where things stand.

Update the shared list straight after the call, not before the next one. If a date moves, move it in the list and say so in the chat, so the person combining everything isn't working from a plan that's a week old.

Between calls, keep questions in one thread rather than in private messages. "Which chart style are we using?" answered once, in front of everyone, saves the same question being asked three times.

When someone doesn’t deliver

It happens in almost every group. Handle it early and in steps:

  • At the first missed internal deadline, message them privately: *"How's the data part going? Need anything?"* Often they're stuck, not lazy.
  • If it's still not moving, agree in the group what happens — someone else takes part of it, and the person picks up something smaller.
  • If the course allows peer review or contribution statements, the shared list of who owned what is your evidence. Don't rewrite history at the end; keep it accurate as you go.

For revision groups rather than graded projects, the study group planner has an example two-week revision schedule. Running a work offsite instead of a class project? See how to plan a small team offsite.

Common questions

What is the fairest way to divide a group project?

By deliverable, with people choosing first and the rest assigned, and with combining the pieces counted as a deliverable of its own. Fair doesn’t mean identical tasks — it means every piece has one owner and roughly similar effort, written down where everyone can see it.

What should you do if a group member does nothing?

Raise it privately at the first missed internal deadline, then agree as a group to move their piece if nothing changes. Keep the record of who owned what accurate as you go, so any peer review at the end reflects what actually happened.

Keep the chat and the plan in one place

Start a plan, drop the invite link in your group, and Voko keeps a written plan — decisions, dates and what's still open — updated from the conversation. Free to start.

Start planning free

More guides

← Back to Study Group Planner