Skip to main content
Deliverables represent the work Kowalah is actively building or running for you inside a project. Most deliverables arrive by promoting an Opportunity once it has been triaged, but you and your Kowalah partner can also create one directly when the work is already scoped.
Deliverables only exist inside Kowalah-managed projects — projects where Kowalah is delivering work alongside you. Customer-managed (private) projects use tasks and milestones instead.

​
Stages

Every deliverable moves through four main stages, displayed as a kanban board on the project page: Two additional statuses sit outside the main flow:
The earlier “idea” stage is now captured as an Opportunity instead of an early-stage deliverable. This keeps the deliverables board focused on committed work.

​
Where deliverables come from

Promoted from an Opportunity

The most common path. An idea is captured and triaged as an Opportunity, then promoted into a deliverable inside the right project.

Created directly

When the work is already scoped and agreed, you or your Kowalah partner can add a deliverable straight to a project.
When a deliverable is promoted from an Opportunity, it carries a back-link to the source so you can always trace where the work came from, what was originally proposed, and how it scored.

​
Ownership

Each deliverable has at least one owner, and usually two:
  • Customer owner — someone from your organization accountable for the outcome
  • Kowalah owner (optional) — the Kowalah team member leading delivery
This dual ownership keeps both sides aligned on who’s driving the work and who needs to act next.

​
Creating a deliverable

1

Open a Kowalah-managed project

Deliverables live inside Kowalah-managed projects. From the project page, open the Deliverables tab.
2

Click "New deliverable"

This opens the creation form. If you’re promoting an Opportunity instead, use the Promote action on the Opportunity itself — that pre-fills most of the deliverable for you.
3

Enter the details

Provide a title (required, 5-200 characters). Optionally add:
  • Description explaining the work
  • Stage (defaults to “planning”)
  • Priority (none, low, medium, or high)
  • Department the deliverable relates to
  • Tags for categorization
  • Milestone to associate with (optional)

​
Deliverable details

Each deliverable tracks:

​
Progress tracker

Every deliverable in planning, in progress, or in review has a progress tracker in the sidebar. This gives you an at-a-glance health check.
The progress tracker shows how far along the work is, the health of the deliverable, who needs to act next, and the estimated completion date.
The status owner tells you whose turn it is:
If a deliverable shows “Waiting for your input,” check the discussions tab or ask your Kowalah partner what’s needed. Quick responses keep deliverables moving through stages.

​
Value tracking

  • Expected value — what you anticipate this deliverable will deliver (e.g., “Save 100 hours/month in invoice processing”)
  • Actual value — measured results once the work is done
  • Success criteria — how you’ll know the deliverable succeeded

​
Dates

  • Start date — when work begins
  • Target date — the agreed deadline
  • Estimated completion — the rolling estimate, updated as work progresses
If the deliverable was promoted from an Opportunity, the sidebar shows a Promoted from OPP-XXXX link back to the original Opportunity, including the rationale and the score that triaged it through.

​
ICE score

Every deliverable carries an ICE score — Impact, Confidence, and Ease on a 1 to 10 scale. Two scores are tracked:
  • Estimated score — set when the deliverable is scoped, captures what the team expects to deliver
  • Final score — set at closeout, captures how the work actually landed
The score history on every deliverable shows who scored, when, and why — including any AI-generated first pass. For the full scoring model, see ICE Scoring.

​
Outcomes

When a deliverable lands in the done stage, the realised business results — money saved, hours freed, adoption milestones hit — are captured as Outcomes. Outcomes can be added at closeout or any time afterwards as new evidence materialises, and customer-side stakeholders linked to the deliverable can capture them too.

​
Linking to milestones

Deliverables can be assigned to a project milestone. When linked:
  • The deliverable appears under that milestone in the project view
  • Milestone-level reporting includes the deliverable’s status and health
  • Milestone completion is calculated from the deliverables that roll up to it
Each deliverable can have:
  • Tasks — actionable items for getting the work done
  • Discussions — threaded conversations about the work
  • Stakeholders — people involved (primary, collaborator, or watcher)
  • Resources — links to Expert Requests, Accelerators, documents, or other deliverables

Opportunities

Capture and triage AI ideas before promoting them into deliverables

ICE Scoring

How estimated and final scores work across the platform

Outcomes

Capture the realised results of a delivered piece of work

Projects

The strategic workspaces that group deliverables

Tasks

Actionable items within deliverables

Milestones

Group deliverables under project milestones