Flow
A request enters the lattice
It routes to the right approver through the live structure, with the context needed to decide attached, not linked.
The situation
An organisation that runs on permission.
Approvals
Expense, $240KaiJawad
Annual leave, 3 daysNadiaJawad
Laptop, MacBook 14PriyaQuinn, IT
Underneath every workforce is a lattice of approvals: leave requests, expenses, document sign-offs, onboarding tasks, policy acknowledgements. Each one is small; together they are how the organisation actually moves. And in most companies they move through inboxes, which means they move at the speed of whoever is busiest, wherever they are on holiday, until someone senior asks why a two-day request took two weeks.
Where it breaks
The problems that live in this world.
Not generic HR pains: the specific ways this environment grinds people teams down, one honest description at a time.
Approval purgatory.
A request routes to a manager who is away, unwell or simply buried. Nobody is notified, nothing escalates, and the requester learns the outcome by asking in a corridor.
Routine decisions consume real time.
A short leave request with notice, a small expense from a trusted employee: decisions with an obvious answer still queue behind a human, costing attention that the genuinely hard cases needed.
Nobody sees the queue building.
The approver at capacity is found when their queue collapses. By then a week of the organisation’s small decisions has silted up behind one calendar.
Nobody can reconstruct the decision.
Who approved it, under what rule, after which escalation? When the question matters, the answer is scattered across notification histories and forwarded emails.
Day to day
Three operational realities, handled.
Attendance, pay and compliance are where this world gets judged. Here is how each one runs on a connected record.
01
The routine resolves itself.
When a request fits the rules you wrote, it approves itself on the spot and writes the rule that decided it into the log, so human attention is spent only where judgement is needed.
02
An absent approver is not a wall.
A request inside your thresholds is decided on the spot. Anything else routes to the real manager, moves to their delegate while they are away, and is chased when it sits too long.
03
Every decision leaves a trail.
Every automatic decision, escalation and approval is logged for review, and workflows route through the real structure, so the process is as auditable as it is fast.
The modules that fit
Take what fits, leave the rest.
HarmoniHRM is modular. These are the pieces that earn their keep in this world, each reading and writing the same connected record.
Flow→
Requests routed through the real structure, decided inside your thresholds, delegated while an approver is away and logged either way.
Organo→
Workflows route through the live structure, so requests reach the real manager, not last quarter’s.
Employee Management→
Hires, role changes and terminations trigger the workflows that should follow them, automatically.
Leave management→
The highest-volume approval in any company, decided with team context and cover for absent approvers.
Connect→
Announcements with acknowledgements, for the approvals whose output is everyone knowing.
A working day, connected
How the day actually runs.
Follow one realistic cycle through HarmoniHRM, step by step, from the first event of the day to the numbers that close it.
01
A request enters the lattice
It routes to the right approver through the live structure, with the context needed to decide attached, not linked.
02
The obvious answer happens instantly
If it falls inside the threshold you set for that request type, it is approved automatically and logged with the rule that decided it, and the requester moves on with their day.
03
An absent approver is not a wall
Workflows are delegated when the approver is away and escalated if they stall past your threshold, so a holiday never becomes a queue.
04
The trail answers the hard question
Months later, who approved what, under which rule, after which escalation, is a log entry rather than an archaeology project.
Who lives this
The people inside this playbook.
Organo
The obvious answer happens instantly
If it falls inside the threshold you set for that request type, it is approved automatically and logged with the rule that decided it, and the requester moves on with their day.
Employee Management
An absent approver is not a wall
Workflows are delegated when the approver is away and escalated if they stall past your threshold, so a holiday never becomes a queue.
Leave management
The trail answers the hard question
Months later, who approved what, under which rule, after which escalation, is a log entry rather than an archaeology project.
Keep reading
Related playbooks in this family.
Asked before buying
The questions that come up every time.
Which approvals can resolve automatically?
The ones you define. You set a threshold per request type, an expense at or under an amount, leave inside the pool you opened, and a request that fits resolves on its own with the rule recorded against it. Everything outside the threshold still goes to a person.
What happens when an approver is on holiday?
Workflows are never left to sit: an absent approver’s queue is handed to a delegate, and anything stalling past the threshold you set is escalated, so no request waits on an empty chair.
What stops a request sitting for a week?
Two things, and neither is a person remembering. An approver who is away hands their queue to a delegate, and a request that sits past the point you set is chased and escalated, with every reminder on the same trail as the decision.
Is there a proper audit trail?
Yes. Every automatic decision, escalation and approval is logged for review, so any decision can be reconstructed later: what was requested, which rule applied, who decided and when.
Run it on your own organisation.
Modular pricing, no long contracts. Start with the modules this world actually needs and add the rest when you are ready.