SCOUTz / What Changed

How does an MSP show a client what changed since the last review?

Pin a scan as the baseline, then use the QBR play to compare the Master Report with it. Findings can be re-issued from stored evidence for 30 days; new data requires a new scan.

By Steve Copeland

What it does

  1. Pin any scan as a baseline.
  2. Open the QBR play.
  3. Use Changes since the last review to compare the Master Report with the baseline.
  4. Re-issue findings from stored evidence.
  5. Keep re-issued findings current for 30 days.
  6. Run a new scan when you need new data.
Screenshot placeholder for SCOUTz What Changed — product screenshot not yet supplied
Screenshot placeholder — What Changed. Product screenshot not yet supplied.

Illustrative example

· Not customer data

The MSP pins 1 scan as the baseline and uses Changes since the last review in the QBR play to compare it with the Master Report.

Questions MSPs ask

Which scan can be the baseline?

Any scan can be pinned as a baseline.

Where is the comparison?

The QBR play includes Changes since the last review, comparing the Master Report with the baseline.

Does re-issuing findings collect new data?

No. Findings are re-issued from stored evidence. New data needs a new scan.

How long do re-issued findings stay current?

They stay current for 30 days.

Read the SCOUTz methodology →

Read site privacy