In this article
A ready-to-start assignment needs a confirmed assignment, completed applicable onboarding and an explicit operational release from the responsible process. Sending an invitation is only one event. Track the remaining decisions separately so nobody treats a candidate’s account as permission to begin work.
Understand the documented sequence
Ascen’s partner guide says to create the client and assignment before inviting the worker; an invitation without an assignment only creates an account. Its worker guidance asks people to review placement details before confirming them. The onboarding checklist varies with worker type, location and settings. These are useful product facts, but they do not reveal the status of any specific placement.
The agency’s readiness record should therefore distinguish at least three questions: does the intended assignment exist, has the applicable review finished, and has the worker completed what that assignment requires? Do not invent a new “green” status in a spreadsheet if the source system still shows an outstanding step. A summary should report the source status and the time it was checked, not replace it.
Use a small readiness card
Keep one operational card per assignment in the approved work system. Record the internal assignment reference, proposed start, actual work location, responsible coordinator, client contact and next unresolved action. Link to the authorized source rather than copying personal documents. The card is a coordination device; it is not a personnel file or a second onboarding portal.
| Gate | Evidence to ask for | What it does not prove |
|---|---|---|
| Assignment exists | Correct source record and reference | That all reviews are complete |
| Details match | Resolved role, location, dates and rate questions | That the worker has completed every step |
| Readiness confirmed | Confirmation through the approved process | That later changes need no review |
| Start communicated | Consistent instructions to the worker and client | That the first day actually occurred |
The card should show the next action, its owner and the time to check again. “Waiting for onboarding” is not enough. “Worker has a question about the displayed start date; coordinator is obtaining a corrected assignment confirmation” tells another team member what is happening without exposing private documents.
Resolve contradictory facts before chasing speed
A worker may see a rate or date that differs from the recruiter’s conversation. Treat that as a real discrepancy, not a minor interface inconvenience. Ask the authorized owner to compare the agreed instruction and the current record. The worker should not be urged to acknowledge information they believe is wrong just to move to the next screen. Use the official support route for the affected process.
A work-location change deserves the same discipline. “Remote” is not a substitute for knowing where the work will actually take place when the responsible team needs that information. Do not guess a jurisdiction from the client’s headquarters. Record that the location requires review and let the appropriate employment, payroll or compliance owner determine what changes are needed.
Fictional scenario: the accepted offer with no assignment
One candidate, two assumptions
A fictional recruiter tells operations that an offer is accepted. Operations confirms that the candidate has an account. The client then adds the worker to Monday’s roster. A readiness check finds that the specific placement was never created. The candidate was not ignoring onboarding; there was no assignment-driven checklist to complete.
The coordinator verifies the client and assignment through the authorized process, obtains confirmation of the outstanding requirements and updates the client’s start expectation. No one creates a duplicate candidate account as a workaround. The lesson is not that the software is unreliable. It is that “person exists” and “placement exists” answer different questions.
Afterward, the team changes its handoff language. Recruiters say “offer accepted; assignment creation requested,” not “ready.” Operations says “assignment created; review pending,” not “done.” Short, precise states are more useful than a long narrative that leaves the reader to infer whether work may start.
Keep the worker’s view understandable
Explain which organization will send the next legitimate instruction and what kind of action it concerns. Do not ask the worker to forward account-setup links or verification codes. If an invitation fails, use the provider’s supported resend or support process. A coordinator can help a person understand the sequence without taking over their credentials or collecting their identity material.
For a blocked step, ask for the category and a non-sensitive description first. “The checklist says an external review is pending” may be sufficient to route the issue. If private evidence is required, the authorized service should specify its secure submission channel. A public editorial inbox, shared task comment or group chat is not an alternative onboarding system.
Close the loop after the start
The first-day confirmation should establish whether the worker actually started, whether the location and duties match the approved assignment, and whether the worker knows how to record time. A no-show, delayed start or changed scope needs an owner. Do not leave the original proposed date unquestioned merely because it is already in several systems.
Use the first week to confirm the time approver and the relevant cutoff. The timesheet approval plan prevents a successful onboarding from becoming an avoidable payroll exception. If a rate or role changes, use a traceable change handoff rather than editing a local note and assuming it will propagate.
A readiness record is finished when the next operational owner has an accurate, accepted handoff, not when every box in a privately invented checklist is ticked. Keep the distinction from the operating model: your coordination record can expose a missing decision, but it cannot make that decision on another party’s behalf.
Sources & scope
Public sources checked October 25, 2026. Product descriptions are attributed to their publisher. The planning methods and fictional examples are original editorial analysis, not official Ascen procedures or legal, tax, safety or financial advice. Your contract, configuration, work location and current official instructions govern actual operations.