Onboarding
A new-starter access request pack that cuts first-week delays
A single request pack that collects role details, approvals, recovery steps, and a day-one check before a new starter signs in.
Start with repeatable IT work that has a clear owner, clear access limits, and a review cadence. Keep risky technical decisions with the manager or provider who owns the system.
Delegation playbook
On this pageJump to section
The first week of a new job is full of small waits, and access is usually the longest. The manager sends a list, the IT team asks for approvals, and the new starter spends a day without the tools they need. An access request pack collects the role, the approvals, and the recovery steps before the start date. The pack turns a scattered conversation into one reviewable request.
List the roles the new starter will hold
Write the job title and the two or three systems the person will use in the first month. Name the access level for each system, such as read, edit, approve, or administer. Include shared mailboxes, distribution lists, and the folders the role needs. A request that says only the job title leaves the administrator to guess.
Separate the access needed on day one from access that can wait until the first project. Day-one access should cover email, calendar, chat, the intranet, and the main business system. Later access can follow the first week once the manager confirms the work. A smaller first request is easier to approve and faster to deliver.
Collect approvals before the start date
Name the manager who owns the role and the system owners who approve each application. Send the pack to those approvers at least five working days before the start date. Ask for a reply in the request record rather than a chat message that will be lost. The administrator should be able to see who approved what without asking again.
Use a standard approval form that lists the system, the access level, and the business reason. If an approver is on leave, name a delegate in advance and record the delegation. Do not let the new starter request their own access on the first morning. The request should arrive complete, not as a series of follow-up messages.
Separate standard access from privileged access
Mark administrator accounts, finance approval roles, and any system that holds sensitive data as privileged. Require a second approval and a named business owner for those requests. Keep the privileged access in its own section so it is not approved by habit with the standard set. Most new starters need standard access first and privileged access only after training.
Record the training or background check that must be complete before privileged access is granted. Set the access to expire or be reviewed after a fixed period. Give the new starter a named person to contact if the access does not work. A privileged request without an expiry becomes permanent access by default.
Prepare the recovery and MFA steps
Decide how the new starter will enroll in multi-factor authentication before their first sign-in. Send the enrollment instructions to a personal address only if policy allows it, and record that choice. Test the phone or hardware token with the identity team before the start date. A new starter locked out of MFA loses the first morning to the service desk.
Set recovery questions, a backup method, and a support route in the pack. Tell the new starter what to do if they lose the device or change their phone. Make sure the helpdesk can verify identity without asking for a password. Recovery that depends on a colleague's memory is not a process.
Schedule a day-one access check
Book fifteen minutes with the new starter on the first morning and a second check at the end of the first week. Ask them to sign in to each system while the manager or assistant watches. Record which systems worked and which produced an error. A check that happens after the person has already given up is not a check.
Give the new starter one place to report a missing permission, with the system name and the exact message. Route that report to the administrator who can fix it, not to a general queue. Keep the original request open until the check is complete. Close it only when the person can do the work the role requires.
Close the request and record the outcome
When the access works, mark each line in the pack as delivered and record the date. Note any access that was denied and the reason, so the next request starts from a known decision. Remove temporary access that was granted only for onboarding. The record should show what the person can reach, not only what was requested.
Review the pack after the first month and remove systems the role never used. Add any tool the manager had to request separately, because that gap will repeat for the next hire. Share the updated pack with the hiring managers and the IT team. A pack that improves with each starter becomes the fastest part of onboarding.
Give the hiring manager a short checklist
Send the hiring manager a one-page checklist two weeks before the start date. It should list the role details, the approvers, the day-one systems, and the name of the person who will run the access check. Ask the manager to return it even when the role is similar to the last hire. A repeated role still needs a current start date and a current owner.
Add a line for equipment, because a laptop that arrives without a login creates the same delay as a missing account. Note the desk, the phone, and any building access the role needs. Give the manager a date for each item and a person to chase. The checklist is complete when every line has an owner and a date.
Sources and next step
Use the CISA Cross-Sector Cybersecurity Performance Goals and the NIST Cybersecurity Framework 2.0 as primary references for the licence, onboarding, backup, vendor, and guest access practices discussed in these guides. The NIST SP 800-53 Rev. 5 supports the account and access records, and the NIST contingency planning guide supports the restore-test log. Apply your own policies, contracts, and system documentation to the workflow. Compare this guide with the new-starter access request pack and the weekly backup restore test log before changing a live process.
Keep decisions, approvals, and evidence in systems the business already controls. If the coordination is recurring and your technical owner can define the boundaries, review the IT virtual assistant service areas and contact ITVirtualAssistant to discuss a limited pilot.
Operating brief
What this guide should help you decide
Routine intake, status updates, records, screenshots, and documentation upkeep.
Approvals, risky system changes, security decisions, and final technical judgment.
How to use this guide
Use this page to decide what an IT virtual assistant should handle first. If the task is recurring, documented, and easy to review, it is usually a better first delegation candidate than work that requires live technical judgment.
Treat the article as an operating brief, not just a topic overview. The goal is to turn loose IT work into a named workflow with inputs, outputs, permissions, review cadence, and a handoff rule that protects the business while reducing manager load.
Workflow
Recommended operating workflow
Define the request
Write what a new-starter access request pack that cuts first-week delays means in your company, where requests enter, and what finished work looks like.
Limit the access
Give the assistant only the tool permissions needed for intake, records, status updates, or documentation.
Run a pilot
Use a two-week sample period so the manager can review accuracy before expanding the workflow.
Review patterns
Summarize repeat issues, blocked requests, and escalation volume so the technical owner can improve the process.
Decision rules
| Question | VA fit signal | Escalate when |
|---|---|---|
| Is the work repeatable? | The same request appears weekly and can be described in steps. | The request changes business policy or system design. |
| Can quality be reviewed? | The manager can inspect the output without redoing the work. | Only a senior technical person can judge correctness. |
| Is access contained? | The assistant can work with read-only or role-limited access. | Admin rights, customer data, or security settings are involved. |
Delegation checklist
- Write the intake source, expected output, and manager review cadence.
- Confirm the assistant has only the permissions needed for the workflow.
- List the events that require escalation before work continues.
- Track examples for two weeks before changing the workflow.
- Save examples of good and bad outputs so the assistant has concrete references.
- Review the workflow monthly and remove permissions that are no longer needed.
Example first-week agenda
Day one should cover the workflow owner, tools, allowed actions, forbidden actions, and escalation language. By the end of week one, the assistant should have produced a small sample of completed work, a list of unclear requests, and a manager-reviewed improvement note.
What to review before delegating
Confirm the owner, access level, review cadence, and escalation path before assigning any recurring IT workflow to a remote assistant.
What should an IT virtual assistant handle first?
Start with repeatable, reviewable work such as ticket summaries, account records, documentation updates, and checklist follow up.
Get free IT support review