Attendance

Clock in. That's the whole job.

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.

Start, Break, Resume, Stop. Expected hours drop on their own when leave is approved.

Start, Break, Resume, Stop on one screenExpected hours from schedule minus leaveKiosk tablet with card or rotating badgePunches never edited - corrections append
What changes

Presence without the police

A working-time record people will actually keep - and a manager can defend.

Time

Four buttons, one screen

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

Camila Ortiz

Product Engineer · Tue 27 Jan

Working
Working

since 09:00 · unpaid meal when you break

BreakStop
Expected today8h 00m
Schedule − approved leave
Time

Hours that already know leave

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

Fixed daily quota8h flat
Leave / HolidaysIgnored
Short 4h · Flagged as late

SquadBear model

Scheduled schedule6h
Approved leave / holiday-2h
Honest expected4h
Reconciled · No surveillance
No webcamNo GPSIndependent recordsGDPR & EU compliant
Time

A tablet by the door

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

Hold your card or badge

Tomas Weber

Card ending · 84F2

In · 07:58

Uplink dropped at 07:40. Punch queued, stamped 07:58.

Clock · Show my badge

SquadBearCLOCK
Wallet

Tomas Weber

Rotates in 4:12

No GPSNo webcamSame punch as Clock
Time

Exceptions, not a spreadsheet

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

Platform · 2 need a decision

Needs review
Tomas Weber

Fri 24 Jan · Correction request

Waiting on you
Recorded09:00 → open · auto-closed 00:58
Proposed09:00 → 17:30 · “Forgot to clock out.”
Marta Nowak

Approve appends new punches. Originals stay, superseded.

Approve
Time

Who is in, without tracking where

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

Platform

2 working1 on break1 not in
  • Camila Ortiz

    In since 09:00

    Working
  • Elena Vargas

    Break since 15:00

    On break
  • Leo Novak

    Annual leave (approved)

    Not in
  • Mila Nowak

    In since 08:30

    Working

A work schedule is a daily duration, not a 09:00 start. Presence reports state, never lateness.

Why teams pick it

People actually clock

Four buttons beat a portal. The habit sticks.

Hours you can defend

Punches are never rewritten. Corrections have a trail.

Shop floor and laptop, same record

A kiosk writes the same punches Clock does.

Managers only see what needs a decision

The queue is exceptions and corrections, not every punch.

See it in action

Or your team can simply ask

Plain language in, the right thing done - correctly, and always within your rules. Here's a real example.

Engineering Lead · ClaudeLive Assistant · Scoped OAuth
Prompt

Show me every attendance review item still open in Platform, oldest first, and say which ones are short days.

Live Recordlist_attendance_review
3 open · Tomas correction (Fri, forgot clock-out) · Camila auto-closed · Jin short day (−46m)
Inspect query parameters{ "status": "open", "teamId": "team_platform" }
Live Recordlist_team_presence
4 working · 1 on break · Camila not in (leave)
Inspect query parameters{ "teamId": "team_platform", "state": "on_clock" }
Three open items, oldest first: Tomas’s correction (forgot to clock out Friday - proposed 09:00–17:30), Camila’s auto-closed shift, and Jin short by 46 minutes. Only Jin is a short day. Camila is on approved leave today, so she is not on the clock. I can approve Tomas’s times if they look right - originals stay on file.
Every tool shown ships in the product

Questions, answered

Is this the same as time tracking?

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.

Do you track location or watch people work?

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.

What if someone forgets to clock out?

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.

Is the kiosk required?

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.

Does this calculate pay or overtime?

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.

Can people clock from Slack?

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.

Can different offices have different rules?

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.

Less admin. More of the actual job.

Try the live demo - three ready-made sign-ins, real data, nothing to set up. Or start free in minutes.