Tomas Weber

Rotates in 4:12
Four buttons for the day. Expected hours already know leave. A lobby tablet writes the same punches. Managers only see the exceptions - not a map of where anyone went.

A working-time record people will actually keep - and a manager can defend.
Start, Break, Resume, Stop. The Clock screen changes with the shift. Times are the server's, so a wrong phone clock cannot rewrite the day.
Attendance · Clock

Product Engineer · Tue 27 Jan
since 09:00 · unpaid meal when you break
Expected time comes from the work schedule minus approved leave. A public holiday is zero. There is no late flag - a schedule is a daily duration, not a 09:00 start.
Traditional surveillance tools
SquadBear model
Pair a kiosk in Workspace settings. People tap a card or hold up a rotating badge from Clock. Offline punches queue and keep the time they were tapped. Same punches as the laptop clock. No GPS, no webcam, no iBeacon.
Kiosk · Building A lobby

Card ending · 84F2
Uplink dropped at 07:40. Punch queued, stamped 07:58.
Clock · Show my badge
Tomas Weber

Rotates in 4:12
Forgot to clock out? The shift auto-closes and lands in Attendance review. Short days, missed breaks, work on leave. People request a correction with a reason. Nobody edits a punch - an approval appends, and the originals stay.
Attendance · Review

Fri 24 Jan · Correction request

Approve appends new punches. Originals stay, superseded.
Live presence is Working, On break or Not in for the people you manage. It does not infer lateness, and it does not know where anyone is.
Attendance · Live presence

In since 09:00

Break since 15:00

Annual leave (approved)

In since 08:30
A work schedule is a daily duration, not a 09:00 start. Presence reports state, never lateness.
Four buttons beat a portal. The habit sticks.
Punches are never rewritten. Corrections have a trail.
A kiosk writes the same punches Clock does.
The queue is exceptions and corrections, not every punch.
Plain language in, the right thing done - correctly, and always within your rules. Here's a real example.
Show me every attendance review item still open in Platform, oldest first, and say which ones are short days.
list_attendance_review{ "status": "open", "teamId": "team_platform" }list_team_presence{ "teamId": "team_platform", "state": "on_clock" }No. Attendance records presence - in, break, out. Time tracking records hours against a project. Either runs without the other. When both are on, My week can show an attendance strip for today; clocking out never writes a time entry.
No GPS, no geofence, no webcam, no iBeacon, no keystrokes. Clock is on the phone or laptop. A kiosk is a shared tablet that reads a card or a rotating badge.
An open shift past the stale threshold closes on its own and opens one review item. Acknowledging it does not change the times. A wrong end needs a correction request, which a manager approves or rejects.
No. Attendance ships as its own module. Kiosk sits under it and stays off until you turn it on. Laptop and phone Clock work without a tablet.
No. It stores worked, break and expected minutes. Export a CSV from My attendance, or read shifts through the API or an agent. Payroll stays in the system you already run.
Not yet. Clock, a kiosk tablet, or an agent with the punch tool. Slack already does leave - /timeoff, /whos-out, Approve and Reject in DMs.
Yes. Several attendance policies at once, bound to a person, a team or a country. Breaks, short-day tolerance, over-schedule threshold, and whether leave warns or blocks at clock-in.
Leave, time, team health and the employee record work as one, so the picture is always joined up - a booked holiday is known everywhere, a new hire's day one starts itself, and a quiet team never slips through.
When booking leave is effortless and cover takes care of itself, people actually rest, managers stop firefighting, and you always know where the business stands.
Time tracking only matters when it's honest and effortless.
Great teams quietly drift long before they visibly break.
The moment someone is hired, their record exists, their onboarding tasks have owners and dates, and the policies that need signing find them by themselves.
SquadBear is the system of record.
Practical guides on this part of the job, written for teams small enough that the person reading this is also the person doing it.
A 2019 CJEU ruling made daily working-time records an employer duty across the EU. What a record must contain, who is exempt, and why a spreadsheet fails.
Read the guide →Hours data without spyware: expected hours from real schedules, a short editing window for honest corrections, and logging that costs seconds, not minutes.
Read the guide →Time tracking is three different products wearing one name. How to tell billing timers from capacity trackers, with verified July 2026 pricing.
Read the guide →Try the live demo - three ready-made sign-ins, real data, nothing to set up. Or start free in minutes.