dpaperwork

Solution · Delivery

Hear about the slip before the client does

You run client work across a dozen projects and a few retainers. Each lives in its own board, so the only way to know what is late is to open every one. By then the client has usually noticed first.

Work slips at the edges, not in the middle

The task nobody touched for a week. The project that is three tasks from done and quiet. The retainer cycle that closes tomorrow with work still open. None of it is hidden. It is spread across boards, and nobody's job is to read all of them. dpaperwork reads all of them, every day, and puts the one about to slip at the top.

It does the legwork. You make the call.

Nothing reaches a client without your yes, and every draft shows what it changed.

1 · Notices

Northwind retainer: October cycle ends tomorrow, 2 tasks still open

Spotted by the Monitor, without you looking.

2 · Drafts

Drafted the next cycle with the 2 open tasks carried over, and a short status note for the client.

Grounded in the record’s real history.

3 · You decide

Approve, edit, or skip

ApproveEditSkip

4 · Done

Sent from your own address

Sent

One list, sorted by what needs you first

Delivery merges every in-flight project, retainer cycle and task across every client into a single worklist. Work in its final stretch, or not yet started, floats to the top. Internal work with no client sits in its own section instead of disappearing.

Sorted by urgency

The late and the untouched come first, the way a program manager would triage them.

Dependencies visible

Mark a task as blocking or blocked, and the chain shows before it causes a slip.

Retainers renew themselves

A new cycle generates each billing period from a task template, plus anything left over.

Same week, different ending

You open six boards on Friday to find out what is late.

One list. The late one is first, with the client attached.

A retainer cycle ends and the next one is set up from memory.

The next cycle is drafted from the template, with open tasks carried over.

Overload shows up as a missed deadline.

A heavy task load is flagged while you can still move work.

What’s doing the work

Every in-flight project, cycle and task across every client, merged into one worklist
Final-stretch and untouched work floats to the top, using the same signals the Monitor watches
Internal work with no client is grouped under its own section, not hidden
Each new cycle starts from a per-label task template plus anything carried over incomplete
A cycle closes when its tasks are done, with or without a client-facing delivery document
When one person’s task load crosses a threshold, the worklist flags it

Questions

Leave the call with your first follow-up drafted.

Every project in one list, and the next step drafted for your approval.

See pricing