What Are Deliverables in Project Management? (Definition, Types & Examples)

A deliverable is any tangible output a project produces that someone outside the work agrees to check, use, or sign off on: a finished website, a signed contract, a shipped feature, a report handed to a client. If a project is the journey, deliverables are the concrete things you can point to and say “here it is, done.”

The word gets used loosely, which is where confusion creeps in. Not everything you produce along the way is a deliverable, and not every deliverable is obvious until you name it. This page walks through a plain definition, how deliverables differ from tasks and milestones, the main types you’ll run into, and how to write one so it’s actually trackable instead of vague.

Deliverable vs. task vs. milestone

These three get used interchangeably, but they answer different questions, and mixing them up is the most common source of confused project plans.

• Task. A unit of work someone does. “Write the first draft of the client report” is a task. Tasks are the how.
• Deliverable. The output that work produces, and that gets accepted or rejected by someone. “The finished client report” is the deliverable. Deliverables are the what.
• Milestone. A point in time that marks progress, usually when a deliverable is due or a phase ends. “Report delivered to client” is a milestone. Milestones are the when.

A useful rule of thumb: if you can hand it to someone and ask “does this meet what we agreed to?”, it’s a deliverable. If it’s just something that happened along the way, it’s a task.

Types of project deliverables

Deliverables usually get sorted along two axes: who they’re for, and whether you can touch them.

• Internal deliverables. Stay inside the team or organization: a test plan, an internal style guide, a budget approved by a manager.
• External deliverables. Go to a client, customer, or outside stakeholder: a shipped product, a signed-off design, a delivered training session.
• Tangible deliverables. Concrete, inspectable artifacts: a document, a piece of software, a physical product, a video.
• Intangible deliverables. Real but harder to point at: a completed training program, an improved process, a certified skill.

Most projects produce a mix. A software launch might have an internal deliverable (a QA sign-off report) and an external one (the live product) in the same week.

How to write a deliverable that's actually trackable

Vague deliverables (“improve onboarding”) are where projects quietly stall, because no one can say when they’re done. A trackable deliverable has four things:

• A specific name. “Onboarding email sequence (5 emails, drafted and approved)” beats “onboarding improvements.”
• An owner. One person accountable for it existing, even if several people contribute.
• A due date. Tied to a milestone, not a vague “soon.”
• Acceptance criteria. What has to be true for it to count as done, ideally agreed with whoever’s accepting it before work starts, not after.

That last one matters most. A deliverable without agreed acceptance criteria isn’t planned, it’s a guess that someone will like what shows up.

A quick example

Say the project is “launch a new pricing page.” The deliverable is the live, published pricing page itself, not any single step toward it. The tasks underneath it might be: write the copy, design the layout, build it, get legal sign-off, QA on mobile. The milestone is the date the deliverable goes live. One deliverable, five tasks, one milestone, three different words doing three different jobs.

Where deliverables live in Taskly

In practice, most teams don’t need a separate “deliverables” system: they need their task manager to hold the distinction cleanly. In Taskly, a deliverable is usually a parent task with the acceptance criteria in its description and the supporting work underneath it as subtasks, so anyone can see at a glance what “done” actually means and who owns getting there.

If you describe a project to Otto, our AI assistant, in plain English, it drafts that structure for you: the deliverable, its subtasks, and a due date, as a proposal you review and approve before anything is created. If you’re evaluating tools for this kind of work more broadly, our breakdown of task management software for teams is a good next stop.