Operations status report template: one status grid, then only what needs fixing

A status report is a short, recurring read on the health of the operations a team runs: sites, suppliers, systems, incidents and the tools people use. Every operation gets a status against thresholds agreed in advance. Green means no discussion. Amber and red get a slide each, an owner and an action.

It is one of the most common reports teams run. Supply health reports, incident reviews and tool adoption reports are all versions of it, and they share one rule: the thresholds decide what gets talked about, not the person building the deck.

The download adds a cover and a how-to slide you delete before presenting.

The thresholds on the appendix slide do most of the work. Write them down once, agree them with the owners, and the colour of each operation is never a debate.

• Agree the thresholds before the week starts. Green, amber and red are set in advance, not chosen when the number comes in.
• Discuss amber and red only. If an operation is green, it gets a line on the grid and nothing more.
• Every red has a cause, an owner and a date. A red with no action is just a colour.
• Keep last week's actions on the slide. Closing them in public is what keeps them closed.
• Send it before the meeting. People read the grid in advance, and the meeting starts with the red.

• Every operation shown in full every week, so the red one is on slide 14.
• Thresholds that change when a number misses them.
• Status colours with no numbers behind them, so nobody can tell how close amber is to red.
• A report built by hand from five systems, which arrives after the meeting it was for.

A status report has a fixed structure, fixed thresholds and numbers that change every week, which is the kind of deck Rollstack keeps current.

In Rollstack:

1. Import this template into your own brand, or start from your current deck.
2. Connect the data behind each chart, from any data source: your warehouse, BI tools, spreadsheets or the systems your operations run on.
3. Set the thresholds once, so each operation's status follows its numbers.
4. Schedule the refresh for Monday morning, after your weekly data lands.
5. For one report per site or region, a Burst creates one version each from the same template, with only that site's numbers.