Set learning review rules for each kind of change

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.

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 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.

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.

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.