Every deployment. Every approval. On the record.
Submit, review, and approve deployments in one system — conflict-checked and logged at every step.
Built around how deployments get approved
Each screen maps to a specific step in an accountable approval process.
Deployment vouchers
Staff submit a voucher with destination, purpose, and dates. It stays pending until a supervisor decides.
Hard conflict guardrail
Approval is blocked outright on a double-booking — the approver sees exactly which voucher conflicts.
Role-based, delegable access
Admins hold full control and can delegate create/edit/reject/cancel rights per person, without a role change.
Full audit trail
Creation, approval, rejection, cancellation, and flagged conflicts — each logged with actor and timestamp.
Calendar & dashboard
Approved deployments by date range and directorate, plus frequency reporting per officer.
Reporting & export
Search and filter every voucher directorate-wide, export to CSV. PDF export is on the roadmap.
From request to record, in four steps
Every voucher follows the same accountable path.
Submit
Staff, or a delegated coordinator, raises a voucher with dates, destination, and purpose.
Review
An admin or secretary checks the request against the officer's existing commitments.
Decide
Approve — blocked automatically on conflict — or reject with a required reason.
Track
Status rolls forward as dates arrive — scheduled, ongoing, then completed.
Access matches responsibility
Three tiers by default, with one exception admins can grant per person.
Admin
Full control- Create, edit, reject, and cancel any voucher
- Approve vouchers — the only role that can
- Manage directorates, staff directory, and user accounts
- Grant or revoke delegated voucher-management access
Built for people who ask "who approved this, and when?"
Controls that are visible, not just implied.
Hashed credentials
Passwords are never stored in plain text — bcrypt hashing throughout.
Signed, typed session tokens
Short-lived access tokens with a separate refresh token; a refresh token can never act as an API credential.
Nothing is silently deleted
Vouchers move through recorded status transitions — never a hard delete.
Single-use password resets
A reset link stops working the moment it's used, or the moment the password changes any other way.
Ready to bring your directorate's deployments on record?
Access is provisioned by your administrator. Sign in, or request access below.