How a review runs

A programme review is not a tour of charts. It is a short project with files, interviews, and a written argument. This page is the sequence we already use so you can judge whether it fits how your team actually works.

Before anything is counted

We send a one-page request: copies, calendars, the event dictionary, and who is allowed to speak for engineering. If a vendor contract forbids sharing raw logs, say so on day one. We can often work from aggregated tables, but we cannot invent delivery counts you do not have.

The reading weeks

Two of us read. One tracks language and timing — Raya, Deepavali, payday Fridays, late-night service messages. The other tracks whether the same person can appear as delivered twice. We write questions in a shared list you can answer in fragments; we do not expect a perfect data room.

The draft you are allowed to dislike

The draft is numbered findings, not a score. You mark what is factually wrong. You may also mark what is politically awkward. We will not delete a finding because it is awkward, but we will rephrase so the person who has to present it can survive the meeting.

The readout

Two hours. Phones down if we are in Petaling Jaya. We walk the findings in the order a sceptical finance partner would ask them, not in the order the vendor’s export is arranged. If you need a second hour later for engineering only, that is scheduled separately and billed from the same quote.

After we leave

You keep the PDF and the glossary. We do not retain copies of your logs beyond 90 days unless a follow-on month of office hours is already booked. If you want us back for a single campaign, that is a campaign readout, not an informal continuation.

When you are ready, request a programme review.