Teams · SOCs

SOC scheduling software for 24/7 teams

SOC Rotate schedules your analysts around the clock: it builds the 24/7 rotation by tier, keeps it inside working-time law, runs leave, swaps, on-call and shift handover around it, and proves the coverage a client was promised.

The problem

Most SOCs still build the analyst rota by hand. It works until it doesn’t.

Manual scheduling doesn’t fail on day one. It fails the day your operation outgrows it.

  1. 01 ·

    Generic tools don’t understand a SOC.

    They have no analyst tiers, no coverage set per tier, no handover, no client SLAs, and no follow-the-sun across offices.

  2. 02 ·

    Building it by hand takes days, every month.

    24/7 cover, the right T1/T2/T3 mix on every shift, and nights and weekends spread fairly are all worked out in a spreadsheet.

  3. 03 ·

    Analysts can’t see next month.

    When the rota is only finished a week or two ahead, leave and childcare get planned around shifts that don’t exist yet, and every late change lands on someone who had already made plans.

  4. 04 ·

    Building your own scheduler never ends.

    It pulls engineers off security work for months, and again every time tiers, rotations or rules change.

How it differs

Built for security operations. Not adapted from retail.

A generic scheduler and SOC Rotate start from different assumptions about what a shift is.

Spreadsheets & generic scheduling software
SOC Rotate
Source of truth
A spreadsheet or generic tool, out of date by the next shift
One live schedule everyone reads from — always current
Coverage
Fill open shifts
Per-tier, per-client minimum enforced — flagged the moment a shift drops below it
Skill mix
Anyone can cover any shift
Tier-aware (T1/T2/T3): coverage counts against the mix a shift actually needs
Delivery
Multi-location, single company — no concept of an external client account
Clients are first-class: each has its own SLA target and the offices that serve it, chained across them for follow-the-sun hand-off
Equity
Tracks hours worked
Fairness ledger scores nights, weekends and holidays against weights you set
Changes
A swap or leave request is a manual grid edit
Leave and swaps arrive with the shifts they empty, who can cover, and the rest check done
Continuity
No concept of a hand-off
Structured handover notes carry incident context between shifts
For MSSPs

Every client watched at the tier their contract needs

SOC Rotate makes sure every client you monitor has the right analysts on shift around the clock, including the senior analyst an escalation needs at 3am, and flags a gap before the client notices it.

Generic schedulers only know your staff. SOC Rotate also knows your clients and the SLA each one signed, so you can show any client the cover they paid for.

For in-house SOCs

Cover the escalation path, without burning out the team

SOC Rotate keeps every shift staffed at the tier your incident response needs, flags a gap before it happens, and shares nights, weekends and holidays fairly so they don’t always land on the same analysts.

Every change is recorded, so you can show the CISO the SOC was covered, all month.

Fit

Where it sits in your SOC stack

A SOC already has a SIEM, EDR, a SOAR or case-management tool, and paging. This is none of those. It decides who is on shift, holds the roster to the coverage rule and the law, and proves the SLA was staffed.

  • Not a SIEM or EDR. It sees no alerts and no telemetry.
  • Not a SOAR or case-management tool. There are no cases or incidents in it — the handover carries text about them.
  • Not paging. On-call is a schedule; it does not send the page. Notifications reach people in the app, by email or by Slack webhook.
  • No API and no PagerDuty, Opsgenie or ServiceNow integration yet.

It sits beside those tools, and tells you which of your analysts were on the floor when an alert fired.

FAQ

Common questions.

Have something specific to your floor? Speak to sales.

How many analysts does a 24/7 SOC need?
More than the seats suggest. One seat staffed around the clock is 8,760 hours a year, and once leave, sickness and training are counted that takes about five analysts, for every tier that must be reachable at all hours. The blog post on 24/7 SOC staffing works it through for a real floor, rounded up per tier.
Do you handle L1, L2 and L3?
Yes. Analysts sit on three fixed tiers, T1 to T3, and each shift can require a number of each, plus a team lead counted by role. A shift with enough people but not the tier it needs is flagged as a gap.
We are an MSSP. Can we show each client their coverage?
Yes. Each client has an SLA target and the offices that serve it, this week’s coverage is measured against the target, and there is a live page per client — this month’s coverage tier by tier, every shortfall listed — that reads straight from the rotation each time it is opened. There is no roll-up across clients and no trend view; it is one client, this month, coverage only.
We run one team across several offices. Does that work?
Yes. Each office keeps its own time zone, holidays and people, and a client served by several offices is a chain whose combined coverage is measured as one picture. Hand-off gaps show before you save and are swept nightly.
Do you integrate with PagerDuty, Opsgenie or ServiceNow?
Not yet. Notifications reach people in the app, by email, or by Slack webhook, and there is no public API today. Tell us which one matters to you; it informs what gets built next.
What size of team is it for?
A 24/7 team of four is rostered on a whiteboard; the product earns its place once there are enough people that the rotation, the fairness and the cover for leave stop fitting in one head.
Is there a free trial or self-serve sign-up?
There is a 30-day trial, after a demo rather than a sign-up form. You get your own account with the rotation built on your own structure, and if you decide to go ahead, onboarding starts from there.
Running a rotation already?

See it on your own rotation, not a demo tenant.

Tell us how your floor is structured: shifts, tiers, sites, who never rotates. We'll build the rotation, walk through where coverage and fairness land, and answer the questions a generalist scheduling tool can't.

  • RotationA month of 24/7 coverage in one action.
  • CoverageEvery gap flagged before it reaches a client.
  • ComplianceEvery change logged, every override on record.