Start hereHow to use this in two minutes
  1. 01
    Pick a problem and press the buttonEach one is a real situation. Start with “A doctor calls in sick”, scenario “cover clean”.
  2. 02
    Or put your own organisation inOpen “Tell Rook about your own organisation” and type your clinic or company name, who is off, who can cover and what you are reporting. Everything that comes back is written about you.
  3. 03
    Read what Rook foundIt has looked across every connected system and changed nothing yet. The Findings say who is affected and why.
  4. 04
    Press Run planWatch the Plan and the Timeline. Each step is checked against the system itself before the next one starts.
  5. 05
    Approve when it stopsRook will not message a patient without a person saying yes. Switch the menu at the top right to the manager and approve.
  6. 06
    Check the proof, not the promiseVerification lists what was confirmed against the live systems. Closed means every one of them passed.
  7. 07
    See what it refused to doOpen “Limits”. Try scenario “cover unreachable” to watch Rook deliberately leave one appointment alone, and say why.
  8. 08
    Take the evidence awayDownload the evidence pack at the bottom: every action, approval, check and a tamper-evident audit trail.

Every system Rook touches here is a sandboxed copy with made-up data. Nothing real is changed, and no real person is contacted.

Start with a problem. Rook takes it from there.

Every industry runs on work that falls between its systems: a clinic, an engineering team, an IT department, a sports club. Pick the one closest to yours, or tell Rook about your own organisation.

Industry

Clinics, practices and anywhere people are booked in to be seen.

What has gone wrong

Tell Rook about your own organisation

Fill in as much or as little as you like. Whatever you type comes back in the incident, the plan, the approval requests and the evidence pack. Anything you leave blank uses the sandbox’s own example instead.

Who you areWho is in the loop

These are names on the sign-in menu, nothing more. Who is allowed to start an incident and who is allowed to approve one is still decided by the sign-in itself, which the agent checks on every request.

Your peopleYour numbersMake it harder
  1. 01A problem comes inA doctor calls in sick, an order is late, someone leaves. Staff raise it, or a connected system does.
  2. 02Rook investigatesIt reads every system the problem touches and works out who and what is actually affected. Nothing is changed yet.
  3. 03Staff approveRook proposes the fix as ordered steps. Anything that reaches a person outside the building waits for someone to say yes.
  4. 04Rook proves itIt checks the result against the systems themselves. Whatever it could not finish stays open, named, and with the reason.
Start
Pick a problem above, then press the button.

Five kinds, from a doctor calling in sick to a key found in a repository. Or open “Tell Rook about your own organisation” and put your own clinic or company in. Every system behind them is a sandboxed copy, so nothing real is touched.

sandboxmock integrationsorg …loadingsign-in coming soon

Incidents

Each run is stored with its plan, checkpoints and audit trail.

Loading…

    What a company is actually buying

    • One place to see the problems nobody has finished yet.
    • Connections into the software the company already runs.
    • An agent that works out what happened and coordinates the fix across all of them.
    • Approval on anything sensitive, a full audit trail, and proof the work actually landed.

    Rook does not replace a clinic’s appointment book, a club’s fixture list or a company’s accounting software. It works across them, on the problems that otherwise need a person to chase information and coordinate a fix by hand.

    Try one

    A doctor calls in sick: twelve people are booked in and none of them know. Rook finds who is affected, finds colleagues with room, moves each appointment and tells each person. Anyone it cannot reach is left exactly where they are and handed to reception, because moving someone who will not hear about it is worse than leaving it alone.

    Things marked done that never happened: a referral, a test result and a prescription the record calls finished. Rook asks the clinic, the pharmacy and the doctor they were meant to reach. Three of the four never happened. The fourth really did, so Rook says so and leaves it.

    A pitch is shut on a Saturday: three matches, six clubs and three referees. Rook finds which pitches are open, moves each match, puts an available official on the one whose referee is away, and tells both clubs. A club whose group chat is dead keeps its match where it is.

    The same engine on infrastructure: a contractor’s API key still running two services, a service failing right after a change, a live key found in a repository. Same investigate, approve, verify, prove.