NEUR.ON
Scheduling, shift management and payroll built for a 26-person medical practice.
Role
Developer & owner
Timeline
Current
Type
Internal web app
Overview
NEUR.ON is built to replace the spreadsheet-and-group-text way a neuroscience practice schedules 26 people across six different roles. It is deployed to an internal environment and in testing rollout — not yet the system of record.
Providers view and request assignments. Staff clock in and out, request shifts, swap them with a peer, and file leave. Admins run the schedule grid, payroll rates and data imports. Every one of those actions moves through a real approval chain with the right person at each step, which is the part that makes or breaks a scheduling tool.
It runs on Supabase with row-level security doing the enforcement on every table, email one-time-password sign-in so nobody manages another password, and batched notification email so a bulk schedule upload will not fire thirty separate messages at a doctor. Email delivery stays switched off until the practice signs off on go-live.
Built with
- Next.js
- React
- Tailwind
- Supabase (Postgres, Auth, RLS)
- Resend
- Vercel
What mattered
Six roles, one permission model
Staff, provider, scheduler and two admin tiers each see a different home screen and a different set of verbs — enforced at the database, not just in the UI.
Approvals that mirror the clinic
Shift swaps need the peer and the admin. Leave checks the hours balance. Requests can be cancelled, denied and re-requested without anyone emailing anyone.
Bulk schedule uploads
A CSV drops a month of assignments in at once and sends one batched notification instead of flooding inboxes.