Group Project Workload Splitter

How this is calculated

THE MISTAKE IS DIVIDING ONLY THE DELIVERABLES. A group splits four sections between four people, everyone writes their part, and nobody has allocated the work of merging them into one document with one voice, one reference list and one format. That work is real, it is usually done by one person, and it lands in the last week. SHARED WORK IS THE PERCENTAGE THAT CANNOT BE DIVIDED: integration, meetings, planning, formatting, the final read-through, and rehearsing anything presented. It is entered separately because it does not shrink when the group grows. ⚠️ SHARED WORK PER PERSON RISES WITH GROUP SIZE, and this is the counterintuitive part. Meetings are the clearest case: a one-hour meeting costs one hour of individual time but SIX person-hours in a group of six. So a bigger group divides the divisible work more finely while spending more total effort on coordination. That is why five people are not five times faster than one. THE COORDINATION SHARE output makes that visible. When it passes about a third, the group is spending more time organising than producing. The usual driver is MEETINGS rather than the shared-work percentage: the defaults here land at 44%, and 24 of those 96 person-hours are meeting time. A group too large for the task, or too much declared shared, are the other two causes. EFFECTIVE HOURS PER PERSON is total hours divided by the group, which is the number people should agree on at the start rather than discover at the end. ⚠️ THIS ASSUMES EVERY HOUR IS EQUIVALENT AND EVERY MEMBER CONTRIBUTES. Neither is reliably true. It also cannot account for skill differences: the person who formats the document quickly should probably do it, and a strictly equal split is not always the fairest one. CONTINGENCY IS SEPARATE AND DELIBERATE. Group projects overrun more than individual ones because a delay by one person blocks others, and a buffer that is not planned gets taken from the integration time.

Common questions

Why does the shared work matter so much?

Because it is real work that usually goes unallocated. A group splits four sections between four people, everyone writes theirs, and nobody has been given the job of merging them into one document with one voice, one reference list and one consistent format. That job exists regardless, it typically lands on one person, and it lands in the final week. Naming it as a percentage up front is what turns it from a crisis into a task with an owner.

Why does a bigger group not go faster?

Because the shared work does not shrink when the group grows, and meetings actively get more expensive. A one-hour meeting costs one hour of your time and six person-hours in a group of six. So a larger group divides the divisible work more finely while spending more total effort on coordination. That is the whole reason five people are not five times faster than one, and the coordination-share output is there to make the trade visible rather than theoretical.

What is a reasonable coordination share?

There is no universal figure, but the output is there so you can watch it move. When it passes about a third, the group is spending more time organising than producing, and the usual driver is meetings rather than the shared-work share — the defaults here land at 44%, with 24 of 96 person-hours spent in meetings. A group too large for the task, or too much work declared shared, are the other two causes. All three are fixable at the planning stage and almost impossible to fix in the final week.

Should everyone really get the same hours?

An equal split is a starting point, not a fairness rule. It assumes every hour is equivalent and every member contributes, and neither is reliably true. It also ignores skill: the person who can format a document and fix the reference list in an hour should probably do it, even though someone else might take three. A good split allocates by hours and by capability, and says out loud who owns integration — which is the task most likely to be nobody's.

Why plan contingency separately?

Because group projects overrun more than individual ones, for a structural reason: a delay by one person blocks the people whose work depends on it, so slippage compounds rather than just adding up. If contingency is not planned explicitly it gets taken from somewhere, and the thing it is always taken from is the integration time at the end — which is the work that determines whether the final document reads as one piece or four.

Take it further with AI

Copy this into ChatGPT or Claude with your own numbers filled in. It hands over the figures this calculator worked out, so the answer is built on real arithmetic instead of a guess.

I used the Group Project Workload Splitter at https://www.bfcbrilliance.com/tools/group-project-workload-splitter.

What I entered:
- Total work in the project (hours): ___
- People in the group (people): ___
- Work that can't be divided (%): ___
- Meeting hours planned (hours): ___
- Contingency (%): ___

What it calculated:
- Hours per person: ___
- Your own section: ___
- Your share of the shared work: ___
- Meetings cost the group: ___
- Time spent coordinating: ___

Use those figures as given — they are already worked out, so please don't recalculate or estimate your own. Help me turn them into a plan: what to buy or do, in what order, roughly what it should cost, and the mistakes people most often make with this job.

More study planning tools