Ovvos

Roster

HR management

Leave that counts the way you count it.

Roster runs leave, holidays and working patterns for teams across several countries — with a two-stage approval that ends in HR and a balance that updates itself.

Roster is a leave and working-pattern system for companies with staff in more than one country. It holds people, departments and managers, leave types and balances, every day taken, and the public holidays of each country the company operates in. Requests are approved by a manager and then by HR, and the balance moves only on that second approval.

The day count

Same dates. Two countries. Two correct answers.

A request from Sunday 1 to Thursday 12 December. For an employee in the UAE on a Sunday-to-Thursday week with National Day on the 2nd and 3rd, that is eight days. For a colleague in Pakistan on Monday to Friday with no holiday that fortnight, it is ten. Roster computes both from the dates, the person’s own working week and their country’s calendar — never from a number the person asking typed in.

Amira · UAE · Sun–Thu8 days
123456789101112

■ Public holiday, never charged   ■ Weekend (Fri–Sat)

Bilal · Pakistan · Mon–Fri10 days
123456789101112

■ Weekend (Sat–Sun)   No public holiday in this fortnight

MANAGER ✓→AWAITING HR→balance moves only here

How it works

Roster, end to end.

  1. 01

    Set up once: counting mode, countries, departments with a manager and a backup, working weeks, opening balances

  2. 02

    Import each country’s public holidays for the year, review them, tick the ones you want

  3. 03

    An employee applies; the day count is computed from their own working week and country

  4. 04

    Their manager — or the backup, or a director — approves first

  5. 05

    HR gives final approval; only then is the balance deducted, skipping public holidays

  6. 06

    Either stage can reject with a written reason, which is emailed to the employee

What's inside

Careful arithmetic, and a record of who agreed to what.

The day count

Choose once whether leave is counted in calendar days or working days. In working-days mode each employee’s own working week is used — not a company-wide Monday-to-Friday assumption. Public holidays are never charged as leave in either mode, and they are the holidays of the country that employee is assigned to. Three countries, three calendars, three correct answers.

Two approvals, on purpose

The manager who knows whether the team can spare the person approves first. HR approves second, and only that second approval moves the balance — nothing is deducted on a maybe. Rejection at either stage requires a written reason. If the manager is themselves on leave, the request goes straight to the department’s backup.

Balances and corrections

An HR console per employee to add days, reduce days or mark a half day, each needing a note and each recorded day by day. If someone’s sick allocation runs short, the remainder comes off their holiday balance and the approver is told exactly what happened. Public holidays load themselves by country and year from a public service.

People, documents and the trail

Departments with a manager, a backup and members. A private file cabinet per employee with named folders, reachable only by the named HR people. A company leave calendar filterable by country, department and person. Every change audit-logged with before and after values, who, when and from where. Six email types, each also an inbox item.

The difference

A public holiday is never charged as leave.

In both counting modes, in approvals and in manual corrections, holidays are skipped — the holidays of the country that employee is assigned to, not one company-wide list. The number of days is computed by the server from the dates, the person’s own working week and their country’s calendar, never typed by the person asking.

Questions

Asked about Roster.

Does it work for staff outside a Monday-to-Friday week?

Yes, and that is the point. Each employee’s working week is set individually, per country. A Sunday-to-Thursday week is treated exactly like any other.

Who can approve leave?

Two people, in sequence. The department manager, the department’s named backup, or a director approves first. Then one of the one or two named HR people gives the final approval, and only that changes the balance.

What happens if someone asks for more days than they have left?

Nothing blocks it — deliberately. HR can still approve, the balance goes to zero, and the approver is shown how many days could not be deducted.

Does it handle payroll, timesheets or performance reviews?

No. Roster covers leave, holidays, departments, working patterns and employee documents.

Can people see each other’s leave?

Managers see their team, directors and HR see the whole company and the shared calendar. The employee list and each person’s leave history are visible to everyone with access — worth knowing before you roll it out.

Shared with every Ovvos tool

One login, one look. The same frame, lists, alerts, light and dark mode and two densities across the whole platform. Learn one tool and you know them all.

One inbox. Anything that needs a person — a new lead, a leave request, a failed check — lands in one platform-wide inbox with a link straight to the record.

Your company only. Every screen, report and export is limited to your own company, enforced on every request — not by hiding buttons.

Your own copy. Most tools are generated per department: name it, choose its icon, grant your people. Two teams can run the same tool and never see each other's data.

Bring your holiday spreadsheet.

We will set up two countries and two working weeks in the demo and show you the same request counted correctly in each.

Book a demo