Timesheets

A timesheet records time actually worked: a person, a position, a location, a start and an end, and the breaks taken. Staff usually create them by clocking in and out in Shiftly; your app can create them too, with timesheets:write, for example from a time clock of your own.

A timesheet your app creates is pending. A manager reviews and approves it in Shiftly, and only an approved timesheet reaches payroll. While it is pending your app can change or delete it; once approved it is read-only to you, and a change answers timesheet_not_pending.

Link a timesheet to the shift it fulfils with shift_id when you know it. Shiftly uses the link to compare rostered and worked time.

Shiftly works out pay from the business's award and pay rules. Your app never sends pay. With pay:read, each timesheet carries what it is worth; without it the pay field is left out.

A timesheet says whether a photo was taken at clock in and clock out, never the photo itself. For the bigger picture, Who's on now lists the staff clocked in right now, Timesheet totals adds up approved and pending hours over a range, and Labour costs sets rostered against actual hours per day and location.

• Timesheets need timesheets:read; creating them needs timesheets:write; pay needs pay:read as well.