Built a No Dues clearance system for my college over a weekend, curious what you'd have done differently

Context for anyone who hasn't dealt with this: before graduating, most Indian colleges make you get a "No Dues" certificate. Basically proof you don't owe the library, hostel, labs, accounts office, etc. In practice this means physically walking to 5-6 offices, waiting in line, getting a signature, repeat. Some people take days. Heard of people missing their own convocation over this.

Built the digital version over a weekend. Used Antigravity for the product side and Runable for the landing page, mostly to move fast without getting stuck on boilerplate.

Stack-wise, kept it simple: departments get their own dashboard to approve/reject, student tracks status live, admin has a full overview. Nothing fancy, just replacing a paper trail with a status board.

What got me was talking to people from 4-5 other colleges and hearing the exact same complaint every time. Different names for the process, same broken workflow everywhere.

Curious how you'd have approached the backend for something like this, especially the approval-chain logic across departments. Also open to "this already exists, here's why it didn't work" if that's the case.