Retainer delivery digest

On the schedule you choose, the agent pulls delivered work and hours, compares them to the retainer scope, computes utilization, flags over- or under-delivery and scope creep, self-critiques the draft, and lands a digest for you to approve.

Saves you ~1.7 h / week

How it works

Trigger
On the “Retainer digest” schedule.
Job
Pull and reconcile delivery against scope, compute utilization, draft the digest.
Outcome
A reconciled client delivery and utilization digest.

What it installs

Agents 2

  • Analyst Agent

    The account's delivery analyst — pulls delivered work and hours, reconciles them against the retainer scope, computes utilization, flags deviations, and drafts a digest self-critiqued for accuracy.

  • Retainer delivery digest Quality Reviewer

    Checks primary evidence, domain controls, deliverable completeness, and communication quality, stopping the run when the work is wrong, unsupported, incomplete, or uncertain.

Teams 1

  • Retainer delivery digest quality team

    The delivery agents produce the work while an independent quality reviewer checks each workflow handoff against explicit evidence, domain, and communication requirements before the run can continue.

Workflows 1

  • Reconcile, classify, draft, self-critique, approve

    Pull and reconcile delivery against scope, compute utilization, draft the digest, self-critique it, and hand off for approval.

Documents 1

  • Retainer scope

    What the retainer covers — included deliverables and hours, cadence, out-of-scope triggers, and the over/under-delivery thresholds — so delivery can be measured against a concrete baseline.

Goals 1

  • Retainer scope honored

    Delivery stays aligned with the retainer scope every period, with utilization tracked and over- or under-delivery and scope creep surfaced before they become disputes. Success looks like: Each scheduled run lands an approved digest with sourced utilization, every scope-creep item flagged, and every deviation paired with a dated recommended action.

Skills 2

  • stakeholder-update

    Tailor a delivery update to its reader (account lead vs client), set an honest Green/Yellow/Red status, communicate each deviation with the ROAM framework, and pair every flag with a specific, dated action. Lead with the conclusion; never bury a margin or under-delivery problem. Adapted from anthropics/knowledge-work-plugins/stakeholder-update.

  • weekly-report

    Structure a clear periodic delivery report: a one-line summary, delivered work written as quantified outcomes (not a task log), a utilization/variance table against plan, deviations with impact and a recommended action, and realistic next-period priorities. Adapted from claude-office-skills/skills/weekly-report.

Schedules 1

  • Retainer digest

    Drafts the retainer delivery digest on the schedule you choose. ## Professional quality control Objective: complete the recurring Retainer delivery digest operating cycle and deliver a review-ready, evidence-backed result rather than merely report that the schedule ran. Start by fixing the review period, reading the current source records and prior run, confirming required access, and listing missing or contradictory inputs. Execute the bundle's full authored method in order, retaining source, calculation, command, or before/after evidence for load-bearing findings. Separate facts from interpretation, apply supplied policy without inventing thresholds, and stop any branch that requires missing authority or an unconfirmed human rule. Produce the complete named deliverable plus an evidence record, assumptions, exceptions, unresolved questions, and concrete next actions with owners where the method calls for them. Run the workflow's independent verifier checks and fix failures before requesting approval. The task is done only when every requested section and quality criterion passes or a blocker is explicit; silence, inaccessible data, or polished prose is not proof of completion. Reconcile names, dates, statuses, commitments, figures, and quotations with source material; surface contradictions and omissions. The document must lead with its purpose, preserve the audience's vocabulary, and remove generic AI phrasing, redundant summaries, filler, and polished language that hides missing evidence or ownership. The human retains authority over publication, sending, spend, signing, merging, deployment, and other consequential external actions.

Folders 1

  • Retainer Digest

Requirements

  • Browser access to your project / time tracking — The agent reads the period's delivered work and logged hours from your project tracker and time-tracking tool through their web interface in your browser and pauses for your approval before anything is shared; until you connect them, it works from attached exports of the period's activity and timesheets.

Setup guide

How to Automate Retainer Delivery Digests

A practical guide to reconciling retainer work, hours, scope creep, and client-facing delivery digests with approval.

Read the setup guide

Don't see your workflow? Describe it.

A sentence or two about a recurring job is enough. We design the playbook that runs it and show you exactly what it saves.

* What keeps taking time you don't have? *



Takes a minute · no account needed