Formal Review
A formal review is a structured static testing activity that follows a defined process with assigned roles, documented results, and specified entry and exit criteria.
“A review that follows a defined process with a formally documented output.”
(Definition reproduced from the ISTQB Glossary. Copyright belongs to ISTQB.)
View the complete ISTQB GlossaryWhat is Formal Review?
Formal reviews systematically examine work products to identify defects, improve quality, and ensure compliance before implementation or release.
Defined process: Formal reviews follow documented procedures.
Assigned roles: Moderators, reviewers, authors, and recorders have specific responsibilities.
Objective outcomes: Results are documented and tracked for follow-up.
Real World Example
A regulated product team is preparing a release where Formal review appears in reviews, test design conversations, or defect triage rather than as an isolated glossary word.
The risk is that the team treats Formal review as interchangeable with nearby ISTQB terms. That makes test scope blurry and can lead to weak evidence for the release decision.
The tester anchors the discussion in the official definition, asks where the concept appears in the product, and designs examples that show the difference between Formal review and similar ideas.
The page becomes useful in practice because Formal review is connected to a specific testing decision, not memorized as a detached definition.
Practice Questions
Question 1
Which statement BEST describes Formal review in the context of ISTQB terminology?
Question 2
A tester needs to explain Formal review to a non‑technical stakeholder. Which approach is MOST appropriate?
Test your knowledge with real ISTQB-style questions
You’ve learned Formal Review. Test your understanding with topic-specific questions in our Mock Exams.