How University Project Teams Can Keep Fair Meeting Records

Every group project has a version of this story. Four people, one shared grade, and by week eight it's clear that two of them are doing most of the work. Nobody said that out loud at the start. There was no moment where roles were assigned in a way anyone could point back to — just a WhatsApp group, a rough sense of who was "doing the slides," and a Google Doc where edits pile up with no names attached to decisions, only to text.

Then the mark comes in, or worse, a peer evaluation form asks everyone to rate each other's contribution, and suddenly the vague arrangement from week one matters a great deal. One person says they were never actually assigned the literature review. Another says they raised concerns about the timeline in week three and nobody listened. Nobody can prove any of it, because nothing was ever written down in a form that survives the scroll of a group chat.

This is not a rare failure. It is the default outcome of running a team through tools built for chatting, not for keeping a record.

Why "we all know what happened" isn't good enough

In a group project, memory is not a reliable record — it's a set of four slightly different stories, each shaped by how much work that person did and how justified they feel about it. That's not anyone being dishonest. It's just what happens when there's no shared, neutral account of what was decided and by whom.

A written record fixes this not by catching anyone out, but by removing the need to rely on memory or reputation at all. If task ownership and deadlines are written down at the time they're agreed, nobody has to argue about who said what in March. The record just says it.

This matters most in three situations: a peer contribution grade where you need to show what you actually did, a dispute where two people remember an assignment differently, and a supervisor or module coordinator asking for evidence that the team met regularly and worked through problems properly, not just at the end.

What's actually worth writing down

You don't need minutes in the formal, corporate sense. You need four things, captured consistently, every time the team meets:

• Who was there. Not who was "in the project" — who actually showed up to that meeting. Absence is data too.
• What was agreed. Not the whole discussion, just the decision: "we're splitting the report into three sections," "we're pushing the deadline for the survey by a week."
• Who owns what, and by when. This is the single most important line item and the one teams skip most often. "Someone will look into the data cleaning" is not an assignment. "Priya owns data cleaning, done by the 14th" is.
• What changed since last time. If a deadline slipped or a task moved to someone else, note it, with the date. This is what protects the person who picked up extra work after a teammate dropped a task, and what protects the person who was reassigned fairly and shouldn't be blamed for the original delay.

None of this needs to be elaborate. A few lines per meeting, written at the time rather than reconstructed later, is worth more than a beautifully formatted document written from memory after the fact.

A lightweight way to hold it

You don't need a company secretary or a project management platform built for a twelve-person department to do this well — you need somewhere the record lives outside the group chat, where it won't get buried by the next fifty messages about pizza orders.

That's the small, specific thing Aboardable is for: open a board for the project, log who's there each time you meet, capture what got agreed and who owns it, and let that build into a record you can actually point to later — not a chat log you'd have to scroll through for an hour to reconstruct. It's meant to be lighter than what a company or formal committee would use, sized for a project team that just needs the record to exist.

One caveat worth being plain about: none of this is legal or academic advice, and it doesn't substitute for your institution's own rules on group work, peer assessment, or academic conduct. If a dispute over contribution or a grade appeal comes up, follow your department's process and talk to your supervisor or module coordinator — a good meeting record just gives you something concrete to bring to that conversation, rather than four different memories of the same semester.