# Plan recurring client delivery without copy-paste drift

Illustrative planning brief; no automatic product import.

Illustrative case: a monthly report package usually follows the same process, but this client needs a new comparison view and a different approval contact.

## Decision

Confirm the current approval route and new view before reusing the delivery sequence.

## Owned work

- Reconfirm the current brief
  - Owner role: Client lead
  - Acceptance evidence: The brief states this period’s deliverables, changed comparison view and agreed approval contact.
- Prepare the bounded package
  - Owner role: Delivery owner
  - Acceptance evidence: The draft follows the current scope and distinguishes the new view from the recurring content.
- Obtain current approval
  - Owner role: Acceptance owner
  - Acceptance evidence: The agreed contact reviews this delivery and records approval or requested corrections.

## Workflow

1. Compare the current brief with the previous delivery before reusing any task outline.
2. Mark client-specific differences and assign their acceptance evidence.
3. After approval, improve reusable steps while keeping client-specific data out of the shared outline.

## Judgment

Do not reuse customer data, commercial terms or approval identities across clients. Examples here contain invented work only.


## Filled illustrative decision

The sample monthly package adds a comparison view and changes the approval contact. The coordinator confirms the new contact before preparing the view and asks that person to accept its comparison boundary. Last month's approval cannot cover the new view or establish the current customer's commitment.


## Workflow questions

### What can safely recur?

The general sequence and evidence expectations can recur. Scope, dates, contacts and confidential inputs need a fresh check.

### How do we prevent template drift?

Separate the reusable outline from each delivery’s brief and record why any local step differs.

## Product connection

Review the current client obligations before adapting a prior task sequence in TeamBoostAI.

Confirm account availability before adopting this manual outline.