Start by agreeing what you are expected to learn, contribute, and decide—not by filling your calendar with activity. A useful onboarding plan connects those expectations to the people, access, training, and feedback you need.
By the end of this guide, you can produce a short plan for your first contribution and a clear way to handle anything that blocks it. The 30-, 60-, and 90-day checkpoints below are suggested planning intervals. Adjust them to your role, working pattern, and employer’s actual requirements; onboarding can continue beyond them.
Establish the conditions for doing the job
Before setting ambitious delivery targets, check four things with your manager:
- Purpose: What problem was this role hired to address?
- Expectations: What would useful progress look like during the first stage?
- Authority: Which decisions can you make, and which need approval?
- Support: What access, equipment, training, and people will you need?
Ask for examples. “Communicate well” is difficult to act on. “Flag a delivery risk to the project owner before changing the deadline” describes a behavior you can follow.
Acas recommends tailoring induction to the worker and their location, spreading out activities, providing relevant training, and reviewing progress. Its guidance is written in the context of Great Britain; the practical planning principles are useful here, while legal requirements must be checked for the relevant jurisdiction. Acas induction guidance.
If your organization already has an induction programme, use it as the starting point. Add role-specific questions rather than creating a competing checklist.
Build your plan around three overlapping activities
Learn how the work actually moves
Find out where requests originate, how priorities are chosen, who owns decisions, and what happens when something goes wrong. Compare written procedures with examples of recent work.
Useful questions include:
- What is a normal request, and what makes one exceptional?
- Where does work usually wait?
- Which information must be checked before we act?
- Who should know about a delay or disagreement?
Record uncertainties as questions. An unfamiliar process is not automatically a broken process.
Build working relationships through real tasks
Meet the people whose work connects to yours. Ask what they need from your role, what you should bring to a request, and how they prefer to receive updates.
You do not need to meet everyone immediately. Start with the people involved in your first assignment and expand as your responsibilities become clearer. For remote or distributed work, agree how to ask questions asynchronously and which issues need a live conversation.
Deliver a contribution with an agreed boundary
Choose something useful that you can complete with the available authority and support. This might be a reviewed analysis, a documented handoff, a tested component, or a resolved set of questions.
Agree who will judge the work and what evidence they need. “Finish a dashboard” is incomplete if nobody has agreed what decision it should support.
Copy this onboarding worksheet
Fill this in with your manager. The phases are prompts, not deadlines you must meet regardless of circumstances.
| Planning phase | Agreed outcome | Evidence of progress | Access, training, or people needed | Check-in and adjustment |
|---|---|---|---|---|
| Initial setup | Clarify responsibilities and working arrangements | Confirmed priorities, questions, and boundaries | Manager, equipment, relevant policies | Record anything preventing a safe start |
| Around the first month |
Keep a separate, short list of blockers: what is missing, who can resolve it, what it affects, and when you will discuss it again.
Worked example: a new project coordinator
This is a fictional teaching example. Its dates and outcomes illustrate a planning process, not an onboarding benchmark.
Asha joins a service team as a project coordinator. Her manager initially asks her to “make handoffs smoother.” Asha asks what this means in practice. They agree that her first contribution will be a small handoff record showing the receiving owner, the next action, and any unresolved decision.
During her first week, Asha talks with the manager and the two teams involved. She learns that some handoffs already have adequate records, while others are missing an owner. She does not propose replacing the whole process.
Her system access is delayed until day 12. She records which assignments are affected and asks her manager to reprioritize. While waiting, she studies approved process documents and builds a sample using invented information. She does not borrow a colleague’s account.
Once access is available and the required training is complete, Asha checks her understanding against authorized examples. Her manager approves a limited trial of the handoff record.
The first version asks for too much information. A colleague explains that several fields repeat material already stored elsewhere. Asha removes those fields and keeps the information needed to identify ownership and next actions.
At the next review, she shows the revised record, feedback from the trial, and remaining uncertainties. The team accepts it for the agreed use. They have not measured a time saving, so she reports that the record was accepted—not that she improved productivity by a particular percentage.
Her next plan is to observe whether the record remains useful before extending it to another workflow.
When progress is blocked
Your manager and another stakeholder want different things. Describe the competing requests and their consequences. Ask the responsible manager to confirm the priority; do not silently promise both.
Access or training is missing. Identify the affected work and agree an alternative assignment or revised date. Do not bypass controls to keep the original schedule.
The first assignment is too large. Propose a smaller useful output, such as a reviewed diagnosis before a full solution. Preserve the original problem, but renegotiate the commitment.
You receive little feedback. Send a concrete artifact and specific questions: “Is the owner correct?” or “What must change before this is usable?” If the designated reviewer is unavailable, ask who can provide an interim review.
The actual role differs substantially from what you accepted. Write down the differences in responsibilities, support, or working arrangements and discuss them promptly with the appropriate manager or HR contact. An onboarding plan cannot resolve a fundamental disagreement by itself.
Your next step
Arrange a conversation to confirm your first useful contribution, its success criteria, and its dependencies. Leave with a next check-in and a list of unresolved questions.
Once the initial role is clearer, use Career Growth with Your Manager to discuss development beyond onboarding. If your next role involves choosing between people management and deeper specialist responsibility, continue with Leader Track vs Expert Track.