Green ClaimsProposal statusEU

EU Green Claims Directive Proposal status check workflow

A concrete workflow for checking whether the Green Claims Directive proposal status has changed across OEIL, EUR-Lex, Council records, and Parliament procedure materials.

Use it when updating public Green Claims pages, timelines, trackers, and implementation notes that depend on the proposal's legislative stage.

Back to main artifact Review sources

Author

Sorena AI

Published

May 9, 2026

Updated

May 9, 2026

Sections

Structured answer sets in this page tree.

Primary sources

Cited legal and guidance references.

Publication metadata

Sorena AI

Published May 9, 2026

Updated May 9, 2026

Overview

This workflow checks the Green Claims Directive as procedure 2023/0085(COD), not as an adopted directive with fixed application dates. It tells editors which official records to snapshot, how to reconcile differences between institutions, and what source changes require an update to Sorena content.

Section 1

Start with a dated source snapshot

Create one status snapshot before changing any public copy. Record the check date, the institution source, the procedure reference, the visible status wording, the latest dated event, and the source URL used for each record.

The minimum snapshot should cover the OEIL procedure file, the EUR-Lex procedure page for 2023/0085(COD), the Council document record for ST 11312/24, and the Parliament first-reading record. If one source is unreachable, do not fill the gap from memory; leave that source as unchecked and avoid updating status claims that depend on it.

OEIL snapshot fields: procedure reference 2023/0085(COD), procedure type, stage reached, latest key event, and any Documentation gateway follow-up documents.
EUR-Lex snapshot fields: procedure status, COM document number, CELEX references, latest procedural step, and any new Council or Parliament document identifiers.
Council snapshot fields: Council document number, meeting date, file reference, document title, and whether the document is a general approach, addendum, corrigendum, note, mandate, or final legislative act.
Parliament snapshot fields: document number, adopted text identifier, first-reading date, committee allocation, and whether a newer plenary, committee, or procedure item has superseded the record.

Sources for this answer

OEIL procedure file 2023/0085(COD)

Use OEIL as the primary Parliament procedure-status snapshot because the grounding record identifies the file as 2023/0085(COD) and shows the stage reached in the procedure.

EUR-Lex procedure 2023/0085/COD

Use EUR-Lex to cross-check the procedure reference, Commission proposal number COM(2023) 166, ordinary legislative procedure classification, and linked institutional events.

Council ST 11312/24 general approach

Use the Council document to verify the Council general approach source, document number, interinstitutional file, and meeting date before describing Council-side progress.

European Parliament text adopted at first reading

Use Parliament's adopted text record to verify the first-reading document identifier and the Parliament action dated 12 March 2024.

Recommended next step

Keep Green Claims status pages tied to official records

Use this workflow to update proposal-status copy only after OEIL, EUR-Lex, Council, or Parliament records support the change.

Research workflow

Open Research Copilot

Check EU procedure records and cited source snapshots before changing public Green Claims content.

Explore next step

Talk to Sorena

Discuss Green Claims updates

Review which proposal-status changes affect timelines, FAQs, and implementation pages.

Explore next step

Section 2

Check OEIL and Parliament records first

Open the OEIL procedure file and confirm that the procedure reference is still 2023/0085(COD). Capture the exact status text and the technical-information row for the stage reached. Then check the key-events and documentation sections for a newer Parliament, Council, Commission, or trilogue-related item.

Use Parliament's adopted text only for what it proves: Parliament adopted a first-reading position for TA-9-2024-0131 on 12 March 2024. Do not treat that adopted text as proof that the final directive has been adopted by both co-legislators.

Update content if OEIL no longer says the file is awaiting the Council's first-reading position.
Update content if OEIL adds a Council first-reading position, Parliament second-reading step, approval, signature, Official Journal publication, withdrawal, or procedure closure.
Update content if Parliament replaces or materially amends the adopted-text record, adds a new plenary stage, or changes responsible committee or rapporteur information that the page mentions.
Do not update public dates from social posts, newsletters, or summaries unless the same event appears in the official procedure record.

Sources for this answer

OEIL procedure file 2023/0085(COD)

Grounds the OEIL status check, including the procedure type, stage reached, and key-event list for the Green Claims Directive proposal.

European Parliament text adopted at first reading

Grounds the Parliament first-reading snapshot and limits the claim to Parliament's adopted position, not final adoption of the directive.

Section 3

Reconcile EUR-Lex and Council document evidence

Use EUR-Lex as the cross-institution procedure ledger. Confirm that the procedure remains ongoing, that COM(2023) 166 is the proposal being tracked, and that the latest listed Council or Parliament documents match the other source snapshots.

Use the Council record for Council-specific wording. ST 11312/24 is a Council general approach approved on 17 June 2024 and shows changes compared with the Commission proposal. If EUR-Lex lists a later Council document, open that document before replacing status language.

Update content if EUR-Lex changes the procedure from ongoing to adopted, withdrawn, blocked, obsolete, or otherwise closed.
Update content if EUR-Lex adds a newer CELEX main document, Council document, Parliament document, or Official Journal publication linked to 2023/0085(COD).
Update content if the Council publishes a later mandate, compromise text, first-reading position, adoption document, corrigendum, or addendum that changes the Council-side status or legal text being summarized.
Keep Council text-change descriptions tied to the Council document number cited; do not merge Council wording into Commission-proposal or Parliament-position summaries without labeling the institutional source.

Sources for this answer

EUR-Lex procedure 2023/0085/COD

Grounds the EUR-Lex reconciliation step because the procedure page identifies COM(2023) 166, ordinary legislative procedure status, and related institutional events.

Council ST 11312/24 general approach

Grounds the Council-side snapshot because the document is the Council general approach for interinstitutional file 2023/0085(COD).

Section 4

Content updates triggered by source changes

A content update is required when an official source changes the legal or procedural status that users rely on. A cosmetic source-page change, a new navigation link, or a duplicated language version is not enough by itself.

When a trigger occurs, update all affected pages consistently: proposal-status pages, timelines, deadlines, FAQs, implementation guides, sitemap-visible article summaries, and any callout that says the proposal is still pending. Keep historical statements dated and institution-specific.

Status trigger: OEIL or EUR-Lex shows a new stage, adoption, withdrawal, closure, or Official Journal publication.
Institution trigger: Parliament, Council, or Commission publishes a newer formal document for 2023/0085(COD) that supersedes or materially modifies a cited record.
Timing trigger: the final act is published and actual entry-into-force, transposition, application, or transition dates become calculable from the Official Journal text.
Scope trigger: a new formal text changes who is covered, which claims are covered, verification timing, microenterprise or small-enterprise treatment, environmental-label rules, or the relationship with Directive (EU) 2024/825.
Citation trigger: a cited source URL stops resolving, loses the relevant passage, changes from a procedure page to a document page, or no longer includes the status being used.

Sources for this answer

European Parliament Think Tank briefing on the Green Claims Directive

Supports the use of key legislative-procedure milestones as update points because the briefing states that Legislation in Progress briefings are updated at key stages.

OEIL procedure file 2023/0085(COD)

Supports the status-trigger list by showing the stage reached, key events, technical information, and documentation gateway for follow-up documents.

Council ST 11312/24 general approach

Supports the formal-document trigger because Council text changes are identified against the Commission proposal in a numbered Council document.

Primary sources

References and citations

Council ST 11312/24 general approach

data.consilium.europa.eu

Referenced sections

Supports the formal-document trigger because Council text changes are identified against the Commission proposal in a numbered Council document.

"The changes compared to the Commission proposal"

EUR-Lex procedure 2023/0085/COD

eur-lex.europa.eu

Referenced sections

Grounds the EUR-Lex reconciliation step because the procedure page identifies COM(2023) 166, ordinary legislative procedure status, and related institutional events.

"Ongoing"

European Parliament text adopted at first reading

europarl.europa.eu

Referenced sections

Grounds the Parliament first-reading snapshot and limits the claim to Parliament's adopted position, not final adoption of the directive.

"Position of the European Parliament adopted at first reading on 12 March 2024"

European Parliament Think Tank briefing on the Green Claims Directive

europarl.europa.eu

Referenced sections

Supports the use of key legislative-procedure milestones as update points because the briefing states that Legislation in Progress briefings are updated at key stages.