What should a coastal-software company clarify before reusing UKHO material commercially?

A company building a non-navigational coastal reporting or environmental service should describe its intended reuse of UKHO material before selecting a licence. The fact that the source is a public body does not remove copyright or the need to check the rights that apply.

UKHO's licensing page distinguishes several purposes of reuse, including commercial web-based services and scientific, technical or consultancy uses. It also explains that some material originates with other organisations and may require additional permission. The licence discussion therefore depends on both the product's use and the rights in the source material. UKHO copyright licensing

Begin with a plain description of the proposed service. Who is the customer, what output will they receive and how will the material appear in it? A downloadable report, a hosted application and a redistributed dataset can create different commercial questions. The licensing team needs to understand the actual model.

Identify all intended users and distribution channels. A company may deliver directly to customers, work through a reseller or incorporate material into a partner's platform. Those arrangements should be covered by the proposed rights rather than added informally after launch.

Keep a record of the source material and its provenance. If another organisation's rights are involved, determine who can grant the necessary permission. A reference to UKHO in a third-party product does not automatically establish that the startup can reuse every part of that product.

The product team should explain whether the service changes the material or combines it with other inputs. This helps clarify the scope of the licence and the acknowledgements required. It also makes the company's own added value more visible in the commercial proposition. The EMSA RPAS procurement analysis separates the operated service from the aircraft within it.

Build licensing into the launch schedule. The company may need to provide supporting information, discuss the intended use and review proposed terms. Do not promise a customer delivery date on the assumption that permission will be immediate or that a familiar licence covers a materially different service.

The financial model should use the actual agreed fee structure. A general website description or another company's arrangement is not a reliable basis for pricing. Consider how licence obligations affect the economics if customer numbers or distribution methods change.

Review the proposed customer terms against the rights the company receives. A supplier should not promise customers unrestricted redistribution if its own licence does not permit it. The same applies to branding: use of data and use of an organisation's trademarks are separate questions. The CISE interoperability and data access distinction matters when technical compatibility is being presented as a right to use information.

This article concerns non-navigational commercial reuse and does not provide maritime navigation guidance or assess any dataset's fitness for an operational purpose. The applicable licence and professional advice determine the legal position. Check EMODnet data licences at dataset level before assuming one reuse permission covers a marine-data product.

Commercial use is broader than charging for a map

UKHO's licensing description includes both direct and indirect charges, and it can also treat a free product that competes with commercial products as commercial use. A company should therefore describe the role of the material in its overall service. A free preview used to attract paying subscribers and a paid downloadable report may both raise commercial licensing questions, even if only one has a price beside it. UKHO commercial-purpose definitions

That distinction matters for software products whose customer never purchases the underlying material separately. The data may support a subscription, a consultancy deliverable or a service supplied through a partner. Its commercial role is embedded in the offering. A licensing enquiry should explain that offering and the intended recipients, rather than assume that a zero price for one visible layer makes the whole use non-commercial.

UKHO also defines navigational purposes more broadly than a vessel's immediate route display, including some maritime management and training uses. A supplier should confirm the applicable category from the actual intended function, rather than classify a product as non-navigational simply because it runs on an office computer. The coastal planning and environmental reporting examples here concern uses that must be described and agreed on their own terms. UKHO purpose categories

Describe the product at the point where the customer receives it

Consider a hypothetical coastal planning consultancy producing environmental reports for commercial property clients. Its intended output is a report containing selected baseline material alongside the consultancy's own analysis. The licensing enquiry should show how that material appears, what customers may do with the report and whether any underlying files are supplied. A statement that the company uses data for research would not fully describe this downstream commercial product.

Now suppose the same company plans a subscription website where clients can create reports themselves. The customer interaction and distribution model have changed. The firm may need to explain access controls, export functions and the role of resellers or partner platforms. Those details are commercially significant because they determine how the material reaches end users and what those users can subsequently reproduce. They should be resolved before the software architecture assumes unrestricted redistribution.

The product team can make the discussion easier by preparing a representative output using appropriately authorised material or a clearly labelled mock-up. The aim is to show the intended arrangement, not to launch the product before permission is established. A concrete example helps the licensing team distinguish a static illustration from a downloadable dataset and a consultancy report from a general data service.

Licence timing and fees affect the launch model

The public page says UKHO aims to offer a commercial licence agreement within 20 working days, while uses outside existing licences may require separately developed terms and an estimated completion time. That is an expressed service aim, not a delivery date a company should promise to its own customer. The launch plan needs room to resolve the actual rights and any additional information requested. UKHO commercial application process

The company's commercial model should then reflect the agreed charging basis. If fees depend on products sold or another usage measure, the software and finance teams need a way to produce the relevant records. A pricing decision made before this is understood can leave a popular product generating obligations that its retail price does not cover. The issue is not whether licensed data is inherently expensive; it is whether the business understands the relationship between permitted use, customer activity and cost.

Source selection can also change the economics. A product assembled from several datasets may involve different permissions, acknowledgements and update cycles. Choosing an input solely because it is technically easy to obtain can create a more complex commercial chain than expected. Comparing alternative sources should therefore consider coverage, currency, fitness for the intended purpose and rights, alongside the engineering work needed to integrate them.

A reliable customer offering makes that chain visible internally. Staff should know which source supports each part of the output, what the company is authorised to do and which customer promises depend on that permission. When the product adds a new export feature, reseller or user category, the team can identify the affected licence before shipping the change. That discipline supports a coastal software business whose distribution model can grow coherently, with its data rights and commercial commitments developing alongside its features.

The practical objective is a clear chain from source material to authorised use to customer offering. When that chain is documented before development becomes dependent on the data, the company can make more reliable decisions about product design, pricing and launch timing.