# Notify only when an event needs attention An event definition, intended recipients and approved channel. Updated October 27, 2026 ## Notifying people about learning events, in short Learning event notifications are single messages sent to the person who can act when something in training needs attention, and to nobody else. They suit managers who maintain training tied to changing instructions and would rather get one useful message than a stream of alerts. Reminders before a deadline or before a certification expires are planned, not available today; today Elvina drafts each message for the people with work still open, and a manager sends it. A notice that a changed source affects a lesson is planned, not available today. Messages through Slack or Teams are planned, not available today. ## 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 course deadline and the date a certification expires | A message for each date, addressed only to people with work still open, for a manager to send | available now | | The updated lesson and the people assigned to it | Completion status per person on the revised lesson, with dates | available now | | The rule for who may be notified and when | Learner messages held as drafts until a manager approves them | available now | ## Who this is for, and when A regulatory affairs manager at a medical device distributor maintains the product-handling training. When the manufacturer updates a handling instruction, the lesson that cites it goes stale, and she finds out weeks later from a sales rep. She wants exactly one message when a source change affects a lesson (sent to the lesson owner, with a link to the draft) and no alert storm for everything else. ## How it works in Elvina Reminders, progress digests and an alert that a source update affects a lesson are planned, not available today; today Elvina drafts each message for a manager to send. - She agrees on what counts as an event: a new revision of a source that at least one lesson cites. - She names the intended recipient (the lesson owner) and the channel a person will send the notification through. - When the owner reports the new revision and the lessons that cite it, Elvina drafts one notification stating which source changed, which lesson it affects, and a link to the revision draft in Creation Studio. - The owner opens the draft, reviews the proposed change, and decides whether to publish. ## A worked example A fictional distributor, Meridian Medical Supply, carries products from 30 manufacturers. The lesson 'Cold Chain Handling for Reagent Kits' cites Manufacturer Handling Bulletin 14. The manufacturer issues Bulletin 15, and the regulatory manager uploads it as a new revision with the same source identity. - One notification to the lesson owner: 'Bulletin 15 replaces Bulletin 14; one lesson cites it; review the draft.' - No notification to the 140 warehouse learners assigned to the lesson, because the change is not yet approved. - The owner reviewed the draft the next morning and published a revision with the new temperature range. ## What to check before relying on it Prevent duplicate alerts and respect permissions. Do not claim delivery until the supported channel confirms it. - One event produces one notification per recipient, with no duplicates. - The recipient is the person who can act on the event, not everyone assigned to the lesson. - The notification links to the exact draft or item that needs attention. - Delivery is confirmed by the channel before it is reported as sent. ## Where a person stays in charge Event-triggered notifications are planned, not available today. Today Elvina drafts the notification and names who should receive it, and a person sends it; she does not claim a message was delivered. Slack, Teams and similar channels are planned, not available today, not assumed. Recipients are limited to people with permission to see the item, and the manager sets the rules. ## Who this is not for, and when another tool fits ### This is not the right fit if - You want every learner told about every change as it happens. - You need a message delivered by text or a messaging app today. - Nobody owns the lessons, so there is no one to notify. ### 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 we notify learners when a lesson they completed changes? That is a separate event with its own rule and recipients. Define it explicitly so learners are told only after the owner has published. **Q:** What stops a source update from triggering ten alerts? Today a person decides when to send, so nothing fires on its own. The planned design defines an event once per source revision and groups it by recipient, so a change affecting three lessons owned by one person produces one message. **Q:** Who should receive a reminder about a deadline? Only people who still have work to do before that date. Leave out anyone who has finished or left, and keep the number of reminders to what your policy allows, so the message still gets read when it matters. ## 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/notify-learning-events#talk-to-elvina) Checked October 27, 2026. No launch date is committed for planned features.