# Set learning review rules for each kind of change

Content types, risk levels and accountable reviewers.

Updated October 27, 2026

## Define who can approve which change

Learning review rules decide which person must approve which kind of training change: policy edits go to the source owner, language variants to a reviewer fluent in that language, layout fixes to the content editor. They suit governance and training leads in teams that span sites or languages and have seen the wrong person sign off. Elvina drafts and versions the rule set with a backup and an escalation contact for each type; a person approving material before it is published or assigned is available now. Enforcement depends on the permissions configured for your deployment.

## 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 kinds of change the team makes and who owns each | A versioned rule set routing each change type to an approver, backup and escalation | available now |
| The languages the training ships in and fluent reviewers | Language variants routed to a reviewer who reads that language before approval | available now |
| Reviewer names, with the sites and languages they cover | Reviewer groups by site and language, each with a named backup | available now |

## Who this is for, and when

A learning governance lead at a software company with teams in Texas, Ontario and Mexico City keeps finding that a French-Canadian lesson was approved by someone who does not read French, and a security-policy change was approved by the localization team. He needs rules that route each kind of change to the right reviewer, cover what happens when that reviewer is out, and are honest that a rule written here is not the same as an enforced permission.

## How it works in Elvina

A rule proposal routes policy changes to the source owner and language changes to a qualified locale reviewer.

- He lists the content types, the risk level of each, and the accountable reviewer role, with owners from Company Knowledge.
- Elvina drafts a rule set in the Web workspace: policy changes route to the source owner, language changes to a qualified locale reviewer, cosmetic changes to the content editor.
- Each rule includes an absence path (who reviews when the primary is unavailable) and an escalation contact.
- He approves the rule set, and the Learning Platform applies it to review requests where the deployment supports enforcement.

## A worked example

A fictional company, Tidewater Systems, maintains training in English, French and Spanish for 600 employees. Content types are policy, procedure, language variant and layout. The security officer owns policy sources; two locale reviewers cover French and Spanish; the content editor handles layout.

- A rule table with four content types, each with a primary reviewer, an absence backup and an escalation contact.
- Policy changes to any security lesson now route to the security officer, with a backup named for her vacation weeks.
- The French lesson approved in error was flagged and re-routed to the French reviewer.

## What to check before relying on it

Define absence and escalation handling. A rule described here is not a guarantee of enforced product permissions.

- Every content type has a primary reviewer, a backup and an escalation path.
- Reviewers for language variants are documented as qualified in that locale.
- The rule set states which rules the platform enforces and which rely on process.
- Rule changes are versioned with the approver named.

## Where a person stays in charge

A rule set describes intent. Whether the Learning Platform enforces a given rule (blocking an unqualified approver, for instance) depends on the permissions configured in the deployment and is confirmed during setup. Elvina drafts and versions the rules; it does not grant or remove anyone's permissions on its own.

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

### This is not the right fit if

- You expect a written rule to block an approver the platform was never configured to block.
- One person approves everything and the material rarely changes.
- You need Elvina to grant or remove anyone’s permissions.

### 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:** What happens when both the reviewer and the backup are out?

The request escalates to the contact named in the rule. If none is named, the rule set flags that gap before approval.

**Q:** Can a reviewer approve their own change?

The rule set can forbid it, and the platform enforces that where configured. Otherwise it is a process rule to audit.

**Q:** How often should review rules be revisited?

Whenever a reviewer changes role, a new language or site is added, or an approval goes to the wrong person. Each change to the rule set is saved as a new version with the person who approved it named.

## 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/set-learning-review-rules#talk-to-elvina)

Checked October 27, 2026.

No launch date is committed for planned features.