> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://tieback.io/docs/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://tieback.io/docs/_mcp/server.

# Lesson 2: How a Delegated Act Becomes an Obligation

> Academy Foundations Module 5 Lesson 2: the path a delegated act travels from Commission draft to binding law, and where scrutiny and objection can still change it.

**Module 5, Lesson 2 of 4. About 9 minutes.**

## Learning Objectives

## Orientation

Once you accept that the real content lives in a delegated act, the next useful question is how
confident you can be in a draft you have been shown. A leaked working document, a consultation
draft and a published act carry wildly different weight, and treating them as interchangeable is how
a supplier contract gets written against a specification that later changes. This lesson walks the
distance between a Commission idea and a binding rule, so you know how to weigh whatever version of
a document lands on your desk.

A tieback framework describing the stages a delegated act passes through: preparatory study,
impact assessment, consultation, Commission adoption, the Parliament and Council scrutiny period,
entry into force, and finally the date of application after the transition period.

**Use it when** you are trying to work out how much weight to give a document someone has shown you,
or when a supplier or vendor claims a requirement is "coming" and you need to locate exactly where in
the process it sits.

**Where it fails:** it describes the standard route. Some detail can arrive through an implementing
act rather than a delegated act, which follows a different, committee based control process. Check
which instrument you are actually looking at before applying this lifecycle to it.

## From Draft to Binding

A delegated act does not spring into existence as law. It is drafted by the Commission after
preparatory studies and an impact assessment, refined through public consultation and expert group
input, and only then formally adopted by the Commission as a text. Adoption is not the finish line.
The framework regulation that grants the delegating power also fixes a scrutiny period during which
the European Parliament and the Council may object. Either institution can object, and an objection
can amend the act or stop it outright. Only once that scrutiny period passes without objection does
the act enter into force, and even then, it typically carries a further transition period before its
date of application, the point at which the obligation actually bites.

That sequence has a practical consequence: at any given moment, several versions of "the
requirement" may exist simultaneously, at different stages of legal weight. A preparatory study is
evidence gathering. A consultation draft is a proposal open to challenge. An adopted text, before the
scrutiny period ends, is provisional. Only a published, in force act, past its transition period, is
an obligation you can be held to.

**The common misreading** is to treat Commission adoption as the moment a requirement becomes real.
Adoption is a milestone, not the finish. The scrutiny period exists precisely because the Parliament
and the Council can still change or reject what the Commission has agreed, and a text can move
between adoption and entry into force. Planning against an adopted-but-not-yet-in-force text is
reasonable as a forecast. Committing capital against it as though it were final is not.

#### [What Are Delegated Acts?](/docs/knowledge-base/regulations/what-are-delegated-acts)

Read both sections in sequence. The lifecycle section is the canonical description of TBF-006, and
the development section fills in who does what at each stage.

#### Reading a draft about the S2's battery pack

A trade association circulates a document describing forthcoming requirements for portable battery
passports, sourced from a consultation the S2 team's battery supplier participated in. The
procurement lead wants to write it into the supplier contract as a fixed specification.

The correct question is not whether the document looks authoritative. It is where the document sits
on the lifecycle: is this a consultation input, a Commission proposal, an adopted text within its
scrutiny period, or a published act. Each answer changes what you should do. A consultation input is
worth tracking and worth feeding your own evidence into. Only a published, in force act, correctly
identified by its Official Journal citation, belongs in a binding contract clause.

#### Locate a document you have actually been sent

Take the most recent "requirement" document that has crossed your desk relating to passports for
any of your products. Place it on the lifecycle: preparatory, consultation,
adopted-pending-scrutiny, or in force. If you cannot place it because it does not cite a parent
act or an Official Journal reference, that absence is itself the answer.

## Knowledge Check

## Takeaways

* A delegated act passes through preparatory study, consultation, Commission adoption, scrutiny, entry into force, and date of application.
* Adoption by the Commission is not final: the scrutiny period can still change or stop the text.
* Only a published, in force act past its transition period is an obligation.
* Weigh any document you are shown by which stage it has actually reached, not by how authoritative it looks.

**If you remember one thing:** adoption is a milestone in the process, not the end of it.

## Sources

[What Are Delegated Acts?](/docs/knowledge-base/regulations/what-are-delegated-acts), sections The
EU Product Regulation Lifecycle and How a Delegated Act Is Developed.

## Related Docs

* [Lesson 3: In Force Is Not the Same as Applicable to You](/docs/academy/foundations/module-5/lesson-3)
* [Lesson 1: Framework Plus Delegated Act](/docs/academy/foundations/module-5/lesson-1)
* [What Are Delegated Acts?](/docs/knowledge-base/regulations/what-are-delegated-acts)
* [tieback Frameworks](/docs/knowledge-base/frameworks/overview)