Construction data ownership: questions before platform selection
Admin · 22 October 2026
Illustrative image. Photo by Andreea Avramescu on Unsplash. Unsplash License.
Project teams often use the phrase our data as if it answers every question about information held in a construction platform. In practice, the organisation needs to understand who can contribute, access, alter, use and retrieve particular records, and what happens when the service ends. Those questions involve different responsibilities and rights. A clear operational brief helps the appropriate advisers assess the proposed arrangement before the platform becomes central to delivery.
This article identifies procurement questions rather than interpreting legal ownership. The actual position depends on the information, agreements and applicable requirements. Clients and contractors should obtain appropriate legal, privacy, security and commercial advice. Their project teams can make that review more useful by explaining how the platform will be used and which information relationships matter.
Describe the information being handled
Identify the types of records the platform will receive or create. These may include design information, site observations, commercial records or asset data. Record which organisations contribute and which receive the outputs. Avoid treating all information as one undifferentiated category, because the proposed uses and relevant requirements can differ substantially.
Explain whether the service holds original records, copies or links to information elsewhere. A platform may appear to contain a complete project file while relying on connected systems. The advisers need to understand that chain, and the project needs to know which record is authoritative for each workflow. This becomes particularly important when an integration changes or a supplier leaves.
Separate the practical questions
Ask who can access, edit, export and reuse the information under the proposed arrangement. These are related questions but should not be collapsed into a single assertion about ownership. The organisation may have practical access without the full uses it expects, or rights that are difficult to exercise through the proposed technology. Both need review.
Describe the organisation’s intended uses clearly, including later operation, dispute records or future projects where relevant. The appropriate advisers should assess what is permitted and what terms are needed. The procurement team should avoid assuming that a standard service description automatically covers every future purpose the business has in mind.
Clarify contributor expectations
Identify how designers, specialists and other participants will provide information and what arrangements govern their contributions. A platform selection should fit the project’s appointments and information requirements rather than creating unexplained conflicts with them. Where responsibilities or rights are unclear, route the question to the appropriate commercial and legal team before reliance grows.
Consider a hypothetical contractor using a platform for supplier technical submissions. The project needs to understand how accepted information can be retained and passed to the client, and how supporting material from another service is handled. The software workflow alone does not settle those questions. They should be addressed through the relevant agreements and a practical delivery test.
Include personal information in the review
Where personal information is involved, ask the organisation’s privacy advisers to establish the roles and requirements for the actual processing. The ICO guidance on controller and processor contracts provides relevant UK context. The ICO flags this guidance as under review following the Data (Use and Access) Act; advisers should check its current status. It should be applied by the appropriate advisers to the proposed arrangement, rather than assuming every platform relationship has identical roles.
The project team can help by explaining the information types, users, purposes and exchanges. It should also identify proposed changes during the service. A review based on a limited reporting use may not cover a later expansion into additional personnel records or connected workflows. Keep those differences visible and obtain further assessment where required.
Assess access in real workflows
Test the proposed permissions using representative roles and tasks under the approved arrangement. Users need enough access to do their work, while the organisation needs the controls defined by its specialists. A demonstration under an administrator account does not show what an external contributor or receiving client will actually experience.
Review changes in personnel and organisational participation. Identify who requests, approves and implements access changes. The process should not depend on informal messages to a supplier contact who may later be unavailable. A clear administrative route supports continuity and reduces pressure for uncontrolled workarounds when a user cannot reach necessary information.
Review provider use and connected services
Ask the relevant advisers to examine the provider’s proposed uses of information and the role of other services in the arrangement. The project should identify consequential expectations, such as restricted material or intended client use, rather than assuming they are understood. Record questions and responses through the procurement process with clear references to the proposed terms.
Distinguish current capabilities from future features that may change information use. A service update can introduce new questions even if the main interface remains familiar. Establish who monitors consequential changes and what triggers another review. The organisation needs ownership of the relationship, not just an initial approval filed at procurement.
Test retrieval and portability
Identify the records the organisation expects to retrieve and the form in which they remain useful. Include attachments, relationships and relevant history where required. Ask users to test a representative output. A successful download may still leave the client unable to connect a decision with its evidence or open a record without an ongoing service.
Use the test to inform the commercial review. If the practical output does not meet the intended need, identify the additional service or arrangement required and obtain the appropriate decision. Do not assume a broad contractual statement about export guarantees every operational detail. The agreement and the usable result need to be considered together.
Plan the end of the relationship
Agree the transition questions before they become urgent. The relevant advisers should assess retention, return, continued access and appropriate treatment of information under the actual requirements. The project should identify timing and workflow dependencies so the organisation can complete necessary checks before the live arrangement ends.
Assign responsibility for preparing, verifying and accepting the retained records. These may be different roles. Keep an account of outstanding information and limitations. A task marked export complete should not imply that the receiving organisation has confirmed usability or that every related service has been addressed.
Keep the decision record usable
Retain the scope of the review, consequential advice and conditions with the supplier record under the organisation’s arrangements. Incoming personnel should be able to understand what use was assessed and what remains subject to further approval. This helps prevent a platform selected for one project workflow from becoming an assumed solution for every information need.
Explain the approved working arrangement to users in practical terms. They need to know where to place records, how access works and whom to contact with a question. They do not need to interpret complex terms themselves. Clear guidance connects the professional review with the everyday behaviour on which the information process depends.
The useful outcome is a shared understanding of information use and continuity. Asking precise questions before selection gives the appropriate advisers a concrete arrangement to review and gives project teams a process they can operate. It replaces a vague claim of ownership with an accountable plan for contributing, using and retaining the records the organisation actually needs.
Review the arrangement at project handover rather than assuming the construction team’s access model suits the operating organisation. Different people may need the records for different purposes, and some project participants may no longer require access. The responsible advisers should establish the revised position, while users test the retrieval route. Preserve the decision and the information set transferred so that later personnel can understand both the scope of the handover and any limitations accepted at that point.
