event check / booking 4 · free workflow
Check an Event Plan for the Access Gaps — Free
Paste what the venue has told you and the check tests the five fields attendees ask about, so the gap is published as a gap rather than discovered on the day.
What this replaces
Access information gets written from what the venue volunteered. This checks the five fields attendees actually ask about, so a missing quiet space or an unconfirmed caption is visible before the event is published rather than at the door.
Tool note. This runs entirely in your browser — no account, no upload, no paid API key. Google NotebookLM is named as the free source-grounded reading path for the material you paste; its published free-tier terms were checked on 2026-09-13 and can change.
The four passes
Collect the smallest useful input
One field per line: route, toilet, quiet space, captions, access contact.
Let the check test all five
Missing fields go to the top of the urgency lane.
Ask the venue in writing
A verbal assurance helps nobody on the day.
Publish the gaps too
Saying a quiet space is unavailable is better than silence.
Try it on the event check / booking 4
The board below runs in your browser. It opens with a worked sample so the result is visible before you paste anything; switch scenarios, edit the text, or reset to the sample.
running the sample…
first-load · sample values are illustrative, not verified facts
Everything you paste stays in this browser tab. Nothing is uploaded, there is no account, and no request leaves the page to generate the result; clearing site data removes anything saved locally.
What breaks, and what to do
Venue answers not yet received
The fields stay empty, which is the useful signal.
Outdoor or temporary sites
Ground conditions matter as much as steps; note them.
Third-party catering
Dietary and access needs may sit with a supplier; ask them directly.
Go deeper — Event Check
The free board above is the whole loop. The paid tier keeps the arranged output so you do not rebuild it.
- Printable check to send to the venue as an access request — estimate: 19 minutes saved per event, basis: 5 fields re-drafted at ~3.8 minutes each
- Saved local history across events — estimate: 13 minutes saved per event, basis: re-entering 5 fields at ~2.6 minutes each
$5 one-time