> 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 3: In Force Is Not the Same as Applicable to You

> Academy Foundations Module 5 Lesson 3: how to read a working plan timing signal correctly, and why a regulation being in force differs from it applying to your product.

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

## Orientation

This is the lesson that fixes the most expensive habit in the whole path: anchoring a programme to a
date that does not actually belong to your product. The habit is understandable. Dates are concrete
and everything else about this regime feels abstract, so a date reads as progress even when it
attaches to the wrong regulation entirely. Getting this right protects both your credibility and your
budget.

Entry into force, once the scrutiny period passes without objection, followed by the date of
application after the transition period. Adoption alone is not enough.

## Learning Objectives

A tieback framework that separates confirmed legal dates from indicative ones, and shows three
parallel lanes moving at once: what the Commission is doing, what industry is doing, and what your
organisation should be doing at each stage.

**Use it when** you need to place your product group on a timeline honestly, or when a stakeholder
asks "what is our deadline" and the true answer is that no delegated act covering the product has
been adopted yet.

**Where it fails:** it will not generate a date for you. If no act exists for your product group, the
correct output of this framework is "no confirmed date," not an estimate dressed up as one.

## Three Different Kinds of "Real"

Three concepts get collapsed into one in most internal briefings, and separating them is the entire
skill this lesson teaches.

**In force.** A regulation is in force once it has been adopted and published, and the framework
regulation itself has been in force for some time. In force describes the regulation's legal
existence. It says nothing about which products currently carry a duty under it.

**On the working plan.** The Commission publishes working plans naming which product groups it
intends to address, in what order, over a stated multi-year horizon. A working plan entry is a
statement of intent to do rule making work. It is not a date on which anything becomes mandatory, and
it carries no legal force of its own. Reading a working plan slot as a compliance deadline is the
single most common timing error in this field.

**Applicable to you.** A requirement is applicable to your product only once a delegated act covering
your specific product group has been adopted, has entered into force, and has passed the date of
application set inside it. Anything short of that is preparation, forecasting or monitoring, not
compliance.

The correct way to read a working plan signal is as a prioritisation cue: it tells you which product
families are more likely to see rule making activity sooner, and therefore which ones deserve closer
monitoring. It does not tell you what the requirement will say, and it does not tell you when it will
bite, both of which are set later, in the act itself.

**The common misreading** is compressing all three into a single sentence: "the regulation is in
force and our category is on the working plan, so we have a deadline." Each clause in that sentence
is true and the conclusion does not follow from any of them. In force tells you the power exists. On
the working plan tells you the Commission intends to act on this category before others not listed.
Neither, singly or combined, creates a date that applies to your product until an act has actually
been adopted and applied.

#### [When Will Digital Product Passports Become Mandatory?](/docs/knowledge-base/regulations/when-will-digital-product-passports-become-mandatory)

Read all three sections. The timeline section is the canonical description of TBF-008 and the
three parallel lanes.

#### The S2's three components, three readings

The trimmer's polymer housing sits in a product group that appears on a working plan: a signal
worth monitoring, not a date to diarise. The lithium-ion battery pack sits under a regime with its
own confirmed dates already fixed in adopted law for the categories it names, independent of ESPR
entirely, which is why battery composition data is worth chasing from the contract manufacturer
now rather than waiting on ESPR news. The textile shoulder strap sits in a product family that may
or may not appear on a future working plan at all.

Three components, three different positions on the timeline, inside one product. Reporting "the S2 is
covered by 2027" collapses all three into a single wrong answer.

#### Classify your own portfolio by these three states

For one product line, write down: is the relevant framework in force (almost certainly yes), is
the product group named on a current working plan, and is there a published, in force, applicable
delegated act. Where the third answer is no, say so plainly rather than substituting the second
answer for it.

## Knowledge Check

## Takeaways

* In force means the instrument has legal effect, not that any specific product has a duty.
* A working plan entry is a prioritisation signal, not a date, not a content specification.
* Only an adopted, in force, applicable delegated act creates a compliance date for a product.
* One product can have components sitting at different points on the timeline simultaneously.

**If you remember one thing:** ask which of the three states you are actually looking at before you write a date on a plan.

## Sources

[When Will Digital Product Passports Become Mandatory?](/docs/knowledge-base/regulations/when-will-digital-product-passports-become-mandatory),
sections Why There Is No Single Compliance Date, The Digital Product Passport Compliance Timeline,
and What Depends on Delegated Acts.

## Related Docs

* [Lesson 4: Working Without the Field List](/docs/academy/foundations/module-5/lesson-4)
* [Lesson 2: How a Delegated Act Becomes an Obligation](/docs/academy/foundations/module-5/lesson-2)
* [When Will Digital Product Passports Become Mandatory?](/docs/knowledge-base/regulations/when-will-digital-product-passports-become-mandatory)
* [tieback Frameworks](/docs/knowledge-base/frameworks/overview)