Divide a group project into work that fits together

Agree what the group is producing

Read the brief together and list the required outputs, such as a report, dataset, presentation or appendix. Confirm the audience, scope and criteria. Ask each person to explain the task in their own words so differences appear early. Record unresolved questions for the tutor rather than letting separate interpretations guide the work.

Identify decisions that affect everyone, including the case, research question, terminology and method. Make these decisions before allocating large writing sections. If the project compares two cases, agree the basis of comparison so one person does not collect financial measures while another collects unrelated descriptive material.

Break the outcome into checkable tasks

Describe tasks by what another person will receive. 'Supply a table of the selected evidence with sources and limitations' is clearer than 'do research'. Include preparation, analysis, drafting, checking and integration. Assigning only the visible final sections leaves essential coordination work unowned.

For each task, note what must exist before it can start. Analysis may depend on cleaned data; the conclusion depends on the group's findings. Put these dependencies in a simple table or shared task list. You do not need specialist project software if the group can see the order and status clearly.

Allocate with capacity and learning in view

Discuss availability, relevant experience and what each person wants to practise. Share less visible jobs such as arranging meetings and checking references. Avoid assigning one person all technical work simply because they have done it before; agree support or pairing where that helps the whole group learn.

Give every task one named coordinator while allowing collaboration. Record a due date for a usable draft and what 'usable' means. The coordinator is responsible for making progress visible, not necessarily completing every element alone. Confirm that everyone accepts the allocation and can raise a problem before the internal deadline.

Review intermediate outputs

Schedule short reviews at points where work feeds another task. Check whether the evidence answers the agreed question and whether assumptions remain consistent. If something is missing, identify the effect on the next step and agree a revised plan. Do not wait for a polished section before discovering that the underlying approach differs.

Keep comments specific and actionable. Instead of asking for 'more detail', identify which claim lacks evidence or which method step is unclear. Record decisions that change the shared approach so other members do not continue using an outdated version of the plan.

Integrate as a shared responsibility

Leave time for the group to read the complete output. Check that sections use consistent definitions, do not contradict each other and lead to a supported conclusion. Give someone responsibility for assembling the file, but have others inspect the result. Integration should not become an invisible emergency job for the last person online.

Before submission, confirm contribution records and any group declarations required by the module. Check the final file together and agree who submits. Keep the receipt accessible to the group. Afterwards, note which task boundaries worked and which created unnecessary handovers so the next project can start with a better division of work.

Your next steps

• Agree shared decisions before dividing the work.
• Describe tasks by outputs another person can use.
• Record dependencies, coordinators and internal dates.
• Reserve time for the whole group to inspect the integrated result.

Keep planning

• Turn module handbooks into one assessment calendar
• Plan independent study using real task estimates
• Translate an assignment brief into writing decisions
• Turn tutor feedback into a plan for the next assignment