> 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 4: The Data You Do Not Hold

> Academy Foundations Module 2 Lesson 4: naming the attributes your organisation cannot supply itself and locating the party in the value chain who actually holds them.

**Module 2, Lesson 4 of 4. About 8 minutes.**

## Orientation

You can now place your organisation in the value chain, separate participation from legal duty, and
read a scope claim properly. The last gap is the one that actually stalls programmes once the
paperwork is settled: a passport needs data your own organisation has never held, was never asked to
collect, and in many cases does not have the relationship to request. Finding that gap in week two of
a programme is cheap. Finding it in month nine, when someone asks for a figure nobody can produce,
is not.

Prepare foundations that do not depend on the eventual field list, such as identifiers, data
ownership and supplier data clauses, and track the act as it develops. Not a compliance deadline,
and not inaction either.

## Learning Objectives

## The Attribute Is Never Yours by Default

A passport is filled with attributes, and every attribute originates somewhere. Some originate
inside the organisation that will eventually publish the passport. A great many do not: material
composition, recycled content, substance declarations and process level detail typically originate
upstream, with a component or material supplier who may never have been asked to formalise, evidence
or hand over that information in a usable form.

This is not a technology problem and it is not solved by building a bigger database. It is a
relationship and a request problem. A supplier that has answered the same technical question for a
customer for years by email is not withholding data out of obstruction; nobody has ever asked for it
in a structured, reusable, evidenced form, and nobody has explained why that matters now. Suppliers
are, in a real sense, affected before their own customers are: if a downstream obligation applies
from a given date, the underlying supplier data has to exist well before that date, not on it.

The practical discipline is to separate three things that get collapsed into one vague worry called
"data gaps". First, name the specific attribute you cannot currently produce. Second, name the
organisation in your value chain that actually holds it, using the map from Lesson 1 rather than
guessing. Third, establish whether a request has ever actually been made, in a form that specifies
what is needed and why, as distinct from an informal conversation that never generated anything
durable.

**The common misreading** is to treat a missing attribute as evidence that the data does not exist
anywhere, and therefore as a problem to be solved by estimation or default values. Composition and
substance data usually does exist somewhere in the chain; it exists with the party who makes or
processes the material, and it has simply never been asked for in the form a passport requires. The
fix is rarely invention. It is identification of the holder, followed by a specific, evidenced
request, usually formalised through the supply agreement rather than left as a one-off favour.

#### [Who Needs a Digital Product Passport?](/docs/knowledge-base/digital-product-passports/who-needs-a-digital-product-passport)

Read the supplier section first for what suppliers are actually expected to provide and in what
form, then the two sections that follow for how lead time and contractual clauses fit together.

#### The S2 battery composition gap

The S2's battery pack requires composition data for its eventual passport. That data sits with the
cell supplier in the manufacturing chain, not with the brand owner and not with the contract
manufacturer, who assembles the pack but does not originate the cell chemistry. Nobody at the brand
owner has asked the cell supplier for this data in a structured form; the existing relationship is
a purchase order and a datasheet PDF, which satisfies neither the completeness nor the machine
readability that a passport needs.

The gap is not technical capability on the supplier's side. It is that a specific, evidenced request
has never been made, and no clause in the supply agreement currently requires one to be answered.

#### Name three of your own unheld attributes

List three attributes you believe will eventually need to appear in a passport for one of your
products, but which your organisation cannot currently produce itself. For each, name the specific
organisation in your value chain most likely to hold it, and note whether a structured, evidenced
request has actually been sent, as opposed to an informal question that has never been answered in
a durable form.

## Knowledge Check

## Takeaways

* Every passport attribute originates somewhere, and it is frequently not the organisation that will
  eventually publish it.
* A missing attribute usually means no structured request has been made, not that the fact is
  unknown to the chain.
* Suppliers need to be ready before their customer's compliance date, not on it.
* Closing a data gap starts with identifying the holder, using the value chain map, then making a
  specific, evidenced request, usually through the supply agreement.

**If you remember one thing:** a data gap has an owner somewhere in your chain; your job is to find
them and ask properly, not to guess the number.

## Sources

This lesson draws on
[Who Needs a Digital Product Passport?](/docs/knowledge-base/digital-product-passports/who-needs-a-digital-product-passport),
sections Component and Material Suppliers, Which Organisations Should Prepare Now and Organisations
Likely to Be Indirectly Affected.

## Related Docs

* [Module 2 assessment](/docs/academy/foundations/module-2/assessment)
* [Lesson 3: Reading Scope Without Guessing](/docs/academy/foundations/module-2/lesson-3)
* [Who Needs a Digital Product Passport?](/docs/knowledge-base/digital-product-passports/who-needs-a-digital-product-passport)
* [Module 2 overview](/docs/academy/foundations/module-2)