PreBrief and PostTest: The Meetings That Prevent Retest
Two meetings separate test programs that retest from test programs that don't.
Neither takes more than 30 minutes.
The pre-test brief. Before commencing the test, the team aligns: what are we testing today, what's the current configuration, what are the conditions, what are the abort criteria, and who owns what decisions. Everything should be ready to go — this meeting confirms there are no gaps and no issues that would prevent a safe test.
The post-test debrief. Immediately after the test, while memory is fresh: what happened, what was the data quality, were there anomalies, what needs follow-up. If you wait until the test report phase to discuss anomalies, you've already lost critical context. Details fade. Notes get incomplete. Retests happen because nobody documented what actually occurred.
Both meetings are short. Both have a simple agenda. Neither requires a formal presentation.
The teams that skip them don't save time. They spend it later.
Pre-Test Brief Agenda
A pre-test brief doesn't need to be complicated. Five items, 15-20 minutes:
Test objective for today. Not the whole campaign — just today's scope. What test points, what conditions, what data are we after.
Current configuration. Hardware rev, software build, instrumentation status, any changes since the last test. This catches "I thought we were on Build 17 but we're on Build 18" before it matters.
Restrictions and squawks. Any new limitations on the test article or facility. Operating envelope changes. Open items from previous tests that affect today's plan.
Abort criteria and safety. Quick review — what stops the test. Not a full safety brief every time, but a reminder of the key triggers.
Roles for today. Who's calling the shots, who's monitoring data, who's recording. Especially important when team composition changes between test days.
Post-Test Debrief Agenda
Done within an hour of test completion. Four items, 15 minutes:
Did we get what we needed? Were all test points completed? Was data quality acceptable? Any points that need rerun?
Anomalies. Anything unexpected — behavior, data, equipment. Document it now, not next week. Include severity and whether it affects the next test.
Observations. Pilot comments, operator notes, anything that won't show up in the data but matters for interpretation.
Action items. Who does what before the next test. Due dates, owners.
These two meetings create a feedback loop that keeps the test program self-correcting. Without them, problems accumulate silently until they become retests.
The Test & Validation Essentials Bundle includes PreBrief and PostTest guide templates with agenda structures for both meetings.
Get the Test & Validation Essentials Bundle → https://solriseengineering.gumroad.com/l/tier1-testvalidationessential