Thoughtful choices. Everyday life.

EducationThe Roswren edit

How to plan a group project before dividing the work

People discuss notes on paper at a table with two open laptops.
Illustrative group-planning photograph. Photo: Scott Graham / Unsplash (Unsplash License).

Before splitting a group assignment into sections, agree on what the finished work needs to do. Then give each task an owner, a clear output and time for review.

Your shared plan should answer four questions: What are we making? Who is doing what? When can the next person use it? How will we check the whole project?

Agree on the finished assignment

Read the brief together. Note the required output, deadline, length or presentation time, assessment criteria and any individual submissions. Check which decisions or activities must be collaborative before deciding what to split up.

Collaboration requirements differ between assignments. In its guidance for designing group projects, Carnegie Mellon University’s Eberly Center notes that some instructors permit separate tasks while others expect more joint work. Ask your teacher or tutor about anything unclear rather than assuming your preferred approach is allowed.

Write a short description of the result you are aiming for. In a hypothetical presentation assignment, that might be: “Explain the problem, compare two possible responses using evidence, and justify our recommendation within eight minutes.” This gives the group something more specific to discuss than “make the slides”.

Also check the course rules for sources, outside assistance and AI tools. Your group agreement cannot override those rules.

Describe tasks as things someone can use

Turn vague jobs such as “research” into usable outputs: for example, “notes comparing the two options, with source links and a proposed conclusion”.

For each task, record:

  • Output: the file, notes, draft or other contribution to produce.
  • Owner: the person coordinating its completion.
  • Reviewer: someone who will check it against the brief.
  • Ready date: when the reviewer or next contributor needs it.
  • Dependency: anything that must be decided or supplied first.

The owner need not do every part alone. Joint work may be required, and anyone can ask for help. The fields make the next action clear.

Include coordination, source checking, editing and submission in the workload discussion. Do not leave them as unassigned jobs for whoever happens to notice. Ask what each member can realistically take on, including any access needs, without requiring private explanations for their availability.

Work back from a complete draft

Start with the submission deadline and reserve time before it for checking and corrections. Set the first complete draft earlier still, then schedule the smaller handovers it depends on.

The University of Waterloo’s group-work guide recommends a timeline, including time to review each other’s contributions or practise a presentation. Treat assembly as scheduled work, not a final copy-and-paste task.

A hypothetical two-week plan

Imagine four students have two weeks to prepare the eight-minute presentation described above. Adapt this example to your assignment; it is not a tested schedule.

  • Day 2 — Shared outline: All four agree on the outline and comparison questions.
  • Day 5 — Evidence notes: Amina prepares notes on option A; Ben prepares notes on option B. They review each other’s notes.
  • Day 7 — Comparison draft: Chen drafts the comparison using both sets of notes. Dev reviews it.
  • Day 9 — Complete presentation: Dev coordinates assembly from everyone’s agreed material. All four review it.
  • Day 11 — Rehearsal: All four practise together and record the corrections needed.
  • Day 13 — Checked file: Dev prepares the submission file. Everyone checks their contributions, and Amina checks the upload requirements.
  • Day 14 — Submission: The agreed uploader submits the checked file and confirms receipt with the group.

Replace the day numbers with real dates and times that fit your assignment and availability, leaving room for corrections or unexpected problems.

Chen needs both sets of evidence notes before drafting the comparison. If one set is late, that affects more than one person’s task. Mark that dependency on the plan and agree what to do if either set is late.

Dev’s assembly work also counts as a contribution. Review the balance before agreeing to it: the list alone does not establish equal effort. Everyone remains responsible for supplying usable material and making agreed corrections to their own work.

Agree how decisions will be recorded

Choose a shared location everyone can access for the current files and plan. Test access before relying on it. Keep decisions there even if the conversation happens in a chat or meeting.

Agree which channel to use for questions, how soon replies are expected and how to flag a delay. A reply by the following evening might suit one group and not another; agree a window that works with members’ schedules.

End each check-in by recording the decision, next action, owner and date. For example: “Use the same comparison questions for both options. Amina and Ben will update their notes by Day 5, before Chen starts the comparison.” Record what needs to happen, not just what was discussed.

Deal with blocked work while there is time

If a handover is missing, ask about the specific task rather than assuming why it is late. Waterloo’s advice on group-project challenges recommends reviewing responsibilities, asking whether support is needed and seeking help from the instructor or teaching assistant if problems persist.

An initial message could be: “We need the option B notes before we can write the comparison. What is ready, and what would help you finish the rest?”

Agree any revised handover together and update the plan. If the new timing puts submission at risk, contact your instructor or teaching assistant promptly. Keep a factual record of tasks and decisions; do not invent penalties or change another person’s assessed responsibilities without checking the course rules.

Check the project as a whole

Before submission, return to the original brief. Does the assembled work answer the question? Are the sections consistent? Can you trace the evidence to the sources? Is any requirement still unassigned?

For a presentation, run it in order and check the timing and transitions. For a written project, read across the sections for repeated points, missing explanations and contradictory conclusions. Agree who will upload the correct version and how the group will confirm it was received.

A plan cannot guarantee a grade or prevent every disagreement. Its purpose is to make responsibilities, dependencies and unfinished work clear enough for the group to act on them.