Work & Career

Before You Take On a New Project: A Preparation Checklist

Organized desk with notebook, sticky notes, pen and laptop for project planning preparation

Key Takeaways

  • Clarifying scope and success criteria before work begins is the single highest-leverage step you can take.
  • Identifying stakeholders and decision-makers early prevents expensive miscommunication mid-project.
  • Realistic time and resource estimates require an honest look at your current commitments, not just the new work.
  • A documented risk and dependency list gives you early-warning signals before problems escalate.
  • Getting alignment in writing — even informally — protects everyone involved.
20–45 min

Summary

18 items · 20–45 minutes

Why Preparation Is the Real Work

Most project failures don't start at the finish line — they start at the starting line. Scope creep, missed deadlines, and stakeholder frustration usually trace back to assumptions that were never tested before work kicked off. Research from the Project Management Institute has consistently found that incomplete requirements and poor upfront planning rank among the leading causes of project failure across industries.

This checklist is designed for workers at any level — individual contributors, team leads, or freelancers — who are about to take on a new project, whether it's a six-week initiative or a two-day deliverable. Running through these steps before a single task begins costs you less than an hour. Skipping them can cost you weeks.

If you frequently navigate high-stakes preparation, you may also find value in our guide to preparing for salary negotiations, which uses a similar evidence-gathering framework.

Scope & Objectives

Write a one-paragraph plain-language description of what this project will deliver and why it matters. Must
Define what is explicitly out of scope — list at least three things this project will not include. Must
Identify the single measurable outcome that will signal the project is complete. Must
Confirm that this objective aligns with broader team or organizational priorities. Should

Stakeholders & Decision-Making

List every person who has a stake in the outcome — including those who will review, approve, or be affected by the work. Must
Identify who has final decision-making authority if the team reaches a disagreement. Must
Confirm your primary point of contact and their preferred communication channel and frequency. Should
Flag any stakeholders who may have conflicting priorities and note how conflicts will be escalated. Nice to have

Time & Capacity

Block out a realistic hour-by-hour estimate for each major phase of the project — don't just guess at a total. Must
Audit your current workload and identify what, if anything, needs to be delayed or delegated to absorb this project. Must
Set and communicate an agreed deadline, including intermediate milestones with specific due dates. Must
Build a buffer of at least 15–20% into your timeline to account for review cycles and unexpected delays. Should

Resources & Dependencies

List every resource you need — budget, tools, data access, team support — and confirm each is available. Must
Identify tasks that depend on another person or team delivering something first, and confirm their timelines. Must
Document any approvals, permissions, or access credentials required before work can start. Should

Risk & Alignment

List the two or three most likely things that could derail this project and write a one-line contingency for each. Must
Send a written summary of scope, timeline, and key contacts to all stakeholders and get explicit confirmation. Must
Schedule a brief check-in at the project's midpoint before it begins — don't wait until problems surface. Nice to have

Tools That Support Project Preparation

You don't need elaborate software to run this checklist — a notes app and a calendar will handle most of it. That said, a few tools make the process more systematic, especially on complex or team-based projects.

Required

Project brief template

A simple one-page document capturing scope, objectives, stakeholders, and timeline in a shareable format.

Required

Calendar or scheduling tool

Used to block time for project phases, milestones, and stakeholder check-ins before work begins.

Optional

Task or project management app

Helps break the project into trackable tasks and assign ownership — useful when more than one person is involved.

Required

Shared document or note-taking tool

Provides a central, accessible record of decisions, open questions, and agreed scope that all parties can reference.

The goal is documentation, not perfection. Even a shared Google Doc or a simple email thread that captures agreed scope, timeline, and contacts is far better than verbal commitments that fade within a week.

Verbal Agreements Don't Protect Anyone

It's easy to assume that a quick conversation locks in shared understanding — but memory is selective and context gets lost. Even an informal email summarizing what was agreed gives you and your stakeholders a reference point when expectations diverge later. Make documentation a default, not an afterthought.

Work & Career Editorial Team is the collective byline for our editorial team and contributor network. Articles published under this byline or an editorial pen name are researched, written, and reviewed according to our editorial standards for clarity, consistency, and independence before publication.

View all articles by Work & Career Editorial Team →
Disclaimer: The content on this site is for informational purposes only and is not a substitute for professional advice. Always consult a qualified professional for guidance specific to your situation.