# Builder Brief Worksheet

Use this one-page brief before asking a developer, designer, contractor, consultant, or AI coding tool to build. The goal is shared understanding, not polished wording.

## Product Snapshot

- Product or feature:
- Date:
- Owner:
- Version:
- Intended setting:
- Primary user:
- Secondary users:

## Core Workflow

Write the first workflow in plain language.

1. What starts the workflow?
2. What does the user see first?
3. What information is captured?
4. What information is shown back to the user?
5. What decision or action should happen next?
6. What proves the workflow is complete?

## Data Path

| Data or event | Source | Sent to | Stored where | Shown to | Needs audit trail? |
| --- | --- | --- | --- | --- | --- |
|  |  |  |  |  |  |

## System Pieces

- User interface:
- Backend or server:
- API endpoints:
- Database:
- Device or sensor:
- External system:
- Notifications or alerts:
- Dashboard, report, or export:

## Failure Behavior

Describe what should happen if something goes wrong.

| Failure | User-facing behavior | Owner | Recovery step |
| --- | --- | --- | --- |
| Internet unavailable |  |  |  |
| Data missing or late |  |  |  |
| Device unavailable |  |  |  |
| User lacks permission |  |  |  |
| Software error |  |  |  |

## Builder Deliverables

- [ ] Screen flow
- [ ] Architecture sketch
- [ ] API contract
- [ ] Data model
- [ ] Test plan
- [ ] Deployment plan
- [ ] Risk list

## Open Questions

| Question | Owner | Needed by | Decision or evidence needed |
| --- | --- | --- | --- |
|  |  |  |  |