PUNCH · geofenced time clock

A shift opens only after you have been inside the fence continuously for the arrive delay, and closes after you have been outside it (plus 25 % slack) for the leave delay. That hysteresis is what stops GPS drift on the property line from chopping one day into a dozen fragments.

Miter has no employee-facing write API, so nothing here can punch you in on their side. Export this sheet and check it against your Miter timesheet — if the two disagree, this one can prove its own history.

The moment the fence confirms you are on site, this chases you until you say you are clocked in: an alert on the phone, then a text four minutes later, then the line calls you and says it out loud at nine. Answer any of them and the rest stop. Leaving the site stops them too — an alarm that keeps going after you have gone is one you learn to ignore.

Miter publishes no employee API, so there is no supported way to punch on their side. This replays the request your own signed-in session makes, which you supply below as a small JSON recipe. Best-effort by design: if it works you are simply clocked in, and if it does not, the escalation above takes over the same second. A stale token costs you nothing but a text message.

The phone app needs a device token — that is what lets it report location in the background without a browser session. Mint one, paste it into the app, and revoke it here if the phone is lost.