# Fictional example: community event registration

## Supplied situation

A fictional organizer copies registration emails into a spreadsheet, asks a volunteer to check dietary notes, and sends a final list to the caterer. The organizer says the repeated copying is frustrating. No timing or error count was supplied.

## Small handoff map

`Organizer → copy email details → spreadsheet row → Volunteer → check dietary note → reviewed row → Organizer → send final list → Caterer`

Unknown: how long copying takes, how often a note is missed, and whether the caterer accepts a shared export.

## Options

- **Eliminate:** remove a duplicate “confirmation sent” column only if no one uses it for a real decision. Check with the organizer first.
- **Simplify:** use one agreed row template with a required dietary-note field and a visible “needs review” value.
- **Automate:** propose extracting fields from a sample email into a draft row, with the volunteer reviewing every row before export.

## Smallest reversible trial

Use the agreed row template for the next ten fictional registrations. Keep the current email and spreadsheet process, have the volunteer review each row, and compare the time to create each row plus the number of corrections. Roll back by returning to the existing columns if the template hides needed information.

No savings or accuracy result is claimed until the sample is observed.