QA Quality Report Deck

About this template

Eight slides for the monthly quality report

The short deck a QA function takes to a monthly review. Eight slides is one body section plus the standard closing set, which is the right size for a standing agenda item rather than a project readout. The argument it makes is the one on slide 5 – a defect caught before release costs a fraction of the same defect caught after – and the closing line, “We find it before the customer does”, is what the whole report is measured against.

Four agenda lines, one body pair

Slide 2 runs defect status, catching it before release and catching it after, key metrics, trend analysis. Only the first line carries a divider and a body slide, on slides 3 and 4. The comparison is slide 5, the cards slide 6, the bars slide 7, and the closing slide 8. Escaped defects, test coverage and the release criteria are not built as their own slides, so duplicate the slide 3 and 4 pair for each one you need, continue the SECTION numbering, and add the matching agenda lines. Most teams need at least the escaped-defect pair, because the escape rate appears as a card on slide 6 with nothing behind it otherwise.

The body slide

Slide 4 carries “218 new – 196 closed”, “87 open, 6 of them critical” and “4.2 days on average to close one”. The three lines are flow in, flow out and the backlog left over, which is the only combination that shows whether the queue is growing. Two hundred and eighteen against 196 means the backlog grew by 22 this month, and that arithmetic is what a reviewer checks first, so keep both numbers rather than reporting a net. Splitting the 87 open by severity is what stops the count being read as one undifferentiated pile – six critical items is a different conversation from 87 minor ones.

The metric cards and the trend bars

Slide 6 holds “New defects” 218, “Open defects” 87, “Escape rate (%)” 6.4 and “Automated (%)” 68. The first two repeat slide 4, so edit them as a set. The escape rate is the one number on this deck that measures QA itself rather than the product, and it needs its basis printed somewhere: escaped defects divided by total defects found in the same release window. Slide 7 falls 32, 27, 21, 14 across Jan to Apr and reads as escaped defects per month, so it is the trend behind the 6.4. Since a falling bar is good news here, keep a line in the label saying so, and replace “Unit: index” with the count you are plotting.

The comparison slide

Slide 5 sets “Found before release” against “Found after release”. “4.2 days to fix on average”, “No customer notice needed” and “Verified inside the regression suite” face “Hotfix release and overnight response”, “Customer notice and compensation review” and “A prevention report to write”. The pairing is cost, not virtue: the right-hand column is three pieces of work that only exist because the defect escaped. It is the slide to use when automation or a longer test window needs funding.

What goes wrong

• Reporting closures without new arrivals. A 196 with no 218 beside it hides a backlog that grew.
• Quoting 68% automated with no denominator. Automated share of what – regression cases, or all cases? The two numbers differ by a lot.
• Letting the escape rate stand alone on the card. Without the escaped-defect section behind it, 6.4% is a number nobody can check or act on.