Does it handle part-time and irregular hours?

Yes, and this is where spreadsheets usually break. Entitlement is derived from the working pattern, including annualised hours and irregular shifts, and bank holidays are pro-rated correctly for people who do not work a standard week.

Can we set different rules per department?

Yes. Holiday year, accrual method, carry-over caps, notice periods, approval chains and minimum cover can all vary by department, site or contract type.

Will it sync with Outlook or Google Calendar?

Yes. Approved absence can publish to Microsoft 365 or Google Workspace calendars, and there is a subscribable feed for team calendars.

Can employees see their balance before requesting?

Always. The live balance, including pending requests, is the first thing shown on the self-service screen - which removes most of the questions that would otherwise reach HR.

Absence Management Software in Newark-on-Trent

We support businesses in Newark-on-Trent the way we would want to be supported ourselves: someone who knows the account, on the end of a phone, and on site when being on site is what the job needs. Newark-on-Trent is comfortably within a morning’s drive of our Olney office.

Holiday tracking in a spreadsheet works right up until it does not: pro-rata calculations for part-timers, carry-over rules, bank holidays for staff who do not work Mondays, and TOIL all conspire to make it wrong. CubeHR calculates entitlement automatically from the working pattern, routes requests through the approval chain you define, and blocks bookings that would breach minimum cover. Sickness is recorded against the same record with return-to-work forms, Bradford Factor scoring and trigger points, so absence is managed by policy rather than by whoever happens to notice.

Automatic
Pro-rata entitlement, including irregular patterns
Prevented
Clashes blocked at request, not discovered later
Consistent
Bradford Factor triggers applied to everyone alike

What it does

Inside absence management software

The parts of CubeHR that make up absence & holiday. Everything here shares one data model, so nothing needs re-keying between them.

Entitlement worked out for you
Pro-rata for part-timers and mid-year starters, accrual or up-front, carry-over rules and caps, bank holidays handled correctly for non-standard working patterns.
Request and approve from a phone
Staff see their live balance and request leave in seconds. Managers approve or decline from a notification, with delegation when they are away.
Team calendar and cover rules
A shared calendar showing who is off when, with configurable minimum cover per team or skill so clashes are prevented at the point of request.
Bradford Factor and triggers
Automatic Bradford Factor scoring with configurable trigger points that notify the right manager - so absence policy is applied consistently rather than selectively.
Return-to-work workflow
Return-to-work forms raised automatically after any sickness absence, completed digitally and stored against the employee record for evidence.
Every absence type
Annual leave, sickness, TOIL, unpaid, parental, compassionate, jury service and study leave - each with its own rules, evidence requirements and reporting.

In practice

Problems this actually solves

Anonymised, but not invented. These are the situations businesses describe to us before they change anything.

Nobody trusted the holiday spreadsheet
The situation
A 90-person business ran holiday on a spreadsheet with a tab per department. Part-time entitlements were wrong, carry-over was applied inconsistently, and disputes at year end were routine.
What changed
Entitlement is now calculated from each person’s working pattern, and every balance is visible to the employee at all times. Year-end disputes stopped, because there is nothing left to dispute.
Two supervisors off in the same week
The situation
A manufacturer twice ran a shift with no qualified supervisor because leave was approved by two different managers who could not see each other’s decisions.
What changed
Minimum-cover rules by skill now prevent a booking that would leave a shift uncovered. The second request is declined at the point of submission with the reason shown.
Short-term absence nobody was managing
The situation
Frequent one-day sickness absences were noticed anecdotally but never measured, so the absence policy was applied only when a manager decided to make an issue of it.
What changed
Bradford Factor scoring with automatic trigger notifications made the pattern visible and the policy consistent - applied on evidence, and defensible if challenged.

Local coverage

Absence & holiday across Nottinghamshire

We cover Newark-on-Trent and the surrounding area, including Town Centre, Balderton, Farndon, Coddington and Bingham, across the NG24, NG22, NG23 and NG25 postcode districts. We also work with businesses in Nottingham, Mansfield and Worksop and elsewhere in Nottinghamshire.

Postcode districts

NG24
NG22
NG23
NG25

Areas we cover

Town Centre, Balderton, Farndon, Coddington, Bingham, Southwell, Collingham and Claypole.

Getting to you

Roughly 64 miles from our office in Olney, Buckinghamshire. Discovery, training and go-live are done on site as standard - not because it looks good on a proposal, but because most of what a system needs to know is learned in the building.

Absence & holiday elsewhere in Nottinghamshire

All of Nottinghamshire

How it happens

What implementation actually involves

The same process wherever you are, and for Newark-on-Trent it is done in person.

Discovery
A structured session mapping how you work now - the systems, the spreadsheets and the bits held together by one person’s memory. We come back with what the platform covers as standard, what needs configuration, and what needs building.
Configuration
Your structure, sites, roles, approval chains, document templates and permissions set up to match the business - not a demo tenant with your logo dropped on it.
Data migration
Existing records brought across and reconciled: customers, stock, bills of materials, employees, holiday balances, contracts. We migrate, you check, then we cut over.
Training & rollout
Role-based training so people learn the parts they actually use, with a pilot team first where it makes sense. Documentation and short screen recordings left behind for new starters.
Ongoing support
UK support from the people who built the platform, with a named contact, agreed response times, and a product roadmap you can influence.

You might call it something else

Absence & holiday goes by a lot of names - if you searched for any of these, this is the page you wanted.

Holiday booking software
Annual leave software
Leave management system
Sickness absence software
Staff holiday planner

Questions

The things people ask first

Yes, and this is where spreadsheets usually break. Entitlement is derived from the working pattern, including annualised hours and irregular shifts, and bank holidays are pro-rated correctly for people who do not work a standard week.
Yes. Holiday year, accrual method, carry-over caps, notice periods, approval chains and minimum cover can all vary by department, site or contract type.
Yes. Approved absence can publish to Microsoft 365 or Google Workspace calendars, and there is a subscribable feed for team calendars.
Always. The live balance, including pending requests, is the first thing shown on the self-service screen - which removes most of the questions that would otherwise reach HR.