Producers asked to share emissions data with a business they sell to put one question ahead of the rest: who wants to see this, and why. It comes up before anything about the platform or the process, and a producer will usually want both parts answered before going further.
Emissions data records how a farm business operates, including where inputs go and how the enterprise performs from one year to the next, and producers treat it as commercially sensitive for that reason. When a request arrives without an account of how the data will be used, they reach their own conclusions. The ones that come up are reasonable ones: that the figures could be used to compare them with other producers, and that sharing early creates obligations later while the benefit sits mostly with the business asking. Because the record builds from one year to the next, the producer is also weighing an ongoing arrangement in place of a single transfer.
On the platform side, the starting point is consent. Data moves only with explicit consent from the producer’s organisation admin, and a partner’s request shows the producer what is being asked for and the stated purpose before any decision is made. What flows through is usually emissions summary data. It can only be used to understand and report on farm-level emissions in aggregated form and cannot be on-shared. A producer who withdraws consent ends access, and nothing further is added from that point. The same control extends to the advisers and accountants who support a producer in the platform, whose access the producer can remove at any time.
Where these requests have gone well, the business has usually built a relationship with the producer before making the ask, and the request has come through someone the producer already trusts. Accountants who handle the financial records and agronomists who visit the property are the usual examples, and NRM and Landcare facilitators who have worked with a community for years hold the same position. A request that arrives that way, in a context the producer recognises as ordinary business, has generally had its first question answered before it is sent. A webinar or a portal carries less of that history.
That leaves the second part of the question, why the data is wanted, with the business asking, since it is the only party that knows what the data is for. Ruminati provides the platform for what happens after the request, and the account of purpose is one only the business can give. The producer sees the stated purpose at the point of consent. Because the use is limited to aggregated reporting, the purpose a business states needs to match what it will do with the data, which makes it worth settling internally before the first request goes out.
For businesses working through what emissions data collection looks like across their producers, or any of the points here, email the team at hello@ruminati.com.au.
