Dashboard
Weekly schedule
Pick a garage, then tap a cell to set that day's shift (start & end, AM/PM). Empty = day off (that worker can't clock in there that day). Only workers assigned to the garage appear. Times use the garage's timezone.
Hours
Clock times are changed by hand only by the clock-time editors (Bayram, Burak, Rakin, Emin).Clock hours (Clock In → Clock Out) is the payroll basis, split into Regular (up to 40/week) and Overtime (beyond 40/week, per Sun–Sat week). A ⚠ badge means some punches couldn't be paired (e.g. a missing clock-out). Tap a worker to see and correct each shift. Overtime is complete only for an admin viewing All garages — the Gusto export always computes it that way.
Labor Cost
Daily labor cost by position. Chart and distributions use flat wage (hours × rate) so segments are consistent. The reconciliation below adds the overtime premium (extra 0.5× on overtime) for the true payroll total — this matches the Hours tab exactly.
Garages
Workers
Two doors, both fine: invite sends a Slack link and the worker picks their own PIN; the form below is the classic way — you type the PIN for people who'd rather have it done for them.
Workers
Organisation
Add user
Access level is what they can see: an admin sees every garage and can manage users; a manager only sees the garages you assign — everything else is invisible to them, including in the API. Job title is just what they're called ("Midwest Regional Manager") — add as many as you like, it changes nothing about their access.
Users
Garage Issue Tracker
What the attendants find on their rounds — leaks, broken concrete, lights out, abandoned cars — reported from any tag with photos, a location and a floor. Click a ticket for the whole story: photos, the history and comments from both sides. Safety issue is the only thing that makes a ticket urgent; Pending → In progress → Resolved; "Still there today" moves the last-seen date. The client (partner login) sees and works the same list, minus what is hidden.
Follow-ups — promises people made
Spark's, Vend's or a supplier's word, with a date. On the due day the bot asks once in the garage's channel; closing stays human.
Launch boards
One board per garage launch, built from the Spark launch playbook (4 phases, 47 items, the go-live gate). The board is a link anyone can open — Spark or Vend, no login: they type their name once, change statuses, set owners, add tasks and comment under every topic. Deadlines are computed from the go-live date and move with it.
Activity
Who changed what. Manual time entries, approvals and pay-rate changes all leave a trace here — so a correction can always be traced back to the person who made it.