First Day at a New Job: A Checklist for Knowing What to Do Next
Prepare for your first day at a new job with a practical checklist, useful questions, remote-work fallback steps, and a simple end-of-day recap.
On your first day at a new job, focus on getting access, understanding who does what, and agreeing on a manageable first task. Confirm arrival details beforehand, ask how to recognize correct work, and finish with a short recap. You do not need to prove your entire value before you know where the shared files live.
Table of contents
- What should you confirm before your first day?
- What belongs on your first-day checklist?
- Which questions are worth asking?
- What if the day is unplanned or something is missing?
- How should you end the first day?
- Frequently asked questions
What should you confirm before your first day?
Confirm the time, location or meeting link, contact person, and required onboarding steps. Follow the employer's instructions rather than assuming every workplace handles equipment, documents, schedules, or dress in the same way.
The University of Oregon's onboarding checklist starts with confirming arrival details with a supervisor, including where and when to report. That is a useful general principle even though the university's specific processes apply to its own employees.
Check the information you already received, then ask only about what is missing. This original fictional message keeps the request compact:
Hi Morgan, I am looking forward to joining on Monday. Could you confirm where I should report at 9 a.m. and who I should contact when I arrive? I have completed the onboarding steps sent by HR. Please let me know if there is anything else I should prepare or bring for the first day. Thanks, Alex.
For remote work, confirm the time zone and how you will contact someone if the work account is not active. Test your own connection and the approved meeting setup, without trying to access systems before you are authorized.
If the offer itself is still being finalized, complete the acceptance checks first. This checklist assumes the role and start date are agreed.
What belongs on your first-day checklist?
Cover people, access, expectations, and one first task. You are building enough context to begin safely and usefully, not trying to absorb every policy and project in a single sitting.
UC San Diego's supervisor checklist includes introductions, the work area, computer access, and role responsibilities. Those categories make a practical employee-facing checklist:
| Area | What to establish | What to record |
|---|---|---|
| Arrival | Who is expecting you and where to begin | Main contact and backup route |
| People | Manager, close colleagues, relevant support contacts | Names, responsibilities, and how to reach them |
| Access | Approved accounts, equipment, and current documents | Missing access and the request owner |
| Expectations | Immediate priorities and what good work looks like | First task, result, and check-in |
| Working norms | Communication, meetings, breaks, and availability | Where to ask urgent and routine questions |
| Administration | Required employer-specific onboarding | Remaining steps and their due dates |
Do not mark an account “working” just because you can sign in. Check whether you can open the document or system needed for your first task. If you cannot, record the exact access problem without sharing passwords or sensitive screenshots in an unapproved channel.
The University of Florida's first-day guidance includes connecting a new employee with teammates, HR, and a buddy. Ask who can answer practical questions when your manager is unavailable; one named contact is more useful than being told to “ask anyone.”
Keep a short list of names, links, questions, and next actions.
Which questions are worth asking?
Ask questions that reduce uncertainty about the work, its quality, and the route for help. You do not need to perform curiosity by asking everything on a long list.
Start with a few that fit the moment:
- What would be a useful first task for me? This creates a concrete starting point.
- Can you show me an example of a good finished result? This makes quality more visible.
- Which source should I treat as current? This helps when documents disagree.
- What can I decide myself, and what needs approval? This clarifies boundaries.
- Who should I contact if I get blocked? This prevents silent waiting.
- When would you like a progress check? This establishes a reasonable feedback point.
UC San Diego's checklist treats responsibilities and the work environment as onboarding topics. Use your questions to make those topics concrete for your role.
An original fictional conversation might sound like this:
I can start by checking the current guide against the product notes. Before I change anything, could you show me which version is authoritative and who should review the corrections? Would a short list of discrepancies be a useful first result?
That response shows initiative without assuming authority you have not been given. If the task is unfamiliar, repeat back your understanding and invite correction before investing hours in the wrong deliverable.
For a later, deeper discussion about expectations, use the one-on-one meeting template. The first day only needs enough clarity to make the next step sensible.
What if the day is unplanned or something is missing?
Tell the appropriate person what is missing and ask for a bounded activity you can do while it is resolved. An empty calendar or inactive account is an onboarding gap, not proof that you should already know how to navigate the organization alone.
Use this original fictional message:
My work account is active, but I cannot open the shared guide yet. I have sent the access request through the help channel. While that is being resolved, would it be useful for me to read the public product overview and collect questions for our check-in? Please let me know if there is a higher-priority starting task.
Oregon's checklist separates preparation, first-day steps, and later onboarding. Treat learning as a sequence. If one step is blocked, identify a suitable next activity instead of pretending the entire orientation should already be complete.
For remote onboarding, keep a backup contact route that does not depend on the unavailable account. Confirm how to join the first meeting and where questions should go. Do not create unofficial accounts or move work files to personal storage simply to appear productive.
If you notice a process that seems inefficient, write down a question before proposing a fix. There may be a constraint you have not seen. “What led the team to use this approach?” opens a better conversation than “At my old job we did this properly.”
How should you end the first day?
Send or discuss a short recap of what you completed, what remains blocked, and what you intend to do next. Confirm the priorities with your manager instead of treating every new request as equally urgent.
Florida's onboarding guidance frames the first day as part of an organized onboarding plan. Your recap helps connect today's introductions and information to the next useful step.
For example:
Thanks for helping me get started today. I completed the account setup and reviewed the current guide. Shared-folder access is still pending with IT. Tomorrow I plan to compare the product notes, collect discrepancies, and bring the list to our afternoon check-in. Please correct that order if something else should come first.
Those three actions are a planning example, not a demand that every first day produce three finished tasks. Adapt to the role and the agreed schedule.
Use the daily planning template to separate actions from information you simply need to remember. Do Only 3 Things a Day gives you a repeatable way to protect the most important work as responsibilities accumulate. You can begin that habit before your calendar becomes crowded.
Frequently asked questions
What should I bring on the first day?
Bring what your employer requested, plus a practical way to take notes. Confirm document and equipment requirements through the official onboarding channel; do not rely on a generic list for organization-specific requirements.
What if no one has planned my day?
Contact your manager or named onboarding contact, explain that you are ready, and ask for the first useful activity. If they are unavailable, use an agreed backup route rather than guessing at work you are not authorized to do.
How do I handle a remote first day?
Confirm time zones, meeting links, account access, and a backup contact method. Ask where current documents live and how the team raises blockers. Keep sensitive information within approved systems.
Should I try to impress everyone immediately?
Aim to be reliable, attentive, and clear about what you understand. Ask useful questions and complete the agreed first task carefully. You will have time to demonstrate deeper judgment once you know the work and its constraints.