Who really owns the S&M data?
2nd November 2025
Digital job systems and client portals have transformed service and maintenance efficiency, but they have also blurred the line between compliance reporting and intellectual property. Will Overton (above), director of Isle-of-Wight-based Vectis Refrigeration and owner of the Wisdom Group FM, asks: who really owns the data in service and maintenance?
Every time an engineer completes a job and uploads a report to a client portal, a quiet transfer of ownership occurs. Temperatures, pressures, model numbers, photos and diagnostic notes all become structured data once they leave the engineer’s hands. That information, stored indefinitely on someone else’s system, is exactly the raw material that can be aggregated and analysed.
Few in the trade realise they may be giving away the modern equivalent of their field know-how for free.
Service data has become a tradable commodity. It reveals asset behaviour, site conditions and performance trends. It feeds predictive maintenance and procurement decisions.
Whoever holds the dataset sets the narrative. Like refrigerant in a circuit, data moves through the system. And like refrigerant, if it is not contained and managed, you lose both efficiency and value.
The transparency trap
Digital job systems and client portals have transformed efficiency. They have also blurred the line between compliance reporting and intellectual property.
Recording that a system has passed an operational check is good practice. Detailing exactly how you achieved that result, step by step with readings and adjustments, can cross into giving away proprietary methods. The second category is your field intelligence. It is your commercial advantage, not a public resource.
This is not an argument for secrecy. It is a call to recognise that not all data is created equal, and that different data classes deserve different treatment.
Beyond HVAC
Although these examples come from refrigeration and HVAC, the principle applies across all subcontracted services. Electricians, plumbers, catering engineers, lift maintenance teams, grounds and BMS specialists all feed client portals with photos, readings, fault notes and decisions every day. As workflows become more digital, the transfer of ownership becomes more invisible.
If you are a service provider in any trade, there are really three kinds of information in play:
1. What must be shared for safety and contractual compliance.
2. What is useful to the client for operational transparency and asset history.
3. The diagnostic logic and accumulated insight that defines your competitive edge.
The first two belong in the client record. The third needs careful stewardship by the people who generate it.
A smarter divide
At Wisdom Group FM, we have been developing ways to separate the data needed for transparency from the knowledge that defines engineering excellence.
In our approach, outcome reporting for clients remains clear and verifiable. The deeper technical detail, the readings and reasoning that make up an engineer’s unique insight, is recorded within a protected framework. That structure allows us to learn from our own work, analyse performance trends and improve training without surrendering ownership.
It is the difference between proving that work was done and giving away the playbook for how it was done.
Owning the future
As data platforms and AI models mature, the contractors who manage their data will control their future. Those who continue uploading unfiltered detail to external systems may find they have trained the very tools that push their rates down later.
Protecting data does not mean withholding service. It means recognising that information has value, and handling different classes of information appropriately.
A practical starting point for any trade:
• State clearly in contracts who owns raw measurements, derived insights and any models trained on your data.
• Separate outcome confirmations from deep diagnostics in your reports.
• Keep your learning data in your own framework so you can refine methods and train people without leaking value.
The Wisdom philosophy is simple: engineers should own their insight and field data should work for the people who generate it, not just for the systems that collect it.
By structuring and managing operational knowledge carefully, we can build a smarter, fairer service economy across all trades, one where transparency and intellectual property are not in conflict, but in balance.
Because the real question is not only who owns the data, it is who understands its worth.
