Introduction
Infrastructure procurement can combine public-sector requirements with privately developed designs and technology. The tender and contract need careful reading before a bidder promises ownership or use rights it cannot supply.
Read the tender allocation
Identify required ownership, licences, source files and continuing government-use rights. Distinguish background tools from commissioned deliverables. Check any approval needed for qualifications, subcontracting or proposed changes to the tender terms.
Read the tender's IP provisions alongside the technical scope, confidentiality terms and required deliverables. Identify whether the authority seeks ownership, a licence, source files or continuing rights to operate and maintain the project. A bidder should check whether it can actually supply those rights through its designers and suppliers. Where a qualification or clarification is necessary, follow the applicable tender procedure rather than relying on an informal assurance. Keep the questions and answers with the bid record so the delivery team understands the commitments that were ultimately accepted.
Coordinate disclosure and continuity
Review confidentiality against applicable disclosure duties. Cover maintenance, emergency use, replacement contractors and supplier support. Do not assume every public project uses arbitration or that a confidentiality clause overrides a legal disclosure requirement.
Background technology should be identified clearly. A contractor may use a standard engineering tool, proprietary method or third-party software while creating project-specific deliverables. Separate these categories and explain any limitations affecting government use, replacement contractors or later modifications. Align subcontract and supplier terms with the rights promised in the main contract. If a component depends on a subscription or outside licence, identify responsibility for continuing costs and access. Government participation does not by itself answer every ownership question, and a broad transfer promise may be impractical if essential components remain owned by others.
Address IP commitments before submitting the bid
Confidentiality needs review against the procurement setting and applicable duties. Bid pricing, technical methods and sensitive project information may require different controls and disclosure treatment. Identify what can be shared with advisers, auditors, subcontractors and competent authorities and under what conditions. Avoid promising that an NDA overrides every legal disclosure requirement. Establish authorised channels for handling project files and a record of what was issued. Where data or security-sensitive information is involved, the relevant legal and operational requirements should be assessed separately rather than treated as a routine copyright clause.
Long-term operation should inform the handover requirements. Public infrastructure may need repair, expansion or a change of operator after the original contractor leaves. Agree the documents, formats, licences and support needed for those events. Record how future modifications will be attributed and who remains responsible for the original and altered work. Review dispute provisions and any approvals relevant to the chosen forum rather than assuming arbitration applies to every public contract. A rights review before bidding can help the contractor price realistic commitments and reduce the risk of unresolved access problems during delivery or maintenance.
Bid teams should pass the final rights commitments to the people delivering the contract. Keep tender clarifications, accepted qualifications and supplier restrictions with the project handover information. A change in personnel should not cause the team to lose sight of a negotiated limitation or a promised file format. Review proposed substitutions against those commitments before approval. This administrative step can be particularly valuable where a project has a long delivery period and several specialist packages, because the technical team making a later procurement decision may not have participated in the original tender review.
Practical checklist
- Tender IP and disclosure provisions
- Background-technology schedule
- Subcontractor and supplier rights
- Maintenance and replacement access
Related reading
- Drafting Strong IP Clauses in Construction and Subcontractor Agreements in Bahrain
- Licensing Intellectual Property in Joint Ventures: Avoiding Legal Pitfalls in Bahrain
- Technology & Software Licensing in Construction: Protecting ERP, BIM, and Smart Site Tools in Bahrain
Conclusion
Resolve rights and disclosure issues before submitting commitments that affect delivery and long-term operation.
For a review of the rights, permissions or agreements relevant to your matter, explore our intellectual property expertise and public procurement legal support.
Contact Manal Dhahi Legal Group to discuss your circumstances. The appropriate next step depends on the documents and facts of the matter.
Frequently asked questions
The applicable law and contract must be reviewed; do not infer the allocation from government participation alone.
Check contractual exceptions and applicable legal disclosure duties before making that promise.
A clear schedule distinguishes existing supplier assets from commissioned deliverables and exposes any permissions, support or continuing licences needed to meet the tender's requirements.