# Website vs web app planning worksheet

By Ajju Iglesias. Use sample or appropriately authorised information. Do not record credentials or private customer data here.

## User task (repeat for each essential workflow)
- Person and responsibility:
- What they need to do:
- Information needed before the task:
- Information submitted or changed:
- Successful outcome:
- Staff work after the action:
- Failure or exception and recovery:

## Existing systems
- Current source of truth:
- Existing product or configuration evaluated:
- Supported integration route and documentation:
- Essential requirement met / unmet / unverified:
- Reason to investigate custom work:

## Records and rules
- Record identities and relationships:
- States and permitted transitions:
- Duplicate or simultaneous changes:
- Availability/approval/confirmation rules:
- Public vs private information:
- User, project and action permissions:
- Departure and access-change process:

## Provisional scope
- Content-led website:
- Website connected to existing service:
- Existing application configured for the task:
- Custom application workflow to investigate:
- Public-site and private-tool handoff:
- First-release task and deferred modules:

## Evidence
- Happy-path acceptance case:
- One important exception case:
- Mockup evidence (layout and understanding):
- Technical evidence (actual behaviour/integration):
- Unverified assumptions and responsible person:

## Operation and decision
- Content, user and data owners:
- Connected-service support responsibilities:
- Recurring costs and maintenance assumptions:
- Migration, training and recovery needs:
- Decision, evidence and remaining questions:
- Trigger for reassessing scope:
