SOPs
Write the procedure once. Starting a run turns its steps into dated tasks with a person against each one.
Not connected to a database
This is the library of procedures a practice runs on. FeelOrganized has no Supabase project behind it yet, so there is nothing to read and nothing to save to. The schema and the access rules this screen runs on are written and tested, in sql/. Adding the environment variables switches this screen on with no code change.
No procedures written
An SOP is a named procedure with ordered steps, an owner per step, and a schedule. Nothing runs until one exists.
Waiting on: a Supabase project
What lives here
- A library of procedures: monthly close, new clinician onboarding, credentialing renewals, insurance panel checks, offboarding.
- Each run is its own checklist with dates, so the procedure and the instance of it stay separate.
- Reminders fire before the due date rather than after, and escalate if a step stalls.
- Completed runs stay as a record of what was done, by whom, and when.