Per-request-type rules
Each request type gets its own approval rule — sequential, parallel, single-approver, or any combination.
What you get
Approval routing, your way.
Real org chart routing
Routes use the requester's actual supervisor chain — not a generic workflow.
Sequential or parallel
Require N approvers in sequence, or any one of M in parallel, or any mix you need.
Reminders & SLAs
Pending approvals nudge approvers automatically. SLAs surface stuck requests for command.
Full audit trail
Every submission, edit, comment, and decision is timestamped — exportable any time.
Learn more
Override controls
Chiefs and command staff can override or recall any decision, with the override logged.
How it works
From submit to decided.
1
Officer submits
Officer requests leave, a swap, or flags a subpoena conflict from any device.
2
Routes up the chain
BlueSummons sends it to the right supervisor(s) in the right order.
3
Approve or deny
Each approver sees the full context — schedule, prior leave, conflicts — and decides in one click.
4
Schedule updates
Approved requests flow into the schedule automatically. Denied requests notify the officer with the reason.
Before & after
What changes once BlueSummons is live.
Without BlueSummons
- Requests submitted via email
- No visibility into who's reviewing what
- Approval order varies by who's available
- Audit trail reconstructed from inboxes
With BlueSummons
- Single submission flow per request type
- Pending queue per supervisor, always current
- Order and quorum enforced by the system
- Every decision audit-logged automatically