Project · Delivery Units
Route /project/deliverables/:projectId Menu Project → Deliverables

Deliverables

Manage project deliverables (tasks) before drilling into granular work items.

Deliverable register for a project with status tracking, assignment, and estimate comparisons.

Delivery units

Tasks on a project — before the finer work items

Deliverables are project tasks: the delivery units you manage before drilling into granular work items. In Tracopus, deliverable means Task unless a separate Deliverable model exists — it does not.

Projects → project → deliverables Route /project/deliverables/:projectId Project Manager · Contributor

The job of this console

Create and sequence tasks, assign, then drill into work items for hours and micro-status. Do not invent a parallel ‘deliverable’ spreadsheet.

Seat at the table

The project team. Resource managers care about assignment load on capacity, not this list alone.

The working rhythm

Open a project’s deliverables, add or edit a task, then open work items or the board. Timesheet rows should point at this work.

Moments that bring you here

Scope breakdown. A missed task blocking a milestone. After a PO change. When someone says WBS — start here.

ⓘ
Deliverable = Task
Naming in UI may say deliverable; the source is Task. Work items are TaskActivity.

Overview

Deliverables sit between projects and work items in the hierarchy. They define accountable outputs and timeline checkpoints.

Screen layout

Header: Create deliverable, filters, sort, search.
Body: Deliverable list with owners, status, dates, estimates.
Actions: Open detail or work items for execution tracking.

Header & filters

Common controls include status chips and text filter. Exact controls depend on project configuration and role permissions.

Summary & charts

Summary section may include status and estimate-vs-actual indicators for the current project's deliverables.

Main content & actions

Open a deliverable to manage checklist, comments, and downstream work items.

Complete feature list

Every control, panel, and workflow on this screen.

  • ✓
    Luxury UI shellEmerald-themed glass cards, sticky gradient header, module sidebar, and responsive layout.
  • ✓
    Documentation searchHeader search indexes all guide pages (docs site).
  • ✓
    Collapsible summary stripKPI row and chart gallery above the register; expand/collapse persists in browser storage.
  • ✓
    Deliverable registerHierarchy list with status and dates.
  • ✓
    CREATE deliverableAdd milestone or work package.
  • ✓
    SHOW / SORT / FilterStatus and text search.
  • ✓
    Summary chartsStatus mix and timeline health donuts.

Before you start

💡
Estimate workshop
Block 30 minutes after project kickoff to fill all deliverable estimates.
ℹ️
Timeline health
Donut due-soon slice — sort register by date to action top five.

Who uses this screen

Project managers and delivery leads tracking milestones and work packages — status, dates, estimates, and summary analytics across one or all projects.

ℹ️
Milestone register
Use with Est vs Actual reports — every deliverable should have hour estimates before work starts.

Key concepts

Deliverable register

Hierarchy list with status, due dates, assignee, estimate hours.

CREATE deliverable

Add milestone linked to parent project.

Summary charts

Status mix and timeline health donuts in strip.

SHOW / SORT / Filter

Status presets and text search on title.

Est vs actual context

Estimates here compare to timesheet actuals on reports.

Permissions

RoleAccess on this screen
Project managerCreate/edit all deliverables in scope.
Delivery leadEdit assigned deliverables; create sub-packages.
Team memberView; update status on assigned items.
FinanceRead-only estimates for planning exports.
📝
Administrator override
Org administrators and service accounts configured in the Admin console may bypass row-level scopes shown above. When in doubt, confirm access with your Tracopus administrator.

Controls reference

ControlDescriptionNotes
CREATE deliverableNew milestone form.Requires project link.
SHOW / SORT / FilterStatus and search.Standard Lux header.
Summary stripStatus and timeline donuts.Respects filters.
Row clickOpen deliverable-details.Work items tab inside.
Project filterScope to one project.From header or pre-nav.
ExportDeliverable list download.Report input.
Bulk statusMulti-select if enabled.PM role.

Common mistakes

⚠️
Zero estimate on deliverable
Est vs Actual report shows 100% variance — set estimate at create.
⚠️
Flat list ignoring hierarchy
Parent/child structure affects rollup — use tree view when available.
⚠️
Past due without status update
Timeline health chart lies — mark blocked or extend date.

FAQ

Deliverable vs work item?

Deliverable = milestone; work item = task/activity executing the work.

Can one deliverable span projects?

No — each belongs to one project; link related items via notes.

How do actual hours arrive?

Timesheet entries tagged to deliverable on billable rows.

Default statuses?

Org-configured — typical: not started, in progress, complete.

Workflows

  1. Create or open deliverable.
  2. Assign owner and due dates.
  3. Track status changes and estimate variance.
  4. Open Work Items for detailed execution.

Tips & best practices

Tip: Keep deliverable estimates updated — downstream utilization and planner analytics depend on them.

More guidance

💡
Remember
Hierarchy list with status, due dates, assignee, estimate hours.
ℹ️
Deliverable vs work item?
Deliverable = milestone; work item = task/activity executing the work.