A bespoke VR training project can include client materials, newly created models, application code and licensed third-party assets. These may have different ownership and usage arrangements. Discuss each category rather than treating the finished experience as one undifferentiated file.
Define the rights you need
Consider who can use the module, where it can be deployed and whether you need permission to modify or distribute it. Source code access and a licence to use an application are different arrangements. The written agreement should describe the intended rights clearly.
Check supplied materials
Confirm that drawings, images, recordings and training content can be used for the project. Identify any restrictions on sharing or publication. Third-party software and assets may retain their own licence conditions even when used within a bespoke application.
Discuss handover and future changes
Ask what files, documentation and support are delivered, and who can maintain the application. High5VR can explain the proposed project arrangements during scoping. The final contract should record what is agreed, without assuming every development project uses the same ownership model.
Discuss your project with High5VR
Tell us your audience, learning objectives and delivery requirements. Contact High5VR to discuss a suitable first step.