# The Pilot Proposal One-Pager (Chapter 16)

**Use when:** you want company funding, installation help, access, or a trial
across a team. The proposal asks for that support. Your ability to learn and
build does not wait for a sponsor's decision.

Name what you need and what the company will get in return. Keep the trial
small enough to evaluate on a date everyone can put in a calendar.

## The one page, fill in every bracket

```
PILOT PROPOSAL
[YOUR NAME], [TEAM], [DATE]

THE SUPPORT REQUESTED
[Subscription or capacity funding, installation, access, or a team trial.
Name the amount, service, or resource, and who would supply it.]

THE TASK
[One task small enough to evaluate in two weeks, with a measurable result.]

THE TOOL AND ACCOUNT
[App, provider, account type, and tier. No passwords or API keys.]

WHAT GOES IN / WHAT STAYS OUT
[Data needed; fields removed; invented rows for rehearsal. Credentials,
secrets, NDA material, privilege, and legal holds stay out under the book's rule.]

THE DATA CHECKS
[Training use; retention and deletion; human review; connected services;
any legal or contractual conditions for the records. Attach the completed
lockdown sheet and Chapter 3 checklist. Payment alone is not a privacy check.]

REVIEW CHECKPOINT
[Date, reviewer, expected benefit, evidence of output quality, and costs.]

STOP PLAN
[How the team trial stops if it fails. Name what reverts and what records
must be retained. No automatic deletion of audit evidence.]

END DATE
[Date the trial ends and company support is reconsidered.]
```

## After the pilot

Log the task in the [audit binder](audit-binder-index.md): the account and data
checks, prompts or descriptions, sources checked, and human sign-off. The sponsor
is deciding whether to commit resources or adopt a shared method. The evidence
makes that decision concrete.