Timesheets for construction and professional services
Your team books hours against projects, holiday and sickness on a fixed Monday-to-Sunday week. Managers approve or send it back with a reason. Overtime has to be authorised before it can be booked, so it is controlled at source instead of argued about at payroll.
No card required · Cancel any time · From £12 a month
| Project | Mon | Tue | Wed | Thu | Fri | Sat | Sun |
|---|---|---|---|---|---|---|---|
| PRJ-118Mechanical services | 7.5 | 4.0 | 7.5 | — | 3.5 | — | — |
| PRJ-204Commissioning witnessing | — | 3.5 | — | — | 4.0 | — | — |
| ABSENCEHoliday | — | — | — | 7.5 | — | — | — |
| Week total | 7.5 | 7.5 | 7.5 | 7.5 | 7.5 | — | — |
Monday to Sunday — fixed week, no locale drift
Comment per project per day — not one note for the week
Immutable audit trail — every approval and rejection kept
Where timesheets usually go wrong
Most timesheet tools record what happened and leave you to sort out the consequences. These three are enforced in the database, not just hidden in the interface.
An employee raises a request, the manager approves the hours, and only then can overtime be entered against those dates. Book more than was approved and it will not save.
Managers cannot send a week back without a reason. The employee sees the comment at the top of the week they need to fix, and the whole exchange stays on the record.
Set the bookable hours on a project and choose whether to warn or to block. You find out at 460 hours of a 500-hour budget, not when the final account is being argued.
One week, start to finish
Everyone starts on Monday, wherever they are and whatever their phone thinks the week begins. Rows carry over from last week if you want them to.
Several projects on the same day, each with its own comment describing what was done. Holiday and sickness sit in the same grid. It saves as you type, on a phone on site or at a desk.
Before it goes anywhere, the week is checked: missing comments, days over 24 hours, unauthorised overtime, projects past their cap. Fix the list, then submit.
Approved weeks lock and can be exported to Excel or PDF, or emailed straight to whoever needs them. Rejected weeks go back with the reason attached.
Unlimited projects and project codes, with per-person allocations if you need to cap who books what.
Absence sits in the same week as project time. No separate system and no add-on fee for it.
Hours per project, hours per person per project, absence, overtime and utilisation, over any date range.
Approved weeks export flat for pivoting, or as a branded PDF you can send to a client or to payroll.
On a phone the week becomes one card per day. Built for people filling this in from a plant room.
Row-level isolation between companies, UK hosting, and a full export whenever you want one.
Pricing
Every plan includes every feature. Add users to any plan, and if the next plan up would cost you less we move you to it and tell you.
30-day free trial, no card required. Prices exclude VAT. Need more than 100 users? Get in touch and we will put a plan together.
Long enough to run four full weeks, including the one where somebody submits it wrong and gets it sent back. That is the part worth testing.