Check your rules and notifications
Rules and notifications drift as a project runs: people leave, works change, and thresholds set at the start stop matching the stage you're in now. Once a month, check the rules, the recipients and the device alerts.
Are your rules still right for the works?
Open Settings > Rules & Notifications.
Each rule is an aspect, a parameter, a threshold and a time of day: noise, sound level, 65 dB, 7 am to 6 pm. Work down the list and ask:
Do the thresholds still match your consent or approval conditions? Approvals get varied, out-of-hours works get approved, and stages change what's permitted. A rule that hasn't moved since mobilisation may be measuring you against conditions that no longer apply.
Do the time windows match how the site actually runs? A daytime rule running 7 am to 6 pm won't catch anything on a Saturday shift or a night pour.
Is every Monitoring Point covered by the rules it should be? Monitoring Points added mid-project often miss the rules the original ones have.
Is anything duplicated? Two rules on the same parameter at similar thresholds fire twice for the same exceedance.
Are the right people getting the right alerts?
Recipients aren't the same as users. A notification recipient exists purely to receive email or SMS, and removing someone from your user list does not stop their notifications.
Work down the recipient list:
Is everyone on it still on the project? Remove anyone who has moved on.
Is anyone missing? New starters, a new environmental advisor, a new site manager.
Is each person on the right rules? Recipients can be scoped to specific rules, so the site manager and the acoustic consultant don't need the same alerts.
Right channel? Email and SMS are separate recipient entries. If someone needs both, add them twice.
💡 If people have started ignoring the alerts, you have too many. If exceedances are being discovered after the fact, you have too few. Adjust the thresholds, or the number of rules that notify, until the alerts are worth reading.
Does every rule need to generate events?
With SiteHive Enviro Pro, a rule can record events, logging every time the data crosses its threshold. Events are worth recording where you'll need to investigate, explain and report the exceedance.
They're not worth recording on a rule you've set purely as a visual reference, or on a threshold so low it trips several times a day.
If you're buried in events, the fix is usually here in the rules rather than in the Events tab. Turn off event recording on rules that only need a threshold line or a notification, and raise thresholds that are catching normal site activity rather than genuine exceedances. How events work: Events: investigate an exceedance.
💡 A backlog of genuine vibration events? Vibration Smart Select picks out the events below your chosen criteria so you can deal with them in bulk rather than one at a time.
Device and weather notifications
Separate from rule-based alerts, and easy to forget. In Settings > Rules & Notifications > Notifications:
Offline device alert: sent at 8 am if a device went offline and did not recover.
Low battery alert: sent at 8 am if a battery dropped below 25%.
Rainfall alert: when the rainfall forecast passes your threshold.
The first two do your weekly device check for you. If they aren't on, turn them on. Steps: Set up rules and notifications.
What's next
Events: investigate an exceedance (categorise and explain exceedances)
Check your site details and records (users, site details and daily notes)
Maintaining your site (the monthly routine this check belongs to)