# Update terminology across a course, with exceptions

An approved terminology change and scope of affected lessons.

Updated October 27, 2026

## Replace a term consistently, with exceptions

Updating terminology across a course means changing a word everywhere it should change, such as a renamed job title, while leaving quotations, product names and archived records exactly as they were. It suits operations and training leads after a company-wide rename. Elvina finds each occurrence across lessons, quiz feedback and job aids, shows it in context and proposes replace or keep; editing any module, slide, text or quiz question is available now. A person approves the list, and narration that speaks the old word is re-recorded rather than altered.

## What happens on the free demo

- Book 30 minutes. Pick a time with Elvina's team. The demo is free and runs on Zoom.
- Show the team your goal. Bring one role or one procedure. The team shows how Elvina would handle it, using sample materials.
- Agree on the next step. You leave with a plan for the first step and its price. Nothing reaches your team until you approve it.

## What you bring and what Elvina returns

| You bring | Elvina returns, for your approval | Status |
|---|---|---|
| The old term, its replacement and the course it appears in | Proposed edits for every occurrence in lessons and quiz feedback, each shown in context | available now |
| The two job aids that also use the old title | Both job aids updated to the new term, quotes and product names left as is | available now |
| The person who signs off on the full change list | A replace-or-keep list for that person’s approval, with spoken narration noted separately | available now |

## Who this is for, and when

A customer-operations lead at a regional internet provider is renaming the frontline role from 'agent' to 'advisor' across the company. The support-skills course mentions 'agent' in lesson text, quiz feedback, two job aids and a recorded customer quote from a case study. She wants the change made consistently everywhere it should apply: and left alone in the customer's quoted words, the product name 'Agent Desktop', and the archived tickets.

## How it works in Elvina

A draft replaces the old role name in lesson text, quiz feedback and job aids while preserving historical quotations.

- She defines the approved change ('agent' to 'advisor') and the scope: the support-skills course, its job aids and quiz feedback.
- Elvina finds every occurrence in Creation Studio and shows each in context, proposing replace or keep for each one.
- Occurrences inside quotations, product names and source titles are proposed as keep by default, with the reason shown.
- She reviews the list, overrides where needed, and applies the change as a new course revision on the Learning Platform.

## A worked example

A fictional provider, Bluewater Broadband, trains 220 frontline staff with a nine-lesson support-skills course. The word 'agent' appears 63 times across the course, two job aids and quiz feedback. Four occurrences are inside a quoted customer story that must stay as written; five are the product name 'Agent Desktop'.

- Fifty-four replacements applied in lesson text, quiz feedback and both job aids.
- Nine occurrences kept: the four in the customer quotation and the five product-name references, each with its reason recorded.
- A revision note listing every change, so the reviewer could spot-check without rereading the course.

## What to check before relying on it

Inspect context before bulk replacement. Product names, source titles and archived records may need to remain unchanged.

- Every occurrence of the old term was shown in context before any replacement.
- Quotations, product names and source titles were kept unless a person chose otherwise.
- The change produced one new course revision with a complete change list.
- Archived records outside the course scope were not touched.

## Where a person stays in charge

Bulk replacement is a drafting aid, not a search-and-destroy tool. Elvina proposes each change in context and defaults to keeping anything that looks like a proper noun, a quotation or an archived record. The operations lead approves the list, and any narration or video that speaks the old term is flagged for re-recording rather than altered.

## Who this is not for, and when another tool fits

### This is not the right fit if

- You want a blind find-and-replace with no review of each case.
- The new term has not been approved yet.
- You need archived records outside the course rewritten too.

### Another kind of tool may fit better

- A course library, when the topics are general skills rather than your own procedures.
- An instructional designer, for a large program with branching scenarios or live workshops.

## Questions

**Q:** Can the change apply to several courses at once?

Yes, course by course, each with its own review list and revision. That keeps the change auditable per course.

**Q:** What about grammatical forms like 'agents' or 'agent's'?

Elvina finds the variants and shows each so the replacement reads correctly. Plurals and possessives are handled per occurrence, not blindly.

**Q:** How do I decide which occurrences to keep?

Keep the old word where changing it would alter a fact: a customer’s quoted words, a product name, a document title or a record of what happened. Replace it where the text describes the role as it is today.

## Two things you can check on this site

- See a sample on the demo. [Book a demo with my team](https://calendly.com/o-dutchak-smartexpert/30min?utm_source=elvina-site&utm_medium=proof)
- Every lesson, plan and quiz stays a draft until you approve it. [Check the approval step in the chat](/skills/update-terminology-across-course#talk-to-elvina)

Checked October 27, 2026.

No launch date is committed for planned features.