Know your coverage gaps
before the shift starts.
OuiShift is scheduling for teams where being short-staffed is an incident, not an inconvenience. Set the coverage you need, watch it live by the hour, and handle every schedule change — swaps, call-outs, overtime, bids — in one place instead of four inboxes.
NOC teams · Operations centers · Healthcare · Retail · Restaurants
Free during beta · Google, Microsoft and Okta SSO included · Export your data any time
Being short-staffed isn't an inconvenience. It's an incident.
Most shift teams run on a spreadsheet, a group chat and an email chain. It works right up until it doesn't — and the moment it stops working is the moment you're short on the floor, with no warning and no record of how you got there.
You find out too late.
Someone calls out at 6am and you learn about it at 6:40, from whoever noticed the empty desk. There’s no early warning, because nothing is watching the staffing level but you.
Requests live in DMs.
Swaps, early outs, overtime — approved over chat, remembered by one person, invisible to everyone else. No queue, no status, no audit trail when someone asks six weeks later who approved what.
Nobody has the same picture.
The spreadsheet, the whiteboard and the text thread disagree, and each manager trusts a different one. Reconciling them is the job now.
Most scheduling tools schedule people. They don't watch your coverage.
You can build a rota in almost anything. The hard part isn't drawing the schedule — it's knowing, at 2pm on a Thursday, whether you still have three network engineers on the floor after two call-outs and a training block. OuiShift treats coverage as a thing you define and the system measures, not something you count by eye.
Everything your team needs to stay covered.
Three people open OuiShift for three different reasons. Pick yours.
You need to know you’re covered before the shift starts — with requests, bids and rotations in one queue instead of five chat threads.
Daily staffing dashboard
HomeWho’s on duty, on leave, out of office or called out — right now. An hourly coverage chart measures the day against your targets, so a gap is something you’re told about rather than something you discover.
Coverage targets
CoverageDefine the headcount a team needs by position and by hour, and let the system measure it. Covered stops being a thing you count by eye.
One queue, 11 request types
RequestsLeave, call-out, early out, late in, shift override, permanent schedule change, RDO swap, shift swap, shift drop, overtime and training — each with the fields and approval path that request actually needs.
Leave that matches HR policy
RequestsTen leave buckets tracked separately: PTO, sick, personal, bereavement, jury duty, FMLA, military, comp time, unpaid and floating holiday. Sick is not PTO and the system knows it.
Shift bidding
Bid EventsRun structured bid events for holidays, schedules or overtime. Award by seniority, lottery, first-come or manual review, with eligibility rules per event and per slot. A defensible process instead of a negotiation.
On-call rotations and call blocks
RotationRotations by position or capability on a weekly, biweekly, four-weekly or monthly cadence, plus a standing weekly call block grid the system can fill automatically — whoever has covered that role least goes first.
Live status board
StatusWho’s reachable right now, without anyone updating a status by hand. Optional Microsoft Teams presence sync puts real availability on the board.
Managers buy scheduling software; employees decide whether it survives. Your schedule, your requests, your swaps — without chasing anyone.
Your schedule, your timezone
CalendarMonth, week and day views of your own shifts, in the timezone you actually work in. Live the moment it changes, so the version on your phone is the real one.
Requests without a middleman
RequestsSubmit a swap, an early out or time off yourself, and watch its status move. You get told when it’s approved — in the app, and by email when it’s a decision you’re waiting on.
Swaps that need two yeses
RequestsA swap waits for your counterparty to accept, then for a manager to approve — two recorded steps, not one message and a nod. Open shifts are there to claim, and an unclaimed dropped shift expires instead of sitting open forever.
Bid rules published up front
Bid EventsSee the eligibility rules and the award method — seniority, lottery, first-come or manual review — before you bid, not after the holiday schedule comes out.
Guided first run
OnboardingA walkthrough on each screen the first time you land on it, so “how do I request a swap” isn’t a training session.
Set the org shape and the permissions once. Everything downstream inherits them — and who sees what is a real setting, not a role dropdown.
SSO from day one
AccessGoogle, Microsoft and Okta. No new credentials for anyone to forget or reuse.
Permissions that follow your org chart
AccessGrant a permission across the company, or scope it to a team, a department, a group or someone’s reporting line — so a shift lead approves for their own team and nobody else’s.
Delegated administration, bounded
AccessAppoint someone to hand out permissions inside one team or department without making them a company-wide admin. Delegated grants are pinned to that container and expire when the person who issued them loses standing.
An audit trail where it counts
AccessRequests, rotations and cross-company schedule shares record who did what and when, including every status transition and who made it. Seat limits are enforced on every invite, not billed after the fact.
Org shape, groups and timezones
PeopleUnits, departments, teams, groups, positions and offices, with a timezone selector in the filter layer — so each manager sees their own slice and nobody scrolls past 400 rows to find theirs.
Skills, certifications and clearances
PeopleTrack capabilities per person — clearance, language, certification, product, customer, tool or skill — with proficiency levels. Rotations can be built from a capability rather than a job title, so the person on call is actually qualified.
Directory identity mapping
PeopleLink each person to their Microsoft 365 account, with per-account sync status and an alternate lookup address for anyone the directory can’t find by their work email.
Work-from-home policy
WFHAn optional module with its own rules — an annual allowance, a weekly maximum, and whether a note is required. Kept separate from leave, so remote days never eat someone’s PTO.
Encrypted third-party credentials
SecurityAny integration secret is sealed at rest and bound to the company it belongs to. It is never displayed back, not even to the admin who entered it.
Works with the accounts your team already has.
Set the coverage you need. Let the system watch it.
A coverage target says what “covered” means for a given team, and the dashboard measures the real schedule against it, hour by hour. You stop counting heads on a calendar.
Scoped where you work. A target belongs to a team, a unit or a department — so the NOC floor and the day-shift help desk each have their own definition of covered.
Down to the position. A target is built from requirement lines: three network engineers or two engineers and a senior. It counts the roles you actually need on the floor, not warm bodies.
Any window, including overnight. All day, a day or night band, or an explicit start and end time that can wrap past midnight. Pick the days of the week it applies to.
Two ways to measure. Sustained asks whether the headcount held across the window — the right question for a floor that must never dip. On-duty asks how many distinct people covered any part of it.
Visible to the right people. A target can be private to its creator, or shared with a team, department, unit or the whole company, independent of what it measures.
Coverage target — NOC Floor
The status board updates itself.
Most “who's available” boards are a list of statuses somebody forgot to change. If your company runs on Microsoft Teams, OuiShift reads presence directly from your own Microsoft 365 tenant and puts it on the board next to the schedule — so “on duty” and “actually at their desk” are the same screen.
Your tenant, your app registration. Presence is read through an app registration you own, in your own directory. We never proxy your users through a shared identity.
Live, and honest when it isn’t. The board polls on an interval you set and knows when its own data has gone stale — a worker outage shows as unknown, never as a confidently wrong green dot.
Scoped to who matters. Poll the whole company, or only named teams, departments, units or groups, so a 4,000-person tenant doesn’t cost you 4,000 lookups every fifteen seconds.
A person can speak for themselves. Someone can set a status message in OuiShift — “covering the floor until 3pm” — with an optional expiry, and it sits alongside their Teams status.
Share a schedule. Not your system.
If you run a joint operation with a vendor, an MSP, a sister site or a client, they can see the coverage that concerns them and nothing else. You choose the team or group you expose, they choose who on their side may look, and either side can pause or revoke it at any time.
You control the disclosure level. Names only, or names and positions — your choice.
Scoped both ways. You pick what’s shared; they pick who on their side sees it.
Reversible and logged. Offer, accept, pause, resume, revoke — every transition recorded with who did it.
Connected out of band. One admin generates a single-use, expiring code and sends it however you already talk. No shared login, no support ticket, nothing to trust but the code.
Who sees what is a real setting, not a role dropdown.
A schedule is a record of who works where, and who is alone on the floor at 3am. It is treated that way.
SSO from day one
Google, Microsoft and Okta. No new credentials for anyone to forget or reuse.
Permissions that follow your org chart
Grant across the company, or scope to a team, department, group or reporting line — so a shift lead approves for their own team and nobody else’s.
An audit trail where it counts
Requests, rotations and cross-company schedule shares record every status transition and who made it.
Encrypted integration credentials
Any third-party secret is sealed at rest and bound to the company it belongs to. Never displayed back, not even to the admin who entered it.
Live in a day, not a quarter.
Sign in with SSO.
Google, Microsoft or Okta. Nobody creates a password.
Bulk-import your people.
Name, position, department, team and timezone from a spreadsheet you already have — schedules import in the same file. Each row succeeds or fails on its own, so one bad row never blocks the rest.
Set your org shape and permissions.
Units, departments, teams and groups, so each manager lands on their own view and admins see everything.
Define what “covered” means.
One coverage target per team is enough to start. This is the step that turns a calendar into an early warning system — don’t skip it.
Run the operation from one place.
Approve requests, watch live coverage, run bid events, publish on-call. The spreadsheet stops being the source of truth on day one.
Free during beta. Honest pricing after.
Every beta team gets the full platform at no cost through v1. When pricing starts, we'll give you advance notice and you can export everything and leave if the numbers don't work.
For small teams getting started.
For growing operations teams.
For large, multi-region organizations.
Beta accounts keep their data. When pricing starts you choose a plan or export and close — nothing is deleted out from under you.
Common questions.
Shift-based operations where coverage is the constraint: NOC teams, operations centers, healthcare units, retail floors and restaurants. If being one person short changes your day, it fits. If your team works a fixed 9-to-5 with occasional PTO, a calendar and a leave tracker will serve you better — and we’d rather say so.
Eleven: leave, call-out, early out, late in, shift override, permanent schedule change, RDO swap, shift swap, shift drop, overtime and training. Each has its own fields and approval path, with status visible to the requester the whole way.
Yes, as separate buckets — PTO, sick, personal, bereavement, jury duty, FMLA, military, comp time, unpaid and floating holiday. Sick time is tracked apart from PTO because the policy around it is different.
Yes. Employees log in and see their own schedule, submit requests, and track status — no manager middleman needed for routine lookups.
Bulk-upload your employee records and schedules from the spreadsheets you have now, or build from scratch in the platform. Most teams are running on real data the first day.
Uploads are capped at 200 rows and 2 MB per file, processed with a per-row result — so one bad row never blocks the rest. A 900-person org arrives in five uploads, not one.
Yes. The timezone selector sits in the filter layer, so a distributed team views the same schedule in local time, and overnight coverage windows wrap past midnight correctly instead of splitting into two half-days.
Yes. A bid event is one of three kinds — holiday, schedule or overtime — and each can be awarded by seniority, lottery, first-come or manual review, with its own eligibility rules.
From your schedule, and — if you enable the presence module — live from Microsoft Teams. OuiShift reads presence through an app registration in your own Microsoft 365 tenant, on a polling interval you control, scoped to the teams or departments you choose. If the sync stops, the board says so rather than showing stale availability as current.
Yes, and narrowly. You expose one team or group, they nominate who on their side may view it, and you choose whether they see names only or names and positions. Either party can pause or revoke it, and every change is logged.
Yes. Capabilities are first-class — clearance, language, certification, product, tool or skill — with a proficiency level and a primary/secondary designation per person. On-call rotations can be built from a capability instead of a job title, so the person paged is qualified for what they’re being paged about.
Google, Microsoft and Okta, on every plan.
No. Everything produces an in-app notification; email is reserved for the decisions someone is actually waiting on — a request approved or denied, a swap proposed to you, a bid awarded.
We’ll give you advance notice before pricing starts. Your data stays yours: pick a plan, or export everything and close the account. Nothing is deleted out from under you.
Yes. Your data is exportable and belongs to you — you can take it with you at any time.