Requests and approvals
Approvals that leave a record, not a chat thread
Leave, expenses, attendance corrections, out-duty and comp off. Raised in the product, decided by the right manager, and kept with the day they belong to.
- One queue,for every request a manager has to decide.
- One record,kept with the day the request belongs to.
- One engine,so a new request type is configuration, not a release.
What changes when approvals run on one engine
The day today
- A reimbursement lands two months late because the approval sat in an inbox
- Two people calculate the same leave balance and get different numbers
- An attendance dispute has no record of who decided what
- A manager spends Friday chasing decisions instead of making them
The day with Emplitrack
- Real chains: levels, conditions, cover when someone is away, and deadlines
- Every decision records who acted, what changed and which request it belonged to
- Finance can defend a reimbursement and HR can defend a balance months later
- Adding a new request type reuses the same routing, notifications and audit trail
One engine, many request types
Simple accept and reject does not survive an enterprise
Nobody plans to run approvals over chat. It happens because the request is small and the manager is busy. Then the month ends and the cost shows up.
- The employee submits from the app, with the detail finance needs
- It lands in one queue for the manager, not in a chat thread
- The decision stays with the day, on the tamper-evident ledger
Where it stands
Marked here the same way it is marked in the demo.
Live today
3In production, with customers, now.
- Leave, expenses and comp off
- Attendance corrections and out-duty
- Decisions kept on the record
In build
3Scoped for the enterprise release. Never sold as shipped.
- Multi-level and conditional routing
- Delegation and escalation
- One catalogue for any request type
Common questions
Can we set up more than one approval level today?
Most request types today follow a single decision step. Multi-level routing, delegation and escalation are in build.
What happens when an approver is on leave?
Delegation is in build for exactly this case. Today the request stays in the queue, which is the gap we are closing.
Can we add our own request type?
A universal request catalogue is in build, so new request types reuse the same approval engine, notifications and audit trail.
Is the approval history exportable?
Approval data appears in reports today, and the audit ledger keeps the underlying record. A report builder is in build.
Get approvals out of the group chat
Bring your approval chains. We will show you what runs today and what the catalogue adds.