How a health review actually runs

The method is a sequence, not a product. It exists so a review does not turn into a tour of graphs. Each stage has a document or a sitting attached.

What we refuse during a sitting

We will not install software. We will not take the pager “just for the week”. We will not rewrite your alert rules in the live system. If a vendor representative wants to attend the readout, we ask them to wait outside; the brief is for the people who own the application.

Timing

Twelve to fifteen working days is typical for one application. Restricted records add time. A severity-one incident in your room pauses the calendar; we do not bill extra for the pause unless it stretches past six weeks.

When you are ready to date a sitting, send the application name. The rate card explains how the figure is built.

Briefing

A call of about forty minutes. We name the application, the environments in scope, who owns on-call, and where the incident records live. You leave with a date range for observation and a list of what to have on the table: ninety days of tickets, alert history, and two hours with the pager owner.

Observation

Three to five working days. We sit in your operations room or join remote hand-offs. Callum watches silences and roster changes. Rowan repeats short interviews rather than one long workshop. We do not require a war-room. Ordinary hours are more useful than a staged incident.

Record reading

Mei-Ling reads the incident set in chronological order and matches pages to tickets. The aim is application health monitoring insights with timestamps: what fired, what stayed quiet, what an operator wrote at 2 a.m. that later vanished from the polished write-up.

Brief and readout

The written health brief comes first. The readout is a conversation through that document, on Eagle Street or remote, with the on-call lead in the room. We do not walk through a product. We walk through sentences you can disagree with.