Reference · Level 2 · one of the five
Operations: the deployment board that knows what is covered tonight
Who is deployed where, for today's shift and tonight's, what has been covered and what is short - then attendance that matches the roster, and incident reports written up in the same place they happen.
Part of the OwnYourAI corporate AI training reference. Who is on which site, today and tonight - the deployment, attendance and incident board an operations team lives on.
A quick look at what you can build: three screens showing the shape of the system and what it does, on illustrative data. No client's system and no client's data is shown. It is fair to want to see the work before you commit a seat.
Three screens
What the people who use it see
Same system, three moments in a working week.
Why the AI version
Why the AI version of operations
A deployment board you already have still needs somebody to fill it in.
- What it costs you now. When an officer goes on leave or MC, the roster is rebuilt by hand, and the uncovered post shows up on the day, in a phone call.
- With the AI version. One sentence - cover next week's shifts and show me what is not covered - and the roster comes back with the gap already marked, before it happens.
- The part your current software cannot do. It holds the rows. This reads the leave, the licence expiry and the post requirements, and does the covering.
Behind the screens
What the course actually builds
The screens are the easy part to look at. This is the part that decides whether the system survives its first month - and the software and the data are the company's own. The machine under it is one we provide or recommend, so there is no hardware to buy; owning the whole thing is Level 3.
- One board, both shifts. Day and night in the same view, so a gap is found before it is a problem.
- Roster against reality. Attendance is compared with what was planned, so the difference is visible the same day.
- Reports that hold up. An incident is written in the five fields an assessor or a client actually reads.
- A person owns each exception. An uncovered post or a missing clock-out is assigned, not just coloured red.
Session by session
The 8 sessions: building the operations board
Every session is online learning at the person's own pace, with a scheduled live touchpoint inside it and a trainer present. Each one ends with something your company keeps: 24 hours in total for L2.
| # | The session | What your team does with it | What your company has at the end |
|---|---|---|---|
| 1 | Pick the job, and count the hours | The nightly coverage board, the incident report and the timesheet chase are put side by side, with the time each one costs the company every week. | One job chosen, with the hours per week it costs now written down. |
| 2 | Map the plan and the reality | The deployment plan, the clock-in records, the site list and the incident form. The team marks what the agent may read and what it may never touch. | A one-page map of where the plan and the attendance records live, plus the do-not-enter list. |
| 3 | Write the brief, and the three limits | What the agent is told to do — hold the board, flag the gaps, draft the incident report — and what it may never do. | A signed brief: it never marks a post covered because a plan says so, it never closes an incident without a person, and it never touches pay rates. |
| 4 | Build the board | Day and night in one view, with the roster compared against what actually happened on the company's own data. | A first working version of the board, running on the company's own plan and attendance records. |
| 5 | Test it against a real night | The team runs it against tonight's deployment and lists every gap it missed and every false alarm it raised. | The difference list against one real night, with a person named against each gap. |
| 6 | Guard it | Who may see the board, what an assessor or a client may read, what is logged, and what always waits for a human decision. | The access list, the log, and the escalation rule. |
| 7 | Put it into the handover | Who updates the plan, who clears the exceptions, and what the morning handover reads from it. | The nightly and morning routine on one page, with a named owner for each step. |
| 8 | The build assessment | A real night's board is run live in front of the trainer — gaps and all — and the team says what it checked. | A running operations board: the agent, its brief, its limits, its log, and a named owner. |
Where these screens come from
A quick look at what you can build: three screens showing the shape of the system and what it does, on illustrative data. No client's system and no client's data is shown.
Built in the company's own accounts, on the company's own documents, with its own staff logins: the software and the data stay with the company. The machine under it is one we provide or recommend - no hardware to buy. Owning the whole thing is Level 3.
We keep it fair: your documents, your accounts, your numbers.
Next step
Start with the free AI Readiness Report
Tell us the team and the work. We send back a written report on what to build first, what it would take, and what it would change - before you commit to a single seat.
No fee is quoted until you ask for one.