> ## Documentation Index
> Fetch the complete documentation index at: https://docs.marcus.involvecloud.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Room Readiness

> Switch rooms off overnight, and prove each one is ready before the day starts.

Room Readiness does two separate jobs. Use either, or both:

* **Power schedule** switches your rooms off each evening and back on each morning, saving energy and giving the equipment a daily restart.
* **Readiness checks** run a **test routine** in each room at a set time, to prove it actually works: the displays are on, the codec is online, the microphones hear audio. Problems are found before the first meeting rather than during it.

A room can have either, both or neither. Each morning you get one digest covering both.

Open **Room Readiness** in the sidebar. It has three tabs: **Power schedule**, **Readiness checks** and **Settings**. You need **View Room Readiness** to see it, and **Manage Room Readiness** to change anything.

## Power schedule

### How a night runs

For each room, on each scheduled day:

1. **Power off** at the power-off time: every device in the room that supports it, such as displays, is switched off.
2. **Power on** at the power-on time.
3. **Warm up**: a short pause while devices boot and report in.
4. **Ready** or **Failed**: the room is ready once every device has switched back on.

If a device doesn't switch back on, the room fails, with the device named. A device that doesn't switch off is recorded in the run, but the night carries on. Devices without power control, such as PDUs and devices monitored by ping, are left as they are.

### Set the schedule

| Setting | What it does |
| - | - |
| **Nightly lifecycle** switch | Turns the power schedule on for every room. Off until you switch it on, so you can set everything up first. |
| **Power off at** / **Power on at** | For example off at 19:00 and back on at 07:30 the next morning, in the timezone on the Settings tab. |
| **Days of week** | The days the cycle runs. On other days rooms stay on overnight. |

Select **Save changes** when you're done.

### Customise a room

The rooms table lists every room by building, with the times it's switched off and on. Select **Customise** on a room (**Edit** once it's customised) and tick **Customise** next to **Power off at**, **Power on at** or **Days of week** to give it its own; leave a field unticked to follow the default.

You can also **exclude** a room up to and including a date. Choose **Exclude until** and a **Reason**, such as planned maintenance or a device awaiting replacement; the reason is required, and the **Note (optional)** is free text. An excluded room is neither switched off nor checked, and has no runs for those days.

Customised rooms show **Customised**, and their button reads **Edit**. Select **Reset** to return a room to the defaults.

### Power schedule by room tag

If you use [room tags](https://docs.marcus.involvecloud.com/admin/room-tags.md), a tag can carry its own **Power off at** and **Power on at** times and **Days**, so every room with the tag shares them. For example, give **Courtroom** a 21:00 power-off for evening sittings.

The **By room tag** card on the **Power schedule** tab lists every tag. Select **Set times** on a tag and tick **Customise** on what it should set; anything unticked comes from the default. **Remove** takes the tag's settings away.

Each part of a room's schedule comes from the room's own settings first, then its tag's, then the default. A room with several tags uses the highest tag in the list that has settings; the arrows set the order, which is the same list as for [readiness checks by tag](#checks-by-room-tag). In the rooms list, a room using a tag's settings shows **From tag**, and its **Customise** dialog shows what it inherits from the tag.

### One-off dates

For a day that differs from the weekly schedule, add a date under **One-off dates** on the **Power schedule** tab. Select **Add a date**, pick the day and the rooms it applies to (one room, the **Rooms tagged** a tag, or **Every room**), and choose:

| On this day | What happens |
| - | - |
| **Closed** | Rooms aren't switched back on that morning, and their readiness check doesn't run. Use it for bank holidays, closures and works. |
| **Open** | Rooms are in use, even on a day the weekly schedule skips (a Saturday sitting). Set **Power on at** and **Power off at** for that day only (a late finish, an early start), or leave them blank for the room's usual times. The readiness check runs that morning too. |

A room's own date wins, then a date for one of its tags (the highest in the tag order, if several have one that day), then a date for every room. So you can close the whole estate, keep the courtrooms open, and still close one court. Dates are in the organisation's timezone, and an excluded room stays excluded whatever its dates say. Select the bin on a date to remove it; the weekly schedule applies again. You need **Manage Room Readiness** to add or remove dates.

### Defer tonight

If a room is in use this evening, select **Defer tonight**. The room skips tonight's power-down and returns to its schedule tomorrow; its readiness check the next morning is unaffected. You need **Defer tonight's power-down**, which operators have by default.

To do it for many rooms, filter the rooms list by [room tag](https://docs.marcus.involvecloud.com/admin/room-tags.md). A bar appears with **Defer tonight**, **Exclude…** and **Clear exclusions**, which apply to every room with that tag. The rooms list on **Readiness checks** has the same tag filter.

### Overnight status and alerts

A device that the power schedule has switched off shows as **Switched off**, not offline, from power-off until the morning warm-up is over. A device that stays reachable in standby keeps showing **Online**.

It also doesn't raise an offline alert while the room is powered down, or during the morning warm-up. If it's still offline after the warm-up, it alerts as usual, within 30 minutes, and the run shows which device didn't come back. Devices that weren't switched off, including any whose power-off failed, alert overnight as normal.

A run that fails raises one alert for the room, through the same channels as other alerts (email, Teams, ServiceNow). A failed readiness check raises **Readiness check failed**, naming the steps that failed and why; a failed power cycle raises **Power cycle failed**, with the reason. If the room fails again before the alert is resolved, the same alert is updated rather than a new one raised. The next run that passes resolves it, and closes any ServiceNow incident with it.

## Readiness checks

### Set the default check

| Setting | What it does |
| - | - |
| **Readiness checks** switch | Turns checks on for every room. You need a routine first. |
| **Default routine** | The test routine every room runs unless it has its own. See [Test routines](https://docs.marcus.involvecloud.com/portal/test-routines.md) to build one. |
| **Run at** | When the check runs, for example 07:45, in the timezone on the Settings tab. |
| **Days** | The days it runs. |

Select **Save changes** when you're done.

If a room's power cycle is still running at its check time, for example still warming up, the check waits for it to finish, for up to 30 minutes, so a room is never tested while it's still starting up. The run records how long it waited.

### Checks by room tag

If you use [room tags](https://docs.marcus.involvecloud.com/admin/room-tags.md), you can give a tag its own check, so every room with that tag gets it without setting rooms up one by one. For example, give **Courtroom** the "Court AM check" at 07:30 on weekdays, and every courtroom runs it, including rooms tagged later.

The **By room tag** card lists every tag. Select **Set a check** on a tag and tick **Customise** on the **Routine**, **Run at** time or **Days** it should set. Anything you leave unticked comes from the default. Select **Remove** to take a tag's check away; its rooms go back to the default, or to another of their tags.

Each part of a room's check comes from the first of these that sets it:

1. the room's own settings (**Customise** on the room);
2. its tag's check;
3. the default.

**A room with several tags** uses the highest tag in the **By room tag** list that has a check. Use the arrows to put the tags in order. Only that one tag applies: if it doesn't set the time, the room uses the default time, not another tag's.

In the rooms table, a room using a tag's check shows **From tag** and the tag's name.

### Customise a room

The rooms table shows each room's routine, time and days. Select **Customise** to give a room its own **Routine**, **Run at** time or **Days**, such as a different routine for a video-conferencing room, or a later time for a room that powers on later. Once a room is customised, its button reads **Edit**. A room's own routine is shown in darker text than the default. Select **Reset** to return it to its tag's check, or the default.

A room whose check time falls while its power schedule has it switched off shows **Room switched off then**. Move the check after the power-on time, or it will fail.

### Run now

Select **Run now** on a room to run its check straight away. Use it to check a room after a fix, or to try out a routine. You're taken to the run to watch each step's result arrive.

## Settings

Settings shared by both:

| Setting | What it does |
| - | - |
| **Timezone** | The timezone the power schedule and readiness checks run in. |
| **Helpdesk email** | Copies the morning digest to your helpdesk, so incidents are picked up without anyone forwarding them. Optional. |
| **Morning digest** | Select **Send test digest** to send one now and check who receives it. |
| **Keep run history for (days)** | How long runs are kept, from 30 to 365 days. Runs older than this are deleted automatically, with their step results. |

## Check the results

Select **View runs**, on any of the three tabs, for the run history: one row per room for each power cycle and each readiness check, with its type, when it was scheduled, its status, and how long it took. A power run's duration is how long the room took to be ready after power-on; a readiness run's is how long its routine took. Filter by date, room, type and status.

To see one room's results, open the room from **Places** in the sidebar, or filter **Devices** to it. A **Room Readiness** card above its devices shows the latest readiness check and overnight power cycle, which steps failed and why if the latest check failed, and a mark for each check over the last 14 days. Select any of them for that run, or **All runs for this room** for its full history. You need **View Room Readiness** to see the card.

Select a run for its details: how far it got, and every step, with what it checked, on which device, what it expected, what it found and any error. For a power run, the steps are which devices switched off and back on.

Each step's result is summarised in a line per device: what it looked for (such as `Judge_Level > -4`), and what it found (such as `online` or `Succeeded`). Select **Raw** under a result for everything the step recorded, including each device's raw reply.

For **Expect status** and **Check metric** steps, each result says where its reading came from. **Fresh poll** means the device was polled for that step, which is the usual case. **Last report, 42 s old** means the step used the device's last regular report instead: ATEN PDUs always do, and so does any device whose fresh poll didn't come back within 60 seconds. **No reading** means no reading was available at all. A last report more than two minutes old is highlighted, because it may predate what the step was checking, such as a power-on or a reboot.

To keep or share a run's results, select **Download PDF** on the run. The report shows the room and its place, whether it passed, when it ran and how long it took, why it failed, and every step's result. It's available once the run has finished.

| Status | Meaning |
| - | - |
| **Ready** | The room came back on (power), or every step passed (readiness). The status filter calls this **Succeeded**. |
| **Failed** | A device didn't come back, or a step failed. The run shows which and why. |
| **In progress** | Running now. |
| **Pending** | Scheduled, or waiting for the room's power cycle to finish. |

### Export

Select **Export CSV** on the run history to download the runs in your current filter, with one row per step and the run's details, including its type, repeated on each row, ready to pivot in a spreadsheet. Runs with no steps still get a row.

### The morning digest

Each morning, 30 minutes after the later of the power-on time and the readiness check time, a summary is emailed to every enabled email channel in [Notifications](https://docs.marcus.involvecloud.com/admin/notifications.md), and copied to the helpdesk address if you set one. It has a section for the power schedule and one for readiness checks.

### Through the API

Integrations can read the same results through the Public API: each room's readiness check and its latest power and readiness runs, every run with its type, and every step. Create a token with the **Read Room Readiness** scope; see [API tokens](https://docs.marcus.involvecloud.com/admin/api-tokens.md) and the API reference.

Updated 06 Nov 2026 14:07 · page 78bd227


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.