EEG tech scheduling software
EEG tech scheduling that respects what each tech can actually work
EEG technologists are not interchangeable, and a schedule that pretends otherwise fails at the worst possible moment. Axiom Shift keeps qualifications, rotations, contracted hours and time-off in one place — and puts each technologist's own schedule on their phone.
Built by Drewe Cosby, R. EEG T., a registered EEG technologist and neurodiagnostic operations leader, for the departments he has actually staffed.
Part of one neurodiagnostic operating system
The EHR owns the clinical record. The acquisition system owns the waveform. Axiom owns the operation. Axiom OrderFlow coordinates EEG orders, studies, equipment, reader follow-up, and billing readiness. Axiom Shift coordinates the people and coverage behind that work. Connected workspaces link clinical identities, qualifications, availability, and workload. Published availability is reviewed in OrderFlow before it is applied; each coverage view identifies the people and equipment evidence it evaluates. Axiom does not replace the EHR, acquisition systems, payroll, HR platforms or physician interpretation. It is the operational layer that connects them.
- A schedule published in Axiom Shift arrives in OrderFlow as governed availability; a supervisor reviews and applies it, and hand-entered exceptions are never overwritten.
- The reader of the day set in Shift flows into OrderFlow so nobody types it twice.
- OrderFlow's "Can we cover tomorrow?" checks every scheduled study against competencies, availability and equipment, with the evidence attached.
- That answer comes back into Shift: while a schedule is being built, each day shows whether OrderFlow can cover the work it has to cover, so the gap is visible before the schedule is published rather than discovered on the day.
Qualification-aware from the start
Every technologist carries what they are qualified and credentialed to work. When the schedule is built, those rules are applied rather than remembered — so a unit requiring a registered technologist never quietly receives someone who cannot work it.
- Units state the qualification they require; the schedule enforces it.
- Specialized procedures route only to the technologists trained for them.
- Students appear on the schedule and are never counted as coverage.
- Travelers carry assignment windows and guaranteed hours.
Every tech's schedule, on their own phone
Each technologist gets a private calendar feed they subscribe to once in Apple Calendar, Google Calendar or Outlook. After that the schedule simply lives on their phone alongside everything else and updates when it changes — no app to open each time, no screenshot in a group chat that is a week out of date. The link is made once, from their own sign-in.
Open shifts, volunteering and swaps
Open shifts are shown to the technologists qualified to work them, and can be claimed with one tap for a supervisor to confirm. Swaps are tracked rather than agreed in a corridor, so the schedule and the people on it never diverge — and the record of who worked survives for the months when it matters.
Weekends, holidays and who keeps absorbing them
Fairness is a memory problem, not a fairness problem. The draft looks back over the last four weeks of weekends and nights before it places anyone, so the same people stop absorbing them, and the fairness report counts each person's weekends, nights and the holidays you have marked on the calendar, so a technologist who feels they always get Saturday can see whether that is true. Where a department's rules give seniority a say in desirable and undesirable shifts, the schedule can reflect that too.
When someone calls out at 5am
The list of people who could cover is ranked immediately — qualified for that unit, not already working, still inside contracted hours, not on approved time off. The person filling the hole starts with real names instead of scrolling a roster while a patient waits.
Common questions
How do technologists see their own schedule?
Each technologist has their own view of what they are working, and a private calendar feed they can subscribe to from Apple Calendar, Google Calendar or Outlook. Once subscribed, the schedule is on their phone and updates when it changes — no app to install and no screenshot passed around a group chat.
Can technologists pick up open shifts themselves?
Yes. Open shifts are visible to the technologists who are qualified to work them, and a tech can volunteer with one tap. A supervisor still confirms, so nobody is scheduled by accident, but the back-and-forth of finding a volunteer disappears.
How are swaps handled?
A swap is offered and tracked rather than agreed verbally and forgotten. Both sides and the schedule stay in agreement, and the record of who actually worked survives, which matters when the month is later used as staffing evidence.
Does it track who keeps working the weekends?
Yes. The draft looks back over the last four weeks of weekends and nights, so it spreads them rather than repeatedly landing on whoever is easiest to schedule. Holidays you mark on the calendar are counted per person on the fairness report. A technologist can see their own history, which turns a resentment into a conversation about a number.
What about registry status and qualifications?
Qualifications are attached to the technologist and enforced when the schedule is built, so a unit that requires a registered technologist will not accept one who is not. Where a credential is required by a unit, the schedule respects it rather than relying on the scheduler remembering.
See it against your own department
Axiom Shift is priced per department, with paid fixed-scope pilots. It schedules staff, not patients, so there is no patient record in it. See how we handle data.