Licensing Training Content Explained

By Brian Tr · Updated Oct 6, 2026

Every training course is a copyrighted work, and every sale of one is really a decision about rights. A company that "buys a course" is almost never buying the course. It's buying permission to use it, on terms: who may take it, for how long, in which languages, and whether anyone else may get it too. If you build or resell training, those terms are the product as much as the video and the quizzes are.

This article explains the main ways training content gets licensed, from off-the-shelf libraries to custom builds where ownership changes hands. It sits under the commercial models covered in corporate training business models and pairs with the buyer's side of the table in enterprise learning procurement. It's general information, not legal advice, so have a lawyer review any real contract.

Key Facts

Key Facts: Training Content Licensing

• Under US law, a commissioned work is a "work made for hire" only if it falls in a listed category (which includes "an instructional text") and the parties expressly agree in a written instrument signed by them (17 U.S.C. 101).
• A transfer of copyright ownership "is not valid unless an instrument of conveyance, or a note or memorandum of the transfer, is in writing and signed" by the owner (17 U.S.C. 204(a)).
• US law counts an exclusive licence as a transfer of ownership, but a nonexclusive licence is not (17 U.S.C. 101).
• Copyright owners hold the exclusive right to prepare derivative works, which is why translation and adaptation need permission (US Copyright Office, Circular 30; 17 U.S.C. 101).
• In the UK, when you commission work, the first owner is the creator "unless you otherwise agree it in writing" (GOV.UK, Ownership of copyright works).

Copyright basics that drive every contract

A few rules explain most of what follows.

The creator owns the work by default. In the US, a person who writes a script or records a video owns the copyright unless an exception applies. The big exception is the work made for hire. The statutory definition has two limbs: a work prepared by an employee within the scope of their employment, or a specially commissioned work that falls in a listed category and is covered by a signed written agreement saying it's a work made for hire. The list includes "an instructional text," defined as a work "prepared for publication and with the purpose of use in systematic instructional activities." The Copyright Office's circular on works made for hire summarizes the same two limbs. That matters for training: a freelance instructional designer you hire to write a course is not an employee, so a missing or sloppy agreement leaves the copyright with the designer, even though you paid for it.

Transfers need a signature. A transfer of ownership must be in writing and signed by the owner. A handshake, an email thread that never mentions rights, or an invoice marked "paid" doesn't move copyright.

A licence is permission, not ownership. A licence lets someone do things that would otherwise infringe. It can be narrow or broad, short or long, exclusive or not. The US definition of "transfer of copyright ownership" includes an exclusive licence but not a nonexclusive one, which means a deal labeled "exclusive licence" may carry the same formal requirements as an assignment.

The UK works similarly, with its own default. The UK Intellectual Property Office says that when you commission work, the first legal owner is the person who created it, not the commissioner, unless you agree otherwise in writing. It also notes that an employer is the first owner of work made by an employee in the course of employment, and that a commissioner without a written agreement may only get a limited non-exclusive licence. Other countries differ again, so a course sold across borders deserves local advice.

The main ways training content is licensed

Most deals fit one of five patterns. They differ in who owns the content, how much the buyer can change it and how much the seller can resell it.

Off-the-shelf library licences

The publisher owns the courses and grants customers access under a standard agreement. The licence is nonexclusive, so other customers receive the same content. It's usually non-transferable, restricted to the buyer's own employees and often limited to internal use. The buyer typically can't edit the course, resell it or extract the files.

This is the default for catalogs sold on a subscription, and the pricing mechanics sit in per-seat vs per-learner pricing. From a licensing view, the interesting questions are the grant ("may access and use for internal training"), the restrictions ("may not sublicense, copy or modify") and what happens to the catalog during the term. Publishers refresh and retire titles, so a good agreement says what the buyer gets if a course is withdrawn.

White-label and private-label rights

White-label means the buyer can present the content under their own brand. A training company, a professional association or an LMS vendor licenses a library and resells it as part of its own offer, with their logo, domain and sometimes course titles.

The rights to pin down:

• Branding scope. Logo and colors only, or can titles and descriptions be changed too?
• Sublicensing. May the reseller grant end customers the right to use the content? Without it, the reseller can't legally sell to anyone.
• Pass-through terms. Many publishers require resellers to flow their end-user restrictions down to customers.
• Attribution. Some deals allow complete rebranding, others require "powered by" credit.
• Exclusivity. Private-label sometimes means the publisher agrees not to license the same course to competitors in a segment, which is a separate and pricier right.

Think of white-label as a reseller licence stacked on top of a content licence. The product is the same, but the grant is wider, which is why it costs more and comes with more reporting duties.

Custom content: assignment or licence-back

When a buyer commissions a course, the contract has to answer who owns the result. There are two common structures.

Assignment (or work made for hire). The developer transfers ownership to the buyer. The buyer can edit, translate, resell or retire the course as they please. Because of the US writing rules above, this has to be done in a signed document, and a work-for-hire clause only works if the work fits a statutory category. Careful contracts therefore use both: a work-for-hire statement plus a backup assignment of any rights that don't qualify. The buyer also needs to confirm that the people the developer used (freelance writers, narrators, illustrators) assigned their rights to the developer first, since a developer can't transfer what it doesn't own.

Licence-back. The buyer owns the finished course, but the developer keeps (or is granted back) a licence to reuse certain elements: its templates, frameworks, generic modules, tools and know-how. This is common because developers build on their own materials. The buyer should define precisely what counts as the buyer's confidential content versus the developer's reusable background. The developer should make sure it doesn't hand over its tool kit by accident.

The reverse structure is developer-owned content licensed to the buyer. The buyer pays for a build but gets a licence, not ownership. It can be cheaper, and the developer may resell versions to others, but the buyer's use depends on the licence terms: term, scope, update rights and what happens if the developer disappears.

If a contract says nothing, you shouldn't assume the buyer gets ownership. In the UK, the commissioner may get only a limited non-exclusive licence. In the US, a commissioned course outside the work-for-hire categories, with no signed assignment, remains the creator's. For a longer view, note that a US author can terminate a licence or assignment decades later unless it's a work made for hire; section 203 excludes works made for hire from that termination right and otherwise opens a window starting 35 years after the grant.

Perpetual vs term licences

The next question is how long the buyer's rights last.

Term licences run for a fixed period (typically one to three years) and renew. Subscription libraries are nearly always term licences. They give the publisher recurring subscription revenue and a way to update content and prices. The buyer's risk is that access ends if they stop paying, even for courses their people have taken many times.

Perpetual licences give indefinite rights to the version delivered. They suit custom content or compliance modules the buyer wants to keep running. The catch is that "perpetual" usually covers a fixed version. Without an updates clause, a perpetual course on a regulation that changes becomes outdated while the licence stays valid. Sellers often pair a one-time perpetual fee with an annual maintenance fee for updates and support.

Hybrid structures are common: a perpetual licence for a delivered version plus an optional subscription for updates, or a term licence with a right to keep using the last version in archive mode after expiry. If you're a buyer, decide how you'd manage the content if the vendor went away. If you're a seller, decide whether a perpetual grant undermines your renewal revenue.

Scope: seats, enterprise and everything else

The scope clause says who may use the content and how many of them.

• Per seat or named user. A fixed number of identified learners. Cheap to start, rigid to manage.
• Per active learner. Pay for people who actually use the content in a period. This is where licensing meets pricing, covered in per-seat vs per-learner pricing.
• Enterprise-wide (site) licence. Unlimited employees of the buyer, often with a headcount band, so growth through hiring may trigger a true-up.
• Affiliates and subsidiaries. Can sister companies use the content? Does an acquisition extend coverage? Many agreements are silent, and that's where disputes begin.
• Non-employees. Contractors, customers, channel partners and franchisees are often excluded unless the clause says otherwise. A company that trains its resellers on licensed content may be outside its grant.
• Internal vs external use. Using a course to train your own staff is different from using it to train paying customers.

For a vendor selling into large companies, the scope clause is also a negotiation tool. A broad enterprise grant for a higher fee often wins faster than a pile of seat-count amendments. The buyer's side of that conversation is part of how companies buy training.

Territory and language rights

Licences can be limited by geography ("the United States," "worldwide excluding China") and by language ("English only"). Two points matter in practice.

First, territory limits often follow where the licensor holds rights, which might be narrower than where the buyer operates. A course built using licensed stock footage or a third-party framework may carry its own restrictions.

Second, language is a separate right. A licence to use an English course doesn't automatically include a Spanish version. Translating a work is making a derivative work, one of the exclusive rights held by the copyright owner, so it needs permission. The statute lists "a translation" among the examples of a derivative work.

Derivative works and localization

Localization goes beyond translation. It can mean swapping examples, adjusting legal references, changing images and re-recording narration. All of it creates a derivative work.

The contract should settle three things:

1. Whether the buyer may create derivatives at all. Library licences usually say no. Custom-content assignments usually say yes.
2. Who owns the derivative. If the buyer translates a licensed course, does the licensor own the translation? Many publishers say yes, which leaves the buyer with a translated course they can't take elsewhere.
3. Who pays for localization and keeps it current. If the source course changes, the translated version drifts unless someone updates it.

For custom builds, ask for editable source files, not just the finished package. A course delivered only as a locked export can't be localized without the developer.

SCORM packaging as the delivery format

Licensing sets what you may do. Packaging decides how the content reaches an LMS. SCORM (Sharable Content Object Reference Model) is the long-standing format: a course is bundled as a zip file with a manifest, uploaded to a SCORM-compliant LMS, and reports completion and scores back through a standard run-time interface. For the wider platform picture, see LMS vs LXP.

Packaging has contract consequences:

• A SCORM file is a copy. Once a customer has the package, they hold a copy of the work. The licence has to say whether they can keep it after the term, and the vendor has little technical power to take it back. This is why subscription publishers often host content themselves and give access by launch link instead of handing over files.
• Delivery format is a deliverable. For custom work, specify the SCORM version and any other formats needed, plus acceptance testing in the buyer's LMS.
• Source versus package. The package is not the source. A buyer who owns the course but receives only a SCORM export may be unable to edit it. Specify delivery of source files.
• Reporting data. The completion and score data produced by a SCORM course belongs to the buyer's learner records, and the contract should say so, along with who can see it.

The contract terms that matter most

Whatever the model, the same terms carry most of the risk.

A few notes on the ones people skim.

Exclusivity is a price lever. An exclusive licence stops the licensor from selling the same content to your competitors, so licensors charge for it and usually limit it by field, territory or time. Remember that, in the US, an exclusive licence counts as a transfer, so it needs a signed writing.

Termination is where perpetual and term licences show their difference. Decide what the buyer may keep (completion records, archived copies) and what must be deleted, and whether a licensor can terminate for convenience.

Third-party materials deserve their own line. Stock photos, music, fonts and quoted frameworks may carry separate licences with narrower scope than the course itself. A seller who promises full ownership of a course that contains licensed stock imagery has made a promise it can't keep.

The mistakes follow from these terms: assuming payment equals ownership, relying on a work-for-hire clause outside the statutory categories, buying a perpetual licence with no updates clause, forgetting contractors or subsidiaries in scope, and receiving a SCORM package with no source files. Each is cheap to prevent in drafting. For how licensing fits a platform revenue model, see course marketplaces, where creators license content to a platform rather than to a buyer.

Related reading

• Corporate Training Business Models
• Course Marketplaces
• Per-Seat vs Per-Learner Pricing
• Enterprise Learning Procurement
• How Companies Buy Training