Illustrated cover reading "Course Branding for Multiple Clients" on an aqua and coral background with a halftone pattern

Course Branding for Multiple Clients: Build One Course, Ship Many Brands

Table of Contents

Share:
Easily share intel
Summarise this page with your favorite AI assistant

Course branding for multiple clients means building one master course and applying each client’s logo, colors, fonts and wording from a separate brand layer, instead of keeping a hand-edited copy for every client. When it works, a fix to the master reaches every client version. When it fails, you maintain ten copies that drift apart.

Searching “course branding” mostly returns courses about learning branding. This post is for a training provider or instructional designer who sells the same course to several corporate clients and needs each to look like its own.

Key takeaways

  • Brand a course in four layers; a theme swap only reaches the first.
  • Keep one master with variants when clients differ only in brand and wording; copy the course only when objectives, scenarios or assessments differ.
  • Check each client’s brand colors against WCAG contrast before building. In our worked example, two of four hypothetical brands fail with white text.
  • Export one clearly named package per client variant, and never overwrite one client’s package with another’s.

What does course branding for multiple clients involve?

Course branding for multiple clients involves four separate layers: visual tokens such as logo, colors and fonts; content variables such as client names and terminology; baked-in media such as screenshots and narration; and the package that carries tracking. Keeping the layers apart lets one master course serve many brands.

Top guides to branding an eLearning course, such as those from TalentLMS and eLearning Industry, focus on logo, palette, fonts and imagery. That is layer one; the other three layers are where multi-client work usually goes wrong.

Layer What changes per client Typical failure
1. Visual tokens Logo, colors, fonts, button style A color set by hand on one screen, which the theme never updates
2. Content variables Company name, product names, role titles, policy names, contacts The previous client’s name left in quiz feedback
3. Baked-in media Screenshots, narration, diagrams, certificates A logo inside a screenshot, or narration that says a client’s name
4. Package and tracking Course title, exported package, LMS import One client’s package overwriting another’s

Keep client marks out of media you cannot easily edit. In a 2019 Adobe community thread, a creator wanted a reseller’s clients to swap in their own logos after publishing, but could not find the logos in the published HTML5 files, and no solution was confirmed. Build the swap before you export.

The contract side of selling a course under a client’s name is covered in our guide to white-label eLearning for corporate clients. This post covers the authoring technique.

Should you keep one master course with variants or copy the course for each client?

Keep one master course with client variants when clients differ only in brand and wording. Make a separate copy, a fork, only when a client needs different learning objectives, scenarios or assessments. Copying is easy; the cost is that every future fix must be repeated by hand in each copy.

Duplicating is usually possible: an Articulate staff member confirmed in a community thread that a Rise course can be copied to brand it differently for different departments. The question is whether you should.

Client request Choose Reason
New logo, colors, fonts, company name Variant Only layers 1 and 2 change.
Their own example or policy on one or two screens Variant with swapped screens Keep those screens as separate, replaceable blocks.
Different pass mark or quiz questions Fork Assessment logic is course design, not brand.
Different objectives or audience Fork It is now a new course that shares material.
Screen-by-screen edits for one client Fork Our rule of thumb: if you keep editing individual screens for one client, it has already become a fork.

What belongs in a client brand intake sheet?

A client brand intake sheet collects every brand decision before production starts: logo files, hex colors, fonts, logo placement, terminology, accessibility expectations and the person who signs off. Collecting it once prevents the rework that comes from guessing the brand from a website.

Connie Malamed’s visual style guide for eLearning (April 2026) lists similar building blocks for one project, such as hex swatches and the logo version for the title screen. Ask each client for:

  • Logo files: SVG or transparent PNG, a light version for dark backgrounds, and a minimum size.
  • Colors: primary, secondary and neutral colors as hex codes.
  • Fonts: exact family names, and whether a browser-delivered course may use them.
  • Logo placement: title screen only, every screen or footer.
  • Terminology: company name as written, product names, role titles, words to avoid.
  • Accessibility: the conformance level expected, such as WCAG 2.2 AA.
  • Approver: one named person, and the number of review rounds included.

Logo placement is a real decision. An experienced Articulate community member advised a splash screen, not a logo on every slide, for an external audience, and a title slide with an “internal use only” note for employees. Others noted some clients want a corner logo everywhere, so show options.

How do you set up course branding as theme tokens?

Set up course branding as theme tokens by naming each design decision by its role, such as primary, text on primary, background and link, and storing the client’s values in one theme, brand or slide master. Switching clients then means swapping values, not editing screens.

  1. Name tokens by role, not color, so one course structure works for any palette.
  2. Store values in the brand object only. Zensai’s Content365 help article warns that manual color changes on an individual screen override theme colors and are not saved back to the theme.
  3. Build one brand per client and apply it to the whole course at once.
  4. Apply the brand to a duplicate of the master, then run the sweep below.

As of October 2026, Articulate’s Rise 360 Brands support article says a brand holds a logo, colors (one primary plus optional additional colors) and heading and body fonts, including uploaded .woff files. An account can have any number of brands, and a brand can be applied to several courses from the dashboard. Layout settings are not listed.

In Storyline 360, the slide master guide (updated October 15, 2026) says updating a master applies to every slide using it. Reusable interactive block templates follow the same logic: build once, restyle through tokens.

Do your clients’ brand colors pass contrast checks?

Client brand colors can fail contrast checks when used for text or button fills. WCAG 2.2 Success Criterion 1.4.3 requires at least 4.5:1 for normal text and 3:1 for large text, and Criterion 1.4.11 requires 3:1 for interface components. Check each palette before you build, not after the client reviews it.

The W3C’s page on WCAG 2.2 Success Criterion 1.4.3 defines large text as at least 18 point, or 14 point bold. It also says “Text that is part of a logo or brand name has no contrast requirement,” but the text and buttons around a logo still have to pass.

The table uses four invented colors, not any real company’s, with ratios we calculated using the WCAG relative luminance formula. A brand color as text on white has the same ratio as white text on that color.

Hypothetical client Brand color White text on it Dark text (#1A1A1A) on it What to do
A (amber) #F5A623 2.03:1, fails 8.59:1, passes Dark text on buttons. For amber text on white, use a darker shade such as #8A5A00 (5.93:1).
B (teal) #1B7F8C 4.71:1, passes 3.70:1, fails White text works with little margin. Do not lighten it.
C (orange) #E8590C 3.58:1, large text only 4.86:1, passes Dark text for body-size labels, or darken the fill.
D (navy) #1F3A68 11.27:1, passes 1.54:1, fails White text; no change needed.

Pro tip: Add An On-Brand Text Token. Do not hard-code white text on colored buttons in the master. Create a “text on primary” token, so Client A’s amber button gets dark text and Client D’s navy button keeps white.

When a client’s exact color fails, keep it for large areas and accents, use a darker shade for text, and get written approval. This is not legal advice; if a contract names an accessibility standard, have a specialist review the course.

How do you keep each client’s tracking and versions separate?

Export one package per client variant and name it clearly, so each client’s LMS tracks its own course record. A SCORM package is a self-contained zip file with the manifest at its root, so a variant is a new export, never an edit to another client’s package.

The SCORM content packaging overview says every file needed to deliver the course should be inside the package and listed in the manifest.

Copies can cause tracking trouble. In an Articulate community thread, staff said each LMS publish from Rise creates a unique identifier, and users reported blank screens when an edited copy replaced a course learners had started. The thread shows no confirmed fix. SCORM Cloud’s versioning guide also warns that changing course files can make existing registrations incompatible.

Import each variant as its own course in that client’s LMS, and test any replacement with a learner who is partway through. Our checklist for updating old SCORM courses covers safe replacement. To track which client has what, keep a variant register:

Client Package name Master version Brand version Last sweep Tested in client LMS
Client A course-name_clientA_m3 3 1 Date Yes or no
Client B course-name_clientB_m2 2 2 Date Yes or no

A client on master version 2 while the master is on version 3 is your update queue.

What should a pre-delivery branding sweep check?

A pre-delivery branding sweep is a fixed checklist that looks for the wrong client’s marks in every place a brand can hide. Run it on each exported variant before sending it, because a theme swap never reaches text, media and package details.

Work through these checks:

  1. Title screen and footer: right logo version, size and client.
  2. Course title and description as they appear in the LMS catalog.
  3. Quiz questions, feedback, narration and captions that name a company or product.
  4. Screenshots, charts and diagrams showing old logos or colors.
  5. Certificate and completion messages.
  6. Alt text on logos and images.
  7. Links, email addresses, phone numbers, hidden slides and notes.
  8. Fonts rendering correctly on a clean browser with no client font installed locally.

Then test the package using our guide to testing a SCORM package before it reaches a client’s LMS.

Pro tip: Keep A Never-Again List. Each time a client finds a leftover, add that location to the sweep.

Which authoring tool features make course branding easier across clients?

Look for a brand or theme stored separately from the course, applicable to many courses in bulk, with custom fonts, logo variants and a way to find per-screen overrides. Ask each vendor to switch one course between two client brands in a live demo.

As of October 2026, vendor documentation shows the range (we did not test these):

  • Articulate Rise 360: Brands hold logo, colors and fonts, applied in bulk.
  • Articulate Storyline 360: slide masters carry theme colors and fonts across slides.
  • Zensai Content365 Authoring: a brand kit with logos, themes and a shared asset library.

Disclosure: SimpliAuthor is a SimpliTrain product, made by the same company that publishes this site. Its published pages describe AI course authoring, editable blocks, a reusable asset library, a free SCORM converter and a paid Visual SCORM Editor for compiled SCORM. They do not describe a brand kit, themes or per-client brand switching, and we did not test any.

What should you do next?

Pick the course you resell most and fill in the four-layer table for it. Mark every item that is currently hard-coded on a screen, such as a logo, a color or a client name. That list is your rebuild plan.

Then check contrast for your three busiest clients, start a variant register and add the intake sheet to onboarding.

To see how SimpliAuthor handles reuse, read about AI course authoring in SimpliAuthor or request a SimpliTrain demo, and ask to see one course switched between two client brands.

Frequently asked questions

Can I duplicate a course for each client?

Usually yes. Articulate staff confirmed a Rise course can be duplicated to brand it differently. Duplicate only for a true fork, such as different objectives or assessments. For brand-only differences, keep one master and apply a separate brand to each variant.

What is the difference between a brand kit and a theme?

Tools use the terms differently. Articulate’s Rise 360 Brands hold a logo, colors and fonts, while Zensai’s Content365 themes bundle colors, fonts and logos inside a brand kit. Check what your tool stores in each, and whether it can apply one to many courses at once.

Do client logos have to meet WCAG contrast requirements?

WCAG 2.2 says text that is part of a logo or brand name has no contrast requirement. The W3C adds that a logo shown at low contrast by the author’s choice is not exempt. Surrounding text, buttons and links still need to pass. This is not legal advice.

Where should a client’s logo go in an eLearning course?

It depends on the audience. Experienced Articulate community members suggest a splash or title screen for external audiences, and the title slide with an “internal use only” note for employee-only courses. Some clients want a logo on every screen, so show options.

Why does an LMS reject or break a copied course?

Articulate community reports link it to the package identifier. Staff said each Rise publish to an LMS creates a unique identifier, and users saw blank screens when an edited copy replaced a course in progress. No confirmed fix appears in that thread, so test replacements first.

Want to learn more?

Reach out to us to learn more.

One Platform for
All Your Training Needs

Get a personalized demo.