Group Project Contribution Record Audit

Check a team record for fairness and clarity.

Added October 15, 2026. Written with AI assistance and checked for clarity and placeholders; not reviewed by a lawyer, accountant, clinician or other professional. How these prompts are made

The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.

[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it (what [VERIFY] means).

Audit our group project contribution record. Tasks, who did what, dates and evidence: [CONTRIBUTION_RECORD]. The assessment rules about group work: [RULES]. Concerns raised: [CONCERNS].

Check whether tasks and outcomes are recorded clearly, whether contributions look balanced, whether evidence exists, and whether concerns have been raised early in a constructive way. Keep the tone neutral and avoid judging individuals.

Return a table with Task, Owner, Evidence and Gap, a suggested team agreement, and a script for a calm conversation. Assessment rules are [VERIFY] with the course leader.

Also suggest regular check-ins, a shared task board, a rule that concerns are raised early and kindly, and a plan for handling a member who stops responding. Add a note on following the course's own process before escalating. Further, suggest how to record decisions made in meetings so that nobody is later surprised by what was agreed.

End with the single question that, if answered, would most improve your confidence in these findings, addressed to the person best placed to answer.

Fill in before use

Optional: type your details and the prompt above updates. Nothing is saved or sent.

Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.

Record review (invented four-person project)
Tasks logged: research (Ana, 12 hours), slides (Ben, 9), report draft (Ana 14, Chi 14), data analysis (Dev, 6, evidence: spreadsheet saved), editing (Chi, 5).
Concern: Dev's contribution was logged late and has no dates.
Evidence: version history shows 3 edits by Dev in the final week only.
Balance: Ana 26, Ben 9, Chi 19, Dev 6 hours by the record. Hours are not value, but gaps should be discussed kindly.
Suggested team agreement: weekly check-in, shared task board, concerns raised within 48 hours.
Script: "I noticed we haven't heard from you on the analysis; can we agree who does what?" Assessment rules [VERIFY].

• audit