For student software teams and their mentors

Stories, tasks, commits and decisions, tied to the people who did the work. Your team can always answer who built this, why it was done that way, and what's left.

Try the demo

Traceability

From requirement to commit, in one line.

Write stories the way your course asks: As a student, I want… Put LF-12 in a commit message and it links itself. For the rest, Trace suggests a match and a teammate says yes or no.

LF-4

Report a lost item

Traced

As a student who lost something, I want to report it with a photo, so that a finder can recognise it.

Tasks

✓Items table and access policiesMI
✓Report form with validationAM
✓Photo upload with compressionIK

Commits

a3f9c21LF-6: report form with validation
7bd0e14compress photo before saving
Looks like LF-7“compress”, “photo”Confirm

Decision

D-3Compress photos to WebP at 1280px, because the free storage tier is 1 GB.

People

AMIKMIAarav, Isha and Meera built this

Today

Close the rings.

Three rings tell you how done you really are: stories traced end to end, tasks finished, commits tied to a story. When all three close, the project is done, and you can prove it.

Stories traced

3 of 10

Tasks done

3 of 17

Commits linked

8 of 28

Receipts

Receipts, not opinions.

Every teammate gets a receipt, and every line on it is evidence: a commit, a finished task, a decision. Anyone can dispute a line. The lead resolves it, and the receipt keeps both sides. No line is written by AI.
AMTrace receiptAarav Mehta
Share32%
Commits
7
Lines
772
Tasks
5
Decisions
4
Even split 25%
IKTrace receiptIsha Kulkarni
Share31%
Commits
9
Lines
640
Tasks
6
Decisions
2
Even split 25%
MITrace receiptMeera Iyer
Share28%
Commits
8
Lines
515
Tasks
4
Decisions
1
Even split 25%

TRACE · CONTRIBUTION RECEIPT

COMMIT a3f9c21 → LF-4LF-6: report form with validation+171 −9
TASK LF-6 → LF-4Report form with validationdone
DECISION D-7Email only for match alerts in v1decided
DISPUTED by Kabir: we paired on the form.→ Shared credit, agreed in lab.

Rewind

Scrub through the whole project.

Drag a line back through time and watch the project rebuild itself, day by day: which stories were traced, who was doing the work. It's all in the record already.

As it stood on

Tue, 4 Aug

8%

1 of 10 stories traced

4 AugToday

Viva

Practise the parts you didn't build.

Flashcards on the code, decisions and requirements your teammates owned, answered from the team's own record. And when someone asks why, Ask finds the decision and the commit behind it.

Codesrc/claims

Meera changed the claim dialog in “LF-17: secret question”. What does it do for LF-16?

Say it out loud, then flip the card.

From the record

  • Commit 3c1e7a0 stores the answer hashed, never in plain text.
  • It serves LF-16: an owner proves an item is theirs before it is handed back.
3c1e7a0LF-16

?Why did we email match alerts instead of push?

Push needed a service worker and Firebase setup the team didn't have time for 1, so v1 emails a match and push moved to v2 2.

Mentors

Every team, at a glance.

A mentor sees every team they guide on one page: how much is traced, who is carrying the work, who went quiet, and which decisions disagree.

LF

Campus Lost & Found

40% traced

Kabir has 10% of the work

MB

Hostel Mess Feedback

71% traced

Looks healthy

LB

Lab Slot Booking

22% traced

No activity for 6 days

CB

Campus Carpool

55% traced

2 decisions may conflict

EV

Club Events Hub

86% traced

Looks healthy

Your project, traced.

Sign up free

Fictional teams. Edit anything: the demo resets every six hours.