Currently, a revision request (or even booking request) has three states: pending, fulfilled, and denied. This misses a key distinction: oftentimes the longest waiting periods for revisions/new rooms are because of CSC Operations, a university office and SGA partner, rather than SGA itself. This distinction should be clear for admins for internal tracking, and to users for transparency.
This should be done by generating two status updates for requests: "Pending" should be converted to "Ops Review" and a new status, "Awaiting CSC" should be created. The progression of statuses would then be:
- User submits request: "Ops Review"
- Operational Affairs communicates the request to CSC Operations: "Awaiting CSC"
- CSC responds: "Fulfilled" or "Denied"
Admins should be able to cycle through these statuses freely, but the Admin UI should suggest the above progression as a default.
Currently, a revision request (or even booking request) has three states: pending, fulfilled, and denied. This misses a key distinction: oftentimes the longest waiting periods for revisions/new rooms are because of CSC Operations, a university office and SGA partner, rather than SGA itself. This distinction should be clear for admins for internal tracking, and to users for transparency.
This should be done by generating two status updates for requests: "Pending" should be converted to "Ops Review" and a new status, "Awaiting CSC" should be created. The progression of statuses would then be:
Admins should be able to cycle through these statuses freely, but the Admin UI should suggest the above progression as a default.