CASE NOTE / CLINIC SCHEDULER

Solver-backed scheduling for clinic operations.

A working system for generating weekly technician schedules across clinics, reviewing draft runs, filling gaps, and keeping an audit trail of schedule decisions.

01 / CONTEXT

The problem was operational, not just mathematical.

The hard part was not drawing a calendar. The system had to encode rules, constraints, approvals, disruptions, and handoffs in a way clinic staff could trust and inspect.

Domain
Clinic operations and technician scheduling
Core
OR-Tools CP-SAT, rule registry, draft/review workflow
Stack
Flask, SQLAlchemy, Postgres, React, Vite

02 / WHAT SHIPPED

A scheduling workflow with review built in.

01

Generate draft schedules.

Run solver-backed schedule generation against known rules, staffing needs, clinic coverage, and availability constraints.

02

Review before approval.

Give managers a visible draft state, gap-filling tools, approval flow, CSV export, and share links instead of treating solver output as final truth.

03

Make operations auditable.

Use RBAC, audit history, admin controls, and disruption recovery so schedule changes can be understood after the fact.

03 / PATTERN

The useful lesson: optimization has to land inside a real workflow.

This is the kind of build Seam is good at: make the rules explicit, automate the repetitive decision, and leave a system that people can inspect, override, and run without calling the builder every week.