How to Split Group Project Work Fairly

The work nobody allocates

Four people, four sections, one deadline. Everyone writes their part.

Then someone has to merge four documents written in four voices into one, reconcile four reference lists, fix the formatting, and read the whole thing to check it argues one case rather than four.

That work is real. It is usually nobody's job. And it always lands in the final week.

Why a bigger group isn't faster

The shared work doesn't shrink when the group grows. Meetings get actively more expensive.

A one-hour meeting costs you one hour. In a group of six it costs the group six person-hours:

Group size	A 1-hour meeting costs
2	2 person-hours
4	4 person-hours
6	6 person-hours

So a larger group splits the divisible work more finely while spending more total effort on coordination. That's the whole reason five people aren't five times faster than one — and it's why adding someone to a struggling project rarely helps.

The coordination-share output exists to make that trade visible while you can still do something about it. Past about a third, the group is spending more time organising than producing. On the defaults here it reads 44% — and 24 of those 96 person-hours are meetings, not integration. That is usually the first thing to cut.

Name an owner for integration

This is the single most useful thing to do at the first meeting.

Not "we'll sort it out at the end" — a name, next to the word integration, on the plan. Same for formatting and the reference list, which are the other two jobs that quietly belong to nobody.

The person who owns integration should also get a smaller section, because integration is not a small job and pretending it is guarantees it gets done badly at midnight.

Set an internal deadline

Group projects overrun more than individual ones for a structural reason: a delay by one person blocks the people whose work depends on it. Slippage compounds rather than adding up.

So the sections need to be due to the group before the project is due to the module — far enough ahead that integration has room. A week is not excessive on a substantial project.

If contingency isn't planned explicitly it still gets taken from somewhere, and the thing it's always taken from is the integration time at the end. Which is exactly the work that decides whether the final document reads as one piece or four stapled together.

An equal split isn't always the fair one

The tool divides hours evenly because that's the honest default, but it's a starting point rather than a rule.

It assumes every hour is equivalent and every member contributes. Neither is reliably true. It also ignores skill entirely: someone who can fix a reference list and unify the formatting in an hour should probably do it, even if it would take another member three.

A good split allocates by hours and by capability, and writes down who owns what. The alternative — an unspoken assumption that it'll even out — is how one person ends up doing the integration, the formatting and their own section.

Agree the boring things first

Format, citation style, file naming, where the files live.

These sound trivial and they're responsible for a large share of the integration effort. Four sections in four citation styles is an hour of somebody's life that a two-minute conversation at the first meeting would have saved.

Agree what happens when someone misses an internal deadline, too. Not as a threat — so that the answer exists before it's needed, rather than being invented under pressure by whoever is most annoyed.