Track delivery

The Delivery view connects your project's measurable outcomes, working agreements, quality evidence, and release decisions in one place.

Before you start

• All project members can view the Delivery page.
• To create goals, add artifacts, or manage releases, you need a Member role or higher.
• Quality gates are defined by your methodology. Scrum projects have more quality gate checks than Basic projects by default.

Steps

View the delivery summary

1. Open your project and click Delivery in the project sidebar.
2. The summary row at the top shows four tiles: Active goals (with a count of goals achieved), Artifacts (approved and current), Policy checks (evidence still required), and Release readiness (whether the project is ready to release).

Create an outcome goal

1. Click the Goals tab (the first tab in the Delivery view).
2. If no goals exist, you see the message "No goals yet." with a Create goal form on the right side of the page.
3. Fill in the following fields in the Create goal panel:
   • Goal — the goal title or outcome question.
   • Description — Markdown supported.
   • Measure — the metric you will track (for example, "Median days").
   • Target — the target value (for example, "2 days").
   • Target date — an optional date by which to achieve the goal.
4. Click Add goal to save.

Manage artifacts

1. Click the Artifacts tab to see working agreements and deliverable artifacts.
2. In the Create artifact panel on the right, fill in:
   • Artifact type — select the type from the dropdown (types are defined by your methodology).
   • Title — a short name for the artifact.
   • Summary — Markdown supported; state the agreement, evidence, or decision.
   • Linked goal — optionally link the artifact to an outcome goal.
3. Click Add artifact to save.

Review quality gates

1. Click the Quality gates tab to see the policy checks your methodology requires. Each gate shows whether evidence has been provided.

Manage releases

1. Click the Releases tab to see release records and their readiness status. The summary tile shows "Not ready" until all readiness gates are satisfied.
2. In the Plan release panel on the right, fill in:
   • Release name — a short identifier (for example, "2026.06 Platform").
   • Target date — the planned release date.
   • Release notes — Markdown supported; include scope, rollout, and rollback context.
3. Click Create release to save. Once created, use Mark ready on the release row when all readiness gates are satisfied, and then Release to mark it shipped.

Result

Your project has documented outcome goals with measurable targets, artifacts are tracked against approval status, quality gates show evidence gaps, and the release readiness tile updates as gates are cleared.