Time Allocation

Open this screen in Saral/hr/time-allocation

For the workers in a group — a factory, an office, a workshop — how each day's hours split across the projects they worked on, typed as normal hours plus any overtime and saved as one grid. It is how wage cost is allocated to projects for the people whose time is not captured site by site on the register. Saral allocates cost; it does not run payroll, which stays in your payroll app.

You enter

Hours per worker per project per day, with overtime on top (a 10-hour day is 8 + 2 OT); Day view is workers down, projects across; Week view is a worker's projects by day.
Assign crew: one project, one figure, a set of workers, every day on screen. Copy yesterday / last week to start from the previous period.
Set method per worker: Recorded (their cost follows the hours they log — the default), Standing (a fixed split pre-filled each week), or Derived (they log nothing; their cost is spread over the company's busiest projects in proportion to hours actually worked).

Saral fills in

The roster from the chosen worker group, each worker's expected hours and how much of their week is logged; the counts line — recorded, standing, derived, and who is under-recorded (below 80% of their expected hours) and should be chased. Derived staff are never flagged: they do not log.
The project columns from existing allocations, plus any you add; the week's totals, tinted when a day runs long.

It produces

Each worker's allocation per project per day, stored as the day's total hours with the overtime part recorded — what the project cost reports and the HR cost views read.

What this page is for

Site workers are captured site by site on the Site Register, so their cost already sits on a project. Factory, office and workshop staff are not: their day is one number of hours and a question of which jobs it went on. This board answers that question for a whole group at once, so the project cost reports carry the true labour cost and the payroll journal can be split by project. It allocates; it does not calculate pay. Payroll runs in your payroll app, and Saral never produces a payslip.

Three methods

Recorded is the default and right for crews whose cost follows what they log: hours are typed here, overtime on top. Standing is for people whose split rarely changes: a fixed split pre-fills their week and they correct it only when it moves. Derived is for indirect staff — accounts, admin, management — who log nothing; their cost is spread across the company's busiest projects in proportion to the hours actually worked on them, so it follows the work rather than an invented percentage. The method is set per person from Set method and remembered.

Normal hours and overtime

Every cell is normal hours plus an OT box. Overtime adds to the day — 8 + 2 OT totals 10 — and is stored as the day's total with the overtime part recorded separately, so cost and pay rules downstream see the total exactly as before while reports can still show the overtime. A day over 12 hours is tinted amber and over 24 red as a prompt to check.

Who to chase

The counts line is the manager's whole job in one row: how many are recorded, standing and derived, and the under-recorded badge — anyone on Recorded or Standing with expected hours who has logged under 80% of them. Derived staff are exempt by construction; flagging them would train everyone to ignore the flag. A monthly confirm-your-time email to office workers exists as a separate rollout switch, off unless your account turned it on, and it never reaches CIS workers.

Where the settings live

Worker groups and their members are HR → Settings → Worker Groups. Each worker's expected hours come from their contract on their worker record. The monthly time-confirmation email and which worker types receive it are on HR → Settings → Project Time Confirmation. The project list is the HR site list on HR → Settings → Sites.

Next screen: /hr/live-map

Not what you needed? Inside Saral, ask Kuku (Alt+K) — if it cannot answer, “Ask a human” sends the question to Saral support with the chat attached.