Operations software for several user roles, combining workforce scheduling, financial reconciliation, audited workflows, reporting and secure deployment.
The problem
Finance, staffing, approvals and historical corrections become fragile when they are treated as isolated features. The engineering challenge was to keep operational state consistent, role-scoped and auditable across the whole workflow.
What was built
A local-first operational platform that connects workforce scheduling, settlement calculations, transaction reconciliation, approvals, document generation, notifications and controlled financial close procedures.
Technical approach
- Responsive, role-aware browser UI
- Server-side authentication and role-scoped API access
- Domain workflows over SQLite persistence
- Live synchronisation and reminder infrastructure
- Containerised deployment, health checks and encrypted backup/restore
Engineering decisions
- Store scheduling time in UTC and display it in local time.
- Archive and deactivate operational records instead of deleting them destructively.
- Lock finalised financial records and route corrections through audited lifecycles.
- Protect state-changing requests with session, origin and CSRF controls.
- Deploy immutable container images by commit, with readiness checks and rollback guidance.
How it was checked
- Automated tests and CI checks exist in the private repository.
- Health and readiness endpoints support deployment verification.
- The backup documentation includes a verified restore workflow.
- Financial corrections and finalised records keep their audit history.
What it shows
Engineering of business-critical internal software: complex domain logic, access control, financial state, auditability, operational automation and production-oriented deployment.
About the source
Internal product engineering. The public description is deliberately limited to operational workflows, data integrity and deployment.