Here is a question your team already asks suppliers: where was this made?<\/strong><\/p>\n\n\n\n Seven words. One field in a form. It looks like the easiest thing you will collect all year.<\/p>\n\n\n\n Now watch what happens when four different colleagues ask it in the same quarter.<\/p>\n\n\n\n The sustainability team asks it because the CSRD value chain disclosures need to know where the impacts sit. They want a country, and they will accept an estimate if the supplier cannot give better.<\/p>\n\n\n\n The customs team asks it because CBAM needs the identity of the installation<\/strong> where the goods were produced, along with the embedded emissions and the production route. A country is worthless to them. They need the plant, and they need it tied to the specific consignment.<\/p>\n\n\n\n The sourcing team asks it because the EU Deforestation Regulation needs the geolocation of every plot of land where the commodity was produced. Not the plant. The land.<\/p>\n\n\n\n The legal team asks it because if an authority sends a request under the Forced Labour Regulation, that request will name a product<\/strong>, and someone will have thirty working days to say which sites made it.<\/p>\n\n\n\n Same seven words. Four incompatible answers. And in most organisations, four separate emails to the same supplier, in the same quarter, from four people who have never met.<\/p>\n\n\n\n This piece is about fixing that, and about the one design decision that makes the difference: treat the purpose of a question as part of the data, not as context that lives in someone’s inbox.<\/strong><\/p>\n\n\n\n The obvious fix is a master questionnaire. One long form, sent once a year, containing everything anybody might need.<\/p>\n\n\n\n It fails for a reason that is now written into EU law rather than merely into supplier patience.<\/p>\n\n\n\n In the reworked sustainability rules, the Commission introduced what it calls the value chain cap<\/strong>. Its own explanatory note is direct about what it does: the cap “prohibits CSRD companies from requiring companies in their value chain that have 1000 employees or fewer, to provide more sustainability information than the content of the sustainability reporting standard for voluntary use.” Companies with ten employees or fewer get additional protection on top.<\/p>\n\n\n\n So the master questionnaire is not just unpopular. For the great majority of your supply base, large parts of it are no longer something you can require.<\/p>\n\n\n\n But read the next sentence in the same note, because this is where the design problem becomes interesting:<\/p>\n\n\n\n “The value chain cap applies only in the context of fulfilling CSRD reporting obligations and does not affect information requests for purposes other than sustainability reporting under CSRD.”<\/p>\n\n<\/blockquote>\n\n\n\n That single sentence is the most useful thing published about supplier data collection this year, and almost nobody is talking about it.<\/p>\n\n\n\n It means the limit does not attach to the question. It attaches to the reason you are asking it.<\/strong><\/p>\n\n\n\n The identical field, requested from the identical supplier on the identical day, is capped when you are collecting it for CSRD and uncapped when you are collecting it because EUDR requires it to place goods on the market. One is a reporting obligation with a burden-sharing rule attached. The other is a condition of market access with no such rule.<\/p>\n\n\n\n Which means a supplier data set that records only what<\/em> you asked can no longer tell you whether you were entitled to ask it. You need to record why<\/em>.<\/p>\n\n\n\n Most supplier information systems store a question, an answer, a date and an owner. Add one more column: the purpose, or purposes, this field serves.<\/strong><\/p>\n\n\n\n It sounds like documentation overhead. It is actually the thing that makes everything downstream possible.<\/p>\n\n\n\n With purpose recorded against every field you can answer, instantly and without a meeting:<\/p>\n\n\n\n Without it, every one of those questions becomes a research project, every time. This is the same argument that makes a proper supplier information management layer<\/a> worth more than a folder of completed forms, and it is the practical half of supplier master data governance<\/a>.<\/p>\n\n\n\n An answer collected for one purpose is reusable for another only if it matches on four axes. Check these before you assume reuse.<\/p>\n\n\n\n 1. What the data attaches to.<\/strong> This is the one that quietly destroys most reuse attempts. Regimes attach their demands to different objects, and an answer attached to the wrong object cannot be converted upwards.<\/p>\n\n\n\n 2. The evidence standard.<\/strong> A self-declared answer and a third-party verified answer are different data, even when the words are identical.<\/p>\n\n\n\n 3. Who you may ask, and under what limit.<\/strong> The caps differ by regime, and they differ in shape, not just in threshold.<\/p>\n\n\n\n 4. The refresh clock.<\/strong> A field that is true annually and a field that must be true per consignment cannot share a collection cycle.<\/p>\n\n\n\n Here is how the main regimes sit against those axes.<\/p>\n\n\n\nWhy the obvious fix does not work<\/h2>\n\n\n\n
\n\n
Purpose as a first-class field<\/h2>\n\n\n\n
\n\n
The four axes that decide whether an answer travels<\/h2>\n\n\n\n