InnerWeb
Skip to main content

Checklist for the quarterly review of report rules and recipients

Report rules are configured once, but the plant keeps changing: people change positions, new halls open and old departments disappear. The checklist below helps the IT and OHS teams check once a quarter whether reports reach the right people and cover the right scope.

5
notification channels in the System activity section
Source: reporting feature card
4
review quarters a year
Source: review rhythm assumption

Why review every quarter

A report that reaches a person who has changed position is noise. A report that the new hall manager does not receive is a gap. Both situations arise because rules are set at the time of implementation and reviewed rarely.

A quarter is a sensible rhythm: it is enough to notice changes without being a burden. A review usually takes a few dozen minutes if there are several rules, and it can be combined with an OHS meeting.

Recipients and roles

Rule recipients are specified by email addresses and by roles. Start the review with the list of named addresses: check whether each person still works in the plant and still should receive the given report.

Wherever possible, replace named addresses with roles. A role does not change along with the person, so the report reaches the successor without any intervention by the administrator. It is also worth checking who has permission to configure rules: the administrator, manager, OHS, technical department and supplies administrator roles.

Areas of the quarterly rule review

Areas of the quarterly rule reviewBar chart of checklist item counts across five review areas0123number of checklist itemsRecipients and rolesRecipients and roles: 3 number of checklist items3Location scopeLocation scope: 2 number of checklist items2Frequency, format, contentFrequency, format, content: 2 number of checklist items2System activitySystem activity: 1 number of checklist items1Disabled and duplicated rulesDisabled and duplicated rules: 2 number of checklist items2
Source: Breakdown of the checklist items on this page

Location scope after plant changes

An empty location scope means all locations, so new halls enter such a rule automatically. Rules with selected locations require manual correction after every structural change: a new hall, a merger of two departments, a closed zone.

Check that every location has at least one rule with the right recipient. Two rules with different locations and recipients can run side by side, so a gap usually stems from a missing rule, not from a conflict.

Frequency, format and content scope

Ask the recipients whether the frequency suits them. A daily report that nobody reads is worth changing to weekly. A monthly report that arrives too late for decisions can be supplemented with a weekly one.

Also check the format and the content switches: whether management still needs the details, or whether charts and the comparison with the previous period are enough, and whether anyone uses XLSX, since it is sent to everyone.

System activity in the report

The System activity section shows logins by real users and notifications by channel: SMS, push notification, email, telephone and webhook. During a review it is a hint as to which channels actually work and whether users use the system.

When there is no data for a channel on a given instance, the report shows an explicit information that it is unavailable, rather than a zero. This should not be read as a lack of activity. The distinction matters when deciding whether to switch on another channel.

Disabled and duplicated rules

Switching a rule off pauses sending without deleting recipients or history, so rules disabled long ago can remain in the system. Review the list: remove the rules that are not needed, and switch back on those that are.

Also check for duplicates: two rules with the same scope and the same recipients mean double messages. The dispatcher sends a report once per rule and period, but with two rules every recipient gets two emails.

Recording the review and next steps

After the review, record the date, the people taking part and the changes. Such a short record is evidence for an audit that the plant supervises the flow of safety information, rather than having switched on reports once.

If the review found gaps, plan the fixes within a week. A test report to one address will help confirm that the change works before sending is switched back on.

Checklist

Video

Frequently asked questions

How often should report rules be reviewed?

Every quarter and after each major organisational change: a new hall, a reorganisation of departments or a change of people in key positions.

Is it better to enter recipients by name or by role?

Roles are more durable, because the report reaches the successor without administrator intervention. Keep named addresses where the report is meant for a specific person.

Does missing channel data mean no notifications?

No. When there is no data for a channel on an instance, the report shows an explicit information that it is unavailable, rather than a zero.

Plan a report review at your plant

We will help set the review rhythm and the list of rules to check. Book a call with InnerWeb.

Let's talk