Monitoring — rules that watch the programme for you
Rules notice inactivity, slipping due dates, expiring credentials and repeated quiz failures, then act. Every rule is configuration you can read and change.
- The problems that quietly derail a rollout get chased without anyone watching a dashboard
- Sensible rules ship switched on — you edit them rather than build them
- Every firing is logged, so you can always see what happened and what it did
- Quiet hours and time zones are respected: nothing lands on someone at 3am
Rules, not code
A monitor is configuration: what to watch for, who it applies to, and what should happen. Nothing on the Monitoring screen needs a release, and nothing runs that you cannot read.
The two kinds of trigger
On a schedule — the rule looks at how long something has been true, on a cron you control, at thresholds you set in days:
| Watch for | Typical thresholds |
|---|---|
| Invite not accepted | 3, 7 days |
| No learning activity | 7, 14, 30 days |
| Due date approaching | 7, 3, 1 days before |
| Credential expiring | 60, 30, 7 days before |
| Seat-time far below the cohort | weekly |
| Time-to-certify running long | weekly |
| Digests | Monday mornings, monthly |
On an event — the rule reacts to something that happened, optionally only after it happens more than once (a quiz failed twice, not once).
What happens next
Actions are the "then" half of the rule: notify the learner, their manager or your admins; assign a path or remedial module; open a review task for a human; add to a cohort; call a webhook; or update a CRM field.
Notifications respect quiet hours and the person's own time zone. A nudge is addressed to the person it is about — it is never a broadcast.
Safe by default
- Shipped rules target active memberships only — nobody who has left is messaged.
- A rule with no audience matches nobody, on purpose.
- Actions can never carry a credential: a token pasted into a rule is rejected by the database, not quietly stored.
- Everything a rule does is written to the firing log with a timestamp.
Monitoring is not judgement
Rules describe a learning plan: what is assigned, what is late, what is expiring. They make no claim about anyone's ability, and none of this is an accreditation.
Frequently asked
What can a rule react to?
Two families. Time-based rules run on a schedule and look at how long something has been true — an invite unaccepted for three days, no learning activity for a week, an exam due in three days, a credential expiring in sixty. Event-based rules react to something that happened: a quiz failed twice, an integrity flag raised, documentation drifting under a published lesson, a credential issued, seats running low.
What can a rule do?
Notify the learner, their manager or your admins (in-app, email, push or Slack); assign a path or a remedial module; open a review task for a human; add someone to a cohort; call one of your endpoints; or update a CRM field. Every rule needs at least one action — a rule that matches and does nothing would look like monitoring without being monitoring, so it cannot be saved.
Do I have to build rules before anything works?
No. Miatz ships a set of safe defaults — inactivity, due dates, credential expiry, repeated quiz failures and documentation drift. The list shows any shipped rule you have not turned on yet, and turning one on creates a normal, editable rule that belongs to you. Nothing runs hidden behind the scenes.
Why does a new rule say it matches nobody?
Because narrow rules fail closed on purpose. A rule with no audience selected does nothing rather than messaging your whole organization by accident. Tick 'everyone in this organization', or pick at least one role, population, membership status, team, cohort or tag.
Will a rule message someone who has left?
No. The shipped rules target active memberships only, so a suspended or off-boarded person is never nudged. If you build your own rule, choose the membership statuses you mean.
Who can change rules?
Owners, org admins and enablement managers can create and edit them. Team managers and analysts can see the rules and the firing log but cannot change them. That split is enforced in the database, not just in the interface.
Related guides
One score per person, rolled up per team and per cohort, from learning done, proof earned and practice applied — with a one-click nudge for whoever is behind.
ReadSend alerts and outcomes where your team already works. Every delivery is signed, and the signing key is shown once and never stored anywhere it can be read back.
ReadLive adoption, progress and readiness for your organization, built from the activity stream.
Read