EVERESTSURGICAL
INSTITUTE
Sign in
Sign in with your email and password.
EVERESTSign in with your email and password.
Use the email address your administrator put on the staff roster.
We sent a verification link to . Open it (check spam too), then come back here.
EVERESTYou're signed in as , but you're not on the staff roster for this tool. Ask Benjamin to add you (Roster tab, with this exact email) and then reload this page.
Loading your day…
The staff schedule for has already been published.
You may still submit an availability change, but this will not change your current work schedule. The scheduler will be notified and must review any scheduling changes separately.
The staff schedule for has already been published. Availability changes for published dates aren't accepted here — please contact your scheduler directly.
Type a name to message one or more coworkers directly — each person gets their own private thread with you. Leave it blank for a general question or request, which goes to whoever has administrative access.
EVERESTEmployment type affects who Auto-fill prefers when multiple available staff could fill the same opening — order is configurable in Settings → Staffing. Add someone's email exactly as they'll sign in with — they get an email with a link to set their password. Use the ✉ button to re-send it. Grant "Admin access" to anyone who should also see Coverage Builder, publish schedules, and answer staff messages.
| # | Name | Type | Department | Team lead | Admin access |
|---|
Your surgical schedule, block plan, and staffing demand in one operational view.
Upload your OR case-schedule export (PDF, image, CSV, or spreadsheet). It's read by AI to pull the OR count plus the surgeon, procedure, and start time for each case — no patient information (MRN, age, sex, allergies) is ever kept. You review and fix everything before it's applied.
Fill in anything the import didn't catch, or build a day's case list from scratch. Edits stay local until you press Save cases — then staff see them on their Case Schedule and any changes are flagged to affected staff.
Private messages sent to you specifically by another staff member — not visible to other admins.
Staff questions and requests, plus threads you've started — anyone with admin access can answer.
Type a name to find staff. Each person you pick gets a private thread — they reply to you, not to each other.
Downloads an .xlsx workbook of exactly what's on screen right now — a Coverage tab (need vs. assigned, gaps highlighted) and a Roster tab — formatted to hand off, print, or attach to your monthly send.
Settings that apply to your whole facility.
The time zone your facility operates in. SYNC uses it to know which calendar date is “today” here — for example, so it doesn’t send a notification about a schedule change on a day that has already passed.
Departments used across Roster, Add Staff, availability, and announcement targeting. Archiving a department removes it from new selections without changing anyone already assigned to it.
| Name | Availability ProfileDetermines which availability choices and automatic staffing roles are available to a group of staff. | Active |
|---|
Used for Roster's "Type" column and the Add Staff dropdown. Renaming only changes the display name — Full-time and PRN keep working exactly as they do today. Archiving removes a type from new selections without changing anyone already on it.
| Name | Code | Active |
|---|
Which staffing groups and roles Coverage Builder tracks, and how many of each are required. Changes here take effect the next time a month is published — the current published schedule and Staff view are unaffected until then.
"Show in Coverage" controls whether the group appears in Coverage Builder. "Contributes to Coverage" controls whether an unfilled role in this group can make the day show Short-staffed — a group can be visible without affecting day status.
| Name | Code | Show in CoverageShows this staffing group in Coverage Builder so administrators can view and assign its staffing roles. | Contributes to CoverageDetermines whether this group's staffing levels affect the day's Short-staffed, Covered, or Overstaffed status. | ActiveThis staffing group is available for use. Turning it off does not delete its configuration or historical assignments. |
|---|
Each role's requirement type determines how many are needed: a fixed number for the day, a number per active OR, or no fixed requirement.
The order Auto-fill prefers when choosing between eligible staff. Everest's current behavior is full-time first, then PRN.
Which availability responses staff see for each department, and how each response translates into automatic staffing placement. Changes here take effect the next time a month is published — the current published schedule and Staff view are unaffected until then.
A department's staff see whichever availability profile that department is assigned to (in the Departments table above).
| Name | Departments using it | Eligible Staffing RolesRoles that staff using this profile may be automatically assigned to when they mark themselves available. | Active |
|---|
Each profile's own set of response tiles, grouped below. "Assignment preference" only appears for a role-preference response, and only offers roles the profile itself allows.
Controls how staff availability affects Draft staffing assignments and what happens when availability changes after a staff schedule has been published.
Everest default: Store availability for scheduler Auto-fill. Automatic Draft updates are a planned future capability — SYNC does not reintroduce the old browser-dependent reactive placement to offer it today.
Everest defaults: Yes, with scheduler review — all three options on.
How far ahead of a schedule change people get notified. Defaults reproduce exactly what SYNC does today.
How many days ahead Team Leads are notified of a schedule change for a day they're not necessarily working.
How many days ahead everyone working that day (not just Team Leads) is notified of a change. Everest's current behavior is 0 — same-day changes only; earlier changes reach Team Leads first.
When a day's very first case moves, also notify everyone working that day (not just Team Leads) as soon as it's one day out, instead of waiting for the standard-notice window.
How long an item stays prominent on staff Home screens. When the time is up it simply stops being highlighted — the announcement is never deleted, it stays in Communication, and nobody’s read or acknowledged status changes.
How long notifications you’ve already handled stay under “Earlier” in the Notification Center. Anything still unread or awaiting acknowledgement is always shown. The announcements and messages themselves are never deleted.
A Daily Huddle belongs to one date. It is current on that date and then drops off Home. Direct messages never expire on a timer.
Whether SYNC sends an external push for each kind of event, and whether staff may turn it off for themselves. This never affects the in-app Notification Center — every relevant event always appears there regardless of push settings.
Staff enroll their own number from their notification preferences. Individual phone numbers are private and are never shown here or anywhere in Settings.