Onboarding
A new-starter first-day IT packet that prevents repeat tickets
What to put in a first-day IT packet so a new hire can set up, sign in, and ask for help without generating a week of avoidable support tickets.
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
A new employee's first day is a test of the company's IT process, whether anyone calls it that or not. If the laptop is not ready, the password does not work, or nobody explains how to ask for help, the service desk spends the week fixing avoidable problems. A first-day packet answers the predictable questions in one place. It also gives the IT assistant a clear checklist and a way to spot gaps before the next hire arrives.
What belongs in the packet
The packet should cover the device, the accounts, the core tools, and the way to get help. Include the laptop and accessory list, the sign-in steps, the expected first-day access, and the name of the person who can approve exceptions. Add a short map of the systems the role will use and the ones it will not. The packet is not a policy manual, and it should not repeat the entire employee handbook.
Write it for someone who has never seen the company's systems. Use the names that appear on the screen rather than internal project codes. Include a single page that the new starter can keep open during the first morning. Everything else can live in linked articles for later reference, so the first-day document stays short enough that a nervous new hire will actually read it.
Write the first-hour sequence
Order the steps the way the new starter will experience them: collect the device, sign in, set up multi-factor authentication, join the network, open email, and reach the first meeting. Put the expected result beside each step so the person knows whether it worked. Add a fallback for the two steps most likely to fail, such as a password reset or a missing app. A sequence is easier to follow than a list of systems.
Give the manager a separate short checklist for the actions they own, such as confirming the start date, the role, and the equipment address. The IT team cannot provision an account without that information, and the new starter cannot fix a missing approval. Separating the two lists makes the handoff visible. It also prevents the service desk from chasing details that belong to the hiring manager.
Explain access without exposing secrets
Tell the new starter how to obtain credentials through the approved process rather than sending a password in the packet. Explain what multi-factor authentication is for and what to do if the phone is lost. Name the person or queue to contact for a reset. A packet that includes a temporary password teaches the wrong habit and creates a record that is hard to protect once the document is forwarded or saved.
Describe the access the role should have on day one and the access that requires a separate approval. New starters often receive too much access because a manager wants to avoid a second request. A short least-privilege note helps the manager ask for the right scope. It also gives the reviewer a reason to remove access that is not needed, which protects both the new hire and the company.
Give one place to ask for help
Choose one support channel for first-week questions and state its hours. A new starter who is told to ask their manager, the IT team, or a colleague will often ask nobody. Link the channel from the packet and from the device setup screen if possible. Monitor it during the first week so questions do not wait behind routine work and the new hire does not conclude that asking is a burden.
Tell the new starter what information to include when something fails: the step, the message, the device, and the time. That small instruction improves the first ticket and reduces the back-and-forth. It also teaches a habit that helps the whole team. The channel should feel like a normal part of onboarding, not an escalation of last resort. That small habit also makes the first-week support load easier to measure, because each request arrives with enough context to route.
Collect feedback in week one
Send a short check-in at the end of the first week with three questions: what worked, what was missing, and what took longer than expected. Ask the manager the same questions from their side. The two views often disagree, and the difference is where the process needs work. Keep the check-in short enough that people actually answer it instead of postponing it until the memory has faded.
Turn the answers into specific changes to the packet, the provisioning checklist, or the access request. Record the change and the date so the next new starter benefits. A packet that is never updated describes the company as it was, not as it is. The review is most useful in the first month, while the experience is still fresh and the person still remembers which instruction was confusing.
Update the packet from real tickets
Tag first-week tickets with a simple onboarding label and review them monthly. Look for repeated questions about the same system, missing access, or a step that the packet explains poorly. Add the answer to the packet and remove the ticket cause if possible. The label turns a stream of small requests into a source of improvements rather than a recurring cost that nobody owns.
Retire instructions for systems the company no longer uses and update screenshots when the interface changes. Assign an owner and a review date to the packet, just as you would for any other operational document. A current packet reduces the load on the service desk and gives every new hire the same starting point. That consistency is the real return on the work, and it shows up in the first week.
Sources and next step
Use the CISA Cross-Sector Cybersecurity Performance Goals and the NIST Cybersecurity Framework 2.0 as primary references for the access, asset, and recovery practices discussed in this guide. Apply your own policies, contracts, and system documentation to the workflow. Compare this guide with the shared login migration plan and the vendor contact directory guide 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 first-day it packet that prevents repeat tickets 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