A 30-60-90 day plan gives you a practical way to turn a new job into clear, manageable steps. This reusable template helps you understand the role, build useful relationships, deliver early results, identify skills gaps, and agree measurable priorities with your manager.
Overview
A 30-60-90 day plan is a short career development plan for your first three months in a new role. It is not a promise to solve everything immediately. Instead, it creates a shared working outline for learning the organisation, contributing to the team, and deciding what success should look like.
The plan should remain flexible. Your priorities may change after onboarding, a project may be delayed, or your manager may identify a more urgent need. Treat the document as a discussion tool rather than a fixed contract. A useful plan usually includes five areas:
- Onboarding: the systems, processes, policies, and context you need to understand.
- Relationships: the colleagues, customers, stakeholders, and subject-matter experts you need to meet.
- Early deliverables: realistic tasks that demonstrate progress without creating unnecessary risk.
- Skills and gaps: the knowledge, tools, or behaviours you need to strengthen.
- Measures of progress: evidence that shows whether you are learning and contributing.
Before writing your plan, ask your manager what they expect from the first 30, 60, and 90 days. If you are joining an internship, contract, remote role, or entry-level position, ask which outcomes are essential and which are opportunities to explore.
A reusable 30-60-90 day plan template
| Period | Main focus | Example actions | Evidence of progress |
|---|---|---|---|
| Days 1-30 | Learn and connect | Complete onboarding, review documentation, understand team priorities, meet key colleagues, and observe how work moves from request to delivery. | Questions answered, access completed, notes organised, relationships mapped, and initial priorities confirmed. |
| Days 31-60 | Contribute and improve | Take ownership of defined tasks, contribute to meetings, identify a small process improvement, and request feedback on your work. | Agreed tasks completed, feedback recorded, risks raised early, and one improvement tested or proposed. |
| Days 61-90 | Own and plan ahead | Lead a suitable piece of work, document a repeatable process, close a skills gap, and agree the next quarter's priorities. | Outcomes reviewed, work handed over clearly, development goals agreed, and future measures defined. |
Checklist by scenario
For a technology or IT role
- List the main systems, repositories, ticketing tools, communication channels, and security procedures you need to use.
- Learn how incidents, changes, deployments, access requests, or support escalations are handled.
- Understand service expectations, approval points, documentation standards, and handover practices.
- Choose an early deliverable that is useful but appropriately scoped, such as improving documentation, resolving a defined backlog item, or automating a repeatable task.
- Record assumptions and dependencies instead of quietly working around them.
For a remote or hybrid role
- Confirm which meetings require attendance, which decisions belong in written channels, and how quickly urgent messages should be acknowledged.
- Set up a reliable workspace and make your availability visible without creating an expectation of constant connection.
- Schedule short introductory conversations with people you will work with regularly.
- Ask how your work will be reviewed when you are not physically present.
- Share concise written updates covering progress, next steps, blockers, and decisions needed.
For more ideas on finding and evaluating flexible roles, see Remote Jobs for Beginners: A Practical Search Strategy.
For an internship or entry-level role
- Ask which skills you are expected to practise, not only which tasks you are expected to complete.
- Identify a person who can answer day-to-day questions and a separate person who can discuss longer-term development.
- Keep a record of projects, tools used, feedback received, and outcomes. These notes can later support your CV and interviews.
- Request a small, well-defined task before volunteering for a large or unclear project.
- Clarify how learning time, supervision, and performance reviews fit into the role.
If you are comparing internship opportunities, the internship offer comparison guide can help you assess learning, mentorship, pay, and potential next steps.
For a freelance or contract assignment
- Confirm the brief, deliverables, acceptance criteria, deadlines, revision limits, and communication process.
- Identify who can approve work and who may provide feedback.
- Separate discovery work from production work so changes in scope are visible.
- Send written progress updates and flag dependencies before they affect the deadline.
- Review whether your agreed rate and project price reflect the actual work involved. The freelance rate guide provides a reusable framework for pricing and quoting.
Questions to ask your manager
- What would make my first 30 days successful?
- Which outcomes matter most by the end of 90 days?
- What should I learn first, and where is the trusted documentation?
- Which decisions can I make independently?
- Who are the key stakeholders and customers for this work?
- How do you prefer updates, questions, and feedback to be shared?
- What risks or recurring problems should I understand early?
- When should we review this plan and adjust priorities?
What to double-check
Before you share the plan, check that every objective is specific enough to discuss. “Understand the team” is a useful intention but not a measurable outcome. “Meet the four colleagues responsible for the workflow, review the process documentation, and summarise open questions by the end of week two” is easier to track.
Check the balance between learning and delivery. A new employee needs context, but a plan made entirely of training courses may not show how learning will be applied. Pair each important skill with a practical use, such as completing a supervised task, documenting a process, or presenting a recommendation.
Check dependencies and authority. If an outcome depends on another team, access approval, customer feedback, or a release schedule, record that dependency. Do not describe a blocked result as though it is fully under your control.
Finally, agree how progress will be reviewed. A useful measure could be a completed deliverable, a documented process, a resolved issue, stakeholder feedback, or a demonstrated skill. The right measure depends on the role; not every outcome should be reduced to a number.
Weekly review workflow
- Record: note what you completed, learned, or clarified.
- Compare: review the week's work against the plan's priorities.
- Escalate: raise blockers, unclear ownership, or changing deadlines early.
- Reflect: write one thing to continue and one thing to improve.
- Reset: choose the next week's three most important actions.
Keep the review short enough to repeat. A simple document or task board is usually sufficient. The goal is a reliable conversation with your manager, not a complicated reporting system.
Common mistakes
- Making the plan too ambitious: ten major objectives can hide the priorities that matter most. Choose a small number of outcomes and list other ideas separately.
- Copying a generic template: adapt the plan to the role, team, manager, work arrangement, and current business priorities.
- Confusing activity with impact: attending meetings and completing training are activities. Explain what they help you understand or deliver.
- Waiting for a formal review: do not save questions or risks for day 30, 60, or 90. Share them when they become relevant.
- Ignoring relationship building: technical output is only part of most roles. Understanding who owns decisions and how work is handed over can prevent avoidable delays.
- Treating the plan as permanent: priorities can change. Update the document when the role or project changes rather than following an outdated list.
When to revisit
Review your 30-60-90 day plan at least once a week during the first three months, ideally before a regular manager conversation. Revisit it immediately when your responsibilities change, a project is cancelled or reprioritised, you move from office-based to hybrid or remote work, or you begin supporting a new stakeholder group.
Use the end of each phase to close one section and open the next. At day 30, summarise what you learned and confirm the next priorities. At day 60, review the quality and usefulness of your early contributions. At day 90, capture evidence of progress and turn remaining gaps into a forward-looking development plan.
The same checklist can be reused when starting a new job, internship, freelance contract, internal transfer, promotion, or team assignment. Before acting, write down three priorities, three questions, and one measurable outcome for the next review period. Then share that outline with the person who can confirm whether you are working on the right things.
