family · local-first tool
Map Care Visits So No Time Slot Is Left Assumed
A named visit and a confirmed person are different facts; see both before the handoff.
Lay out care visits by date, time, assigned person, and confirmation state, then flag gaps and overlaps.
What changes the result: the dates, visit lengths, and volunteers who have actually agreed to help.
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
Parse same-day local clock times, group entries by date and person/resource code, and mark overlapping active intervals. Overnight work must be split into separate entries. No travel time or time-zone conversion is inferred.
Question to keep open: Should a care rota aim for equal turns or for reliable coverage that matches each helper's real constraints?
Boundary: A schedule cannot establish clinical safety, competence, consent, or a person's care needs. Follow the care recipient's plan and qualified instructions.
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.