Aprub

The Problem

University clearance processes involve multiple approvals from different departments — library, registrar, finance, adviser — each with paper forms that students physically carry between offices. The process takes days and forms get lost.

The Solution

I built Aprub as a digital clearance workflow platform using the MERN stack.

• Role-based access — Students, department approvers, and admins each have scoped views and permissions.
• Multi-step validation — Clearance requests flow through a configurable approval chain. Each department approves or rejects independently.
• Audit trail — Every action (submission, approval, rejection, comment) is timestamped and logged for accountability.
• Modular backend — Each approval step is a discrete API endpoint, making it easy to add or reorder departments in the chain.

What Went Wrong

The initial approval chain was hardcoded — adding a new department required code changes and redeployment. Different degree programs had different clearance requirements, but the system enforced a single chain for everyone.

The fix: I made the approval chain configurable per program. Admins define the required departments and their order through the dashboard, and the backend dynamically generates the approval workflow for each student based on their enrolled program.

Results

• Configurable approval chains per degree program
• Complete audit trail for every clearance action
• Eliminated days of physical paperwork with a digital workflow