A QA audit is worth doing when it supports a concrete decision: a release, a project handover or a process change. The better the start is prepared, the less time goes into gathering context and the more goes into actual testing.

1. Name the decision the audit should support

“Check the app” is not enough. Better: “Can we release the new checkout next week?” or “Should we accept the project from the vendor?”. The decision defines the scope, priorities and output format.

2. Point out the critical journeys

Not everything matters equally. Pick two or three journeys whose failure would hurt users or the business most - for example sign-up, payment or submitting a form.

3. Prepare the environment, accounts and data

Missing access is the most common cause of delay. Before starting, confirm:

  • the test environment address and its stability,
  • accounts with the right roles,
  • test data for the selected scenarios,
  • the browsers and devices that matter.

4. Share what you already know

Known bugs, user reports, requirements or even meeting notes. Missing documentation does not block an audit - we record it as a limitation - but every hint shortens the path to the most important risks.

5. Agree what the outcome looks like

A report should lead to action: confirmed issues with evidence, user impact, repair priorities and explicit scope limitations. Also agree whether blockers should be reported immediately.

A good audit does not promise a bug-free product. It gives an honest picture of risk within the agreed scope.

Want to see what such an outcome looks like in practice? Take a look at our sample report or describe your product and we will help define the scope.