A 2024 proposal sought to reuse fourteen engineering packages developed through different collaborations. The technical team could locate the drawings and knew how several assemblies worked. The programme plan nevertheless assumed that availability meant the packages could be modified and supplied for a new application. I asked the engineering sponsors to identify what they intended to reuse and the commercial and legal owners to examine the actual arrangements supporting that use. The CTO could describe the technical dependency but could not determine rights by inspecting a folder.
The review identified nine packages available for the defined intended application, three subject to limited licences requiring further agreement and two whose position remained unresolved. These were conclusions within the actual fictional review, not general rules about ownership of collaborative work. The distinctions depended on the relevant agreements and proposed use. We did not assume that contributing engineering effort gave the company unrestricted rights to everything in a package or that an unresolved item was necessarily somebody else's property.
The review and initial redesign work cost ₹73 lakh. The product sponsor wanted to proceed with all fourteen while negotiation continued, arguing that the technical team could quickly adapt any affected detail. I supported a narrower programme using the nine available packages, with qualified owners retaining the next decisions for the other five. Negotiation, an alternative design and a revised application remained separate options. The schedule could no longer rely on unrestricted reuse that had not been established.
The consequence was a smaller immediate reuse proposition and additional work before the remaining packages could enter it. We did not report the limited licences as expanded, the unresolved rights as settled or the expenditure as a recovered investment benefit. I would define likely future applications and the relevant responsibilities at the start of a collaboration, then revisit them when the intended use changes. A design library records technical material; it is not, by itself, a commercial permission structure. Keeping that distinction clear protects the engineering plan from depending on an agreement that only exists in the team's expectations.