What are deliverables?
Deliverables are the specific outputs or results that a project team produces and hands over to a client or stakeholder.
They can be documents, designs, reports, prototypes, features, or final software releases.
Deliverables define what success looks like for each stage of a project and are essential for measuring progress and completion.
In software development, deliverables connect project effort with tangible results that can be reviewed, tested, and approved.
Why deliverables matter
- define what the client will actually receive
- make project scope measurable and concrete
- help manage expectations and avoid misunderstandings
- allow progress tracking and milestone validation
- tie directly to payment, sign-off, and success metrics
Without clear deliverables, even well-planned projects can face disputes over what “done” really means.
Types of deliverables in software projects
| Type | Description | Example |
|---|---|---|
| Internal deliverables | Produced for the team or internal use | Architecture diagram, test plan, code documentation |
| External deliverables | Delivered to the client or end user | Design mockups, API, app prototype, final release |
| Tangible deliverables | Physical or visible output | UX design files, website, mobile app |
| Intangible deliverables | Less visible results | Performance report, insights, training session |
| Interim deliverables | Created during the project as checkpoints | MVP version, wireframes, sprint demo |
| Final deliverables | Completed outputs marking the end of the project | Full software system, documentation, training materials |
Examples of common deliverables by phase
Discovery phase
- requirements document
- project roadmap
- estimation and proposal
- scope of work (SOW)
- user stories and acceptance criteria
Design phase
- wireframes and UI mockups
- clickable prototype
- design system or style guide
Development phase
- working software modules
- backend and frontend code
- APIs and integrations
- database schema
- deployment scripts
Testing phase
- QA reports and bug lists
- test cases and results
- user acceptance testing feedback
Launch and post-launch
- production release
- documentation and training materials
- maintenance plan or SLA
How to define project deliverables
1. Start from the scope of work
List each agreed output in the SOW and connect it to the project objectives.
2. Make them measurable
Each deliverable should be verifiable by completion or acceptance criteria.
3. Assign responsibility
Define who is responsible for preparing, reviewing, and approving each deliverable.
4. Link to milestones
Group deliverables under milestones or phases for better visibility.
5. Use consistent naming
Keep file names, versioning, and documentation consistent across projects.
6. Clarify the format and medium
Specify whether it is a document, design file, deployed feature, or report.
Example deliverables list
PROJECT: SaaS Platform MVP
Deliverables:
1. Requirements document (PDF)
2. UX wireframes (Figma)
3. UI design system (Figma)
4. API specification (Swagger)
5. User dashboard (React app)
6. Admin panel (Next.js)
7. QA report and bug log
8. Deployment to staging and production
9. Final project documentation (PDF)
10. Maintenance handover checklistHow to track deliverables
- use a project tracker with a “deliverables” section
- assign owners and due dates to each deliverable
- update progress regularly (for example 80% complete, in review, approved)
- share deliverable versions with clients for feedback
- mark deliverables as “approved” only after client sign-off
Deliverables vs milestones
| Aspect | Deliverables | Milestones |
|---|---|---|
| Definition | Specific outputs or results | Key checkpoints marking progress |
| Purpose | Provide tangible outcomes | Track completion of key phases |
| Examples | Design files, app module, report | Design approval, MVP release |
| Frequency | Many per project | Few per project |
| Measurement | Based on acceptance criteria | Based on timing or completion event |
Best practices
- document deliverables clearly in the proposal and SOW
- version control every deliverable for traceability
- review deliverables jointly with the client before approval
- ensure each deliverable meets its acceptance criteria
- store deliverables centrally for easy access
Common mistakes
- Vague deliverables - unclear or hard to measure
- Too many deliverables - unnecessary complexity and overhead
- Missing internal deliverables - skipping documentation or testing artifacts
- No acceptance process - lack of formal sign-off creates confusion
- Untracked revisions - causes version mismatches or scope issues
How deliverables connect to project estimation
Deliverables are the foundation of accurate estimation.
When you define each output clearly, you can assign realistic time, roles, and costs.
They also help align expectations early, avoiding disputes later.
Example:
Feature: User dashboard
Deliverables: UI design, API integration, working feature in staging
Estimated effort: 64 hours (developer + QA + review)
FAQ
What are deliverables in software development?
They are specific outputs or results that the project team produces and delivers to the client, such as designs, code, or reports.
What is the difference between deliverables and milestones?
Deliverables are tangible outputs, while milestones are key points marking when those outputs are completed.
Who defines deliverables in a project?
Usually the project manager, together with the client and team, during the discovery or planning phase.
How do I make deliverables clear for clients?
List them in the scope of work, define acceptance criteria, and connect them to milestones or payments.
Can deliverables change during a project?
Yes. Any changes should be handled through a formal change request process to adjust scope and timeline.