The method
Get started with TSEP
Start with a specific question, a limited scope and one control. The dossier connects what you wanted to check, the retained evidence and what it supports.
Prepare a first evidence dossier
These editorial pointers help prepare the work. Exact requirements remain those of the selected control and protocol version.
- Define the question
Record the objective, selected URLs, date, available access and exclusions. Explain the sample selection; it does not automatically represent the whole website.
- Choose the control and its version
Open the catalogue and record the TS identifier, version and required evidence. Read applicability, expectations and limitations before collecting data.
- Retain evidence and record gaps
Keep original observations with their source, date and tool. Link each item to its URL. Record denied access, missing observations and required human judgments; do not substitute assumptions.
- Explain the outcome and next step
Link each conclusion to evidence and applicable expectations. Retain unknowns and limitations. Identify evidence to complete or corrections to review, then share the dossier with the person responsible for review.
Read the outcomes
Read an outcome together with its control, version, scope and evidence. The four codes are not a whole-site score.
- C
- Expectations satisfied
All applicable expectations are satisfied in the assessed scope, with the required evidence. This outcome does not extend to unassessed URLs.
- NC
- Evidenced contradiction
Evidence establishes a contradiction of an applicable expectation. The finding should identify the expectation and evidence involved.
- NT
- Not tested or inconclusive
Available material does not support a conclusion. Missing evidence or unavailable access remain visible; they do not become C or NA.
- NA
- Non-applicability established
Required evidence establishes that the control does not apply to the scope. Lack of access is not enough to declare it non-applicable.
Use the protocol tools
0.1.0-draft.28 : 44 documented controls, including 12 with executable rules. The catalogue presents what this version documents; it does not run checks on your website.
Commands, expected inputs and prerequisites are described in the distribution. For replay, use the tools and dossier format of the version that produced the outcome. Synthetic examples explain the workflow; they do not describe a real audit.
View the distributed versionTSEP Control: the public beta
The hosted beta supports a bounded HTTP observation of a public URL with downloadable evidence, and offers a guided TS02 workflow. A simple observation does not produce a TSEP verdict. Google connection remains disabled.
The protocol and application have their own versions. Rules in the protocol do not imply an available application workflow. Each integration retains its engine version; existing dossiers are not silently migrated.