learning · local-first tool
Keep Student Support Contacts and Follow-Ups Together
An office name, message date, and next contact can stop a support question from vanishing between systems.
Chronologically track a school-office contact, general topic, response status, and user-entered next date without keeping sensitive details.
What changes the result: your chosen office, non-sensitive topic label, and the school's own reply instructions.
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 and order user-entered dates; keep the status separate from the event description. An open or waiting entry whose date has passed is highlighted for review, not treated as an official deadline or proof that an event occurred.
Question to keep open: Should a student wait for a response or follow the office's stated follow-up channel and timeframe?
Boundary: Do not enter student ID numbers, diagnoses, financial account details, or confidential documents. This log does not determine aid eligibility or school policy.
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.