01
Rules
Instance-wide under policy, and per form in the builder. An event, a scope, the recipients, push or not.
Where it starts
Everyone is copied, so nobody reads it
Results go out on a distribution list, session changes by text message, expiring licences by a reminder in somebody's own calendar. The important message sits in the same inbox as the forty others, and the trainee finds out about the moved session from a colleague.
- One mailing list for everything
- Calendar entries typed by hand and never updated
- No record of who was told what
What Qualify does
Rules say who is told, people say how
A notification rule names an event, the form or programme it applies to, and the recipients: the person the record is about, and the people you name, such as the fleet manager or the training postholder. "Tell me when this form fails" lives on the form itself. Each person then decides how they are reached: in the app, by email, by push, and whether they want calendar invitations.
- A do-not-disturb switch that holds messages in the bell rather than losing them
- Whole areas muted with one switch, and a list of everything you muted
- An invitation for every session you are on that updates itself when it moves
- Queues and lists that refresh on their own while the panel is open
What you end up with
Fewer messages, all of them read
- The trainee's acknowledgement of a result, prompted the moment it is approved
- An instructor booked without authorisation reported to whoever watches compliance
- Expiring licences, medicals and checks warned about on the schedule you set
- Every notification kept, with a link to the thing it was about
How the product runs it
Three layers, narrowest last
02
Channels
Each person's own: in-app, email, push, calendar invitations, and do not disturb.
03
Categories and events
Mute an area, or one event inside it. New events arrive switched on, never silently muted.