A regulatory watch is only as good as its ability to tell one kind of document from another. A consultation asking for your opinion, a guidance telling you what supervisors expect, and a sanction naming a firm that got it wrong all land in the same inbox, yet each demands a different response, a different owner, and a different deadline. Treating them as one undifferentiated stream of "regulatory news" is how teams miss the item that actually mattered. This is a field guide to the main document types a European watch has to distinguish, and what each one really means for the people who read it.
Why the type is the first thing to read
Before the subject line, before the regulator, the document type sets the stakes. It tells you whether you are being invited to comment, warned to prepare, instructed to comply, or shown an example of enforcement. Get the type wrong and everything downstream is wrong: a consultation misfiled as a binding rule wastes effort, and a sanction dismissed as background reading misses a live risk signal.
Across roughly 85 European regulators, the labels are not perfectly standardised. A "communication" from one authority resembles a "communique" from another, and "guidance" from a data-protection authority carries different legal weight than "guidelines" from a banking supervisor. Still, a workable taxonomy holds up well in practice. The categories below map closely to the document types Seqlense Doc uses (sanction, consultation, guidance, opinion, regulation, report, qa, communique).
The core document types
Consultation. The regulator proposes something and asks for feedback, usually within a fixed window. Consultations are the earliest reliable signal that a rule is coming. They matter because the text you comment on today is often close to the text you must obey in eighteen months. Owner: policy and public-affairs, with input from the teams who will operate the rule.
Guidance and guidelines. These explain how the regulator expects existing rules to be applied. In the EU, guidelines from the European Supervisory Authorities carry real weight through a "comply or explain" mechanism: national competent authorities must confirm whether they comply, and firms are effectively held to them even though a guideline is not a regulation in the strict sense (see Article 16 of the EBA founding Regulation and the EBA compliance framework). Treat guidance as "do this," not "consider this."
Opinion. A reasoned position on a specific question, often addressed to other authorities or to the Commission. Opinions rarely bind directly, but they shape supervisory expectations and preview how a regulator reads an ambiguous provision. They are early-warning material.
Regulation. Here the label means a legal act or the transposition of one: hard law with a defined application date. This is the category where dates, thresholds, and scope must be captured precisely, because the compliance clock is real.
Sanction. An enforcement decision against a named firm or individual. Sanctions are the most concrete guidance you will ever get, because they show exactly which conduct crossed the line and what it cost. Read against your own controls, they are a free gap analysis. Owner: risk, compliance, and the relevant business line.
Report and Q&A. Reports (thematic reviews, market studies, annual priorities) reveal where supervisors are looking next. Q&A documents answer recurring practical questions and are often the fastest route to a defensible interpretation. Neither is binding, but both are strong indicators of direction and tolerance.
Communique. Short public statements: press releases, warnings, coordinated announcements. Individually light, collectively useful as a pulse on regulator attention.
A quick reference
| Type | Binding? | Primary use |
|---|---|---|
consultation |
No | Shape and anticipate a future rule |
guidance |
Comply or explain | Know what supervisors expect now |
opinion |
No | Read supervisory intent early |
regulation |
Yes | Track hard deadlines and scope |
sanction |
Yes (to the party) | Benchmark your controls against enforcement |
report / qa |
No | Spot direction and get interpretations |
communique |
No | Monitor attention and warnings |
Turning types into a workflow
Once the type is explicit, routing becomes simple. Consultations go to policy with a diary date for the response deadline. Regulations open a project with an application date. Sanctions trigger a control review. Guidance and Q&A update your internal interpretation notes. Reports feed horizon-scanning. The type decides the owner, the SLA, and the artefact you produce.
This is also where filtering earns its keep. A watch that lets you slice by document type, source, and language turns a firehose into a queue. In Seqlense Doc the same taxonomy is queryable through SEQQL, so a DPO can ask for doctype:guidance source:cnil lang:fr while a markets team pulls doctype:consultation source:esma, each seeing only what their mandate requires. The mechanism matters less than the habit: read the type first, then decide what the document is asking you to do.