Designing Fairness Into Group Work: A Pre-Project Agreement for UK Teams

Group assignments are a familiar feature of UK degree programmes, and they are intended to develop collaboration, negotiation and project management skills. Yet many teams begin with enthusiasm and no operating agreement. Roles remain implied, response times are assumed, and the first disagreement about a missed deadline or an uneven contribution arrives at precisely the moment when calm discussion is hardest. A short pre-project agreement, often called a charter, addresses this risk before it becomes a problem. It does not need to be lengthy or legalistic. One page, agreed early and stored where everyone can find it, is usually enough.

Why agree the process before the work begins

Most students focus immediately on the task: the report, presentation or prototype. That is understandable, but it skips an important step. A group is a small working organisation, and even temporary organisations benefit from explicit expectations. When expectations are unspoken, people default to their own habits. One student may check messages twice a day; another may expect an immediate reply. One may prefer to decide by discussion; another may want a vote. Neither approach is wrong, but the mismatch can be costly.

A pre-project agreement shifts attention from personality to process. It also supports assessment literacy. If the brief rewards individual contribution, coordinated research or reflective evaluation, the team can design its workflow around those criteria. The purpose is not to create bureaucracy. It is to make the ordinary running of the group predictable, so that creative and analytical effort goes into the assignment rather than into managing uncertainty.

What belongs on a single page

A useful agreement is concise, specific and easy to revise. It should cover six areas.

1. Purpose and shared standard

State the assignment in one sentence and agree what a credible submission looks like. For example, the team might agree that every section will be checked against the marking rubric before it is accepted into the final document. This keeps quality discussions tied to evidence rather than taste.

2. Roles and deliverables

List named responsibilities, not vague titles. Instead of 'research lead', specify who will coordinate sources, who will draft which sections, who will manage the reference list and who will assemble the final file. Include deadlines for each deliverable. Where the brief allows, rotate or share tasks so that no one is left with invisible labour such as formatting, proofreading or chasing updates.

3. Communication and response times

Agree the main channel and a realistic response window. A team might decide that routine messages receive a reply within 24 hours on weekdays, while urgent queries are flagged clearly. Avoid promising instant availability. The aim is reliability, not constant contact. It is also sensible to agree where files will live, such as a shared drive or the university's virtual learning environment, so that work does not disappear into private message threads.

4. Decision-making

Specify how the group will settle disagreements. Simple decisions may be delegated to the responsible lead. Larger decisions might require a discussion and a majority view, with a documented rationale. For tie-breaks, name a fallback such as a short written summary followed by a vote at the next meeting. This prevents repeated circling and reduces the chance that the loudest voice becomes the default authority.

5. Meeting norms

Agree frequency, duration and format. A 30-minute weekly meeting with a clear agenda is often more productive than an open-ended session. Include start and finish times, note-taking arrangements and a rule that decisions are recorded. If meetings are online, ask participants to keep cameras on where practical and to use the chat for evidence links and action points.

6. Escalation route

This is the part teams most often omit. Set out what happens if a member misses agreed commitments, communication breaks down or a contribution dispute arises. A proportionate route might begin with a direct, documented check-in, then a team meeting, then a request for a tutor's guidance where the brief permits it. The agreement should remind members to keep brief records of decisions and contributions. Escalation is not punishment; it is a way to prevent small problems from becoming retrospective accusations.

A ten-minute template

The team can adapt the following structure in a first meeting:

• Assignment and submission date: one sentence.
• Quality standard: the two or three rubric criteria the group will check at every review.
• Roles: name, task, deliverable and due date.
• Communication: main channel, expected response time, file storage location.
• Decisions: who decides routine matters, how larger disagreements are resolved.
• Meetings: day, time, length, agenda owner, note-taker.
• Escalation: first step, second step, when to involve the tutor.
• Review date: when the agreement will be checked and updated.

Everyone should confirm the final version in writing. A shared document with a short message such as 'agreed by all members on this date' is sufficient.

Making it stick without over-managing

A charter works best as a living reference, not a forgotten formality. Revisit it at the midpoint or after a major milestone. If a member's circumstances change, update the roles and deadlines rather than allowing resentment to accumulate. Keep the language neutral. The agreement should describe expected behaviours and routes for resolution, not make personal judgements.

When the agreement is not enough

No document can guarantee equal effort. If a member repeatedly disengages despite clear communication, follow the escalation route and seek departmental advice. Keep records factual: dates, agreed tasks, messages and outcomes. The aim is to protect the group's work and to ensure that assessment reflects contribution as fairly as the process allows.

A one-page agreement will not eliminate every difficulty, but it gives a team a shared reference point before pressure rises. By fixing the process early, students create the conditions for the marking criteria, rather than group politics, to decide the grade.