UK-built · CDM · CIS · MTD
Requested on the phone. Approved in a tap. Out of the labour run before the week is planned.
Leave management software records who has asked for time off, who approved it, and how much of their annual entitlement is left. In construction the part that decides whether it was worth buying is what happens next: whether the weekly plan knows.
The holiday planner is Unibuild's leave module. Requests are raised on the phone as individual dates, each marked a full day or a half, an approver decides with the running total in front of them, and approved leave is read by the labour run as it draws the week.
And invisible to anyone who is not standing in front of it.
Individual dates rather than a from and to, added one at a time, each marked a full day, a half day in the morning or a half day in the afternoon, with a description.
The request pushes to the approval committee, which is a named list of people rather than one supervisor who might be on a roof. The approver sees every date and the total before deciding.
The one that pays for the module. As the week renders, the labour run asks for every person and every date whether there is approved leave. On a full day the project selector is not drawn at all.
Every active person down the side, every day of the month across the top, weekends and company holidays shaded, and an icon on each approved day showing whether it is a full day, a morning or an afternoon.
An annual figure held against each person with the year's approved days counted against it automatically. The yearly overview lists entitlement, days taken, days left and a note, for a year you choose.
The office needs to record "he is not available on Thursday" for reasons that are nothing to do with annual leave. That is a day off: entered directly on the labour run, with a mandatory reason.
Ask to see a man booked on a job he is on holiday for.
It is the fastest way to judge this module, because you cannot. Watch somebody try it on the labour run and the control is simply not there.A day on the labour run is either bookable or it is not, and half a day is genuinely half. This is what the person planning Friday's week actually sees.
The ordinary state. The project selector is drawn and the day can be allocated as normal.
The badge replaces the control, with the description underneath. There is nothing to click, so there is no allocation to make by mistake.
The badge appears and the selector stays, because a morning off still leaves an afternoon that somebody has to plan.
Most of the year this is invisible. It matters on the day somebody leaves, or disputes what they were owed, or an inspector asks how you know.
Not a summary. The requester, every individual date, the day type on each one, the description he typed, the calculated total, the decision, who made it and when. A request from eighteen months ago opens with all of it still attached.
A rejection cannot be saved without one. The typed reason is stored on the request, shown against the rejected badge in the office list, and pushed to the requester's phone at the time. There is no version of events to reconstruct later.
A half day counts half a day against entitlement, prints as Halfday on the timesheet, and shows as a half-filled marker on the month grid, rotated for a morning and not for an afternoon. Nothing is rounded up quietly.
Company and bank holidays are named dates on a maintained list that shades both the planner and the labour run. Whether Good Friday is on it is a decision somebody made once, on a date, rather than an answer that changes depending on who is asked.
A day covered by approved leave with no hours against it prints HOLIDAY on the timesheet grid, and the same lookup runs when the timesheet PDF is produced, so the printed sheet carries it too. The hours reconcile without anybody adjusting them.
The office sets the annual figure per person, informed by the contract, and the platform counts approved days against it and shows what is left. Fractional figures are normal. Whether somebody's 5.6 weeks is 28 days is your commercial decision, and the record shows what you decided.
Leave is only worth automating if the plan reads it.
A leave register that does not touch the labour run is a spreadsheet with a login. If the weekly plan is where your problem actually is, that is the conversation worth having.Same platform, same login. These are the modules that plan the work, record it, and hold the evidence it was done properly.
What somebody is owed, what an absence costs you, and the records that matter when it is disputed.
