Getting started
System rules & definitions
The decisions HumanR makes on its own — how a leave day is counted, when a ticket falls due, who lands on a payslip, why a name drops off a chart. None of these live on a settings screen, so this page is where they are written down in plain language. If a number here surprises you, this is the page to point at.
This is the guide HumanR users read inside the product, published as-is. It is written for someone with the screen in front of them, so it describes buttons you cannot click from here — which is rather the point: you can check how the product behaves before you commit to it.
Who counts as staff
A great many screens answer "for the people who are currently with us." That group is everyone whose status is Active, On leave, Pending arrival (hired, not yet landed) or Missing. People marked Resigned or Terminated drop out of the active workforce — they stay in history and reports, but not in the day-to-day counts.
The pay month
A payroll month does not follow the calendar. The month labelled June runs from 25 May to 24 June — it opens on the 25th of the previous month and closes on the 24th. Attendance and leave are lined up to the same window, so a day counted for attendance is a day paid in the same run.
A payroll run only pays people who are Active or On leave for that month. Everyone else is skipped.
Leave & entitlement
Annual leave is counted in working days.
For annual leave the days charged are the calendar span minus the Fridays and public holidays inside it. Every other leave type (sick, emergency, no-pay…) charges the plain run of days, Fridays and holidays included.
First-year annual leave is pro-rated.
In someone's first year the annual-leave entitlement builds up at roughly 2.5 days a month of service (the tracker's "days served ÷ 12"), rounded to whole days. Once a full year is served they get the flat yearly entitlement. The credit lands on the anniversary of their join date, not on the join date itself.
| Rule | What it means |
|---|---|
| Balances do not carry over | Each cycle (the year between one credit and the next) starts fresh at the full entitlement. Unused days are not banked, and a negative balance does not follow anyone into the next year. |
| Unpaid leave never goes below zero | No-pay and unauthorised balances floor at zero — but the days are still deducted from that month's pay. |
| Spans include both ends | 17 Mar to 20 Apr is 35 days, not 34 — the first and last day both count. |
| Friday is the weekly day off | Fixed throughout the system. |
Home tickets
A paid home ticket falls due on an interval that depends on the staff level. The intervals are set on Leave › Ticket rules and the seeded defaults are:
| Level | Ticket falls due |
|---|---|
| Support (SPT) | every 4 years |
| Supervisory (SPV) | every 2 years |
| Managerial (MGR) | every 1 year |
The clock runs from the later of the last ticket granted and the join date, plus the interval. Only foreign staff earn tickets, and only those not marked "not eligible". The Leave › Standing page is where the next-due date shows.
This same level list is what the workforce dashboard groups staff by, in the order the levels appear on the ticket-rules screen. The Lead tick there marks the levels whose departure the dashboard counts as a regrettable loss — so a level you add shows up in the charts on its own, rather than as "(unknown)".
Pension & allowances
| Item | Rule |
|---|---|
| Pension (MPRF) | 7% from the employee and 7% from the employer. |
| Ramadan allowance | A flat MVR 3,000, paid once a year in the Ramadan run, to staff recorded as Muslim. Always paid in rufiyaa, even for staff on a dollar package. |
| Dollar reporting rate | Where dollar and rufiyaa pay are shown side by side, USD is converted at a fixed 1 USD = 15.42 MVR. This is for reporting only — it does not change what anyone is actually paid. |
| Multi-package staff | Someone with more than one salary package has one main package (the one with the larger basic). Pension, overtime, the Friday allowance and increments all attach to that one; deductions go to whichever package matches their currency. |
End-of-service gratuity defaults to 0 days per year — the Maldives has no statutory gratuity, so nothing is accrued unless a policy is set.
Overtime & late fines
Both overtime and late fines are off until you switch them on, and every number below is a default you can override per work site or per salary package on Attendance. Nothing here is baked in.
| Setting | Default |
|---|---|
| Standard hours / break | 8 hours a day, 1 hour unpaid break |
| Overtime rate | 1.5× the hourly rate |
| On-time cutoff | 08:45 — a punch after this is late |
| Grace period | 0 minutes |
| Fine basis | Charged on basic salary, over a 30-day month |
| Rounding | Lateness truncated to whole minutes (07:12:59 late counts as 7 minutes) |
A late fine works out to: minutes late × (basic ÷ 30 ÷ 8 ÷ 60) × the multiplier, added up day by day. The Attendance guide walks through it in full.
Attendance days
- Every Friday is treated as a holiday — never counted as a working day.
- When a day is scored, the order is Present (there is a punch) beats On leave beats Holiday beats Absent. A punch always wins.
- The attendance figures refresh on their own about every 15 minutes, so a late-arriving punch is folded in without anyone re-running anything.
See the Attendance guide for the upload wizard and the register / timesheet screens.
Work status & deployment
On the deployment tracker a person's status for a day is worked out in a set order, and the most specific answer wins:
- Approved leave — if they are on leave, that is the status, full stop.
- A manual override for that person and day.
- Their unit — the vessel or machine they are on, versus the site it sits at. If both carry a status, the more serious one wins; on a tie the machine's status beats the site's, because it is the closer claim.
- The default — see the callout.
What dashboards leave out
Charts trim themselves to stay readable. It is worth knowing what gets trimmed, so a small figure "missing" is never a mystery:
| Where | What it does |
|---|---|
| Time range | Analytics run over 3 to 36 months (12 by default). Shorter is too noisy to read a trend; longer is rarely useful. |
| "Other" bucket | Charts keep only the largest few groups and fold the rest into Other — the top 10 departments, top 8 nationalities, top 7 leave types. A small department can disappear into Other. |
| Thin attendance | A department with fewer than 20 recorded attendance days is left off the attendance-rate chart — too little data to be fair. |
| "Regrettable" leavers | When turnover is split into regrettable and not, only exits at a level ticked Lead on Leave › Ticket rules count as regrettable — supervisory and managerial by default. Other exits are still counted in overall turnover, just not flagged as the losses that hurt. |
| Retirement watch | Staff aged 56 and over are surfaced as approaching retirement. |
| Appraisal scores | The score scale is read from the data — out of 5, out of 10, or out of 100 — so bands adjust automatically. Comparing scores captured on different scales can mislead. |
Several dashboards also flag things by age: onboarding stalled past 14 days, a recruitment request older than 90 days, a disciplinary letter unacknowledged past 14 days, a document lapsing within 30 days.
Default report scope
Most lists open already filtered to the rows you usually want, with a scope chip at the top telling you so. Clear the chip to see everything. The common defaults:
- Staff lists exclude terminated and resigned people ("excluding past staff").
- Employee documents show those expiring within 90 days.
- Onboarding shows those in progress; deployments show open placements.
- Disciplinary cases hide closed and withdrawn; recruitment hides cancelled and onboarded.