GPR
46
08
93
Red card · 09
Casey
Content · MIA
12
▣ An accountability layer for group projects

The ref your
group project
never had.

GPR reads your meeting transcripts, watches your tickets, and scores your team automatically. No bias. No politics. No excuses.

Casey 12 ptsRiley 67 ptsMorgan 55 ptsJordan 94 ptsMaya 88 ptsSam 71 ptsAlex 45 ptsPriya 82 ptsCasey 12 ptsRiley 67 ptsMorgan 55 ptsJordan 94 ptsMaya 88 ptsSam 71 ptsAlex 45 ptsPriya 82 pts
01The problem

You already know who’s not pulling their weight. You just can’t prove it.

The ghost
You wrote the report. They put their name on it.
The procrastinator
The meeting had action items. Nobody did them.
The scapegoat
The deadline passed. Someone blamed the tools.
02How it works

You run the project. The ref runs the receipts.

01 / Set up

Connect your project

Create a project, invite your team, link your GitHub repo. GPR starts watching from day one.

02 / Ingest

Run your meeting normally

After any meeting, paste the transcript. Voice notes, Zoom exports, copied Slack threads — GPR reads it all.

03 / Verdict

The ref calls it

GPR extracts every commitment, scores every member, and issues cards automatically. Yellow for falling behind. Red for going dark. MVP for carrying the squad.

04 / Memory

Evidence builds over time

Every meeting adds to your project knowledge base. Ask GPR anything — who committed to what, what was decided, who’s been quiet for a week.

03The rulebook

Three calls. One rulebook.

Yellow card

Falling behind

Vague commitments. Tickets going stale. The ref books you, and the team sees it.

Red card

No contact

No-shows, missed deadlines without notice, deliverables ghosted for days.

MVP

Top contributor

Quietly carrying the project. The ref keeps receipts so you don’t have to defend yourself in retro.

04A real match report

Receipts. With timestamps.

Sam 71Alex 45Priya 82Casey 12Riley 67Morgan 55Jordan 94
Final
Sprint 04 · Meeting recap

Project Falcon

Two members carried the load. One has not delivered in eleven days. Detailed verdict and commitments below.

01Jordanbackend94
02Mayafrontend88
03Priyadesign82
04Samqa71
05Rileyops67
06Morganresearch55
07Alexpm45
08Caseycontent12
Open commitments
Jordan — Finalize the API contract by Thursday EOD. Thu
Maya — Migrate auth middleware before next stand-up. Mon
Sam — Send the stakeholder update with sprint metrics. 2 days ago
Casey — Reply to anything in the channel. 11 days ago
19
Sample digest, week 19
“The work was not evenly shared. Two members carried the load. One has not delivered in eleven days. The team agreed on a contract; the contract was not honored. ”
— GPR Weekly Digest · Confidential · Do not forward
05Capabilities

Everything a good ref needs.

Meeting analysis

Reads transcripts so you do not have to. Pulls every commitment, every silence, every excuse.

01

Knowledge base

Remembers everything so nobody can say they forgot. Searchable across every meeting, ticket, and message.

02

Leaderboard

Who is carrying the squad. Updated after every meeting.

03

Ask GPR anything

It only knows what your team has done.

04

GitHub integration

Commits don’t lie. Neither does GPR.

05

Multi-source

Transcripts, GitHub, Jira, Slack. Every angle covered.

06
06Field reports

The ref keeps receipts. People notice.

“I used to be the one doing everything. Now I have proof.”

Final-year CS student
University of Canterbury

“Our group project went from chaos to accountability in one meeting.”

Product team
Early-stage startup

“The red card on my teammate was the most satisfying thing I have ever seen.”

Anonymous
…but we know who

Stop being the one
who does
everything.

Let GPR keep the receipts.