01What the role actually costs.
The coordination job is invisible in the deliverable and enormous in the week. Chasing people who have not replied. Deciding things nobody else will decide. Merging pieces that arrived in four different shapes. Being the person who notices, on a Thursday, that a section has not been started.
None of that appears in the document a marker reads, which is the whole problem. The work is real, it consumes evenings, and there is no row on the sheet awarding it. Somebody who both coordinates and writes their own section has done two jobs and will be marked for one.
It also lands unevenly and predictably: on the person who replies first, on the one with visible organisational competence, and disproportionately on the person who has already been that person before and is therefore known to do it.
02Declining without becoming the difficult one.
The move is not refusal, which reads as disengagement, but redistribution. Four ways, in rough order of how well they work.
- Propose a structure instead of taking a role. Suggesting that somebody owns each section, somebody merges, and a date exists is leadership without becoming the leader, and it usually gets accepted because nobody objects to structure.
- Volunteer for a defined job early. Taking the section you want, explicitly and first, is much easier than declining an undefined one later.
- Name the merge as a job rather than a leftover. Once compiling is described as work, groups allocate it deliberately instead of leaving it to whoever cracks first.
- Rotate it out loud where a course has several group tasks, which most groups will accept as fair because it obviously is.
- And where you do take it, say so as a contribution rather than absorbing it silently, because a group that knows somebody is coordinating behaves differently from one that assumes it happens by itself.
03When taking it is the right call.
Sometimes it is, and pretending otherwise would be dishonest. Where the mark genuinely matters and the group looks likely to produce something incoherent, coordinating is the cheapest insurance available, because the alternative is a document you cannot control carrying your name.
It is also worth taking deliberately in a course where you have capacity and the other work is light, banking the goodwill for a term where you do not. Groups remember who did it last time, and that memory is usable.
What is not defensible is ending up with it by default, in silence, every single time, purely because nobody else spoke first. That is how a person finishes four modules having done two jobs in each and calls it being organised, when it was unpaid labour nobody requested and no sheet records.
04The record that protects you either way.
Keep a dated note of what you handed to the group and when. It costs nothing, it is a by-product of doing the work, and it is the only evidence that survives if the thing comes apart.
Where a course runs peer evaluation, fill it in specifically and factually rather than kindly. A vague positive assessment of somebody who did nothing removes the only lever an instructor has, and those get written constantly out of embarrassment.
And where a group is coming apart, write to your instructor while it is coming apart. A note filed in the middle of the trouble protects you; the same account delivered once the date has gone reads as an excuse no matter how accurate it is. That timing rule appears again in the issue on writing to a professor, and it is the most dependable protection available to anybody.
05Why coordination costs what it does.
Worth understanding rather than simply enduring. What it takes to coordinate grows with headcount rather than with page count, because every pair of people in a group is another channel that can fall silent, disagree, or do the same thing twice.
So four people working together can eat more of a week than one person writing the entire document would have, and the extra is invisible because it disappears into messages, waiting and reconciliation. None of that reaches the page anybody marks.
Which makes the twenty minutes spent in week one writing down who owns what the highest-return time in the entire project, and the reason it is so rarely spent is that in week one nothing has gone wrong yet. Where the group has already come apart, what can and cannot be salvaged is set out at the business desk.
Questions at this desk.
Will declining make me look uncooperative?
Not if you propose structure or take a defined section instead. What reads as uncooperative is silence, not a refusal of one particular role. Suggesting that somebody owns each part and a date exists is visibly constructive and it removes the vacuum that produced the role in the first place.
Nobody will take the merge. What then?
Suggest rotating it where the course sets several group tasks, or swap it for a shorter writing share, since it is genuine work and deserves treating as such. What fails is leaving it unassigned and hoping: the person who ends up with it is whoever loses their nerve first, at the last possible moment.
Should I do somebody else's section if they vanish?
Sometimes, and make it visible when you do. Write to the instructor while it is happening rather than once the deadline has passed. Absorbing the work in silence saves this mark and sets you up for the same position again, because nothing on any record shows that the imbalance existed.
Does any of this get marked?
Rarely, directly, which is precisely the point of this issue. Some courses award a portion for process or use peer evaluation, and where they do, that is worth reading carefully at the start. Where they do not, coordination is unpaid work and should be allocated knowingly rather than absorbed.
Notes in the margin, from the people at the desks.
READ THE LETTER