From the leader's Today's Crew roster, each name carries a Clock in / Clock out button. The entry records member_id as the worker but submitted_by, entered_by and entered_by_name as the leader, with clock_source='leader'.
Also called: clock in for another worker · dead phone · forgot to clock in · crew lead timesheet fix
- 1The leader taps Clock in beside a name; the request carries forMemberId.
- 2The server refuses unless the token belongs to a leader and that person is on his own crew, matching on the roster id or any alias the person has ever been known under.
- 3The job is taken from the LEADER'S open shift when he has one, since the crew works one job at a time and he is standing on it.
- 4With no shift of his own it falls back to deriving the worker's own current work, and refuses rather than guessing when that is ambiguous.
- 5Clock-out computes hours and stamps corrected_at plus the leader's name.
Someone forgets, someone's phone is dead, someone doesn't carry one — and that man still worked. A crew leader can clock a member in or out, and every entry made that way carries the leader's name, which is the difference between a record you can audit and a number you have to trust. He is not asked which job while his crew is on one, because that is a tap spent on a question that answers itself; it only asks when the crew is genuinely assigned to several. A man whose link was issued before he gained an office account still resolves to himself, so the leader never sees not on your crew beside a name he is looking straight at.
- A dead or absent phone leaving a worker with no record of the day.
- Untraceable manual timesheet edits.
- Leaders needing admin access just to fix one entry.
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →