Check Where and When Staff Clocked In

Job Check-Ins helps supervisors verify when and where field work started. Use the record alongside the job assignment and completion evidence, not as the only measure of work quality.

What you will accomplish

By the end of this guide, you will be able to complete a staff check-in review from the correct CleanOver screen, understand the important checks before saving, and verify that the result is visible to the people who use it next.

Before you begin

• Choose the service date and staff member.
• Understand the business policy for location and time review.
• Sign in to the Admin workspace and confirm you are in the correct business context.
• Use real operational dates and the property’s local timezone when the workflow includes time.

Step 1: Open Job Check-Ins

Go to Team Management > Job Check-Ins. Set the date or reporting range before applying other filters.

Expected result: The table covers the intended work period.

Step 2: Filter by staff or unit

Use the staff and unit controls to narrow the list. Keep the scope broad enough to see consecutive jobs when reviewing a route.

Expected result: Relevant check-ins are easy to compare.

Step 3: Compare planned and actual time

Open Jobs for the same date and compare assignment, expected window, check-in, and completion. Allow for approved travel or access delays.

Expected result: A real exception is distinguished from a normal timing difference.

Step 4: Review location context

When location information is available, compare it with the property and known device accuracy. Treat weak GPS as a signal to investigate, not automatic proof of misconduct.

Expected result: Location concerns are evaluated fairly and factually.

Step 5: Check missing or duplicate records

Look for jobs with no check-in and multiple records for the same person and job. Confirm sync status before making a correction.

Expected result: The timeline has no unexplained gap or duplicate.

Step 6: Document a correction

If a manual backfill is required, record the verified local time and reason. Preserve the original evidence in the appropriate operational note.

Expected result: The audit trail explains the change.

Step 7: Escalate material exceptions

For a meaningful discrepancy, contact the supervisor and follow the business’s review process rather than editing records casually.

Expected result: The right owner is handling the exception.

Step 8: Close the daily review

Confirm all high-risk jobs have a reasonable start record or documented explanation.

Expected result: The day’s check-in review is complete.

How to confirm the workflow is complete

• Refresh the destination list or calendar and confirm the saved record appears only once.
• Check the unit, date, status, owner or assignee, and any linked record before leaving the page.
• Open the next downstream view mentioned in the guide and confirm it shows the same information.
• Record an internal note when the action corrects historical data or changes another person’s responsibility.

Common issues and what to do

The expected record is missing

Clear old filters, check the date and business context, then search by the most specific identifier available. If the data comes from a connected provider, check connection and mapping status before recreating it manually.

A button is disabled

Look for a required field, incomplete checklist item, missing permission, locked lifecycle status, or unresolved linked task. Complete the highlighted requirement instead of trying to bypass it.

The page shows different information after refresh

Another user or integration may have updated the record. Compare timestamps and the source system, then apply the correction in the system that owns the data.

You are unsure whether to continue

Stop before cancelling, overwriting, revoking, or issuing a financial document. Ask the workflow owner to confirm the intended outcome and add that decision to the internal record.

Best practices

• Use clear names that make sense to a new team member without extra context.
• Prefer the smallest safe scope for bulk actions, filters, permissions, and date ranges.
• Keep guest-facing communication separate from internal diagnostic notes.
• Verify a high-risk change in a second view before considering it finished.
• Update the source configuration when the same correction is needed repeatedly.