If you live in Tamil Nadu, you've felt it — one month the electricity bill is ₹1,400; two months later, after one slightly warmer week, it's ₹3,100. The usage didn't double. The bill did. That gap is the cost of crossing a slab boundary at the wrong time. A smart home that watches your slab position in real time and warns you before you cross is the single highest-ROI feature in residential energy software for Indian households. This post explains the math, the mechanism, and what you'd actually do with the alerts.
The basics: TNEB's domestic tariff is slab-based
TNEB doesn't charge a flat rate per unit. It charges a different rate for each "slab" of usage in a bimonthly cycle. As you consume more, each additional unit costs more — sometimes substantially so. The exact rates revise periodically (the Tamil Nadu Electricity Regulatory Commission publishes them), but the structure has been the same for years:
- A small free-units allowance at the start
- A low rate for the next slab
- A noticeably higher rate above the next threshold
- One or more high-rate slabs above that
The headline number is the bimonthly cycle: TNEB bills every 60 days, not every 30. So your "monthly" feeling is misleading — what matters is the total kWh over the 60-day window. A household using 250 kWh in one month and 280 kWh in the next is at 530 kWh for the cycle, which puts you across the next slab boundary even though neither month felt unusual on its own.
The "cliff effect" — where the money is lost
The slab structure creates a counterintuitive cost shape. Most households assume electricity cost is linear: use 10% more, pay 10% more. It isn't. Here's an illustrative example using a typical slab structure:
| Total bimonthly units | Average cost per unit | Total bill |
|---|---|---|
| 480 | ~₹3.20 | ₹1,540 |
| 500 (slab boundary) | ~₹3.30 | ₹1,650 |
| 510 (just over) | ~₹4.10 | ₹2,090 |
| 540 | ~₹4.40 | ₹2,380 |
That's a ₹440 jump for 30 extra units. The 10 units immediately after the boundary cost more than the 30 units immediately before it. This is the "cliff" — and the failure mode is psychological: by the time you've crossed, you have no incentive to be careful for the rest of the cycle because the damage is done.
If you knew, around day 45 of a 60-day cycle, that you were trending to cross the boundary on day 51 — you'd switch to off-peak geyser timing, run the AC at 26°C instead of 22°C, unplug the standby loads. None of that is hard. The hard part is knowing where you are.
What "slab-aware bill prediction" actually does
Three things, in sequence:
1. Counts kWh per-appliance, not per-house
A bulk smart meter tells you "you've used 320 kWh so far." A smart-switch system measures every channel independently and tells you:
| Appliance | kWh so far | Trend (per day) | Trajectory at day 60 |
|---|---|---|---|
| Bedroom AC | 142 | 3.6 | 213 |
| Geyser | 58 | 1.5 | 88 |
| Living room lights + TV | 31 | 0.8 | 47 |
| Fans (4) | 27 | 0.7 | 41 |
| Kitchen (exhaust + appliances) | 21 | 0.5 | 31 |
| Standby (TVs, STBs, etc.) | 14 | 0.4 | 23 |
| Other | 27 | 0.7 | 41 |
| Total | 320 | 8.2/day | ~490 |
This is the same shape of breakdown a utility would otherwise pay an analytics consultancy to estimate from the bulk waveform — at 70% accuracy. With per-appliance metering, it's measured.
2. Projects forward
The system applies a few well-tested predictors to the per-day trend:
- Seasonality — AC usage trends up in March-June, geyser usage up in November-January
- Day-of-week — most households use more on weekends
- Recent ramp — a 3-day spike that's holding gets weighted heavily; an isolated bad day gets less
- Outliers — a Diwali day with all lights on isn't extrapolated forward
The forward projection is bounded — we don't pretend to know what your usage will be on day 59 with point-precision. What we give is a band: "your bimonthly trajectory is between 478 and 502 kWh, central estimate 488 kWh."
3. Alerts when the band crosses a slab boundary
The math is straightforward but the timing matters. Three thresholds trigger different alerts:
- Band overlaps the next slab. "Heads up — your trajectory is close to the next slab. Small actions today will likely keep you under."
- Central estimate crosses. "You'll cross the 500-unit slab around day 51 at current pace. Tap to see which appliances are driving it."
- Band entirely above the slab. "You're committed to the next slab this cycle. Focus on managing the units inside it rather than crossing back."
Each alert is actionable — clicking through shows the top contributors to your daily kWh, ranked, with one-tap actions you can take immediately.
A worked example
The household: a 2BHK in Coimbatore, 4 occupants. Cycle starts April 1, billed June 1.
Day 28, alerts arrive: Bedroom AC drove 8.8 kWh yesterday, up from a 30-day average of 4.6. Bedroom AC is on track to consume 71% more this cycle than the previous cycle.
The user investigates. The bedroom AC set point has been at 22°C all week — the kids were sleeping in. They raise it to 25°C, add a "wake at 6 AM, off by 7 AM" schedule. AC usage drops back to 5.1 kWh/day average.
Day 41, alert: Trajectory is now 472 kWh — comfortably under the 500-unit slab boundary. Estimated bill: ₹1,510 vs ₹2,180 if the original AC pattern had continued.
Day 60 (cycle end), actual: 478 units, bill ₹1,540.
The saving in this cycle: roughly ₹640, achieved by changing one setpoint mid-cycle. Annualised across 6 cycles, that's ~₹3,800/year on a single behavioural change.
The system enables many such changes across the year. Most homes see two or three slab-crossing risks per year (hot week, festival lighting, an unexpected guest staying for two weeks); reliably avoiding even two of them is worth ₹1,000–₹2,000 a year. Combine with standby drain detection (₹150–₹400/month flagged) and the system pays for itself well within its hardware warranty period.
Why a bulk smart meter can't do this
Tamil Nadu is rolling out smart meters that report household kWh at 30-minute intervals. That data feeds the bill, but not the prediction:
- The bulk meter doesn't know what the AC drew vs what the geyser drew. Any prediction that ranks contributors needs per-appliance data the bulk meter doesn't have.
- The bulk meter's data goes to TNEB first, then to you days later. Per-appliance data from your switches is on your phone in real time.
- The bulk meter's data is 15- or 30-minute aggregated. Behavioural intervention (turn down the AC now) needs second-resolution data on what's running.
The detailed reasoning is in our power-metering whitepaper if you want the engineering depth. Short version: bulk meters were designed for billing, not for behaviour change. A smart switch behind every load was designed for behaviour change from the start.
Data and privacy
A reasonable question: "You're predicting my bill. Where does that data live?"
- Per-appliance kWh lives on your home device first, syncing to our cloud only if you've enabled cloud features (Premium tier or Pro).
- The AI prediction model runs in our cloud — your last 30 days of aggregated daily totals (not appliance-level events) are sent to the prediction service. No appliance names, no schedules, no times.
- The output (your projected bimonthly bill) returns to your app only — never shared with TNEB, never sold to anyone, never used for ads.
- You can disable it in Settings → AI Features → toggle off. Your switches keep working; only the prediction goes away.
All of this is governed by our Privacy Policy and India's DPDP Act 2023. We are explicit about what leaves the home and what doesn't.
What you should do today, even before installing anything
Two free actions that this exercise illuminates regardless of whether you have a smart home yet:
- Find your bimonthly cycle dates. Look at your last TNEB bill. The "Bill Period" or "Service Period" tells you when your current 60-day window started and when it ends. Until you know that, you can't manage to it.
- Look at your last six bimonthly bills. Plot the kWh number for each. If you see one cycle that's wildly higher than the others, find out what changed — it was probably a slab boundary crossing you didn't notice. The amount you would have saved by knowing is real money.
That said, doing this by hand is a chore most people don't sustain past the first month. A smart home that does it for you, without asking you to keep a spreadsheet, is the practical version.
Bottom line
Slab-aware bill prediction isn't an "AI feature" — it's regular arithmetic applied at the right time. The "AI" framing is mostly because the projection involves some seasonality and trend smoothing. What actually saves money is observing every appliance, projecting forward honestly, and alerting before the slab cliff — none of which a bulk meter or a guess-based household budget can do reliably.
If your bimonthly bill has ever surprised you, this is the feature that prevents that from happening again.
Book a free site visit — we'll show you the bill predictor running on a real installed system and walk through what your specific home would look like. Or call us on +91 75500 58208.
