How do you get a new cleaner ready to work at our locations?

Slate uses a role-aware onboarding checklist to move a new cleaner from “not ready” to ready for assigned work. The cleaner sees the required steps they can actually complete, the current status of each step, and a link to the right place to finish it. Operations can use the corresponding readiness information to see what is complete, what is still blocking, and which items belong to the office rather than the cleaner.

Start with the required work

The cleaner opens Onboarding at /onboarding. Slate loads that cleaner’s current required steps, completion count, status labels, completion timestamps, and any help text. A step can link into the cleaner app, such as Academy training or a profile action, or open a configured external onboarding destination.

This distinction matters when onboarding includes payroll or identity work. Sensitive payroll and I-9 information is handled in the Zeal-hosted flow; Slate does not store the cleaner’s Social Security number or bank details. A cleaner should not be asked to email those details to an operations team or enter them into an unapproved Slate note.

Show progress without showing the wrong owner

The checklist is not a dump of every internal hiring task. The server marks whether a step is actionable by the cleaner. Admin-owned work—such as an office-managed invite, background-check step, or other configured gate—can remain tracked for readiness without appearing as a task the cleaner is expected to perform. Steps the office has skipped are also removed from the cleaner’s action list.

For a step that is actionable, the cleaner can see whether it is pending, in progress, or done and follow the deep link provided. If a course is attached to an onboarding step, the checklist can provide a secondary link to that course. Completion is refreshed when the cleaner returns from an external flow; a pending Zeal onboarding step can also be polled so the status does not depend on a manual refresh.

When there is no remaining actionable work, Slate redirects the cleaner away from the checklist. That prevents a stale “almost done” page from becoming the source of truth after the person is ready.

Resolve blockers in the right order

For the operations team, the useful question is not simply “Was this person invited?” It is “Which required item is incomplete, who owns it, and can the cleaner act?” The staff view can roll up completed and total onboarding steps, blocking-step labels, job-readiness state, and the time the person became ready. That gives a coordinator a practical follow-up list: help the cleaner with an app-owned step, complete an office-owned step, or check an external-provider status.

Onboarding completion also respects the published handbook. When a handbook is assigned, the current version must be signed with the required acknowledgments before onboarding can be completed. If no handbook is published, that specific gate is satisfied; Slate does not invent a handbook requirement for an account without one.

What this means for a multi-location client

You get a repeatable handoff rather than a manager’s memory of who is “probably ready.” Before assigning a cleaner to a location, the team can review the readiness record and follow up on the actual blocker. The cleaner receives one clear next action instead of a list of internal tasks that someone else must complete.

The exact steps, labels, external links, and readiness rules are account-configured. Onboarding status is not a promise that a cleaner has been assigned to a particular location, has attended a shift, or has completed every administrative action visible to authorized staff. Permissions also determine which staff members can view broader personnel details.

See the onboarding workflow

Ask Slate to map your hiring gates to cleaner-owned and office-owned steps, including the Zeal handoff, handbook requirement, Academy links, and the readiness review your operations team uses before placing someone at a location.

Discuss your onboarding workflow