What to expect in your first week
Day 1 — setup
Finish the setup checklist. Create at least one live job. Add every worker who will be on site this week. Share app link + PINs. You should aim to have workers clocked in by end of day 1.
Don't expect the AI briefing to be clever yet. It has no data.
Day 2 — first clock-ins
Workers should clock in on their phones. Watch the Workers on site KPI on the dashboard — it updates live. If nobody's showing up, check Worker troubleshooting — it's almost always camera or GPS permission on first install.
Upload your first RAMS document so it's ready for workers to sign on day 3. See RAMS sign-off.
Day 3 — RAMS + messages
Workers see the RAMS in their app and sign off. Track progress in Compliance → RAMS. Try the Messages panel — send a quick message to a worker. You'll see replies appear in the console the same minute they send them.
Day 4 — the briefing starts getting real
With 3 days of clock-ins and RAMS, the morning briefing starts to flag things: workers who haven't signed in to a RAMS yet, certs expiring, anything that slipped. This is when Gaffer earns its keep.
Day 5 — Friday payroll dry-run
Open Payroll. You should see the week's hours per worker, overtime, and totals. Review for gaps, fix any missing events, approve. See Payroll & timesheets.
This is the first Friday where you shouldn't be reconstructing from WhatsApp screenshots. If you are, email us — we'll help you tighten the workflow.
When to worry vs. when to wait
- Worry now: workers can't log in, no clock-ins coming through, GPS rejected on site.
- Worry by end of day 2: briefing still blank, dashboard shows no activity.
- Wait a few days: the briefing feels generic, compliance score looks low, AI feels "light". It needs data to be sharp — that happens around day 4.