Institutional workflow systems
AUST Digital Operations
Connected institutional systems for admissions, approvals, memos, requisitions, and payments.
- Role
- Backend and system architecture
- Stack
- Python
- FastAPI
- PostgreSQL
- WebSockets
Problem
The problem
University admissions, requisitions, memos, and payments cross many departments and decision-makers. Paper-led and disconnected processes make state difficult to track, duplicate work, and weaken accountability across institutional operations.
System model
A connected operational flow
System flow: Admissions, requisitions, memos & payments to Multi-role approvals; Multi-role approvals to Notifications; Multi-role approvals to Auditable records.
Context
Institutional work crosses departments
AUST Digital Operations is a connected body of institutional systems rather than a collection of unrelated websites. Admissions, requisitions, memos, and payments each move through multiple roles and decisions.
Responsibility
Translate operational rules into software
I focused on backend and system architecture for multi-role approval workflows, role-based access, notifications, and auditable operational state. The goal was to make complex administrative processes understandable and dependable in daily use.
Engineering decisions
Make workflow movement visible
FastAPI provides a focused backend interface, PostgreSQL retains durable workflow records, and WebSockets support timely coordination where a changing state needs to be visible. The system emphasizes accountability over paper-led handoffs.
Outcome
What the system enables
Connected multi-department workflows so operational state, approvals, notifications, and accountability can be handled as reliable software.