A monthly electricity savings review meeting is a short, disciplined review of bill trends, demand, PF, production context and open saving actions. It keeps energy work alive after the audit, vendor visit or owner instruction. Without a monthly routine, even good savings actions slowly fade.
The meeting does not need drama. It needs the right people, the latest bill and a short action tracker. The owner should leave knowing what changed, why it changed and who will act before the next bill.
Who should attend the meeting?
Invite people who can explain the bill and change behaviour. A meeting with only accounts will become accounting. A meeting with only maintenance will miss tariff and production context.
A practical group includes:
- Owner, director or plant head.
- Accounts person who handles the electricity bill.
- Maintenance or electrical in-charge.
- Production or operations representative.
- Purchase or project person when capex is active.
- Consultant or vendor only when their action is under review.
Keep the group small enough to decide. If every department sends a listener, nobody owns action.
Which bill KPIs should be reviewed?
Review the fields that explain cost movement. Do not stare only at the final payable amount because tariff adjustments, arrears and taxes can blur the signal.
Use a simple dashboard:
| KPI | Question |
|---|---|
| kWh and kVAh | Did energy use or PF behaviour change? |
| Maximum demand | Was there a peak event? |
| PF or penalty | Is correction still working? |
| ToD rows | Did timing help or hurt? |
| Production notes | Does the bill match business activity? |
The monthly bill tracking article gives the base discipline. The meeting is where those fields become decisions.
How should abnormal months be handled?
Abnormal months should be marked, not ignored. A festival shutdown, new machine trial, monsoon humidity, order rush, power cut or maintenance breakdown can distort comparison.
Ask:
- Was production higher or lower?
- Did shift timing change?
- Was any large equipment added or removed?
- Did the DISCOM bill include arrears or adjustment?
- Was there a breakdown or bypass running?
- Did any saving action stop working?
One note beside the month can prevent a long argument later. Owners remember big events, but details fade quickly.
How do you keep action trackers useful?
An action tracker should be short and alive. It is not a report appendix. Every open action should have one owner, one next step and one proof method.
Good tracker columns are:
- Action.
- Area.
- Owner.
- Target bill or operating effect.
- Due date.
- Current status.
- Proof seen.
Close actions only when evidence is visible. For example, “compressor leaks fixed” should mean leak points were repaired and compressor behaviour was checked, not only that a contractor visited.
How can the meeting keep vendors honest?
Vendors are useful, but their claims need review. APFC, VFD, compressor, HVAC, lighting and solar vendors may all show savings differently. The monthly meeting should compare claims with bills, logs and site conditions.
Ask vendors:
- What baseline was used?
- Which bill line should change?
- What measurement proves the result?
- What maintenance is needed to keep saving?
- What has changed since commissioning?
For larger projects, use M&V for electricity savings. It gives the meeting a fair method instead of a shouting match.
What is a good agenda?
A simple agenda works best:
- Review latest bill and dashboard.
- Compare with production and shift notes.
- Discuss abnormal items.
- Review open saving actions.
- Check capex or vendor claims.
- Assign next actions.
- Record decisions.
The meeting should be short enough that people attend regularly. If a topic needs technical detail, create a separate working session.
What records should be ready before the meeting?
The meeting works only if the inputs are ready. Keep the latest bill PDF, previous dashboard, production notes, demand event notes, APFC or VFD logs where relevant, and the current action tracker in one folder. Accounts should not spend the meeting searching for files, and maintenance should not rely on memory for what happened during the month.
A short pre-meeting routine helps. Enter the bill, mark abnormal rows, ask production for context, then circulate the dashboard. When people arrive prepared, the meeting becomes a decision forum instead of a data collection exercise.
Do not allow the meeting to become only a fault-finding exercise. It should also protect good work. When an action clearly reduced waste, record the proof and keep the operating rule active. Recognition is practical because teams repeat what management checks and values.
Tips from the field
- Hold the meeting only after the latest bill is downloaded and entered into the tracker.
- Ask production to bring shift and output context so maintenance is not blamed for business changes.
- Review maximum demand separately because one peak event can hide inside the payable amount.
- Close an action only when the agreed proof is seen, not when someone says work is done.
- Keep vendor claims on the same dashboard as bill facts so assumptions are visible.
- Record one-line reasons for abnormal months before memories become fuzzy.
How does this fit the larger efficiency roadmap?
The monthly meeting is the control room for the energy efficiency roadmap. The roadmap creates actions. The meeting checks whether they are still working.
A factory that reviews electricity every month learns faster. It catches failed capacitor steps, forgotten schedules, demand spikes and vendor gaps before they become normal. The habit is simple, but it changes how seriously the organisation treats the bill.