Published: September 24, 2026

The days between acceptance and a virtual assistant's start date are easy to neglect. Recruiting considers the candidate hired, the manager is preparing work, and onboarding may be waiting for paperwork or access approvals. The new hire receives silence and cannot tell whether the start is on track.

A prestart contact plan solves a communication problem. It gives the new assistant a reliable contact, a small number of useful updates, and safe instructions for required actions. It should not create unpaid work, distribute credentials early, or turn every internal delay into a vague reassurance.

Set the contact rhythm from the actual wait

A person starting in three days needs a different plan from someone starting in a month. Map the dates that matter: acceptance, required paperwork, equipment or workspace decisions, access approval, manager introduction, and first-day meeting. Place updates where they answer a likely question.

For a ten-day wait, two messages may be enough. The first confirms start details and secure next actions. The second provides the first meeting, support contact, and completed setup instructions. Add a message only when there is new information or a delay that affects the candidate.

Do not send daily notes merely to appear attentive. Repetitive messages make it harder to spot the one action that matters.

Give one person responsibility for replies

Name a prestart contact and a backup. The contact may route employment, payroll, security, or technical questions to specialists, but they remain responsible for acknowledging the message and following up.

The candidate should not have to guess among the recruiter, hiring manager, IT desk, and payroll inbox. State which channel to use, normal response expectations, and what to do if an urgent start-day issue occurs.

Create a small routing table internally. Questions about accepted terms go to the authorized employment owner. System access goes to the system owner. Requests for accommodation follow the approved confidential route. The coordinator should never improvise an answer because the proper owner is slow.

Write updates around candidate actions

Every message should make the next step obvious. Include the confirmed start date and time zone, what changed since the last message, any action the candidate must take, the approved channel, the deadline, and the next planned update.

Distinguish complete from pending. "Your account request is approved" is different from "your account is ready to use." If setup is pending, say who owns it and when the candidate will hear more. Avoid "everything is all set" unless the readiness record supports that claim.

Do not send confidential forms as ordinary attachments if the organization has a secure intake system. The Federal Trade Commission advises businesses to know what personal information they hold, keep only what they need, protect it, and dispose of it securely. Prestart messages often touch addresses, identity details, payment information, and account setup, so the channel matters.

Keep work out of the waiting period

Welcome material can help a new assistant understand the company and first week. It becomes a problem when "optional reading" is extensive, deadlines appear before the start date, or the manager assigns a real customer task.

Label any preview clearly and keep it genuinely optional unless the approved employment arrangement says otherwise. Do not ask the person to join routine meetings, monitor an inbox, create production accounts, or complete substantive training off the clock. Questions about pay and working time belong with qualified advisers for the relevant arrangement.

The U.S. Department of Labor provides federal information about hours worked under the Fair Labor Standards Act. Other jurisdictions and worker arrangements differ. A coordinator should follow the organization's approved process rather than making a classification or compensation judgment.

Protect credentials and access

Never email shared passwords or ask the candidate to use another person's account. Account invitations should come from the approved system, expire appropriately, and support identity verification through the responsible team.

If access is provided before day one, state whether the candidate is expected to act and what support is available. Often the safer choice is to complete approvals in advance and activate access during a supervised first-day session.

NIST SP 800-63B covers authenticator management concepts that security owners can use when designing account setup. It does not prescribe a staffing email sequence. Follow the company's security design and escalate failed identity or recovery steps.

Prepare for changes

Start dates, managers, shipping plans, or first meetings sometimes change. Decide who may approve each change and who communicates it. A coordinator can explain that a decision is pending, but only an authorized owner should change an accepted term.

When a material change occurs, send one corrected summary rather than a chain of partial updates. Identify what changed, what remains the same, what the candidate should do, and where questions go. Correct the source record so later reminders do not repeat old information.

If the candidate stops responding, check delivery before escalating. A bounced message, spam filter, wrong address, or inaccessible portal is not evidence of disengagement. Use the approved alternative contact method and keep notes factual.

Run a final prestart check

Before the last message, verify the candidate's start confirmation, time zone, manager, first meeting, secure paperwork status, minimum access plan, support contact, and any open blocker. Review the message as the candidate will see it. Test links without an employee session and check that dates match the calendar invitation.

The final note should not dump the whole onboarding schedule into an email. Give the person what they need to arrive prepared and tell them when the rest will be introduced.

After day one, close the prestart record or link open items into onboarding ownership. Remove temporary contact lists and duplicate documents according to retention rules.

OnboardingEmployees helps teams coordinate virtual assistant placement handoffs and first-week readiness. Review onboarding operations support or request a staffing support plan.

Common prestart questions

How often should a company contact a new virtual assistant before day one?

Contact them when there is useful information, a required action, or a meaningful change. Set the next update date so silence has an explanation.

Should the hiring manager send a welcome message?

Yes, when it is coordinated with the official plan and does not introduce new terms or assignments. A short note can confirm who the manager is and when they will meet.

What if paperwork is incomplete?

State which approved step remains open, provide the secure route, and name the support owner. Do not ask the candidate to resend sensitive data through an unsafe channel.

Can training begin before the start date?

Follow the approved employment and compensation process for the arrangement. Do not label required work as optional to move it outside that process.

Continue building the workflow

Connect this process to the virtual assistant role brief, then use the virtual assistant onboarding checklist for the next handoff. The U.S. Equal Employment Opportunity Commission explains that employment selection procedures should be job related and consistent with business necessity.