Open the queue before the offer is accepted
A preboarding queue should exist as soon as the start date is real, not after the new hire arrives. The queue is the place where the offer letter, identity documents, tax forms, policy acknowledgements, equipment request, and access request become visible as separate items. Each item needs an owner, a due date, and a definition of done. The hiring manager owns the role context and the first-day plan.
The people operations coordinator owns the document request and the follow-up. The payroll or finance contact owns the tax and payment fields. The IT or access owner owns the account and equipment path. If one person owns everything, the queue will hide the dependencies that actually determine whether the start date works.
Name the owner as a role plus a person. A queue that says HR or IT does not tell the new hire whom to contact when a document link expires. A named owner also makes backup coverage possible, because the team can see who else has the authority to act. Record the backup for each critical item before the first follow-up.
Separate employee tasks from employer tasks
A preboarding queue contains work the new hire must do and work the employer must do. Mixing them makes the status misleading. The employee may need to upload an identity document, complete a tax form, choose a benefits option, or acknowledge a policy. The employer may need to review the document, confirm a payroll field, order equipment, or create an account.
Use two status fields, one for the employee side and one for the employer side. A document can be received from the employee but still waiting for employer review. A tax form can be complete from the employee but still waiting for payroll validation. The combined status should reflect the next action rather than the most recent activity. When the employee says they submitted something, do not mark it complete until the employer side confirms receipt in the approved system. A confirmation email is useful evidence, but it is not the same as a record that appears in the payroll or HR platform. The queue should link to the system record and note the date it was checked.
Use a document list that matches the role and location
The required documents depend on the employment relationship, the location, and the role. A remote employee in one state may have different tax and notice requirements from an employee in another state. A role that handles regulated data may need additional acknowledgements or background steps. The queue should be built from an approved checklist, not from a generic packet copied from another hire.
Keep the checklist versioned and record which version was used for each new hire. If the checklist changes during the preboarding period, note the change and decide whether the hire must complete the new item. A version field prevents a later reviewer from assuming that every hire saw the same requirements. Do not ask for documents that the team does not need. Collecting extra identity or personal information increases risk and creates retention obligations. If a document is required only after the start date, keep it out of the preboarding queue and name the later trigger. The queue should be complete for its purpose, not exhaustive for every possible future need.
Make the follow-up cadence predictable
The new hire should know when to expect a message and what to do if a link fails. A simple cadence might include a welcome note with the checklist, a reminder two business days before the due date, and a final check one business day before the start date. The cadence should be written down so it does not depend on whether the coordinator remembers. Each follow-up should reference the specific open item and the approved channel.
Avoid a vague reminder that says please complete your paperwork. A message that names the missing form, the deadline, and the person to contact is easier to act on and easier to audit. Record every follow-up and the response. If the new hire does not respond, escalate to the hiring manager rather than sending more messages through the same channel. The escalation should preserve the original request and note what was tried. A pattern of failed contact may be a candidate-experience problem, not a document problem.
Handle exceptions without stopping the whole queue
Exceptions are normal in preboarding. A document may be unreadable, a name may not match, a start date may move, or a system may be unavailable. The queue should have a small set of reason codes and a named owner for each. Missing document, mismatch, access delay, system outage, and start-date change are enough for most teams.
An exception should not freeze unrelated items. If the tax form is missing, the equipment request can still proceed and the welcome meeting can still be planned. The queue should show which items are blocked and which can continue. This distinction helps the team protect the start date without pretending the file is complete. When an exception affects pay, benefits, or legal eligibility, route it to the accountable HR or payroll owner. The coordinator can prepare the facts and the timeline, but should not decide the employment outcome. Record the decision and the date, and keep the original exception note with the resolution.
Review the queue before day one
A short review one business day before the start date should compare the queue with the approved checklist. Confirm that each required item is either complete, waived with an owner, or scheduled after the start date with a reason. Confirm that the manager knows which items are still open and what the new hire should do on the first morning. The review should also check the access and equipment path.
A complete document file does not help if the new hire cannot sign in. Confirm the account request, the equipment shipment, and the first-day contact. If any of those items is waiting on a third party, record the expected date and the backup plan. Close the review with a short handoff note that names the open items, the owner, and the next check. Send the note to the hiring manager and the people operations lead. The note becomes the first entry in the new hire's onboarding record and the starting point for the first-week review.
Learn from the first month
After the new hire has started, compare the preboarding queue with what actually happened. Which items were missing, which links failed, which approvals took longest, and which exceptions repeated across hires? This review is more useful than a satisfaction survey because it uses the record the team already created. Choose one change for the next cohort.
It might be a clearer document list, a different reminder schedule, a new owner for a bottleneck, or a revised checklist for a location. Name the owner and the date of the next review. A small change that is tested is more valuable than a long list of improvements that nobody owns. Keep the review notes with the queue template. A later coordinator should be able to see why the process looks the way it does. The goal is not a perfect preboarding file; it is a queue that makes the next missing item visible before it becomes a first-day problem.
Continue building the workflow
Related support: onboarding operations support, contact us. The USCIS Form I-9 Employment eligibility verification guidance.
Related reading

Day-one access verification before the welcome meeting
A first-morning access check that verifies the named account, the required systems, the recovery path, and the owner before the welcome meeting begins.

Benefits enrollment handoff without silent assumptions
A benefits enrollment handoff that keeps eligibility, elections, dependent records, and carrier confirmation visible to the right owners.

A first-week check-in agenda that produces evidence
A repeatable first-week check-in agenda that reviews observed work, unresolved questions, access barriers, and the next practice step.
