Skip to content

Check-In and Site Arrival

Check-in creates accountability around who started work, where they were going and whether required checks were completed first.

WorkersBusiness adminsCoordinators reviewing attendance
Use this when

How SiteRun handles worker check-in, arrival, travel time, onsite time, blocked actions and clear recovery reasons.

SiteRun mobile Today dashboard showing required actions, alerts and bottom navigation for field use.
A blocked first job still shows site information while preventing check-in until the prestart is complete.

Workflow

  1. Open the assigned job from Today or Schedule.
  2. Review the address, site access notes, client contact and preparation notes.
  3. Start travel if the business tracks travel time.
  4. Tap Check in or Arrive once the required checks are complete.
  5. If blocked, read the reason and follow the linked action before trying again.

Operational notes

  • Server-side checks confirm the worker is assigned to the job before check-in is accepted.
  • Vehicle readiness, site requirements and critical defects can block field actions where the business enables those rules.
  • Blocked attempts should be visible to admins so the office can see why work was delayed.

Common mistakes to avoid

  • Assuming a blocked check-in means the job cannot be opened.
  • Using Arrive to bypass a missing prestart or site requirement.
  • Leaving travel or onsite time unrecorded when the business relies on timesheets.

Mobile notes

  • Keep location permission language plain so workers understand why arrival capture is requested.
  • Use Open maps from the job detail rather than copying addresses manually.
  • Retry a blocked action after completing the required check.

Ready to try this workflow?

Open SiteRun, create one real job record and test the steps with the crew member who will use it onsite.