When sustainability data is scattered across ERP systems, energy invoices, HR files and loose spreadsheets, the first reflex is often: which tool solves this. That question sounds practical, but it skips the step that determines whether a tool solves something or merely relocates it. A tool works with what you feed into it. If no one has recorded which data point comes from which source, who is responsible for it and which quality rules apply, then the tool imports that ambiguity one to one. The screen becomes tidier, the underlying figures do not.
The costs of buying first and organizing afterwards are not always immediately visible, but they are predictable. A tool acquired before the data point register exists must later be reconfigured based on insights that should actually have come first: which fields exist, who supplies them, where the breakpoints sit in the lineage from source to report line. Being reconfigured takes time, and in the meantime the organization keeps running on figures that no one can say with certainty where exactly they come from. The page on what a tool actually costs when placed on top of a disorganized process works out that mechanism further: it is not a matter of a wrong choice, but of a tool that takes over a problem instead of solving it.
There is a second cost item, which has less to do with money and more with trust. Once a reporting tool is in use, the impression arises that the data side has been arranged. Questions about origin and ownership are then no longer asked, because the system appears to answer them. That is precisely the risk: a neat report about figures that no one can substantiate when an accountant or regulator asks further questions.
The reason that setting up the process first and only then choosing a tool does work is simple. If the data point register is in place first — with source, owner and quality rule per data point — then you already know before the purchase what a tool needs to be able to do. You assess a tool based on your own situation, not based on a demo built around a generic example. Which integrations are needed, which fields must be mandatory, who may modify which screen: all of that follows from the work already done before a supplier came into view. More on this can be found on the page about which functional requirements arise from your own process before you select a tool.
This order also prevents a commonly made mistake in the selection itself. Without a clear picture of one's own data flows, a tool is often chosen based on features that sound impressive, while no one can verify whether those features fit the organization's own landscape of systems and spreadsheets. What that verification looks like is described on the page about how you choose a tool without regretting the purchase afterwards. The core is always the same: first know what you have, only then choose what you need alongside it.
The places where sustainability data originates vary greatly by industry, which makes it difficult to select a tool that fits everywhere without your own inventory. In construction, relevant figures are often scattered across project administrations, materials procurement and subcontractor reports, as described on the page about exactly where sustainability data in the construction sector comes from. In the installation sector, the sources are often different again, for example service tickets, vehicle data and energy consumption per location, as worked out on the page about where sustainability data in the installation sector is located. Anyone who does not first map these sources first runs the risk of choosing a tool that is set up for a different kind of data landscape than their own.
The question of whether you buy a tool first or set up the process first is in fact one question viewed from two sides. Both times the same answer surfaces: without insight into where the data originates, who is responsible for it and which rules determine quality, every tool is a gamble. That is exactly where a data point register with source-to-report lineage, ownership and quality rules per data point makes the difference — not as a replacement for a tool, but as the basis on which a tool choice can only then be made responsibly.
Once it is clear which data exists and where it needs to come from, a follow-up question arises: how much of the work of collecting, checking and structuring that data can be left to automated support. The work scan from FTE TO AI calculates per task which part of it can be taken over by AI, making visible where people remain necessary and where repeatable work can be taken off their hands. That scan connects to the moment the process has been set up: at that point it becomes visible not only what needs to happen, but also who or what can best do it.
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.