# Workflow evaluation worksheet

Recommended template from the Kill My SaaS field report, October 11, 2026.
This is a proposed protocol, not a claim that all these checks occurred in the challenge.

## Freeze the observation
- Submission ID / project:
- Build hash and deployment URL:
- Governing brief version:
- Observation date, time and timezone:
- Evaluator role / test account:
- Seed data and account expiry:
- Human help required:

## For each task
- Persona and goal:
- Starting state:
- Expected transition and downstream effects:
- Actions performed:
- Outcome: passed / failed / inaccessible / not tested
- Evidence (timestamped clip, screenshot, trace):
- Confidence and limitations:
- Time and human interventions:
- Recovery path:

## Suggested journeys
1. Open-call speaker submits, returns, receives a decision and completes deliverables.
2. Invited speaker joins directly without an unnecessary competitive application.
3. Sponsor contact provides the correct assets with appropriate permissions.
4. Organizer changes a decision and checks access, messages and schedule state.
5. Organizer moves a session into conflict and resolves it.
6. New organizer reaches the first useful event state from a fresh session.
7. Expired invitation is recovered without duplicate identities or lost data.

Keep contest build observations separate from later improvements.
Record research, human editing, agent runtime and review time separately.
Do not infer a missing feature solely from an access failure.