---
name: "playbook-client-onboard"
type: playbook
description: The prescribed sequence for opening a new A1 client engagement — create the client project under the A1 team, frame the engagement (advisory-led by default), scaffold the per-client decision log, set up the phase/milestone structure, and file the first validation ticket. Read and follow this whenever an A1 engagement starts, so the scaffold is repeatable instead of re-derived by hand each time (a1.Muse, a1.Heroes, a1.MeirionPritchard, a1.firmup were each done ad hoc). Composes convention-linear, convention-decision-log and convention-ticket; sits on the a1.OS shelf beside playbook.website-build and standard.proposal. Proposed first draft — confirm shape before adoption.
license: CC BY-NC-SA 4.0
status: proposed
---

# Client onboarding (A1)

The repeatable scaffold for standing up a new A1 client engagement. Standing one up — project, decision log, phase structure, first ticket — has been done operator-directed, step by step, for every client so far; this playbook fixes the sequence so the next one is followed, not re-derived. It is **read and followed, not run**: it composes existing conventions and is mostly operator-directed, automating only the parts that already have a workflow. Owned on the a1.OS shelf, beside `playbook.website-build` and `standard.proposal`.

## When to use

A new A1 client engagement is starting — a signed or committed piece of consultancy work that needs its own home, log, and plan. Not for a lead or a pitch (those live as opportunities in Pipeline / Pitches and graduate here only once the engagement is real).

## The sequence

Follow in order; each step names the convention that governs it.

### 1. Create the client project (A1 team)

Per `convention-linear`: one **project per client engagement** under the **A1 team**, named `a1.<Client>` (e.g. `a1.firmup`). Link it to the **A1 initiative**, set the lead to **Aled**. A1 standards and playbooks stay in `a1.OS`; only the engagement's delivery work goes in the client project.

### 2. Frame the engagement

State the engagement's shape in the project description: the mode (**advisory-led by default**, unless the work is a defined build or a fixed deliverable), the objective, and the success measure. Keep it to a few lines — the detail lives in tickets and the decision log. Where the commercial frame matters, point to `standard.proposal`.

### 3. Scaffold the decision log

Per `convention-decision-log`: create the per-client log `a1-<client>.log-decisions` (hyphenated `a1-` prefix, then the project name), with the index doc and the first weekly child doc `a1-<client>.log-decisions.YYYY-Www`. Log the engagement's framing decision (mode, objective) as the first entry, so the basis is recorded from day one.

### 4. Set up the phase/milestone structure

Per `convention-ticket` (*Structure*): model the engagement's **sequential, gated delivery phases as project milestones, not epics** — milestones carry the time order; `type:epic` is reserved for a genuine body of work *within* a phase. Lay the phases out as milestones up front so promotion-to-ready has a spine to hang on, and avoid the create-then-convert churn of modelling phases as epics first. **Give each milestone a target date at project setup** — the phases are a dated spine, not merely an order — so the engagement schedule is legible from the board and due dates inherit **milestone → leaf** (a refined leaf takes its milestone's date unless it carries an earlier one). (`convention-ticket` *Structure*; APP-625.)

**Lay a review-and-revisions milestone on the spine, and state where included work ends.** The spine above carries the delivery order; it does not say how much reviewing and revising the fee covers, so every change after sign-off arrives as goodwill and the engagement absorbs it. Add one **`Reviews and revisions`** milestone at setup, between the main delivery milestone and go-live, and put two things in its description. First, **the number of included review rounds** — state the figure explicitly; this playbook does not pick it, it is a commercial choice per engagement, and an unstated figure is the whole defect. Second, **the line past which a new request is scoped work**: once the included rounds are exhausted, or a request changes agreed scope rather than correcting against it, it is quoted and invoiced as its own piece of work before anything is built, never folded into the current phase. Open a chargeable-change gate leaf beside the milestone in the gate shape step 5 uses, so the boundary is on the board rather than remembered. Where the engagement is advisory-led rather than a defined build, say so and name the review cadence in place of a round count. (Owner directive, 2026-10-19. On the Meirion engagement nothing in the structure marked where included review rounds ended and chargeable change began; the sign-off gate moved four times and the *Launch* milestone ran well over. APP-2421 — the slip dates, the payment position and the D135 log entry are **reported**, not read by this pass.)

### 5. File the first validation ticket

Open the first **leaf ticket** in the client project, in the standard ticket shape (`convention-ticket`): a small, concrete first step that validates the engagement is moving — typically a discovery or framing-confirmation task. Capture it (Backlog), not ready; Aled promotes it. This gives the engagement an actionable starting point rather than an empty board.

**Scaffold the engagement's client-dependency gate at the same time.** Every engagement has something only the client can supply — sign-off, content, access, a decision — and the board cannot tell that apart from unscheduled work unless it is structural. Open one gate leaf per known client dependency in the standard shape (`convention-ticket`, *Obligations belong in structure, not prose*): named conditions, a `blocks` relation onto the tickets it holds, and a due date as the review prompt. Where no dependency is known yet, say so in the framing decision rather than leaving the question unasked — the gate is cheap to open later and expensive to discover through a month of escalation (APP-1443).

**Scaffold the engagement's client-facing delivery log at the same time, and name what happens each time something ships.** The decision log in step 3 records *why*; it does not record *what the client has been given*. Create the engagement's delivery log at setup — one row per deliverable, numbered `D-nn`, with what was sent, to whom, and the date — and state the standing obligation beside it: **a deliverable that goes to the client gets its log row and its ticket of record as part of sending it, in the same session that sends it.** The ticket half is already governed (`convention-ticket`, *work begun without a ticket gets one*); the row is what that rule does not cover, because the log is client-facing and sits outside Linear. Both are cheap at send and expensive later: a chat session doing client work loads no skill that owns the send step, so without this the log and the ticket depend on someone remembering, and the gap surfaces only when the Owner checks ahead of a client call. (Worked case: a1.Muse, 2026-10-06 — D-02 and D-03 had shipped on 05.10 with the log stopped at D-01 and no ticket for any of the four deliverables; all backfilled the same day. APP-2119.)

## Guardrails

- **Real engagement only.** Scaffold when the work is committed; a lead or pitch stays in Pipeline until it graduates.
- **Capture, don't promote.** The first ticket lands captured (Backlog); Aled moves it to ready. Never advance on his behalf (`convention-ticket`).
- **Compose, don't duplicate.** This playbook points at `convention-linear`, `convention-decision-log` and `convention-ticket` for the mechanics; it does not restate their rules. If one of them changes, this still holds.
- **Advisory-led is the default frame, not the only one.** Name the mode explicitly when it differs, and log the choice.
- **Proposed.** This is a first draft assembled from the way the last four engagements were stood up; confirm the sequence and the a1.OS placement before treating it as adopted.

## Tone

Calm, precise, sentence case, British spelling, no exclamation marks, outcome before adjective. (cos.tov.)
