accessibility · local-first tool
Share Communication Preferences Without Storing a Full Case File
A short preference card can tell a new contact how to communicate, while leaving private details out.
Create a user-controlled card for preferred channel, response time, plain-language needs, and who to ask before a handoff.
What changes the result: the communication method, language, format, and details the person chooses to share.
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 reusable card be broad enough for every situation or tailored to the next interaction?
Boundary: The user decides what to disclose and to whom. This is not a medical record, does not prove consent, and should not contain passwords or unnecessary sensitive information.
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.