CTOCoach

CTO board update template

Fill in your quarter and get a one-page engineering update in the five-block structure boards can read in two minutes: headline, progress, risks, people and spend, and the ask. Copy it as Markdown or print it to PDF. No signup, nothing stored.

By the CTO Coach Team · Last updated 2026-10-11 · Open a prefilled example

Everything stays in this tab and the page address. Nothing is sent or stored.

1. Quarter and outcomes shipped

2. Delivery metrics (all optional)

Use your own numbers and say how you measured them. Definitions follow the DORA guide.

How often you ship a change to production.

Time from a change being committed to it running in production.

Share of deployments that need a fix, rollback or hotfix. Enter a number.

How long it takes to recover when a deployment causes a failure.

3. Incidents and top risks

4. People, spend and the ask

100 means on budget.

Red, amber and green thresholds (yours to set)

These defaults are placeholders, not industry benchmarks. Set them to what your board agreed at the start of the year. A block takes the worst colour of its signals.

Fill in at least one outcome, risk, headcount or spend figure, or load the example, to see your one-page update.

How to use this in a board meeting

  1. Send it before the meeting. Share the one-page memo as a pre-read so the meeting time goes to questions, not to reading out status.
  2. Open with the headline. Say the first sentence aloud, then stop. If it is amber or red, say so and name the area; a board that hears bad news from you first trusts the green.
  3. Walk the colours, not the bullets. Spend most of your time on the blocks that are not green. Agree the thresholds with your CEO ahead of the quarter so no colour is a surprise.
  4. Make one ask. A decision with a date attached gets a decision. A list of wishes gets a nod. If you have no ask, say that, and use the time for the top risk instead.
  5. Keep the slides to six. Use the slide titles under the memo only if the format demands slides. Put anything else in an appendix.

For the reasoning behind the structure and how to translate engineering into board language, read board-ready CTO communication. If you are preparing your first readout after joining, the 30-60-90 day plan generator includes a readout outline, and the tech debt calculator writes a one-line summary you can paste into the risks block.

How the colours and metrics work

Each block checks a few signals against thresholds you can change under the form. Progress looks at the share of your planned outcomes delivered (partly delivered counts as half) and the change fail rate. Risks looks at high-severity risks, customer-impacting incidents and whether every risk has a mitigation and an owner. People and spend looks at spend against budget and headcount against plan. A block shows the worst colour of its signals, and the headline shows the worst of the three. The defaults are placeholders, not benchmarks.

The four delivery metrics use the names and definitions in the DORA guide. DORA now also lists a fifth measure, deployment rework rate, which you can add to the memo by hand if you track it. Metrics are optional: leave a field empty and it is left out of the memo.

Frequently asked questions

What should a CTO include in a board update?

Five things, in this order: a one-sentence headline on whether engineering is on track, progress against the plan with the business effect of what shipped, the top risks with a mitigation and an owner each, people and spend against plan, and the single decision or ask you need from the board. Everything else belongs in an appendix or in your answers to questions.

How long should a CTO board update be?

One page, sent as a pre-read, plus a few slides if the board meeting format requires them. A page forces you to choose the three outcomes and three risks that matter. If a board member wants more, you can open the detail, but you should not start there.

Which engineering metrics should go to the board?

Fewer than you track. Pick the delivery measures that explain whether the plan is on track, such as deployment frequency, change lead time, change fail rate and failed deployment recovery time from the DORA guide, and show them as a trend with one sentence on what they mean for the business. Keep team-level and individual measures out of the board pack.

How are the red, amber and green colours decided?

By thresholds you set, not by an industry benchmark. Each block looks at a few signals, such as the share of planned outcomes delivered, the change fail rate, customer-impacting incidents, high-severity risks, spend against budget and headcount against plan. The block takes the worst colour among its signals, and the headline takes the worst of the blocks. Agree the thresholds with your CEO before the quarter starts so the colours are not a surprise.

Is my data stored or sent anywhere?

No. The template runs in your browser. What you type lives in this tab and in the page address, so you can bookmark or share the link. Anyone with the link sees the text in it, so do not put confidential figures in a link you share.

Sources

  1. DORA's software delivery metrics: the four keys dora.dev, Current

How we source and check figures: Methodology.