---
template: client-brief/1
id: CB-NNN            # CB-NNN or CB- plus the request id the form gave (CB-20261121-101500-ab12cd); never reused
title: Client brief — [short name of the request]
status: received      # received | digested | estimated | decided — the lead moves it on; `decided` means the owner has recorded G0
version: 0.1.0        # version of this brief; the client's own words (section 1) never change, the digest does
received: YYYY-MM-DD
source: [web form /start/ | email | call | introduction]
---

# Client brief — [short name of the request]

<!-- Template from the UASK Engineering Hub, playbook mgmt.project-foundation, stage 1 Intake.
     Save as intake/CB-NNN.md (or briefs/) in the project's own private repository or folder, never in the public Hub:
     section 1 holds a person's name, email and company. Section 1 is the request exactly as the client gave it: copy,
     do not edit, do not correct. Sections 2 to 5 are the lead's digest; replace every [bracketed] value. A section that
     does not apply says "none" and stays. When the brief leaves the project, remove names, contacts and other details.
     The client never talks to agents: the questions of section 4 go to the owner, who sends them (mgmt.roles-and-decision-rights). -->

## 1. The request as given

<!-- One row per field of the web form at /start/ (handler site/public/start/submit.php). The names in the first column
     are the form's own, so a brief that arrives by mail or by phone is written into the same rows. A field left empty is
     "—". Consent is required by the form: without it there is no brief to keep. Name, Email and "What they need" are the
     form's required fields. The checker does not require every row: a brief that arrives by mail or by phone may lack some,
     and a missing row is a gap to ask about in section 4, not a reason to guess. -->

| Form field | Name | What the client wrote |
|---|---|---|
| Name | `name` | [name] |
| Email | `email` | [email address to answer] |
| Company | `company` | [company, or —] |
| Phone or messenger | `contact` | [a faster channel, or —] |
| What they need | `needs` | [one or more of: Online shop · Custom solution · Hosting · Support of an existing site · Promotion · Not sure yet] |
| Current site | `site` | [address, or —] |
| Content | `content` | [Ready · Partly ready · Help needed · Not sure, or —] |
| Deadline | `deadline` | [As soon as possible · Within 1 month · 1–3 months · 3–6 months · No fixed date, or —] |
| Budget (GBP) | `budget` | [Under £2,000 · £2,000–£5,000 · £5,000–£10,000 · £10,000–£25,000 · Over £25,000 · Not sure yet, or —] |
| How they heard of us | `heard` | [text, or —] |
| Consent | `consent` | [given with the form, on the received date; the data note's version date as the handler prints it] |

**Goals and what success looks like** (`goals`):

[the client's text, or —]

**Audience** (`audience`):

[the client's text, or —]

**Must-have features and integrations** (`features`):

[the client's text, or —]

**Anything else** (`more`):

[the client's text, or —]

## 2. Problem

<!-- One paragraph in the lead's own words: who has what problem, what they want to be true afterwards, and what is
     already there. No solution yet. If the request does not allow a paragraph, say what is missing and put it in section 4. -->

[Who, what problem, what outcome, what exists.]

## 3. Proposed service and tier

<!-- The service is one of the five on the home page (Online shop, Custom solution, Hosting, Support of an existing site,
     Promotion), or "none: decline" with the reason. The tier is a proposal only: the owner decides it at G0
     (mgmt.governance-tiers R2); when two seem to fit, take the higher. Name the criteria applied: who is harmed if it
     fails, whether there are payments or personal data, whether it is live. -->

- Service: [service]
- Proposed tier: [lightweight | standard | high-assurance]
- Why this tier: [criteria applied, one or two sentences]
- Not clear yet: [what could change the service or the tier, or none]

## 4. Questions to the client

<!-- Only questions whose answer would change the service, the tier or the appetite. Each has a default that applies if
     the client does not answer, so work is not blocked. The owner sends them and brings the answers back. -->

| # | Question | Why it matters | Default if unanswered | Asked on | Answer |
|---|---|---|---|---|---|
| 1 | [question] | [what it changes] | [assumption] | [date, or not yet] | [the client's answer, or open] |

## 5. First appetite

<!-- The time the owner would give this, in agent-days (one agent-day is one working day of one agent session), with its basis:
     the closest past case and how this one differs, and what was counted. The appetite is a first guess made
     from the request alone; the owner sets the real one at G0. What is left out if it is reached is one line. -->

- Appetite: [n] agent-days
- Basis: [closest past case or cases and what was counted; for example "similar shop, 9 agent-days, one more integration"]
- Left out if the appetite is reached: [what goes first]
- Range of doubt: [the lowest and the highest figure that would not surprise the lead, and what separates them]

## G0 record

<!-- Optional. Written when the owner decides at gate G0 (mgmt.project-foundation, stage 1; process.project-lifecycle R4).
     Copy the owner's decision in the owner's own words and say where the full record lives (issue, run record).
     An example brief or record that leaves the project is synthetic or from a UK project, with no client data. -->

- Decision: [go | no-go]
- Appetite and tier set by the owner: [n agent-days; tier]
- Owner's words: [verbatim]
- Recorded on: [date, and where]
