Inheriting a Project or Workstream Mid-Flight: What to Audit in Your First Two Weeks
Most project management advice assumes you were there from the start. You helped write the charter, built the schedule, and know why every decision was made. Inheriting a project or workstream mid-flight is a different job; you're accountable for outcomes shaped by decisions you didn't make, commitments you didn't agree to, and relationships you haven't built yet.
It happens more often than we talk about. A PM gets reassigned, leaves the company, or a reorg shuffles portfolios, and suddenly the work is yours. I've spent most of my career starting new projects from scratch, but I have taken over an established workstream midstream, and the lessons apply at any scale.
The first two weeks are your window to learn before you're expected to lead at full speed. This checklist breaks that window into phases so you know what to verify, what to question, and what to hold off on.
The one rule for the entire two weeks: don't commit to new dates, budgets, or scope until you've finished your audit.
A quick note on timing: two weeks is a target, not a guarantee. If a milestone is due Friday, compress the phases below. The order still matters even when the calendar doesn't cooperate.
Women of Project Management Conference June 2027 Chicago Illinois - Tickets on Sale Now!
Before Day One: What to Request From the Outgoing PM
The handoff is your best chance to capture knowledge that isn't written down anywhere. Treat it as a priority, not a formality.
Documents to Gather
Project charter or business case
SOW, contracts, and vendor agreements
Current schedule plus the original baseline
RAID log (risks, assumptions, issues, dependencies)
Budget, forecast, and actuals
Change log and approved change requests
The last several status reports
Meeting cadences and distribution lists
Access to tools, shared drives, and communication channels
Questions for the Handoff Conversation
What is most likely to go wrong in the next 30 days?
Have you made any promises to stakeholders that aren't documented?
Which stakeholder needs the most attention right now, and why?
What decisions are pending, and who is waiting on them?
If you were staying, what would you change?
When the Outgoing PM Is Already Gone
Meet with the sponsor first to get their view of project health and priorities
Ask the most tenured team member for a walkthrough of the work
Reconstruct recent history from email threads, meeting notes, and tool activity
Assume the documentation is incomplete until you've confirmed otherwise
Women of Project Management Conference
Days 1 to 3: Triage What Can't Wait
Before you audit anything in depth, find out what's about to break.
Find Everything Due in the Next 30 Days
Deliverables and milestones
Contract dates and payment milestones
Open escalations
Approvals sitting with someone who's waiting on the project team
Confirm Your Authority and Reporting Line
Verify who the sponsor is and that they know you're now the PM
Clarify your decision rights on budget, scope, and vendors
Map the escalation path
Ask the sponsor to announce the transition to stakeholders so your authority is clear from the start
This mirrors advice from Michael Watkins' The First 90 Days, which emphasizes clarifying expectations, metrics, and communication rhythms with your boss early so there are no surprises later. For an inherited project, your sponsor plays that role. hireinsouth
Week One: Audit the Schedule, Scope, and Budget
These three areas line up with PMI's current standard. The PMBOK Guide, Eighth Edition organizes project work into seven performance domains: governance, scope, schedule, finance, stakeholders, resources, and risk. Week one covers scope, schedule, and finance. Project Management Institute
Schedule Health Checks
Compare the current schedule to the original baseline, and flag it immediately if no baseline exists
Look for tasks with past due dates still marked as in progress
Check for missing or broken dependencies
Test whether the critical path reflects reality by asking the people doing the work
Review resource assignments for people who have left or are overallocated
Scope Drift
Compare the charter to what the team is actually building
Identify undocumented changes, especially "small favors" agreed to in meetings
Confirm that acceptance criteria exist and that stakeholders agree on them
Budget and Vendor Commitments
Compare burn rate to forecast
Separate money spent from money committed but not yet spent
Review contract obligations, renewal dates, and penalty clauses
Check for pending invoices or disputed charges
Weeks One to Two: Audit Risks, Issues, and Decisions
The Little Black Book of Project Management Advice
A RAID log tells you what the previous PM was worried about. Your job is to find out whether those worries were the right ones.
RAID Log Reality Check
Reclassify risks that already happened as issues
Reassign items owned by people who have left
Update mitigation plans that haven't been touched in weeks
Add the risks you spotted during your week one audit
Reconstructing the Decision History
Figure out why the project is structured the way it is before judging it
Review steering committee decks, meeting minutes, and key email threads
Start a decision log going forward so the next person doesn't have to do this work
Hold off on reversing any decision until you understand the reasoning behind it
Week Two: Audit Stakeholder Relationships
Documents show you the plan; stakeholders show you how the project is actually perceived. This is where most of the unwritten information lives.
Stakeholder Interview Questions
What does success look like to you?
What's working well, and what isn't?
How and how often do you want updates?
Do you have concerns that haven't been addressed?
What the Previous PM Promised
Listen for commitments stakeholders mention that aren't in any document
Note expectations about dates, features, or access that you'll need to confirm or reset
Record everything, even if you can't honor it, so you can address it directly in your readout
Team Morale and Capacity
Hold one-on-ones with each core team member
Ask what slows them down and what they need from you
Watch for signs of burnout or frustration left over from the transition
When I took over a workstream, this was where I spent most of my energy. Getting to know every stakeholder, learning the operations behind the work, and treating knowledge transfer as a real priority is what got me through a challenging start. The documents told me what was happening; the people told me why.
End of Week Two: Deliver Your State of the Project Reset
Your audit is only useful if you share what you found. A short readout to the sponsor and key stakeholders turns your two weeks of learning into a clear starting point.
What to Include in the Readout
An honest status of schedule, scope, and budget
Gaps and risks you uncovered
What's on track and working well
Undocumented commitments that need to be confirmed or reset
Your recommendations
Decisions you need from the sponsor
When to Re-Baseline
The schedule or budget no longer reflects a realistic path to completion
Approved scope has changed significantly since the original baseline
Key resources or vendors have changed
Stakeholders are working from conflicting expectations
Where to Bring Your Own Ideas Without Breaking What Works
Once you understand the work, it's time to move it forward. In my workstream, keeping momentum meant coming up with fresh ideas once I had a solid grasp of the operations; stabilizing things was only half the job.
Build on what's working before changing what isn't
Start with improvements that are visible, low risk, and solve a problem stakeholders already feel
Tie each new idea to something you learned during your audit
Watkins makes a similar point about early wins; visible results that show competence without alienating long-tenured colleagues build the credibility you'll need for bigger changes later. hireinsouth
Red Flags That Mean You Need More Than Two Weeks
Some inherited projects need a deeper reset. Escalate to your sponsor and ask for more time if you find:
No baseline, or a baseline nobody recognizes
A sponsor who is unclear, disengaged, or recently changed
Active contract disputes with vendors
A budget overrun no one can explain
High team turnover during the transition
Stakeholders who contradict each other on what the project is supposed to deliver
Quick-Reference Checklist for Inheriting a Project
Before day one
Gather documents and schedule a handoff conversation
Get access to every tool and channel
Days 1 to 3
List everything due in the next 30 days
Confirm your sponsor, decision rights, and escalation path
Week one
Audit schedule against baseline
Check for scope drift
Review budget, commitments, and contracts
Weeks one to two
Clean up the RAID log
Reconstruct key decisions and start a decision log
Week two
Interview stakeholders
Surface undocumented promises
Meet one-on-one with the team
End of week two
Deliver your state of the project readout
Re-baseline if needed
Identify your first improvement
Inheriting a project or workstream means starting behind, but a structured audit closes that gap quickly. Give yourself two weeks to learn before you lead, and the decisions you make afterward will rest on what's actually true about the work.
Join.
Join the full discussion inside the Women Of Project Management Membership. Listen to part of our conversation on the Women Of Project Management Podcast.
If you're new to our community, Women Of Project Management is the only community created to support & amplify the voices of women & women of color in every specialty of the project management industry worldwide. We support women in every stage of their career, learn more at Women Of Project Management.
