Workforce · time off
The one thing a paper process never tells an approver: who else is already away.
We rebuilt it in September 2026, and most of the work went into the approver’s side. Because a leave decision takes about fifteen seconds.
Who else is off, before you approve
The fastest fix is the one you make yourself
Tenure-based

Trusted by the Caribbean’s best-known employers
Airlines, telecoms, utilities, hotels, credit unions and the National Insurance Board itself.

The approver’s side
A manager approves leave in between two other things. So the question we asked was simple. What can they see without leaving the request?
The coverage board
Who else is away, laid out across the team and the period. A paper process, an email chain or a shared inbox never tells an approver that in time.
You know what happens without it. Two approvals, each one reasonable. And a Tuesday with nobody on the desk.
The approver impact panel
Shown at the moment of the decision, on the request itself. You don’t have to run a report or check a calendar. The overlap is right in front of the person deciding, while they’re deciding.
Denial codes
A refusal carries a reason on the record. That protects the approver as much as the employee, because six months later somebody can still answer “why was mine refused when hers was not”.
An undo window
Right after a decision. The fastest correction is the one the approver makes themselves, in the next ten seconds.
All four do the same thing. They move information or control to the moment of the decision. Coverage before. Impact during. A reason at the point of refusal. A correction straight after. Most leave systems get built around the request, because the request is what you can see. And the request is the part nobody struggles with.
Those four are what the September 2026 rebuild changed. The request form barely moved, because the request was never the problem.
The employee’s side, and the policy behind it
What an employee can see
Balance rings, and a balance and entitlement breakdown they can read without asking. Most leave questions HR gets aren’t requests at all. They’re people checking a number they can’t see.
A signed personal calendar link, so an employee subscribes to their own leave from whatever calendar they already use. It’s a read-only subscription, signed so nobody can guess it. It isn’t a productivity-suite integration.
Requests also come from the mobile app, or at the terminal for a workforce with no desk and no company phone.
What the policy carries
- Tenure-based policies, so entitlement that grows with service is a rule
- Blackout dates, for the periods a business really can’t cover
- Bulk balance import, for a migration or a year-end correction
Tenure quietly saves the most work. Keep an entitlement ladder by hand and it’s wrong for somebody every year. And it’s always wrong against the employee, because nobody chases an entitlement they didn’t know they’d earned.

Approval chains here are advisory
Know this before you buy, so it doesn’t surprise you in month two.
A time-off approval chain routes and records. It does not block. The request reaches the people it should, in order, and every step is on the record. But the chain won’t physically stop anybody taking leave.
Ask yourself whether that suits you before you buy. For most organisations it’s the right call. Leave is a negotiation between a person and their manager. Hard-block it and you get a WhatsApp message and an absence nobody recorded. That’s worse than an approval that was skipped but logged.
Where hard gating does exist
Approval on a pay run is staged properly, with recall and cancel and a line-level audit trail, because money leaving the business is a different kind of decision from a Thursday off. We gate what needs gating.
Where leave meets the rest of the workforce
Leave doesn’t stand on its own. It feeds the roster, and it feeds pay.
Into scheduling
The roster has to respect approved leave, so the coverage board and the schedule read the same data.
Into the timesheet
A day off and a missed punch are different things. Leave and attendance are worked out together, so nobody chases a missing clock-in on an approved leave day.
Into the pay run
Paid and unpaid leave reach the run as what they are. And the pre-run review flags the setup where uninsured time off replaced pay.
Rostering is where getting leave wrong actually costs you. An approved absence the schedule doesn’t know about becomes a shift with nobody on it. Found that morning. Covered by whoever answers the phone. Paid at a premium nobody budgeted for.
That last flag shows why these belong together. The problem sits right on the seam between leave and payroll, and a system that only owns one side never sees it.
Statutory leave entitlements differ in every territory we support, and each is published with its instrument and its verification date on that territory’s pages: The Bahamas, Jamaica, Barbados, Trinidad and Tobago, Turks and Caicos and Saint Lucia. The policies you set up here are your own. Those pages are the floor they have to clear.
What it doesn’t do
It routes and records. It does not police.
Approval chains are advisory. Blackout dates and policies state what you intend. The calendar link is a read-only subscription.
What it does is make leave visible and evidenced. Who asked, who decided, on what basis, with what coverage at the time, and what the balance was before and after. All of it is on the record, and you can answer for it later.
If you need a system that physically stops people taking leave without approval, this isn’t it.
Articles
Further reading
The one thing a paper leave process never tells an approver
Who else from the same team is already away that week.
Read the article ArticleCoverage is what an approver is deciding
The balance says whether they may. Coverage says whether you can.
Read the article ArticleCarry-over, expiry and the year end
The policy questions that only come up in December.
Read the articleQuestions about time off
What does the approver see when deciding?
Do approval chains actually block leave?
How does entitlement that grows with service work?
Can an employee see their own balance?
Is the calendar link an integration with our email system?
What if we need to correct a decision?
See it on your own data
Bring a fortnight of real leave and a team that’s hard to cover. We’ll show you what the approver would have seen.
- The coverage board across a real team and period
- The impact panel on a request with a genuine clash
- A tenure-based policy and the balance it produces
- Leave reaching the timesheet and the pay run
- SOC 2 Type II attested
- AES-256 at rest
- 99.9% uptime
- Built in The Bahamas
Where to go next
Time off sits inside Workforce and touches scheduling and pay. These are the pages around it.
Time off is part of the Workforce module and was rebuilt in September 2026. Statutory leave entitlements are published per territory with their instruments and verification dates. Security: AES-256 at rest via AWS KMS, TLS 1.2 and above in transit, SOC 2 Type II attested against the Security criteria with the report available under NDA, and AWS US multi-AZ as standard with on-premises or Caribbean regional cloud on request, subject to scoping. See also Core HR, Payroll and Talent · the six territories · contact.
