# Scope & estimate worksheet

Project: [name] · Decision owner: [name] · Version/date: [reference]

## Outcome and boundary

Visitor/task: [who needs to do what]
Observed problem: [evidence reference]
Desired behavior: [testable change]
In scope: [files/routes/states/deliverables]
Excluded: [related work that is not approved]

## Dependencies before estimating

| Dependency | Owner | Evidence/decision required | Ready? |
|---|---|---|---|
| Intended business flow | [name] | [approved description] | No / Yes |
| Content/asset rights | [name] | [source and permission] | No / Yes |
| Access/test environment | [name] | [authorized route, no shared secrets] | No / Yes |
| Release/rollback authority | [name] | [exact approval] | No / Yes |

## Work breakdown

| Work unit | Assumptions | Low effort | High effort | Owner | Acceptance evidence |
|---|---|---|---|---|---|
| Reproduce / diagnose | [known vs unknown] | [hours] | [hours] | [name] | [trace] |
| Implement | [bounded change] | [hours] | [hours] | [name] | [diff] |
| Verify / review | [devices and states] | [hours] | [hours] | [name] | [test result] |
| Release / handoff | [approval and deployment path] | [hours] | [hours] | [name] | [receipt] |

Agree estimates and commercial terms with the client. Do not treat this blank worksheet as a quote or invent a rate. Record external costs separately and obtain approval before using paid services.

## Uncertainty and change control

What could change the estimate: [unknowns]
Smallest investigation to resolve them: [bounded test]
Stop/re-scope trigger: [specific evidence]
New request: [description]
Effect on scope/timing/price: [owner-approved revision]
Approval record: [person/date/exact wording]

## Worked example boundary

For fictional JCR-04, start with label/explanation changes after workflow confirmation. A new scheduling system is a different scope. No implementation hours or revenue gains are asserted by the example.
