Check your rules and notifications
Rules and notifications can drift as a project runs — people leave, works change, and thresholds set at initiation stop matching the stage you're in now.
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, 7am–6pm. Work down the list and ask:
Do the thresholds still match your consent conditions? Approvals get varied, out-of-hours works get approved, 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 7am–6pm won't catch anything on a Saturday shift or a night pour.
Is every monitoring point covered by the rules it should be? New points added mid-project often miss the rules that the original points have.
Is anything duplicated? Two rules on the same parameter at similar thresholds will 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's 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, they need to be added twice.
💡 If people have started ignoring the alerts, you have too many. If exceedances get discovered after the fact, you have too few. Consider adjusting the threshold or frequency of rules that notify if they are a problem
Does every rule need to generate events?
With SiteHive Enviro Pro, rules can record events, logging every instance where the data crosses it.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 rules rather than in the Events tab. Turn off event recording on rules that only need a threshold line or notification, and raise thresholds that are catching normal site activity rather than genuine exceedances. → Events
💡 If you have a backlog of genuine events to work through, Smart Select groups similar events so you can explain 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 — 8am, if a device went offline and didn't recover
Low battery alert — 8am, if a battery drops below 25%
Rainfall alerts — when forecast or recorded rain passes your threshold
The first two do your weekly device check for you. If they aren't on, turn them on.
→ Set up rules and notifications
What's next
Events — categorise and explain exceedances
Check your site details and records — users, site details and daily notes