Write useful notes when something goes wrong at a photo booth

When a photo booth issue occurs, record what happened, when it happened and which step was affected. Useful notes help the provider investigate and the organizer understand guest impact. A message saying “the booth broke” provides little evidence.

Record observable facts.

Note the time window, active configuration and visible behavior. Identify whether capture, output, delivery or printing was affected. Record the support contact, advice received and action taken.

Keep confirmed facts separate from guesses. A missing delivery does not by itself prove a network failure. Avoid repeatedly changing settings without the provider’s guidance, because that can obscure the original issue.

Protect participant information

Use the provider’s agreed support process for records needed to investigate a guest request. Do not paste addresses or photos into a broadly shared event debrief unless appropriate and necessary.

After resolution, confirm the working state and any remaining guest handoff. Plan the debrief around patterns and decisions, not blame or a list of unverified explanations.

A compact incident record

Observed [time]. Affected step [capture/output/delivery/print]. Visible symptom [fact]. Guest impact [known scope]. Action [what changed]. Support [contact/reference]. Recovery check [result]. Open handoff [owner].

Use “cause not yet established” when that is the truth. The note should let support reconstruct the sequence without turning an early guess into the official explanation.

Record a successful check after the action. “Restarted” describes an intervention; “new test image printed and opened from delivery” describes recovery evidence. Keep personal details in the designated support record and use only the minimum needed in the shared event summary.