Sharing fleet information with partners: agree the purpose and access

A partner asking for “full visibility” may need something much narrower: confirmation that an allocation is ready, a record of completed work or an explanation of an unresolved interruption. Establishing that need first can make information sharing both more useful and easier to manage.

Within a mobility partnership, the aim should be a shared understanding of the work. A larger data export does not necessarily produce that understanding, particularly when participants use different definitions or need information at different times.

Start with the decision and its recipient

Identify who will use the information and what they are expected to do with it. A service coordinator may need a current status and a next action. An asset owner may need a periodic record of care, approvals and unresolved exceptions. A researcher may need an appropriately prepared dataset for an agreed question.

Describe the minimum detail each role requires. Consider whether a summary, an event record or a restricted view can serve the purpose. Avoid giving every participant the same access merely because it is easier to create one shared folder or report.

Agree what the shared words mean

Terms such as available, active, completed and paid can refer to different states. Record the definition used, the period covered and the point when information was last updated. Explain whether a value is confirmed, estimated or awaiting reconciliation. The recipient should be able to tell what decisions the record can support.

This is especially important when connecting operational and financial information. The Finance & Leasing context may require a distinction between work performed, an amount invoiced and money received. Those records can be related without being interchangeable.

Set the purpose and access boundary

The OECD Privacy Guidelines connect purpose limits with data quality, safeguards and accountability. These principles are useful when designing an exchange that contains information about identifiable people. Establish the relevant permissions and requirements for the actual arrangement before sharing begins.

Make the approved use understandable to the people involved. Specify who can receive information, whether onward sharing is permitted and who handles questions or corrections. A report provided to resolve an operating issue should not silently become material for an unrelated presentation, product test or public claim.

Keep the arrangement usable over time

Choose an owner for maintaining the shared definitions and managing access changes. When someone leaves a role, review their access rather than relying on an old group membership. If the receiving team needs a new field or a different purpose, assess that request explicitly and update the arrangement.

Plan retention and the end of the exchange. Decide which records remain necessary, how corrections reach recipients and what happens when the partnership ends. A modest information flow with reliable meaning can support better decisions than a comprehensive archive that nobody can interpret or govern confidently.