business · local-first tool
Give Every New Client Setup Task an Owner and Status
An email thread can make a missing access step look finished; keep each deliverable visibly open until confirmed.
Build an owner/date/status checklist for user-defined onboarding tasks and export a client-safe task summary.
What changes the result: your actual service workflow, client-approved steps, and target dates.
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 open and received entries separately from verified entries. Missing source labels remain visible. The app cannot decide whether an agency, school, provider, or contract has received enough documentation.
Question to keep open: Should onboarding be optimized for speed to kickoff or for reducing the number of assumptions carried into delivery?
Boundary: This is a planning worksheet, not a verified external record or instruction. Check the original source, confirm dates and responsibilities with the people involved, and keep sensitive details out of shared notes.
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.