Building the ticket issuance and admin console for an employee-benefits service with Laravel + AWS

What changed

• Ticket issuance to redemption
  Whole flow consolidated into one screen
• Operational load
  Inquiry volume held down
• Release
  Landed on the planned schedule

Challenge

Benefit tickets go through many phases — issuance, distribution, redemption, and reconciliation — and if the admin console is hard to follow, the load on the operations team spikes. Because the issuance logic is complex, any inconsistency at the redemption phase funnels inquiries straight to the operations team. Yet that team isn't made up of dedicated engineers, so we couldn't design around the assumption that they'd memorize complicated procedures. We needed to carefully design both the correctness of the issuance logic and an admin console the operations team could "use without hesitation."

Approach

1. 01 Organized the ticket lifecycle from issuance through redemption
2. 02 Designed and implemented the admin console and issuance API in Laravel
3. 03 Unified environments from local to production with Docker
4. 04 Structured delivery and data handling on AWS as well
5. 05 Built the screen layout around the operations team's workflow, aiming for a state usable without a manual
6. 06 Designed the issuance logic and admin console together so neither side's constraints distorted the other's experience

Key success factors

Lifecycle organized first

We organized the issuance, distribution, redemption, and reconciliation lifecycle up front and unified the direction for the admin console's structure.

Screen design driven by the operations team

We built the admin console around the operations team's workflow, structurally holding down inquiry-driven load.

Issuance logic and admin console designed together

We designed the issuance API and admin console as a set so neither side's constraints distorted the other's experience.

Stable operations through a unified environment

We aligned local-to-production environments with Docker + AWS, making the post-release standup of operations smooth.

Solution

We implemented the admin console and issuance logic in Laravel and set up the operating foundation with Docker + AWS. We organized the screen layout around the operations team's actual workflow, shaping it to hold down inquiry-driven load. Post-release inquiries came in below expectations, keeping the cost of standing up operations low. By consolidating the issuance-to-redemption-to-reconciliation flow into a single screen, the operations team reached proficiency in a short time.