Timesheets that add themselves up, and lock when you're done

Every clock-in becomes a timesheet line with hours, breaks, overtime and pay worked out by your rules. Fix what needs fixing with a reason, approve the week and close the pay period.

Free for up to 10 people, with every feature. Not a trial.

KiteClock timesheets for one week: hours per day for each person, the total, regular hours and pay.

How it works

  1. Hours arrive

    Clock-ins, breaks and clock-outs become shifts, split at midnight UK time, with pay worked out by your pay rules.

  2. Issues are flagged

    Missed breaks, long shifts, clock-ins outside the fence and missing pay rates show as issues to review.

  3. Approve and lock

    Staff submit, managers approve, and closing the pay period locks every hour in it.

One grid for the whole team

The week grid has one row per person with their hours each day, the total, regular and extra hours, and pay. Issue badges show where something needs a look.

Shifts that cross midnight stay whole and are split at local midnight for pay, and the clocks going forward or back are handled, so a night shift is always paid for the time actually worked.

  • Week, month and pay-period views
  • Everyone, with issues, or with hours
  • Method and policy shown for each clock-in

Edits with a reason, every time

A manager can add a missed shift, fix a clock-out or add a break, and every change needs a reason. The old value, the new value, who changed it and when are kept.

Staff can ask for a change from their app; a manager approves or rejects it. Shifts can't overlap, and deleted shifts are kept for the record.

  • Reasons on every edit
  • Full change history
  • Staff edit requests

Pay rules, then a period you lock

Pay rules cover daily and weekly overtime, pay-period thresholds, consecutive days and bank holidays, with multipliers, and never count the same minute twice. A missing pay rate leaves the amount blank and raises an issue; it's never shown as £0.

Pay periods can be weekly, fortnightly, 4-weekly or monthly. Open issues and anyone still clocked in block approval. Once a period is closed, no hours in it can change; reopening is for admins, with a reason.

  • Overtime and bank holiday rules
  • Approval blocked by open issues
  • Closed periods locked in the database

Questions

How are overnight shifts handled?

A shift that crosses midnight stays as one shift and its hours are split at midnight UK time for pay, including on the nights the clocks change.

Can managers change a timesheet?

Yes, with a reason each time. KiteClock keeps who changed what, when, the old and new value and why.

Can staff see and confirm their hours?

Staff see their week in the app, can ask for a change, and submit their timesheet for approval.

What stops hours changing after payroll?

Closing the pay period locks every shift, break and edit in it. Reopening needs an admin and a reason, and is logged.

Does it work out overtime?

Yes. Pay rules for daily, weekly and pay-period overtime, consecutive days and bank holidays, with multipliers, apply automatically.

What if someone has no pay rate?

The pay is left blank and an issue is raised so it's fixed before payroll. KiteClock never shows unknown pay as £0.

Free for up to 10 people

Every feature, not a trial, no card needed. Bigger team? Try everything free for 14 days, or book a demo.