Who came in today?
A row for everyone who works with you — whether they turned up or not — with their hours beside it. No location tracking and no device fingerprint.
Here, finished, and not in
A whole day at a glance: who is on the premises now, who has finished their shift, and who never came in at all. The person who never came in gets a row too — because the question you open this screen with is who is missing.
Clocking in from the top bar
Staff clock in and out from the same place they work all day, not from a screen they have to go to. A shift you navigate to is a shift somebody forgets to close.
Forgot to clock out? Correct it
The owner can move the end of a shift. It is never reopened — putting an honest end time on it is truer than leaving somebody on the clock two hours after they went home. The correction itself is recorded, before and after.
There is no such thing as "late"
Nothing in the system records what time anyone was expected, so lateness cannot be computed — and we are not going to invent it. The screen reports hours; judging them is your job.
Questions before you start
Do you record where staff are?
No. A shift holds who, which site, the time in and the time out — and nothing else. No coordinates, no IP address, no device fingerprint, and no permission in the app asks for a location at all. Competitors market coordinate-verified attendance; this is a refusal rather than a missing feature.
Who can see the rest of the team’s hours?
Only somebody with the team-management capability. Everyone else sees their own shifts. The screen refuses to open for anyone else rather than opening and showing one row — a list silently trimmed to one person is a screen that lies about being complete.
Does it produce payroll?
No. It gives you accurate hours and lets you export them, but there is no pay calculation, no overtime and no deductions. What it holds is what actually happened; the rest is a management decision rather than arithmetic that should happen by itself.