Delivery

Delivery is the cross-company worklist: every active Project and Cycle, every client, sorted by urgency. It's the answer to "what's owed and slipping right now, across all my clients?"

Work that's close to the deadline or untouched floats to the top — mirroring exactly what the Monitor is watching.

Projects

A Project is a one-off engagement with a defined end. It's created automatically when you close a Project-type deal as Won, or you can create one manually for internal work.

A Project has:

• A title, status, start date, and deadline
• A set of Tasks (the actual work)
• A link to a Company (or marked Internal if there's no client)
• Quoted hours, if you've agreed a scope

Projects end when all tasks are complete and the work is delivered.

Cycles

A Cycle is a recurring unit of work inside a retainer engagement. A new Cycle is created automatically at the start of each billing period (monthly, quarterly, etc.) with your standard task template pre-loaded. Any incomplete tasks from the previous Cycle are carried forward automatically.

Each Cycle carries a Label — the service it belongs to (e.g. "SEO", "Content Marketing"). If a client is on multiple services, each runs as a separate, labelled Cycle under the same Company.

A Cycle closes when either:

• All tasks are complete and a delivery document has been sent to the client
• All tasks are complete with no client-facing deliverable needed

Closing a Cycle doesn't end the retainer — the next Cycle begins on schedule regardless.

Tasks

Tasks are the atomic units of work inside a Project or Cycle. Each Task has:

• A title, status, priority, and dates
• An Assignee (a team member or Automation)
• Optional estimated hours — drives the workload view
• A Timeline — a timeline of status changes, comments, and decisions

Task statuses

Tasks flow through five columns on the board:

Status	Meaning
Backlog	Captured but not yet started — the current sprint's not committed to it
Todo	Picked up and waiting to begin
In Progress	Actively being worked
Review	Done but awaiting review or sign-off
Done	Complete

Tasks can also carry a Blocked flag — orthogonal to status — so a task stays where it is in the workflow while everyone can see it's stuck.

Dependencies

Tasks can depend on other tasks. Set a dependency ("blocked by another task") and dpaperwork tracks the chain for you:

• A task that's waiting on others shows Blocked by N on its card and in its detail view
• The full chain — what blocks this task, and what it blocks in turn — is visible and editable from the task's right rail
• Dependencies feed the at-risk logic: an overdue blocker makes its dependents at risk too

The Kanban board

Opening a Project or Cycle shows a Kanban board — tasks organised in columns by status (Backlog / Todo / In Progress / Review / Done). You can move tasks between columns to update their status, or click into a task to see its full detail view.

Projects and Cycles themselves do not have a Timeline — all comments, updates, and decisions live at the Task level (and on the Company Hub for the client as a whole).

Task detail

Clicking a task opens its dedicated page, showing:

• Title, status, assignee, and dates (all editable inline)
• Priority and estimated hours
• A description field for context or instructions
• Sub-tasks — break a task into smaller checklist items, each with its own completion state. Sub-tasks aren't independently assignable; they roll up under the parent task.
• The Timeline below — a live timeline of status transitions (auto-logged), manual updates, and decisions logged by team members

Decisions on a task

The Timeline composer has two modes: Note and Decision. Posting a decision marks it with a Decision badge — optionally assigned to an owner and a due date. If a decision implies a follow-up task, dpaperwork creates it on the spot and links it to the decision. Decisions recorded here also feed the Company Knowledge Decisions layer.

Labels, search, and shortcuts

• Managed Labels — beyond the Cycle-level service Label, individual tasks can carry Workspace-managed Labels (e.g. "blocked", "needs review") for finer filtering across a Project or Cycle.
• Search and filter — use the search bar on a Kanban board to find tasks by title, or filter by assignee, Label, or status.
• Board keyboard shortcuts — with a task selected, use keyboard shortcuts to move it between columns or assign it without reaching for the mouse. Press ? on a board to see the current shortcut list.

Capacity and workload

Tasks carry an optional estimated hours figure. dpaperwork sums these for the work due this week to build a per-person workload:

• The Workload strip at the top of Delivery shows each person's open task count, overdue count, and weekly hours, flagging anyone over threshold
• The same numbers power the Team workload card on Home
• The weekly threshold (default 40 hours) is configurable in Settings → Monitor

If someone is consistently over their threshold, that's a signal to redistribute work before it slips.

Urgency sorting

Delivery surfaces the most critical work at the top:

• Cycles entering their final 5 days with incomplete tasks
• Projects with all tasks overdue
• Cycles that have been untouched for the first 7 days

Internal work (no client) is grouped at the bottom under Internal.

Try it in a walkthrough

Walkthroughs follow one job end to end, in real Chat exchanges:

• Kick off delivery
• Run a retainer