Exploratory Testing Charter Template — With 8 Examples (2026)
The exploratory testing charter template used by session-based teams at Microsoft and Shopify. Includes 8 real charters, a 90-minute session log format, and how to report findings to product.

Last updated 2026-07-20 · 10 min read · By Avinash Kamble, reviewed by Priyanka G.
Scripted tests cover what you already know can fail; exploratory testing finds the unknowns. James Bach's session-based test management (SBTM) formalizes it: a charter, a 90-minute session, a debrief. This guide gives you the exact charter template we use plus 8 charters you can lift for common features.
Key takeaways
- The 4-line charter format that fits on a Post-it.
- A 90-minute session log template with time-boxing.
- 8 ready-to-run charters for login, search, checkout, and API flows.
- How to fold findings back into automated regression.
1. The 4-line charter format
EXPLORE: {area or feature}
WITH: {resources, personas, data}
TO DISCOVER: {information the team needs}
TIME-BOX: 60 or 90 minutesExample: Explore the coupon field WITH expired, malformed, and unicode coupon codes TO DISCOVER validation and error-handling gaps. Time-box 60 min.
2. Session log — the SBTM template
Charter: {above}
Tester: Priyanka G.
Duration: 60 min (setup 8, testing 42, bug filing 10)
Coverage: coupon field, cart totals, order summary
Bugs: QA-2411, QA-2413
Issues: staging DB slow (blocked 2 checks)
Notes: unicode coupons cause 500 in v2 API, not v13. Eight ready-to-run charters
- Login — WITH SSO, magic-link, expired sessions TO DISCOVER auth race conditions.
- Search — WITH empty, unicode, 5k-char queries TO DISCOVER escaping and pagination bugs.
- Checkout — WITH declined cards, 3DS, zero-total orders TO DISCOVER payment state machine issues.
- Signup — WITH disposable emails, plus-addresses, and Cyrillic names TO DISCOVER validation gaps.
- Upload — WITH 5GB, 0-byte, and executable files TO DISCOVER size and MIME checks.
- API auth — WITH expired JWTs, missing scopes, replay tokens TO DISCOVER 401/403 consistency.
- Notifications — WITH timezones, DST, unsubscribed users TO DISCOVER delivery correctness.
- Admin panel — WITH role escalation attempts TO DISCOVER authorization holes (see our security testing guide).
4. Feeding findings back into regression
Every reproducible bug from an exploratory session gets a matching automated test in your Playwright or Selenium suite so it never regresses. Cross-reference with your regression strategy. The canonical SBTM paper is Bach & Bolton's SBTM primer.
Frequently asked questions
1.How long should an exploratory session be?
2.Can exploratory testing replace scripted regression?
3.Who writes the charters?
4.Do I need SBTM tooling or is a spreadsheet enough?
Practice these questions
Run a live QA mock interview tailored to this topic and get per-skill scoring in minutes.
Was this article helpful?
More from Manual Testing Basics
Test types, defect lifecycle, exploratory testing.
- Career & Interview PrepThe Honest Truth About Manual Testing Salaries in 2026 (Real Data)
- Manual TestingTest Pyramid 2026 — The 70/20/10 Rule Senior QAs Actually Ship
- Manual TestingHow to Write Test Cases for a Login Page (with Examples)
Keep building your QA edge
Pillar guides- Manual Testing Complete GuideSoftwareTestPilot's manual testing walkthroughEnd-to-end manual testing tutorial — techniques, test cases, bug reports, exploratory charters.
- Manual Testing Interview Q&Athe full manual QA interview prep pack150+ manual testing interview questions with model answers, from freshers to leads.
- QA Practice HubSoftwareTestPilot's practice labsHands-on labs — Selenium, Playwright, API, SQL exercises with sample apps and solution walkthroughs.
Continue reading

What Is Software Testing? The Complete 2026 Guide for QA Engineers
16 min read
Types of Software Testing — Functional vs Non-Functional (25+ Types Explained, 2026)
18 min read
Software Testing Life Cycle (STLC) — 6 Phases with Entry & Exit Criteria (2026 Guide)
14 min readRelated concepts, tools & standards around Software Testing Fundamentals
A quick reference of the people, companies, frameworks and technologies most often mentioned alongside Software Testing Fundamentals in real QA teams — useful when you're mapping a learning path, preparing for interviews, or scoping a new project.
Join the QA Community
Connect with fellow testers, share job leads, and get career advice.
Stop Reinventing the Wheel. Upgrade Your QA Arsenal.
Take your testing skills from beginner to Lead Engineer. Supercharge your daily workflow with our premium digital resources.
- Ready-to-use testing strategy templates
- Advanced API & UI automation guides
- ⏱️ Save 10+ hours a week on test planning
Discussion
Ask a question, share your experience, or correct us. Be kind — real people are reading.