30 60 90 Day Plan Template: The PM Guide (2026)

A 30-60-90 day plan is a structured document that outlines what a professional intends to learn, build, and deliver across three consecutive 30-day phases when starting a new role, project, or leadership assignment. Used well, it transforms a period of uncertainty into a disciplined, milestone-driven transition that mirrors how experienced project managers initiate any new engagement. This guide explains what the plan contains, how to create one from first principles, and why a project management lens makes all the difference.

What Is a 30-60-90 Day Plan?

A 30-60-90 day plan is a written roadmap covering the first three months of a new professional engagement. It divides that period into three distinct phases, each with its own objectives, activities, and success measures. The first phase focuses on learning and orientation. The second shifts toward contribution and relationship-building. The third concentrates on delivering measurable outcomes and embedding good practice.

What separates a practitioner-grade plan from a generic checklist is the deliberate application of project management thinking. When you baseline your deliverables, map your stakeholders, and identify early risks before the first week is over, you are not simply writing a to-do list. You are initiating a project. The table below captures the essential structure at a glance.

Who Should Use a 30-60-90 Day Plan?

The 30-60-90 day plan is most commonly associated with job interviews and new-hire onboarding, but its value extends far beyond that narrow context. Anyone entering a new environment where clarity, credibility, and early momentum matter will benefit from this kind of structured thinking. Project managers stepping into a new programme, senior leaders taking on a divisional remit, consultants beginning a client engagement, and team leads inheriting an existing function all face the same fundamental challenge: too much to absorb, too little time, and high expectations from the outset.

The plan is particularly powerful for professionals moving into leadership positions, where the temptation to act before listening is greatest. A well-constructed plan signals to stakeholders that you are thoughtful, organised, and aware that durable results require a period of grounded discovery before decisive action. It is equally useful for experienced project managers who want a repeatable initiation framework they can adapt to each new engagement rather than starting from scratch every time.

What Should Be Included in a 30-60-90 Day Plan?

A thorough plan contains more than a list of tasks. Drawing on IPMA competence frameworks and standard project initiation discipline, a practitioner-grade 30-60-90 day plan should address six core elements across all three phases: context and objectives, stakeholder mapping, key activities and milestones, resource needs, risks and assumptions, and success criteria.

Context and objectives establish why the plan exists and what success looks like at the 90-day mark. Stakeholder mapping identifies who holds influence, who will be affected by your work, and who needs to be engaged early. Key activities and milestones translate broad objectives into concrete, time-bound actions. Resource needs surface any dependencies on people, budget, or tools before they become blockers. Risks and assumptions apply the same discipline a project manager would use at project initiation, acknowledging what could go wrong and what you are taking on trust. Success criteria ensure that progress can be evaluated objectively rather than by impression alone.

Each of these elements should appear in every phase of the plan, adjusted to reflect the shifting nature of the work. In days one to thirty, your success criteria might be relational and informational. By days sixty-one to ninety, they should be quantifiable and deliverable-focused.

How to Format a 30-60-90 Day Plan

Format follows function. The right format for your plan depends on how it will be used, who will read it, and how frequently it needs to be updated. There is no single correct format, and the popularity of tools such as Word, Excel, Google Docs, PowerPoint, and Canva reflects the genuine variety of professional contexts in which the plan appears.

Document and Spreadsheet Formats

A 30-60-90 day plan template in Word or Google Docs suits written narrative, detailed objectives, and stakeholder notes. These formats are easy to update, share, and version-control, making them the default choice for most project managers. A template in Excel works well when you want to track progress numerically, link activities to dates, or manage multiple workstreams in parallel columns. A PDF version is ideal for formal submission or printing, but it is less useful as a living document because editing is cumbersome.

Visual and Presentation Formats

PowerPoint does include basic timeline and table layouts that can be adapted for a 30-60-90 structure, though it does not ship with a dedicated named template. Canva offers visually polished designs that work well in interview or stakeholder presentation settings. The risk with purely visual formats is that they can prioritise appearance over substance. A slide that looks impressive but lacks specific milestones, stakeholder names, and measurable outcomes is decoration, not a plan. For practitioners, a clean table-based document format paired with a one-page visual summary tends to offer the best of both worlds.

How to Create a 30-60-90 Day Plan: Step-by-Step

Building a plan that holds up in practice requires a sequenced approach. The steps below apply the same discipline a project manager would bring to initiating any new engagement, scaled appropriately to a personal transition context.

Steps One to Three: Discovery and Framing

Begin by defining the engagement context. What is the primary purpose of this role or assignment? What does the organisation or client most need from you in the first quarter? Gather any documentation available before day one: job descriptions, project charters, team structures, organisational strategies, or client briefs. Next, identify your key stakeholders. List the people whose support you will need, whose expectations you must manage, and whose knowledge you most urgently need to access. Finally, draft your 90-day objective: a single, clear statement of what a successful first quarter will look like. This anchors every activity that follows.

Steps Four to Six: Phase Planning and Risk Review

With your objective set, work backwards through the three phases and populate each with specific activities, milestones, and success measures. Use SMART goal discipline throughout: every objective should be specific, measurable, achievable, relevant, and time-bound. Once your activities are mapped, conduct a simple risk review. Ask what assumptions you are making and what could prevent you from hitting each milestone. Document these assumptions explicitly rather than leaving them implicit. Finally, identify the resources and support you will need to deliver each phase and flag any that are not yet confirmed. A plan that ignores resource constraints is a wish list, not a professional document.

30-60-90 Day Plan Template (Free Download)

A reliable template removes the blank-page problem and gives you a consistent structure to populate with your own context. The IPM recommended template is built around six sections per phase and is available in formats suited to different working styles.

For each of the three phases, the template includes a phase objective, a stakeholder focus list, a table of key activities with target completion dates, a resource and dependency log, a short risk and assumption register, and a success criteria checklist. The phase objective is written in one sentence and connects explicitly to the overarching 90-day goal. The stakeholder focus list names specific individuals or groups and notes the nature of the relationship and the intended engagement approach. The activity table uses no more than eight rows per phase to maintain focus and avoid the common mistake of over-planning the early days while under-planning the critical third phase.

Template formats available include a Word and Google Docs version for narrative-rich planning, an Excel version for tracking and progress monitoring, and a one-page PDF summary for presentation or formal submission. Each version uses the same underlying structure so that switching between them does not require rebuilding your content. When choosing your format, consider not just how you will create the plan but how you will use it week by week. A plan that sits in a drawer is not a plan at all.

30-60-90 Day Plan Example for a Project Manager

Abstract frameworks become real through worked examples. The following example is drawn from a project manager joining a mid-sized infrastructure consultancy as programme lead for a portfolio of public-sector contracts. It illustrates how the plan operates as a genuine initiation tool rather than a superficial exercise.

Days 1 to 30: Establishing Context

The phase objective for this period reads: understand the current state of each active contract, identify the key internal and client stakeholders, and establish a baseline view of programme health against existing schedules and budgets. Activities include structured interviews with each project manager in the team, a review of all live project documentation, attendance at scheduled client meetings in an observer capacity, and a preliminary risk assessment drawing on the programme’s existing risk registers. Success criteria at day 30 include a completed stakeholder map, a written programme health summary shared with the sponsor, and at least one identified quick-win opportunity per active project.

Days 31 to 60: Building Credibility Through Contribution

The phase objective shifts to: introduce consistent reporting standards across the portfolio, establish regular governance touchpoints with client leads, and begin delivering on the quick-win opportunities identified in phase one. Activities include designing a one-page programme dashboard, facilitating the first cross-project lessons-learned session, and presenting initial findings to the senior leadership team. By day 60, the success criteria include a governance calendar agreed with all client leads, the first programme dashboard published and accepted by the sponsor, and at least two of the quick-win actions resolved and closed.

Days 61 to 90: Delivering Measurable Value

The phase objective for the final period is: demonstrate programme-level improvements in schedule adherence and risk visibility, and secure stakeholder confidence in the new governance approach. Activities include a mid-year portfolio review with the executive team, a structured client satisfaction conversation with each account lead, and a written 90-day review document submitted to the sponsor. Success criteria include a measurable improvement in on-time reporting across the portfolio, positive feedback from at least three client leads, and a confirmed programme governance model adopted as the team standard. This example shows how each phase builds on the last and how every activity connects to a concrete, evaluable outcome.

Setting SMART Goals Within Your Plan

Goal quality is the single biggest determinant of whether a 30-60-90 day plan produces results or simply produces paperwork. SMART goal discipline, familiar to any practitioner trained in project management, is the most reliable way to ensure that objectives are genuinely useful rather than aspirationally vague.

A specific goal names an exact output: not ‘improve stakeholder communication’ but ‘establish a fortnightly written update to all Tier 1 stakeholders by day 21.’ A measurable goal defines how progress will be confirmed: not ‘build team confidence’ but ‘achieve a team satisfaction score of at least 7 out of 10 in the day-60 pulse survey.’ An achievable goal is realistic given the resources, time, and authority available in the relevant phase. A relevant goal connects directly to the overarching 90-day objective rather than reflecting personal interest or convenience. A time-bound goal carries a specific date, not a phase label, so that accountability is unambiguous.

When reviewing your draft plan, test each activity against these five criteria. Any activity that fails more than one criterion should be rewritten or removed. Plans that contain vague, immeasurable, or irrelevant goals tend to collapse in the second phase, when the initial energy of a new start fades and the absence of clear accountability becomes apparent.

Does a 30-60-90 Day Plan Include Weekends?

This is one of the most frequently asked practical questions about the format, and the answer is straightforward. The 30-60-90 structure is based on calendar days, not working days, so weekends are included in the count. Day 30 falls 30 calendar days after your start date regardless of how many of those days were weekdays. This matters because milestone dates should be set with reference to calendar dates rather than working-day counts, which keeps the plan aligned with how deadlines are communicated in most organisational settings.

In practice, most of the activities within each phase happen during working hours on working days. The calendar-day framing simply provides a consistent boundary for each phase and ensures that the plan remains readable and comparable regardless of where in the week or month the start date falls. If your organisation operates a compressed working week or if your role involves shift patterns, it is worth noting the effective working days available within each phase as a separate line in your resource section, so that your activity schedule is realistic rather than theoretically achievable on paper but unworkable in practice.

Common Mistakes to Avoid When Building Your Plan

Even practitioners with strong project management instincts make predictable errors when constructing a 30-60-90 day plan for the first time. Recognising these mistakes before you write a single line saves considerable rework later.

The most common error is front-loading the plan with activity while leaving the third phase vague. Days one to thirty receive ten carefully worded objectives while days sixty-one to ninety carry a single aspirational statement. This reflects the discomfort of committing to outcomes before you fully understand the environment, but it is precisely the discipline of committing early, and revising with evidence as you learn, that distinguishes a professional plan from a personal journal.

A second common mistake is omitting stakeholder mapping entirely. Without knowing who influences decisions, who controls resources, and who holds institutional knowledge, even a technically sound plan will stall. A third error is treating the plan as a submission document rather than a working tool. Once written, the plan should be reviewed weekly, updated as circumstances change, and used as the basis for conversations with your manager or sponsor. A plan that is never revised is a plan that has never been used. Finally, avoid the temptation to include every possible activity. Constraint creates focus. A plan with eight activities per phase that are all completed is far more valuable than a plan with thirty activities where only half are achieved and the rest are quietly abandoned.

Using PM Frameworks to Strengthen Your Plan

One of the clearest differentiators between a generic 30-60-90 day plan and a practitioner-grade one is the deliberate application of established project management frameworks. Whether your background is in PMBOK-aligned practice, IPMA competence development, or agile delivery, the conceptual tools available to you as a trained practitioner add rigour that no generic template can replicate.

From a PMBOK perspective, the first phase of your plan mirrors the initiating process group: you are defining scope, identifying stakeholders, and establishing the governance baseline. The second phase mirrors planning and executing: you are refining objectives, allocating effort, and beginning to deliver. The third phase reflects monitoring, controlling, and closing: you are tracking performance against baseline, managing emerging risks, and consolidating lessons learned.

IPMA competence frameworks add a behavioural dimension that is particularly relevant to leadership transitions. The framework’s emphasis on self-reflection, stakeholder engagement, and context awareness maps directly onto the listening and orientation activities of a well-constructed first phase. Agile practitioners will recognise the three-phase rhythm as analogous to three extended sprints, each with its own goal, review, and retrospective, which makes the plan particularly adaptable to iterative delivery environments. Whichever framework informs your professional practice, making that connection explicit within your plan signals to every reader that your approach is grounded in something more durable than good intentions.

Frequently Asked Questions

A 30-60-90 day plan is not a formality to satisfy a hiring manager or a checklist to file after your first week. Approached with the rigour of a project initiation, it is one of the most effective tools available for translating a period of uncertainty into structured, measurable progress. The practitioners who use it well treat it as a living document: specific, evidence-informed, and updated as reality unfolds. If you want to develop the framework thinking that makes that kind of disciplined planning second nature, a formal project management education is the most direct path forward.