# Exploratory Test Charter

Version 2.0 · Updated 2026-09-21 · Testing

Define the purpose, scope, risks, and evidence to capture during exploratory testing.

Adapt this template to your intended use, applicable requirements, and approved procedures.

## When to use it

Exploratory testing is suitable but needs a clear purpose and record.

## Information needed before starting

- Approved intended use and functional-risk assessment
- Available supplier and local evidence
- Test environment, representative data and competent reviewers

## Field instructions

- **Charter:** State the exploratory objective, important risk and questions the session should investigate. Define the session boundary.
- **Configuration:** Record the tested application, tenant, version and local rule/configuration identifiers so observations can be reproduced.
- **Scope:** List included functions, users and record states, and identify the paths outside this session.
- **Risks:** Identify credible failures that the session should challenge, with their potential effects on the process or record.
- **Starting conditions:** Record the initial data, user roles, system state and setup required before exploration begins.
- **Activities:** Describe the planned interactions and challenges. During execution, record what was actually explored and any changes to the plan.
- **Evidence:** Identify attributable observations, data and record IDs, logs and relevant captures needed for another reviewer to understand the results.
- **Findings:** Record observed behavior, important coverage and anomalies contemporaneously. Distinguish observations from interpretations and link defect records.
- **Follow-up:** Assign each unresolved finding or additional check to an owner and due date; state the completion evidence required.
- **Conclusion:** Record the supported decision, restrictions, unresolved issues and rationale. Identify the accountable reviewer/approver and dated evidence under your procedure.

Could a reviewer understand the coverage and findings without watching the session? Do not invent a pass/fail history after the fact.

## Completed fictional example

Fictional teaching example; replace its values with your own assessed facts and evidence.

| Field | Completed example |
| --- | --- |
| Charter | Explore CAPA reassignment and ownership |
| Configuration | Test tenant 8.4; route configuration RC-12 |
| Scope | Active, inactive, unauthorized, and unavailable assignees |
| Risks | Orphaned records, bypassed escalation, unauthorized reassignment |
| Starting conditions | Open CAPAs in investigation and effectiveness review |
| Activities | Reassign, cancel, reopen, attempt unauthorized updates, inspect resulting ownership |
| Evidence | Record IDs, role combinations, state changes, logs and relevant screen captures |
| Findings | One inactive-user path leaves task unowned |
| Follow-up | Defect D-07; correction and targeted regression before release |
| Conclusion | Ownership control is not yet supported for all assessed paths |

## Blank template

System / record ID: ____________________

Prepared by / date: ____________________

Required review / approval under local procedure: ____________________

| Field | Your entry |
| --- | --- |
| Charter | ____________________ |
| Configuration | ____________________ |
| Scope | ____________________ |
| Risks | ____________________ |
| Starting conditions | ____________________ |
| Activities | ____________________ |
| Evidence | ____________________ |
| Findings | ____________________ |
| Follow-up | ____________________ |
| Conclusion | ____________________ |

## Related guidance

- [Choose a testing approach](https://csvtocsa.com/learn/foundations/testing)

- [Open the test strategy template](https://csvtocsa.com/templates/test-strategy)

Canonical page: https://csvtocsa.com/worksheets/test-charter