An Attendance Log That Answers One Question Honestly
Check in and out from the browser, optionally geo-tagged with a real street address. One shift per person, no overlaps, and corrections that leave a trail.
Attendance answers "were you on the clock", and deliberately nothing else. A shift is one span with no title and no project, so checking out never writes billable hours — that is what timesheets are for. What it does give you is a record you can defend: one open shift per person enforced in the database, overlapping spans rejected outright, and a location on the check-in if the person allows it.
- 1Check inOne tap when the day starts. If you allow location, the check-in carries the address it happened at; if you decline, the shift records anyway.
- 2Check outOne tap when it ends. Runs shorter than a minute are treated as misclicks and discarded instead of stored.
- 3Review, or correctYou see your own shifts; a manager sees the team's over any range up to 92 days. A wrong shift can be corrected rather than argued about.
Attendance log, in the concrete.
- Check in and out from the browser — nothing to install, no desktop agent
- Optional location on check-in and check-out, reverse-geocoded to a full street address
- Sharing location is refusable: decline and the shift still records, marked as no location given
- One open shift per person and no overlapping spans — enforced by the database, not by a screen
- Sub-minute misclicks are dropped rather than stored as a 12-second working day
- A shift left open past 16 hours is flagged for a human, never silently auto-closed
- Correct a wrong shift after the fact — the corrected times are what the log shows
- Team history for managers: any range up to 92 days, searchable by name and location
- Checking out records presence only. It never creates a billable entry or touches an invoice
3 steps, start to finish
No timer to start, no form to remember.
Check in
One tap when the day starts. If you allow location, the check-in carries the address it happened at; if you decline, the shift records anyway.
Check out
One tap when it ends. Runs shorter than a minute are treated as misclicks and discarded instead of stored.
Review, or correct
You see your own shifts; a manager sees the team's over any range up to 92 days. A wrong shift can be corrected rather than argued about.
The things people ask before signing up
No. Location is captured at the moment you check in and the moment you check out, and nowhere in between. There is no background tracking, no live map, and no location history — that last one is explicitly not built.
The shift still records. The refusal is stored as a refusal, so the log says "no location given" rather than silently showing a blank as if none was asked for.
No, and that separation is deliberate. Attendance is one span per shift with no project and no title; a check-out never writes a timesheet line. Billable hours come from your calendar, chat or the work timer.
Nothing is invented on your behalf. Past 16 hours the shift is flagged as stale and left for a person to fix, and it blocks your next check-in until it is resolved — deliberate pressure, rather than a made-up end time.
OpenStreetMap's Nominatim service, from the coordinates your browser reported. If it is unreachable the shift keeps the coordinates and skips the address.
