Timesheets and holidays, without the HR project.
Outgrown spreadsheets? Don't replace them with an HR system you need a project to run.
For teams of 5 to 200+ who bill clients by the hour, and are still doing it in a spreadsheet.
Priya Raman
Week ending Fri 12 Sep
| Client | Mon | Tue | Wed | Thu | Fri | Total |
|---|---|---|---|---|---|---|
| Northwind Rail | 7 | 7 | 8 | – | 4 | 26.0 |
| Halcyon Group | 1 | 1 | – | – | 3.5 | 5.5 |
| Annual leave | – | – | – | 7 | – | 7.0 |
| Total | 8 | 8 | 8 | 7 | 7.5 | 38.5 |
38.5 hours, submitted to Dan Okafor
ApprovedFill it in on Friday. Invoice it on Monday.
Everyone logs their own hours
One sheet covers every client someone worked on that week. Half days, TOIL and non-working days come from their working pattern, so nobody does the maths by hand.
Managers approve their own team
Permissions are set per person, so a manager sees their team and nobody else's. Approve a week, or send one back with a reason attached.
Book time off in the same place
Someone picks the days and their manager approves them. The allowance updates itself, and bank holidays for their region are already on the calendar.
Claim what the week cost
Lines go on a request with the type, the reason and the cost, and the total adds itself up. Submit it and it joins the same approval queue as the hours.
Report on it by client
Break a month down by client or project, then export it in the shape your invoicing needs. The numbers reconcile because they came off the same sheet.
30 sec
to review and approve a full week
Everything it does today.
Everything on this list is available on the day you sign up.
One sheet, every client.
Half days, TOIL and non-working days come off the working pattern, so nobody does the maths by hand.
A manager sees their team and nobody else's.
Approve a week, or send it back with a reason attached.
Leave stops living in email.
Someone requests it, their manager approves it, and the allowance updates itself.
Part-time, compressed and four-day, all of it.
UK bank holidays by region, applied automatically.
Receipts stop being emailed around.
Someone submits an expense with the receipt on it, their manager approves it, and on approval it can go straight to your accountant's inbox.
A month broken down by client, in the shape your invoicing needs.
The numbers reconcile because they came off the same sheet.
One current record per person.
The alternative is four versions of it in four folders.
No app to install.
It works in the browser people already have.
8
capabilities, every one included
What we left out.
We built this for ourselves before we sold it to anyone, so the things that are missing are missing on purpose.
No role hierarchy to model.
Permissions are granted per person, per action: the same three for hours, holiday and expenses. A manager who approves for three people approves for exactly those three.
No workflow builder.
Requesting leave, approving a week and exporting a month are the workflows. They do not need configuring.
No modules to buy.
Everything is in the £6.
0
modules to buy
Where the hours end up.
An approved week is only useful once it reaches the place you invoice from. Exports are configured rather than fixed, so what comes out is the shape that client already expects.
An approved week
The same figures the manager signed off. Nothing is retyped on the way out.
Shaped per client
Columns, grouping and headings belong to the export, and a client can carry its own as a default.
A spreadsheet
Formatted, grouped and titled, ready to sit beside an invoice.
An email
The breakdown in the body, addressed to whoever needs it, including an inbox outside the company.
Enterprise level security without enterprise cost.
Where it runs
- Your own database
- Your own application service
- Hosted in the UK on AWS
Checked by somebody else
How it is handled
- TLS 1.2+ in transit, AES-256 at rest
- UK GDPR and Data Protection Act 2018
- An appointed Data Protection Officer
Your data isn't shared.
Most HR platforms keep every customer's records in one database, with everyone else. We give each customer their own database and their own application service, with its own credentials.
How most platforms do it
One database. Every customer in the same tables, told apart by a tenant column. A query written wrong is a query that reaches somebody else's people.
How we do it
Your database and your application service run on infrastructure that serves nobody else. There is no shared table to write the wrong query against.
1
database, and it is yours alone
£6per person, per month.
Plus VAT. No enterprise-sized HR bill, no minimum term, no modules to buy. Every feature below is included.
- Timesheets across unlimited clients and projects
- Approvals, with per-person permissions
- Holiday booking, allowances and a team calendar
- UK bank holidays and custom working patterns
- Expense requests, with receipts attached
- Per-client and per-project reporting, with exports
- Onboarding and offboarding
- Works on a phone without an app to install
From spreadsheet to first approved week.
Add your people
One at a time, as they are today. There is no import project to run first.
Set working patterns and allowances
Part-time, compressed and four-day patterns are all supported, and holiday allowance goes on at the same time.
Add the clients you bill against
The same names you already put on invoices.
Invite the team
They log their first week the same day.
10 min
to set a team up from scratch
The things you'd ask on the call.
Chinchill.hr is built, supported and used by Fat Potato, the UK software engineering company behind it. We bill by the hour ourselves, and needed to know what each client actually cost us. The tools we tried either priced us out or could not answer that question. Fat Potato holds ISO 27001 and Cyber Essentials Plus, and the platform sits inside the scope of both.