# Pilot Scope Sheet
## Seven-Day MCP Service Sprint

Use this operational scope alongside the agreement appropriate to your business. Confirm all bracketed details with the client before work starts.

**Pilot name:** [name]  
**Client:** [client]  
**Service provider:** [name]  
**Version/date:** [version/date]

## Outcome

The pilot will produce **[quantity and format]** for **[one task/project]**, using **[approved sources]**, so **[reviewer]** can **[intended use]**.

**Fictional example:** One draft Friday project-review brief for Project Alpha, using the approved project folder, so the studio owner can review milestones, missing inputs and decisions.

## Included work

1. Review the approved input collection and confirm the reporting period.
2. Configure or run the agreed workflow for the single pilot task.
3. Prepare [deliverable and required sections].
4. Check the result against [acceptance criteria].
5. Complete [number] revision round(s) addressing the agreed criteria.
6. Provide the operating instructions, worked example and test record.

## Client responsibilities

- Provide the approved source collection by [date].
- Authorize the specific access required through the supported account process.
- Identify the authoritative source when information conflicts.
- Make [reviewer] available during [review window].
- Return consolidated feedback by [date].

## Boundaries

This pilot does not include [additional projects, ongoing maintenance, external sending, publishing, transactions or record changes]. New requests will be described and agreed before work expands.

**Fictional example:** The studio pilot prepares a draft only. It does not send client messages, change due dates, update budgets or add other projects.

## Acceptance

The reviewer checks:

- [ ] [Required section/field is present].
- [ ] [Every factual status has a source or is marked unknown].
- [ ] [Conflicting information is flagged].
- [ ] [Required owners and dates are included].
- [ ] [No action outside the agreed scope occurred].

**Acceptance method:** [written response/checklist]  
**Reviewer:** [name]  
**Review window:** [duration]

## Timing and dependencies

**Start:** [date, after prerequisites are met]  
**Draft delivery:** [date]  
**Revision delivery:** [date or interval]  
**Handoff:** [date]

If an input, authorization or review is delayed, the parties will agree a revised delivery date. If the integration is unavailable, use [manual fallback] or pause for [owner’s decision].

## Commercial and access details

**Price and payment terms:** [agreed terms]  
**Direct costs included/excluded:** [details]  
**Support period:** [scope/duration]  
**Access at completion:** [remove or retain under a separate agreement]  
**Future maintenance owner:** [person]

**Scope confirmed by:** [client/provider and date]
