See who actually did the work.
Hours and activity logged per person and team, so payday is based on real work, not a rough guess.
Free forever plan · No credit card required
- click to start the clock
- 0click to start the clock
- spreadsheets to reconcile
- 0spreadsheets to reconcile
- places each hour lands: your week and your pay run
- 0places each hour lands: your week and your pay run
The last week of the month
One is a message somebody has to answer from memory on the 30th. The other is a record that was already there on the 12th.
The 30th, without it
sent to 4 peopleNobody is lying. They are reconstructing a month from calendar invites, and two people reconstructing the same week will not produce the same week.
The 30th, here
nothing to askThe hours were recorded as they happened, both sides can open the same record, and the pay run reads these numbers rather than a re-typed total.
Time tracking only works if it happens during the week. Everything after that is archaeology.
Planned against actual
The week you scheduled, against the week that happened.
Every day is drawn twice — a dashed ghost for the shift you planned, a solid bar for the one that was worked. Thursday ran long. Friday is still running. The total at the end is what payroll reads.
On the clock right now
05:31:00
Alex K. · clocked in at 09:10
Straight into the pay run
- Hours tracked
- 0.0h
- Rate
- £35/h
- This week
- £0.00
Nothing was re-typed to get here.
From a shift to a number, without the archaeology
Hours only survive if they're written down while they're happening. Three steps, none of them at month end.
One click starts the clock, and the week fills itself in while you get on with it.
The rota you planned and the week that actually happened, drawn on the same axis.
The hours you tracked are the hours that get paid — nothing re-typed in between.
A standalone tracker will record the hours accurately
Then it exports them, and somebody re-types the totals into whatever runs payroll. That export is where the errors come from.
One week, across four tools (the messy way)
A week rebuilt on the 30th is a guess, however carefully it's done.
7 steps · 3 tools · 6 hand-offs
- Reconstructing the week from memory
- Cross-checking calendar invites
- Asking whether someone was in
- Reconciling two different totals
- Re-typing the hours into payroll
What gets lost along the way?
The same thing on one surface
3 steps · 1 tool · 0 hand-offs
One record · written while it happened · nothing re-typed
The hours were never the hard part. Getting them into the pay run without a spreadsheet in between was.
What gets tracked
The clock
Clock in and out
A running timer in the header, so tracking is one click rather than a habit to remember.
Schedule
The week's schedule
Shifts on a calendar everyone can read, in their own timezone.
History
Per-person history
Every day, clock-in, clock-out and total — no rebuilding it from memory at month end.
Team
Team activity
See who's on the clock right now without asking anyone.
Day end
Clock-out summary
A short recap when the day ends, so gaps get caught while they're still fixable.
Payroll
Straight into payroll
The hours you tracked are the hours payroll uses. Nothing gets re-typed.
Three teams, three reasons to track
The rota and the reality in one place
You planned the week on a calendar; you should be able to compare it to what actually happened.
- Shifts scheduled ahead, visible to everyone
- Clock-ins recorded against the day they belong to
- Both readable in each person's own timezone
04Straight answers
The questions teams ask about timesheets
If the answer you need isn't here, the free plan will get you to it faster than we can.
Start freeNo. It records clock-ins, clock-outs and scheduled shifts — the things a timesheet has always held. There's no screenshotting, no keystroke logging and no activity scoring.
Included in the same plan
It works with everything else you already have here.
Pick the perfect TeamCastle plan
Start free, upgrade when you outgrow it, or own it for life. Priced per person — cancel whenever.
Free
For a single team getting started.
Best for trying TeamCastle with one teammate
Get started freeNo credit card. No trial clock.
- 1 Workspace
- 2 Team members
- 2 Projects2 top-level projects, with unlimited sub-projects inside each.
- Team Schedule
- TimeSheets
- 5 Documents5 top-level documents, with unlimited sub-documents inside each.
See if it fits, with no clock running.
Pro
For growing teams that need the whole castle.
Best if you need Forms, ChatRooms or Onboarding
Start ProCancel anytime. Every member picks their own plan.
Everything in Free, plus:
- Unlimited workspaces, members & projects
- Unlimited documents
- Forms
- Team Onboarding
- ChatRooms
3 months FREE on LiraaNew Pro teams get 3 months free access to Liraa.
3 months FREE on NotavoNew Pro teams get 3 months free access to Notavo.
Everything unlocked, for each person on it.
Lifetime (LTD)
Pay once. Keep Pro forever.
Best if you'd rather never see this invoice again
Get Lifetime dealPays for itself in about 11 months of Pro.
Everything in Pro, plus:
- Lifetime access to the Pro plan
- All future Pro features included
- No subscription, no renewals
Cheaper than monthly Pro after 12 months.
- No credit card to start
- Cancel anytime
- Free plan never expires
- Your data stays yours
Your whole team, running from one castle.
Projects, docs, rooms, timesheets, and payroll under one login and one bill. Set it up in about two minutes.
- 1Create your workspace
- 2Move one live project in
- 3Watch the status-chasing stop
No credit card required · Free forever plan · Cancel anytime