30-60-90 day plan for project managers

A project manager is judged on something they do not directly control: whether other people deliver on time. That makes a 30-60-90 day plan for the role unusual. The milestones are not about what the new PM personally builds but about whether the project's status is known, honest and moving, and whether stakeholders believe the PM's forecast. The plan below is built around the documents a project actually runs on: the schedule, the RAID log, the status report and the change log.

This is the project manager role: delivery of a defined scope, to a date, with a budget. If you are hiring a product manager, who decides what to build, use the 30-60-90 day plan for product managers instead. The general template for any role is the 30-60-90 day plan template for new hires.

Why a new project manager inherits a mess

Most project managers are hired into a project that is already running, often because the last owner left or the project got into trouble. The paperwork will say one thing and the team will quietly know another: the schedule in the tool was last updated six weeks ago, two risks in the log have already become issues, and a scope change was agreed in a hallway without anyone logging it. A new PM who takes the documents at face value inherits the gap between them and reality, and then owns it.

So the first phase is a reassessment, not a continuation. By day 30 the new PM should be able to say, with evidence, where the project actually stands.

Days 1-30: Reassess the real status

Goals

• Read the project charter or statement of work, the current schedule, budget tracker, RAID log (risks, assumptions, issues, dependencies) and the last six status reports.
• Meet one-to-one with the sponsor, each workstream lead and the main vendor contacts. Ask each the same question: what do you think the real finish date is?
• Walk the schedule's critical path task by task with the people doing the work, and mark every task whose estimate they no longer believe.
• Attend every recurring project meeting without changing its format.
• Get admin access to the project tool (Jira, Asana, Smartsheet, MS Project or whatever the team uses) and the budget system.

Deliverables by day 30

• A refreshed RAID log, with owners and dates on every open item and anything stale closed out.
• A status reassessment memo to the hiring manager: current forecast finish date, budget position, top five risks, and whether the baseline needs to be reset.
• A stakeholder map: who approves what, who needs weekly updates, who only needs to hear about exceptions.

Days 31-60: Run the project's operating rhythm

Goals

• Own the weekly status report end to end, sent on the same day every week, with a red, amber or green rating the PM can defend line by line.
• Run the steering or sponsor meeting, including a request for decision if the reassessment showed the baseline needs to change.
• Put change control into practice: every scope change goes through a written request with an impact on time and cost before it is approved.
• Hold a weekly risk review with workstream leads, not just a quarterly one.

Deliverables by day 60

• An approved rebaseline, or a documented decision by the sponsor that the current baseline stands.
• A change log with every scope change since the PM started, including the ones that were refused.
• Four or more status reports whose ratings held up, with no "surprise red" in the following week.

Days 61-90: Deliver a milestone and forecast reliably

Goals

• Land at least one milestone on the rebaselined date, or flag the slip at least two weeks ahead with a recovery plan.
• Resolve one cross-team dependency or vendor issue that had been stuck before the PM joined.
• Run a lessons-learned session for the phase just finished and turn its findings into two or three concrete process changes.

Deliverables by day 90

• A milestone delivered, with acceptance signed off by the sponsor or client.
• A forecast for the rest of the project that the sponsor and workstream leads both say they believe.
• A short write-up for the day-90 review: what the PM changed, what they would still fix, and where they need more authority.

On track or off track at each checkpoint

A filled example

Status reporting: the skill the plan is really testing

Nearly everything in a project manager's first 90 days feeds one skill: saying accurately where the project stands. It is easy to describe and hard to do, because every incentive pushes toward optimism. Workstream leads report their own tasks as on track, sponsors prefer good news, and a new PM wants to look in control.

Watch for three things in the weekly reports. First, whether amber is ever used; a report that goes straight from green to red is a report that was hiding amber. Second, whether each red or amber item has a named cause, a named owner and a date, rather than "monitoring." Third, whether the forecast finish date is stated at all. A PM who writes "on track" without a date has not made a forecast.

What the hiring manager owes the new PM

• A real handover from the previous owner, even a remote one, including what was promised verbally.
• An introduction to the sponsor that makes clear the PM speaks for the project, so stakeholders do not keep going around them.
• Clarity on authority: can the PM approve a small change, reassign a task between workstreams, or escalate to a vendor's account manager without asking first?
• Cover for bad news. If the reassessment shows the project is late, the hiring manager should back the PM in delivering that message, not ask them to soften it.

Mistakes that stall a new project manager

Adapting the plan

• Construction and field projects: add site walks, the submittal and RFI logs, and a safety orientation to the first 30 days; the day-90 milestone is often a physical inspection passed. The construction project manager screening questions cover the skills to test before hire.
• Agile software delivery: replace the schedule baseline with the release plan and the team's velocity history, and treat the backlog as the change log. Where a scrum master already runs ceremonies, the PM's focus shifts to cross-team dependencies and release forecasting; the scrum master screening questions help separate the two roles.
• Client-facing agency projects: add a day-60 goal to run a client status meeting solo and a day-90 goal tied to invoice milestones.

If the role is still open, the project manager phone screen questions test for exactly the behaviors this plan rewards: honest status, written change control, and bringing bad news early. Pair the plan with the new hire onboarding checklist so tool access is ready before day one.