01
Define the department’s rules
We map requirements, preferences, course categories, teaching loads, fixed commitments, and the decisions that must remain human.
Course scheduling, under human control
Configure the rules once. Import structured faculty and course inputs. Optimize teaching assignments and meeting times. Then use a local workbench to revise, checkpoint, compare, and export.
Please keep the first email high-level. Do not attach faculty records, preference files, or other confidential material.
✓ Deterministic optimization
✓ Local browser interface
✓ Reversible checkpoints
Synthetic walkthrough · fictional data
See the Schedule Workbench in action
No black-box schedule
Rules and tradeoffs stay visible
No hosted scheduling account
A local browser-based operating model
No forced final answer
The department’s scheduling lead decides
From intake to export
Every department has its own canonical courses, rules, exceptions, and decision habits. The first cycle translates those realities into a tested configuration that can be reused.
01
We map requirements, preferences, course categories, teaching loads, fixed commitments, and the decisions that must remain human.
02
We configure an agreed Form or spreadsheet format and validate the inputs before they become a scheduling project.
03
Run deterministic proposals for teaching assignments and meeting times while respecting locks, availability, and hard constraints.
04
Use the workbench to test changes, save checkpoints, compare versions, restore earlier work, and export the final schedule.
Built around judgment
The point is not to press a magic button. It is to make a difficult scheduling process faster, more consistent, and easier to reason about—without hiding the decisions that matter.
Your approved rules are configured and testable—not inferred on the fly by a chatbot.
Accepted inputs and configured rules produce a rule-driven proposal with visible locks and tradeoffs.
Optimization starts the conversation. You can lock, adjust, save checkpoints, compare, and restore.
The pilot delivery design keeps the convenience of a browser while the scheduling application runs on the local device.
Every implementation begins by translating the department’s actual policies and intake into a tested profile.
Export clear spreadsheet and CSV outputs for review, downstream work, and institutional systems.
Early collaborator feedback
An earlier scheduling implementation was developed in close collaboration with a large academic department. The department’s scheduling lead especially valued the editable workbench after optimization. This feedback describes that collaboration, not a claim of universal compatibility.
“I was skeptical that this was going to work, but I'm very enthusiastic now. Before, I spent 15–30 hours per semester working in our spreadsheets. Now, it's 1–2 hours, plus more efficient meetings with my colleagues.”
Where AI fits—and where it does not
AI-assisted development helps configure a department-specific profile and intake strategy. The scheduling application itself applies explicit rules and deterministic optimization.
That distinction keeps the rules and constraints inspectable and preserves a human-controlled workbench for every consequential decision.
Questions
Every department is a little different. These are the boundaries that stay consistent.

Direct implementation and support
I’m Graham Clay. I work directly with each department to understand its scheduling process, configure the rules and intake, test the resulting workflow, and support you through the first cycle.
Email GrahamA useful first conversation
We’ll discuss the inputs, rules, handoffs, and pain points from one real cycle at a high level and decide whether this is the right shape of problem for a pilot.
Start by emailPlease do not email confidential records or attach faculty data. We will agree on a secure, limited data boundary before any files are shared.
automatedteach@gmail.com