What Are Deliverables in Project Management?
A deliverable in project management is any tangible or intangible output a project produces and hands over — a document, a product, a result, or a capability. Deliverables are the “what” of a project: the things you promise stakeholders, not the tasks you do to produce them. “Build the training module” is a task; the finished module is the deliverable.
Defining deliverables clearly, agreeing what “done” looks like, and tracking them is one of the biggest differences between a project that lands and one that quietly drifts. Here’s how they work.
What counts as a deliverable
Formally, a deliverable is any unique, verifiable output produced to complete a process, phase, or project. A useful way to picture it: deliverables are promises made to stakeholders. They aren’t tasks or activities — they’re the tangible results that provide value once the work is finished.
Types of deliverables
Deliverables fall into a few standard categories, and most projects produce all of them. The two distinctions that matter most are internal vs external, and process vs product.
| Type | What it is | Example |
|---|---|---|
| Internal | Supports delivery; the client may never see it | Project schedule, resource plan, QA documentation |
| External | What you promise the client or end users | Finished e-learning module, completed training programme |
| Process | Created to manage the project itself | Project plan, status reports, risk log |
| Product | The actual thing you’re building for stakeholders | The software, course, or materials delivered |
Internal and external describe who sees it; process and product describe what it’s for. Strong process deliverables (a clear plan, honest status reports) usually lead to better product deliverables.
What makes a good deliverable
A deliverable only earns its place if it’s clear, time-bound and genuinely useful. Three characteristics separate a good one from a vague one:
- Specific and measurable. Define exactly what “done” looks like. Not “create training materials”, but “five interactive e-learning modules with assessments, each 20–30 minutes long.” If you can’t test whether it’s finished, it isn’t specified yet.
- Time-bound. Deliverables without deadlines drift. Each one needs a timeline that fits the wider schedule and accounts for what depends on it.
- Value-driven. Every deliverable should move the project towards its objective. If you can’t answer “what does this actually help us achieve?”, question whether it belongs in the plan.
Managing deliverables
Once deliverables are defined, they need managing — not just listing. Three habits do most of the work:
- Document them properly. Keep a deliverables register with specifications, acceptance criteria and dependencies. It saves hours of stakeholder back-and-forth and makes quality checks straightforward.
- Review and adjust. Projects change, so deliverables should be reviewed with stakeholders to stay aligned with the goal rather than a plan written months ago.
- Control quality. Peer reviews, stakeholder feedback and a formal acceptance step catch problems early — far cheaper than fixing them after handover.
Common pitfalls to avoid
- Underestimating how complex a deliverable really is
- Missing the dependencies between deliverables
- Involving stakeholders too late to influence the outcome
- Chasing quantity over quality
- Neglecting documentation until it’s needed and missing
Clear roles and stage-by-stage control help here, which is exactly what structured methods teach — see our guide to governance in project management and how RAID logs track risks and dependencies.
The bottom line
Deliverables aren’t items to tick off a list — they’re the building blocks of project value. Define them clearly, tie each one to a deadline and an objective, document them, and review them as the project moves. Do that and you remove most of the ambiguity that sinks projects.
It’s a skill worth building deliberately. If you’re mapping out how to become a project manager, managing deliverables well is one of the abilities that marks you out — and it’s a core part of any accredited project management course.