# Client Workflow Intake
## Seven-Day MCP Service Sprint

Complete this with the task owner before proposing access or implementation. Use one task and one source collection for the first pilot.

**Client:** [client]  
**Task owner:** [name/role]  
**Reviewer:** [name/role]  
**Intake date:** [date]

## Understand the last real example

Ask: “Could you walk me through the last time you completed this task, from the request to the final result?”

Record:

- **Trigger:** [what starts the task].
- **Frequency:** [how often it happens].
- **Current sequence:** [steps in order].
- **Current output:** [format and example].
- **Current effort:** [observed or reported time; identify which].
- **Common corrections:** [what the reviewer usually changes].
- **Consequence of error:** [what could go wrong].

## Define the requested result

**One-sentence outcome:** [result the client wants]  
**Required sections or fields:** [list]  
**Reporting period:** [date/range]  
**How the reviewer will accept it:** [observable checks]

**Fictional example:** One Friday review brief for Project Alpha, containing milestones, missing inputs, decisions, owners and source links. Every status must be sourced or marked unknown; conflicting dates must remain visible.

## Map the source and access

| Source collection | Owner | Approved use | Freshness rule | Access method |
| --- | --- | --- | --- | --- |
| [Name] | [Person] | [Specific task] | [Date/version] | [Client-authorized method] |

**Information excluded from the pilot:** [records or fields]  
**Who authorizes access:** [person]  
**Who can resolve conflicting facts:** [person]  
**Access end date or review point:** [date/event]

Do not place passwords, tokens or private credentials in this document. Use the service’s supported authorization process.

## Confirm practical constraints

- Client tools/accounts available: [list].
- Required format or brand rules: [details].
- Delivery channel: [agreed channel].
- Review availability: [dates and response window].
- Manual fallback: [how the task can be completed if the connection fails].
- Actions requiring a separate agreement: [sending, publishing, changing records or expanding scope].

## Next step

**Sample to prepare:** [artifact using approved or fictional material]  
**Material approved for that sample:** [sources]  
**Review date:** [date]  
**Owner of each next action:** [person/action]

### Confirmation note

“I understand the first pilot as [task] using [source] to produce [output] for [reviewer]. The first sample will use [material]. Before connecting a live source, we will agree the scope, access and acceptance criteria.”
