Field Staff Onboarding Checklist

This checklist takes a new cleaner or field technician from an invited user to someone who can safely see, start, and complete assigned work.

What you will accomplish

By the end of this guide, you will be able to complete a field staff account 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

• Have the worker’s preferred name, email or phone number, company, manager, and first working date.
• Decide which job types, teams, and locations the worker should be allowed to access.
• 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 Users

Go to Team Management and select Users. Review the existing company and subgroup structure before creating the worker so the account is placed in the correct reporting line.

Expected result: The company and user groups are visible.

Step 2: Create the user profile

Select the add-user action and enter the worker’s contact details exactly as they will use them to sign in. Avoid shared addresses because notifications and audit history belong to one person.

Expected result: A unique user profile is created.

Step 3: Assign company, role, and permissions

Choose the worker’s company or subgroup, set the field role, and grant only the modules needed for assigned work. A cleaner normally needs Jobs and checklist access, not financial administration.

Expected result: The worker has the minimum correct access.

Step 4: Set job and deep-clean eligibility

Review job-type permissions and any Deep Clean Tracker authorization switches. Enable specialized work only after the worker has been trained for it.

Expected result: Dispatch can distinguish regular and specialized staff.

Step 5: Add availability

Open Resource Planning and record the worker’s normal availability, time off, or recurring schedule. Accurate availability prevents dispatchers from assigning work during unavailable hours.

Expected result: The worker appears on the planning board with a usable schedule.

Step 6: Publish the onboarding notice

Use News to share the current operating instructions, emergency contacts, or first-week announcement. Keep sensitive credentials out of the post.

Expected result: The worker can see the relevant onboarding communication.

Step 7: Test with a real assignment

Assign one low-risk job, then ask the worker to sign in, open the job, read the unit notes, and locate the checklist without completing the job.

Expected result: The worker can access the correct job and cannot access restricted areas.

Step 8: Complete the first-shift review

After the first shift, check Job Check-Ins, checklist answers, and completion notes. Correct access or training gaps before assigning independent work.

Expected result: The onboarding record is complete and the worker is ready for normal scheduling.

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.