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.A real conversation on the left — and the plan Voko kept from it on the right. Scroll either side.
MKT201 group project
Internal deadlines before the real one
Work back from the due date:
- Submission — the real deadline.
- Final edit done — two days before.
- All pieces handed to the person combining them — three or four days before.
- 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 freeMore guides
Study Group Planner
Run a study group that actually covers the syllabus
How to plan a small team offsite
Write down the two or three outcomes the offsite is for, then fix the date and a place within easy reach. Ask the team what they want to discuss before you build the agenda, keep sessions to a few per day with real breaks, and end with a written list of decisions, owners and dates. Six to eight weeks of lead time is enough.
What to do when bridesmaids don’t respond in the group chat
Ask one closed question at a time, with a deadline and a default (“reply by Friday — no answer means the €60 option”). Write each decision down somewhere everyone can see, so nobody has to scroll. Follow up privately with the one or two people who haven’t answered rather than tagging them in front of the group.
How to pick dates for a group trip
Collect everyone’s hard no’s first, then offer two or three specific date windows instead of asking when people are free. Give the vote a deadline — 48 hours is plenty — and lock the dates as soon as enough people commit, even if one person still can’t make it. Dates first; destination and budget come after.