# First-release scope worksheet

Blank planning template from Acadify Solution. This is not a quote, contract or client deliverable.

## Problem and decision
- Intended user and the job they need to complete:
- What happens today, and what evidence describes the problem:
- Decision owner and the person accepting the work:
- Why change the workflow rather than use an existing tool:

## One complete journey
- Starting state:
- User action and required permissions:
- Expected record or user outcome:
- Important error, empty and recovery states:
- What belongs in the first release:
- What is deliberately excluded:

## Acceptance record
For each scenario, record: starting state, action, expected state, actual result, evidence location, reviewer and open issue.
- Core journey:
- Input validation:
- Relevant roles and access boundaries:
- Integration failure and retry, if applicable:
- Existing behaviour to preserve:

## Dependencies and responsibilities
- Approved data and source permissions:
- Repository and environment arrangements:
- Integration documentation, accounts and approvals:
- Hosting, licences and third-party costs:
- Review checkpoints and availability:
- Release approval, rollback and operating owner:
- Unresolved question, responsible person and next decision:

## Handover and commercial scope
- Source access and ownership terms:
- Test evidence and remaining issues:
- Setup and deployment notes:
- Included support and separately scoped future work:
- Currency, invoicing, applicable tax and payment milestones to agree:
- Collaboration hours and communication expectations to agree:
- Price and delivery plan to be established in the actual proposal:

Evaluation recording, publication and model-training reuse require separate, specific permission. An NDA or repository access is not permission for these uses. Do not put credentials or confidential customer records in a public enquiry.