How do you know our cleaners actually showed up?

You should not have to infer attendance from an invoice or wait for a complaint. Slate gives each scheduled visit a record that can be reviewed against the cleaner’s check-in, location result, work progress, and check-out. That record is operational evidence—not a claim that software can prove every moment of a person’s presence—but it gives your team a clear place to start when a visit needs review.

Start with a scheduled visit

Before service begins, the visit is tied to a property, client, scheduled start, scheduled end when one is configured, and assigned cleaner. Slate’s cleaner workflow shows the visit on the day’s work list and on the visit detail screen. The cleaner can confirm the visit, mark that they are on the way, and then open the scheduled visit to begin the on-site workflow.

That sequence gives operations a useful expected-versus-recorded comparison. You can see which location was scheduled, what time window was planned, and whether the visit moved into an active state. A scheduled row by itself is not proof that someone arrived; the value is in the subsequent visit events.

Use GPS-supported check-in, with exceptions visible

At check-in, Slate can request the cleaner’s device location and compare it with the property’s geofence. The visit record can retain the check-in time, coordinates when available, the check-in source, and the resulting location context. Depending on the job’s configured geofence mode, an out-of-range result may be observed for review or may require an approved recovery path before the visit proceeds.

That recovery path matters in real buildings. A weak device signal, a permission problem, or a location that cannot be verified should not become a hidden failure. The cleaner can receive a clear location error and, where the workflow allows it, use the selfie-bypass path for an exception that operations can review. A bypass is not the same as a successful GPS match, and it should remain visible as an exception rather than being presented as ordinary location proof.

Check the visit record, not just the clock-in

The visit detail keeps the rest of the timeline with the check-in. Operations can compare the visit status with the recorded check-in and check-out, checklist progress, photos, and any location warning. Check-out is intentionally recoverable: a cleaner can finish the time record even when a device cannot provide GPS or the device is outside the fence, while the response preserves the outside-fence or no-location result for follow-up.

That separation is useful for client conversations. If a cleaner checked in inside the expected location and completed the visit evidence, the record supports a confident operational review. If the check-in used a bypass, happened outside the configured fence, or has no coordinates, your team has a specific exception to investigate rather than a vague “we think they were there.”

What the evidence can—and cannot—tell you

GPS is location evidence at a point in time, not biometric identity verification or a guarantee that every task was completed. A timestamp can be affected by device settings, permissions, connectivity, and the configured geofence. A visit can also be shared by a crew, so each cleaner’s progress needs to be read in the context of the assigned roster. For a quality or attendance review, combine the visit record with checklist completion, required photos, notes, and any access or incident report.

The result is a practical audit trail: scheduled work, a recorded arrival attempt, location context, work evidence, and a recorded departure. It helps facilities teams act quickly without overstating what a digital record proves.

See a clearer attendance workflow

Ask Slate to walk through how your locations would use scheduled visits, GPS-supported check-in, exception handling, and visit records—along with the review process for a no-location or outside-fence result.

Request a quote for your cleaning program