accessibility · local-first tool
Keep a Workplace Access Request Beside Its Follow-Up Date
A request, an acknowledgement, and an implemented change are different stages; track only what you know.
Log a request topic, date, contact, response stage, and next user-selected follow-up without determining rights or eligibility.
What changes the result: the date, non-sensitive topic label, and contact channel you choose.
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
Validate the date as a real YYYY-MM-DD calendar date, keep the user's status label, and order open items by their entered date. A past date is a comparison to the device's current local date; it is not a statutory or contractual deadline calculation.
Question to keep open: Should a follow-up happen on a fixed date or after the organization confirms the process?
Boundary: Employment accommodation rights and timelines vary. This tracker does not provide legal advice; confirm the process with your employer, a qualified advocate, or the relevant agency.
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.