How SiteLog works

Getting the crew on

Nobody self-activates. An account starts in a pending status and stays invisible to the rest of the app until someone above them in the chain turns it on. The chain runs top to bottom: an admin activates supervisors, a supervisor activates foremen and quality control, and a foreman activates workers, surveyors, environmental staff, and safety reps. Each activator can only act within their own company, and only while their own account is active, so a suspended foreman cannot bring anyone else onto the site.

After activation, an account is active and gets the navigation shell, the dashboard, and everything its position permits. From there it can move to inactive or suspended if it needs to be pulled from the site; a pending or inactive account sees no navigation at all, just a plain screen telling them to wait for activation.

Clocking in is not the same as being cleared to work

Workers and foremen clock in from their phone at the start of the shift. That starts the time record for the day, but it does not by itself mean someone is cleared to be on site. The app tracks a second gate: whether that person has filed their Field Level Risk Assessment (FLRA) for the day. A foreman's crew board shows each worker as ready, needing an FLRA, or not present, so a foreman can see at a glance who has clocked in but still has not filed the hazard assessment, and send a reminder push before assigning them anything.

Circle checks work the same way for anyone operating equipment: they are logged independently of clock-in and clock-out, so a completed circle check is its own record, not a side effect of starting a shift.

Creating and assigning a task

Only a foreman or supervisor can create a task. When they do, they assign it to one or more workers and attach the PPE and hazard level the job calls for. If any assigned worker is a surveyor, the task must also be typed as either layout or as-built; the form and the underlying service both enforce this, so a surveyor task can never be saved without one of those two types set. The foreman who creates the task is recorded as its foreman, and if it needs sign-off later, it starts life flagged for approval.

Assigned workers and surveyors see the task on their own list and update its progress as they go, backing it with photos. When progress reaches 100 percent, the task is automatically marked completed. If it was flagged for approval, that completion is what puts it into the quality control queue; otherwise, it is simply done.

The QC gate

Tasks that require sign-off sit in a pending state until quality control reviews them. QC can approve the work, which closes it out, or reject it. A rejection is not a dead end: it automatically creates an alert that the foreman and supervisor can see, so the person who assigned the work is told immediately, without QC having to message anyone directly. Workers, environmental staff, and safety reps do not see that rejection alert; it is scoped to the people who can act on it.

What happens after a rejection

A foreman, supervisor, or admin can re-assign a rejected task from a dedicated section in the task list. Re-assigning does not edit the original task in place. It archives the original, and creates a new task carrying the same assignment details, with the QC reviewer's comments folded into the new task's notes so the crew sees exactly what needs to change. The new task keeps a pointer back to the one it replaced, so the lineage from the original attempt to the redo is never lost.

Archived tasks are hidden from the normal task views for most positions, but workers and surveyors still see their own archived, rejected tasks in their historical task view, marked with archived and rejected badges, so the person who did the original work can see how it was handled.

Seeing the whole picture

Hours, task status, and safety records roll up automatically as the crew works through the day. A supervisor's dashboard scopes this across the sites they oversee, an admin's scopes it globally, and a foreman's scopes it to their own company and site. None of this is a separate reporting step; it is the same data the crew is already entering through clock-in, tasks, and safety forms.