accessibility · local-first tool
Give Each Meeting Topic More Than One Way to Contribute
If the only path to a decision is a fast spoken interruption, some participants may never get a turn.
Map agenda items to agreed participation channels such as spoken turn, chat, shared document, or follow-up; record the facilitator and confirmation status.
What changes the result: the participants' chosen channels, facilitator, agenda, and the platform's actual capabilities.
Privacy: Calculations run in this browser tab. This tool has no input-upload, account, or AI endpoint. The site may send a page-view signal to Cloudflare; this tool does not add form entries to that signal. A draft is stored only if you choose “Save draft on this device”; that browser storage is not encrypted. Avoid identifiers or sensitive details, and delete saved drafts when finished.
Your entries
The starting rows below are fictional examples. Edit them, replace them with non-sensitive labels and values, or load the sample again. The result is not advice or a source verification.
Amount fields use the same units you enter; the app does not choose a currency. Dates are the ones you provide. Up to 100 rows per run.
Calculated output
What the calculation does
Count short labels that lack a source, location, review date, or confirmed status, depending on the row type. The tool stores pointers, not the underlying documents, meter accounts, access codes, or proof that a record is current.
Question to keep open: Should a meeting reserve one channel for everyone or allow different ways to contribute to the same decision?
Boundary: This is a meeting-design worksheet, not an accessibility compliance certification. Ask participants what works for them, verify platform capabilities, and do not assume captions or chat are sufficient.
Copy includes the headline, aggregate metrics, and boundary—not the row-by-row input. The CSV contains entries you choose to download. Review it before sharing.