Planvera — Workforce Scheduling Platform
A senior security firm was managing complex multi-site monthly shift schedules manually — no off-the-shelf tool matched the real operational workflow.
- Role Sole engineer, designer & planner — spec to deployment
- Stack Full-Stack · AWS (private codebase)
- Result Deployed to production; validated through live trial runs with the client’s real operations team — replaced a manual scheduling process
Proof: production data from day one, live trial validation with client operations team, role-based access, multi-user scheduling logic
Key decisions
Chose a server-backed architecture over local storage because schedule data needed to be authoritative and shared across the team. Built role-based access from the start to support multi-tier users (admin, project manager, worker). Prioritised the monthly scheduling view as the core interaction — matching how the client actually worked, not how a generic calendar would expect them to.
Constraints
Private codebase. Production data from day one. No QA team — I wrote and executed all tests, then validated live with the client during scheduled trial runs against real operational data and real edge cases.
What I’d do differently
I’d build a regression test suite earlier. Live trial feedback was direct and valuable, but reactive — edge cases in the scheduling logic surfaced in real operations that structured unit tests would have caught during development.