The punch is kept on the phone
The app writes the punch to the phone's storage, with the time in UTC and the phone's time zone, the location and the photo if one was taken.
Works with no signal
Construction happens where the cell signal does not: basements, steel buildings, new subdivisions, rural lots. In BuildMore a punch made with no signal is saved on the phone with the exact time it happened and sent automatically when the connection returns. The timesheet shows it at the real time, and a retry never records it twice.
No card to start. Cancel from the panel in one click.

The app writes the punch to the phone's storage, with the time in UTC and the phone's time zone, the location and the photo if one was taken.
When it reaches the server, the punch keeps the moment it was made. A clock-in at 7:02 AM sent at 9:40 AM is a 7:02 AM clock-in.
When the phone gets a connection, or the app comes back to the screen, the queue is sent in order. Nobody has to remember to sync.
Each punch carries an id made on the phone. If the network fails halfway and the app sends again, the server recognizes it and keeps one.
When a photo is required, uploading it is part of sending the punch, so a punch never arrives without the photo it was made with.
The foreman can record the material a job consumed with no signal as well. It is queued and sent the same way.
Yes, for what happens on the site: clocking in and out, and recording material used. The punch is saved on the phone and sent when there is a connection. Signing in for the first time needs a connection.
No. The punch carries the time it was made, in UTC with the phone's time zone, so it is recorded at that time no matter when it arrives.
The queue is a file on the phone, not memory, so it survives the app closing or the phone restarting. It is sent the next time the app has a connection.
No. Every punch has an id created on the phone, and the server keeps only one punch per id.
30 days free, no card. Unlimited crew on every plan.