Project Manager Onboarding Checklist
Everything you need to onboard a project manager from Day 1 through their first 90 days. Customizable for your company size and work setup.
Last updated May 21, 2026 • By Pro Sulum • Free to use, no signup
Get My Free Project Manager Onboarding ChecklistSample Project Manager Onboarding Checklist
Day 1: Get the PM fully provisioned on all tools and oriented on the current sprint status before attending their first team meeting.
- Provision Jira or Asana with admin-level project access — Create the account and grant edit access to all active project boards. The PM needs to see backlog, sprint board, and velocity data from day one, not after a week of read-only access. critical
- Sign IP assignment agreement and confidentiality agreement — Technology company PMs have visibility into unreleased product roadmaps and client project details. Both agreements should be signed before the PM accesses any project documentation. critical
- Provision Confluence or Notion for documentation access — Add the PM to the company's documentation workspace with edit rights. Share links to the engineering team's working norms, sprint templates, and any existing PM playbooks. critical
- Complete new hire paperwork and benefits enrollment — Process tax forms, direct deposit, and benefits elections. Benefits open enrollment deadlines in tech companies are often strict. This should be completed before any technical orientation begins. critical
- 1:1 with hiring manager to review current project portfolio — Walk through every active project, its current status, and the PM's eventual ownership scope. Discuss what is going well and what the new PM is being hired to fix or improve. critical
- Provision GitHub or GitLab with read access — Add to the company's version control system with viewer access. PMs in tech companies need visibility into pull request volume, release branches, and deployment schedules. important
- Introduction to engineering team and assigned buddy — Brief team meeting or video call where the PM meets the engineers they will work with. Assign a senior engineer or experienced PM as a 30-day buddy. important
- Set up Slack with all engineering and product channels — Add to #engineering, #product, #standup, #incidents, and any project-specific channels. Review the channel purpose guide so the PM knows where different types of communication happen. critical
Week 1: Observe all sprint ceremonies, understand the current methodology, and produce a first draft of the stakeholder map by Friday.
- Attend all sprint ceremonies as an observer — Sit in on daily standup, sprint planning, backlog refinement, and any sprint review or retrospective scheduled in week one. Take notes on format, participation, and any visible friction points. critical
- Methodology orientation session with engineering lead — One hour with the engineering lead covering whether the team uses Scrum, Kanban, or a hybrid, sprint length, definition of done, and how scope changes are handled mid-sprint. critical
- Draft initial stakeholder map for all active projects — Identify every stakeholder by name, role, and how they interact with each project. Note communication preferences, decision authority, and any known tensions. Share draft with manager by Friday. critical
- Review last three sprint retrospective documents — Read the documented retrospective outputs in Confluence or Notion. Identify recurring issues the team has flagged and what action items were committed to but not resolved. important
- 30-minute 1:1 with each engineer on the primary project team — Schedule brief one-on-ones with each direct engineering collaborator. Ask about their current blockers, what they wish the previous PM had done differently, and their preferred communication style. critical
- Review the current product roadmap with the Product Manager — Understand the 90-day and six-month roadmap priorities. Clarify the boundary between PM and Product Manager ownership at this company, as the split varies significantly by organization. critical
- Complete security awareness training — Finish the company's annual security training covering phishing recognition, data handling, and access control policies. PMs in tech companies often access client data and internal roadmaps. critical
- Configure personal Jira or Asana dashboard for active sprint tracking — Set up personal views, filters, and saved searches to track the projects the PM will eventually own. Review velocity charts and burndown graphs for the last four sprints. important
- End-of-week debrief with manager covering observations and questions — One-hour structured conversation where the PM shares their initial observations, asks clarifying questions about authority and scope, and gets feedback on the stakeholder map draft. important
Month 1: Lead at least one sprint ceremony independently, own the project status report, and deliver a written team capacity and current project health assessment.
- Lead daily standup independently for two consecutive weeks — Facilitate the standup without the manager present. Take notes on blockers and own the follow-up process for any items that surface. critical
- Deliver first sprint planning session as the primary facilitator — Run sprint planning from agenda to story point commitment. Review with the engineering lead afterward to calibrate on what worked and what to improve. critical
- Complete and distribute written team capacity document — Document each engineer's weekly available hours, known planned absences in the next 90 days, and current sprint allocation. Share with the manager and product lead. critical
- Complete Jira Advanced certification or internal Jira training — Finish the Atlassian advanced Jira certification or the company's internal Jira workflow training. Focus on custom dashboards, automation rules, and cross-project reporting. important
- Meet with QA lead to understand testing integration in the sprint — Learn how QA fits into the sprint cycle, how bugs are filed and triaged, and what the PM's role is in prioritizing bug fix work alongside feature development. important
- Write first project health report for all active projects — Produce a one-page status summary per project covering schedule health, blockers, risks, and upcoming milestones. Share with the manager and relevant stakeholders. critical
- 30-day performance review with manager — Review the stakeholder map, capacity document, and sprint facilitation quality. Set specific measurable goals for month two including project ownership milestones and process improvements. critical
- Shadow a sprint retrospective and prepare to run the next one — Observe how the current facilitator runs the retro. Prepare a revised format or facilitation approach for the next retrospective and get manager approval before running it. important
90 Days: Independently own at least one project end-to-end, deliver a retrospective with documented process improvements, and set measurable OKRs for the next quarter.
- Complete first independently owned sprint cycle from planning through retrospective — Own all ceremonies for one full sprint: planning, daily standup, sprint review, and retrospective. Document the retrospective outputs and assign action items with owners and deadlines. critical
- 90-day performance review with written self-assessment — Write a one-page assessment covering sprint velocity trends, the process improvements implemented, and three things to focus on in Q2. Review with the manager and set Q2 OKRs. critical
- Propose and implement one process improvement to the team — Based on 90 days of observation, identify one change to the sprint process, standup format, or documentation standard that would improve team efficiency. Propose it, get buy-in, and implement it. important
- Complete risk management training or internal escalation protocol review — Either finish a formal risk management course (PMI or Scrum Alliance) or document the company's internal escalation protocol for scope changes, missed deadlines, and technical blockers. important
- Present project status update to senior leadership or a client — Deliver at least one presentation to an audience beyond the immediate team. This may be an executive sprint review, a client status call, or a department all-hands update. important
- Audit the project portfolio for documentation completeness — Review every active project in Jira and Confluence. Flag projects with missing scope documents, outdated milestones, or no documented owner. Present findings to the manager with a remediation plan. important
- Confirm all required compliance certifications are current — Verify that security training, IP agreements, and any role-specific certifications are documented and current in the HR system. Identify any certifications the company should add to the PM role profile. critical
- Close formal buddy relationship and document onboarding feedback — Have a closing conversation with the buddy and write three to five specific improvements for the project manager onboarding checklist. Submit feedback to HR for the next PM hire. nice-to-have
Small business owners hiring a Project Manager for the first time often feel overwhelmed. With a small team and no HR support, onboarding can feel like a huge task on top of everything else. Time is tight, and there is no existing playbook or clear process to follow. This can make it hard to know where to start or how to set the new Project Manager up for success. Without a structured approach, the risk of mistakes or delays grows, adding stress to an already busy schedule. During the first week, the most important priority is to get the Project Manager familiar with your business’s top projects and communication style. They need to understand the key goals, who the main stakeholders are, and how decisions are made day to day. This means introducing them to the team, sharing project details, and clarifying expectations early on. Giving them a clear sense of what success looks like in the role helps the new hire focus and start contributing quickly. One effective way to train your new Project Manager without micromanaging is what we call the "Record & Delegate" method. Before your new hire starts, take 5 to 10 minutes to record a short video showing yourself doing the 3 to 5 most important tasks they will handle. This might be how you update project schedules, communicate with clients, or report progress to the team. The video becomes a simple training guide the Project Manager can watch anytime. Instead of constant back-and-forth questions, they watch the video and take over those tasks. This approach reduces bottlenecks because you are not the only source of knowledge, and it helps the new hire gain confidence faster. A common onboarding mistake small business owners make is trying to hand over too many responsibilities too quickly without clear instructions or priorities. Because you wear many hats, it’s tempting to dump everything on the new hire at once. This causes confusion and frustration because the Project Manager may not know what to focus on or how to do certain tasks. Instead, set clear priorities for the first few weeks and break down responsibilities into manageable chunks. This allows the new hire to build skills gradually and prevents overwhelm. At 90 days, a Project Manager who is ready to work independently can manage key projects from start to finish without constant input. They communicate clearly with the team and clients, keep projects on schedule, and solve problems as they arise. They have a good grasp of your business priorities, know who to ask for help, and can delegate tasks appropriately. Most importantly, they act as a reliable point person for project updates and decisions, freeing you to focus on growing the business. If you want a Project Manager who documents their own processes and builds systems as they go, rather than requiring you to document everything first, that is what a Virtual Systems Architect does. Start with this checklist.
Frequently Asked Questions
I hired someone for this role before and it did not work out. What usually goes wrong?
Most failed Project Manager hires come down to one of three problems: the owner skipped structured onboarding in week one, there was no documented process for the hire to follow, or expectations were never made explicit. The new hire guessed, made mistakes, and the owner assumed the person was the problem. In most cases the process was the problem. This checklist closes all three gaps. Start with a clear first week, a Record and Delegate video for each core task, and written expectations before the hire ever logs in.
What should I look for when hiring my first Project Manager?
Look for someone with strong communication skills, experience managing projects similar to your business size, and the ability to work independently without much supervision.
How long does it usually take for a Project Manager to get up to speed?
Typically, it takes about 60 to 90 days for a new Project Manager to fully understand your business and run projects independently.
Should I create detailed manuals for my new Project Manager?
Instead of lengthy manuals, short videos showing how you do key tasks can be more effective and easier for your new hire to follow.
How can I avoid micromanaging while onboarding?
Use the "Record & Delegate" method by recording your process for important tasks so your Project Manager can learn independently and reduce the need for constant check-ins.
What are red flags during onboarding to watch out for?
Watch for confusion about priorities, missed deadlines, or reluctance to ask questions. These can signal gaps in training or unclear expectations.
Can a Project Manager help free up my time as a small business owner?
Yes, once onboarded properly, a Project Manager can take over project coordination and communication, allowing you to focus on strategic growth.
Related Onboarding Checklists
Read Next
Go beyond the checklist
What if someone else ran this onboarding process for you?
Pro Sulum's Virtual Systems Architects document your processes and run new-hire training from Day 1 through Day 90, so you never have to.
97% stay past year one.
Schedule a Free 30-Minute Discovery Call