Hourly employee

An hourly employee is paid for the time actually worked at an agreed rate per hour, rather than receiving a fixed salary regardless of how the month falls. Work forty hours and the pay reflects forty hours; work thirty-two and it reflects thirty-two.

Two things this is often confused with. It is not the same as temporary or short-term work, because an hourly employee can hold a permanent position for years. It is also not the same as low-skilled work, which is a stereotype rather than a rule. The only variable that defines the term is how pay is calculated.

What changes once pay is per hour

• The time record becomes the payroll basis. With a salary, an imperfect record is an administrative annoyance. With hourly pay it is the number people get paid on, so errors are disputes rather than tidy-ups.
• Overtime stops being abstract. Every hour past the norm has a price attached, which makes scheduling decisions visible in the cost line immediately.
• Income varies. A short month, a public holiday or a quiet week all land on the employee, which is the main fairness question this model raises.
• Borderline time needs a rule. Travel between sites, handover before a shift, standby, training: each is either paid or not, and that has to be decided in advance rather than argued about later.

Where hourly pay genuinely fits

It fits where the volume of work is uneven and known only shortly in advance: shift operations, retail and hospitality, warehouses and logistics, support lines with peaks, and seasonal work. It also fits professional services that bill by time, where an hourly cost per person is what makes project profitability calculable at all.

It fits badly where the output is not proportional to hours. Paying a designer or an analyst by the hour rewards slowness and quietly penalises the person who solves the problem in two hours instead of six, which is the opposite of what the arrangement is supposed to do.

What it costs to get wrong

Almost every dispute in hourly work comes down to the same thing: the employer cannot prove what was worked. Records reconstructed at the end of the month from memory, rounding that always falls in the company's favour, unpaid handover minutes that add up to hours across a year. In an inspection or a claim, the absence of a reliable record is generally read against the employer rather than the employee, so the record is a protection for both sides rather than a bureaucratic chore.

The second recurring failure is treating overtime as a scheduling convenience. Hours past the norm carry a premium and often a cap, and a roster built without checking either turns into a payroll surprise and a compliance problem in the same week.

How PeopleForce handles hourly work

The record itself sits in Time, where hours are logged against days and projects and pass through approval before they count, so what reaches payroll has been reviewed rather than typed in at the end of the month. Attendance policies define what the norm is, which is what makes an hour past it identifiable as overtime instead of a manual comparison.

On the money side, each person carries a cost rate and a billable rate on their profile, and both can be overridden per project with their own start and end dates. Logged time is converted into cost using that rate, so an hour recorded becomes a number in the project view without a separate spreadsheet, and the gap between cost and billable rate is visible where it matters. The employment arrangement itself is a separate work type field in Core HR, so hourly staff can be reported on separately from salaried employees.