> ## Documentation Index
> Fetch the complete documentation index at: https://docs.kowalah.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Deliverables

> Track committed AI work through planning, in progress, in review, and done inside your Kowalah-managed projects.

export const DeliverableDefinition = () => <>
    A <strong>Deliverable</strong> is committed work inside a Kowalah-managed project. Each deliverable moves through four stages, planning, in progress, in review, and done, with on hold and cancelled available outside the main flow. Deliverables typically arrive by promoting an Opportunity, and they carry a back-link to the Opportunity they came from for full traceability.
  </>;

<DeliverableDefinition />

Deliverables represent the work Kowalah is actively building or running for you inside a project. Most deliverables arrive by promoting an [Opportunity](/platform/opportunities) once it has been triaged, but you and your Kowalah partner can also create one directly when the work is already scoped.

<Note>
  Deliverables only exist inside **Kowalah-managed projects** — projects where Kowalah is delivering work alongside you. Customer-managed (private) projects use tasks and milestones instead.
</Note>

## Stages

Every deliverable moves through four main stages, displayed as a kanban board on the project page:

| Stage           | What it means                                                              |
| --------------- | -------------------------------------------------------------------------- |
| **Planning**    | The deliverable is scoped and ready to start, but active work hasn't begun |
| **In progress** | Kowalah is actively building or running the work                           |
| **In review**   | Work is complete and waiting for your team to review or accept             |
| **Done**        | The deliverable has been accepted and is delivering value                  |

Two additional statuses sit outside the main flow:

| Status        | What it means                               |
| ------------- | ------------------------------------------- |
| **On hold**   | Temporarily paused, may resume later        |
| **Cancelled** | No longer being pursued, kept for reference |

<Tip>
  The earlier "idea" stage is now captured as an [Opportunity](/platform/opportunities) instead of an early-stage deliverable. This keeps the deliverables board focused on committed work.
</Tip>

## Where deliverables come from

<CardGroup cols={2}>
  <Card title="Promoted from an Opportunity" icon="arrow-up-right" href="/platform/opportunities">
    The most common path. An idea is captured and triaged as an Opportunity, then promoted into a deliverable inside the right project.
  </Card>

  <Card title="Created directly" icon="plus" href="#creating-a-deliverable">
    When the work is already scoped and agreed, you or your Kowalah partner can add a deliverable straight to a project.
  </Card>
</CardGroup>

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

<Steps>
  <Step title="Open a Kowalah-managed project">
    Deliverables live inside Kowalah-managed projects. From the project page, open the **Deliverables** tab.
  </Step>

  <Step title="Click &#x22;New deliverable&#x22;">
    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.
  </Step>

  <Step title="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)
  </Step>
</Steps>

## 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.

<Info>
  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.
</Info>

| Field                    | What it shows                              |
| ------------------------ | ------------------------------------------ |
| **Progress percentage**  | A visual gauge showing completion (0-100%) |
| **Health status**        | On track, some risk, or concerned          |
| **Status owner**         | Who needs to act next                      |
| **Estimated completion** | When the deliverable is expected to finish |

The **status owner** tells you whose turn it is:

| Status                     | What it means                                    |
| -------------------------- | ------------------------------------------------ |
| **Kowalah working**        | The Kowalah team is actively building            |
| **Waiting for your input** | Kowalah needs a decision or information from you |
| **Customer action needed** | Something for your team to do                    |
| **Blocked externally**     | Waiting on a third party                         |
| **Under review**           | Being evaluated or reviewed                      |

<Tip>
  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.
</Tip>

### 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

### Source link

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](/platform/scoring) — 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](/platform/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](/platform/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

## Related features

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

<CardGroup cols={2}>
  <Card title="Opportunities" icon="lightbulb" href="/platform/opportunities">
    Capture and triage AI ideas before promoting them into deliverables
  </Card>

  <Card title="ICE Scoring" icon="gauge" href="/platform/scoring">
    How estimated and final scores work across the platform
  </Card>

  <Card title="Outcomes" icon="trophy" href="/platform/outcomes">
    Capture the realised results of a delivered piece of work
  </Card>

  <Card title="Projects" icon="folder-open" href="/platform/projects/overview">
    The strategic workspaces that group deliverables
  </Card>

  <Card title="Tasks" icon="square-check-big" href="/platform/tasks">
    Actionable items within deliverables
  </Card>

  <Card title="Milestones" icon="flag" href="/platform/projects/milestones">
    Group deliverables under project milestones
  </Card>
</CardGroup>