Sustainability Data Readiness
A tool layered on top of an unorganised process just produces neater reports about the same unreliable figures. What does help is putting the structure in place first — the data point register, the lineage, the ownership — and only then choosing who carries out the work. That choice is threefold, and the order is not arbitrary: whoever can structure it themselves doesn't need to hire anyone. More on the composition of that register can be found at what it is, and on how it works at how it works.
This route delivers the bootcamp template per topic, a register export, and a controls checklist for assurance. The tool lines up the data points, offers the source-to-report mapper for lineage and RACI, and generates functional requirements once the process is in place. What the client does with that themselves stays with the client: filling in, assigning, checking.
This route suits an organisation that already has someone who can read data flows — a controller, a data analyst, someone with a CSRD or VSME background who understands what a RACI means and what a valid-values rule produces. It requires time, discipline to keep the register up to date, and the willingness to settle the ownership questions independently.
This route does not suit a situation where nobody has the time or the mandate to actually do that work. Filling in a tool is not a project that drives itself; without an owner on the matter itself, this register too will stall.
Here a partner runs the three-day data bootcamp around one topic — usually CO2 first — while the tool continues to hold the register and the lineage. The client gets the same output as in route 1, with this difference: the design work during the bootcamp happens under guidance, not just following a template.
This route suits a situation where there is capacity to maintain the register, but not the experience to design a lineage process from scratch — which sources, which transformations, who is responsible for what. Three days of structured attention on a single topic prevents each team from doing it slightly differently.
This route does not suit a situation where several topics are stuck at the same time and there is no room to tackle them one after another, or where the organisation actually has a structural capacity problem that one bootcamp will not solve. A partner always operates after the report, outside the tool — this product does not arrange consultancy itself, it only points to it when the client chooses that.
This route places the entire setup with the partner: register, lineage, RACI, and quality rules are built on FTE TO AI's own environment, so based on the client's own systems and people, not on a generic template. The client receives a working file without having to build it themselves.
This route suits a situation where there simply is no internal capacity to take this on, or where the pressure of an approaching assurance deadline leaves no room for a learning process. What the client must be able to do themselves: grant access to the right systems and people, and take over ownership after the setup — outsourcing the build is not an exemption from maintenance afterwards.
This route does not suit an organisation that wants to gain grip on the subject matter itself, or where the budget for external support is lacking. Full outsourcing solves the starting problem, not the fact that someone internally must ultimately be responsible for upkeep and re-measurement.
In every route, the tool remains the file: the register, the lineage, the audit trail. Nobody from this product is involved in route 1 or 2 — the guidance and the execution in routes 2 and 3 lie with the partner, separate from this tool. What changes is who does the filling-in work, not where the truth about the data is recorded.
That distinction is not cosmetic. An organisation that hires a partner but does not use the tool as the file is back to manual consolidation with an extra invoice. Conversely: an organisation that does everything itself without ever considering a bootcamp or an external check risks getting stuck on exactly the blind spots that bootcamps and partners exist for.
For those who want to know more about what surfaces per topic, further background is available in the knowledge base. The button to start a route is, incidentally, still on the waiting list — the tool itself is still under construction, and that is not being concealed here.
This subject only becomes reality in tasks, hours, and systems: who does it, how much time it takes, and which systems it touches. Anyone who wants to calculate that before choosing a route will find the work scan from FTE TO AI at ftetoai.com.
Vraag maar waar een datapunt vandaan komt. Dat is meestal de hele vraag.
Answers come from this site’s knowledge base. Not tailored advice, and not a scan of your company.