PUZINSKI / ORIGINAL SAMPLE
Fictional app release checklist. No client code, records, or results are represented.

RELEASE: A small internal request-review workspace

PRIMARY USER
A staff member responsible for reviewing and organizing a request.

ESSENTIAL FLOW
Open a request -> inspect permitted information -> set the next action -> save -> see the updated state.

OUTSIDE THIS RELEASE
Additional user roles, native mobile distribution, payment collection, complex analytics, data migrations, and an AI decision-making feature.

REQUIREMENTS TO CONFIRM
- Information source and source of truth.
- What each user may view or change.
- Valid statuses and required fields.
- Integration access and limitations.
- Device/browser needs and accessibility requirements.
- Appropriate information handling and retention.

ACCEPTANCE CHECKLIST
[ ] The user can complete the essential flow.
[ ] Missing and invalid inputs produce understandable messages.
[ ] Users cannot perform actions outside agreed permissions.
[ ] Saving updates the intended record and shows the result.
[ ] Loading and failure states are usable.
[ ] Representative agreed device sizes are checked.
[ ] The responsible person has reviewed the release against the brief.
[ ] Known limitations and deferred work are documented.

HANDOVER CHECKLIST
[ ] Agreed source-code and account ownership are recorded.
[ ] Hosting and other running costs are identified.
[ ] Deployment and operating notes are provided.
[ ] The team knows how to report an issue.
[ ] Maintenance scope and support window are agreed.
[ ] New features remain separate from bug correction and routine care.

AI-ASSISTED DEVELOPMENT
AI can support implementation. Requirements, access decisions, code review, functional testing, and release acceptance remain explicit parts of delivery.

This document is a sample checklist, not evidence that a production app has passed these checks. Actual scope and fees require a separate signed proposal.