A high-usage alert arrives on Friday afternoon. Three people see it, nobody owns it, and by Monday it has disappeared beneath newer messages. The platform detected a possible issue. The operating process failed to turn that signal into a decision.
Useful alerts need more than thresholds. They need a response path that tells the team what to check, when to escalate, and what evidence closes the issue. A short playbook can make a small team more consistent without adding a meeting for every notification.
In this guide
Describe the signal accurately
An energy alert identifies an unexpected condition in the available data. It does not establish the cause. A spike may reflect a legitimate event, a delayed upload, a unit error, or an equipment issue. First record the property, meter, timestamp, observed value, and expected range.
Match the alert wording to data frequency. A monthly bill upload supports a retrospective consumption review. It cannot identify a fault in the minute it happens. Explain those limitations so operators know which notifications need immediate site investigation and which need a data check.
Assign an owner and a backup
Make one person responsible for the initial response at each property. Name a backup for leave, weekends, and shift changes. The owner can delegate technical work, but should retain responsibility for the status and next step.
Set response expectations based on operational risk and the suspected magnitude of waste. A noncritical consumption deviation may wait for the next working day; a condition affecting safety or critical operations must follow the site's established emergency procedures. An energy notification should not replace those systems.
Check the data before sending a technician
Confirm that the period is complete, the units are correct, and the reading is not a duplicate or correction. Check planned events, holiday schedules, new tenants, and unusual weather. A short documented review can prevent unnecessary callouts.
Do not dismiss a signal simply because the first explanation sounds plausible. If extended operating hours explain the increase, compare the magnitude with those hours. Record the evidence and review again if the pattern continues beyond the event.
Use a practical triage table
| Finding | Next action | Closure evidence |
|---|---|---|
| Duplicate or incorrect record | Correct with traceability | Reconciled source and active total |
| Planned operating event | Document dates and expected impact | Return to expected profile after event |
| Unexplained after-hours load | Check schedules and equipment status | Verified cause and follow-up readings |
| Persistent mechanical symptom | Escalate to qualified maintenance staff | Repair record and operating check |
Use statuses such as open, investigating, awaiting repair, and resolved. Acknowledged means someone has seen the alert; it should not mean the issue has been fixed.
Prioritize with a bounded estimate
For illustration, an unexplained additional 10 kW sustained for 12 hours is 120 kWh. At an assumed $0.15/kWh marginal energy price, that is $18 of energy for the period. If it persists for seven similar days, the simplified energy amount becomes $126.
That estimate helps prioritize investigation, but it does not include demand charges or establish the cause. Avoid multiplying a brief spike by a month unless evidence shows it is continuous. State the assumed duration so the priority remains understandable.
Close the loop after the action
Record the cause, action, owner, completion time, and verification period. Compare the subsequent profile with expected conditions. If the alert returns, reopen the issue or document why the threshold should change. Silencing the alert is not verification.
The Department of Energy's measurement and verification guidance reinforces the value of a defined baseline and post-action comparison. For everyday alerts, apply that principle at a scale proportionate to the decision.
Review the rules that create noise
At a regular operations review, examine repeated alerts, false positives, and issues that took too long to resolve. Adjust rules for legitimate schedule changes and known data delays. Keep a record of why a threshold was altered so noise reduction does not hide a real deterioration.
Energy Wiz can help organize usage, budgets, and notifications. The practical improvement comes from connecting the available signal to a named person, a documented action, and evidence that the problem is resolved.
Turn your next energy review into action
Bring your utility records, operating observations, and improvement priorities together with Energy Wiz.
Get started