Building Submetering IoT Water Meters: NB-IoT vs LoRaWAN for Multi-Tenant Buildings

When Marcus took over a 300-unit garden-style property in spring 2024, he inherited a single master meter and flat-rate billing. A couple in a two-person studio paid exactly what a family of six paid in the three-bedroom next door. That math felt unfair, and worse, it gave nobody a reason to use less while hiding the running toilets draining thousands of gallons a month.

A building submetering IoT water meter system fixes that. It keeps the utility’s master meter at the property line and installs a submeter on every apartment’s supply line, so each unit’s actual consumption is measured and billed directly. When tenants pay for what they use, they use less, typically 15% less according to the U.S. EPA, and the building starts surfacing leaks that flat-rate billing never revealed.

The hard part is rarely the meter itself. It’s the connectivity: how do you pull reliable readings out of every unit when many sit in basements, meter closets, and concrete risers? Two low-power wide-area standards dominate the answer, and our full NB-IoT vs LoRaWAN water meter connectivity guide compares them head to head. This guide applies that decision to multi-tenant buildings, so you can choose the right building submetering IoT water meter for your site.

Here is what we will cover: how submetering works, where NB-IoT and LoRaWAN each win inside a building, the data path from meter to tenant invoice, the privacy rules you cannot skip, and a five-step decision framework. By the end, you’ll know exactly what to specify in your RFP.

What Is Building Water Submetering, and Why It Is Growing

At the property line, a building has one utility-owned meter, the master meter. The utility bills the owner for the whole building’s consumption. Submetering adds individual meters at each apartment, so every tenant’s actual water use is captured and billed. That change turns water from a fixed operating cost into a measured, recoverable utility expense.

Master Meter vs Submeters vs RUBS

There are three ways to bill water in a multi-tenant building, and only one measures reality.

• Master meter only. The owner pays the utility bill and either absorbs it or charges a flat fee. Nobody has an incentive to conserve, and leaks are invisible.
• Submeters. A meter on each unit’s supply line captures real consumption. The tenant pays for exactly what they use.
• RUBS (ratio utility billing system). No meters at all. Costs are allocated by a formula, usually square footage, number of occupants, or number of fixtures.

Measured billing beats allocation on the balance sheet. Submetered properties recover 90 to 95% of water costs, while RUBS recovers only 70 to 85%, per Synergy Utility Billing. The gap comes from accuracy: formulas guess, meters measure.

There is also a difference between 100% capture and partial allocation. Full capture meters every unit’s supply line, including hot water where the building runs centralized boilers. Partial allocation retrofits, common where only hot water is metered, measure some units and estimate the rest. Full capture is the standard that makes tenant billing defensible, and the one regulators increasingly expect.

Regulations Are Now Requiring It

The legal landscape is shifting from permissive to mandatory. Colorado’s HB26-1284 requires individual submeters in all new residential construction from January 1, 2027. Texas has required them since 2003. In the EU, the Energy Efficiency Directive and the Energy Performance of Buildings Directive push consumption-based billing and give tenants the right to their own usage data.

The driver is straightforward: metered buildings use 15 to 30% less water when tenants are billed for actual usage. That number closes the business case, and it is why property owners, not just regulators, are pushing submetering forward.

Curious what this hardware actually looks like on a unit? Explore Black Ant’s ultrasonic water meters with NB-IoT or LoRaWAN connectivity to see the meter, the radio, and the data path in one device.

NB-IoT vs LoRaWAN for Building Submetering: Side-by-Side

Once the meters are decided, the radio question follows. Every submeter needs a way to report its reading, and the two dominant options differ sharply in how they’re built and owned.

NB-IoT: Licensed Cellular, Built for Basements

NB-IoT (Narrowband IoT) rides on licensed cellular spectrum from carriers like China Mobile, Vodafone, and AT&T. Each meter carries a SIM and talks directly to the carrier network, so there is no gateway infrastructure to deploy inside the building.

NB-IoT’s defining advantage is its 164 dB link budget, the highest of the low-power standards. The signal penetrates deep: through 2 to 3 concrete basement levels, into meter closets, and out from under cast-iron pit covers. A single base station supports 100,000+ devices, so capacity is rarely a constraint in a building of any size.

The trade-offs are recurring cost and carrier dependence. Each meter typically runs a $2 to 5 monthly SIM charge, and you rely on the carrier’s network quality and longevity in your region.

LoRaWAN: Private Gateways, Built for Campus Coverage

LoRaWAN runs on the unlicensed ISM band and uses gateways you deploy and own. Gateways listen for nearby meters and forward transmissions to a network server, which feeds your head-end platform.

Because you control the infrastructure, one well-placed gateway covers a lot of ground. The canonical example: a single gateway covering a 50-acre garden-style property or a 15-story high-rise, with no SIM fees and data staying on your private network under AES-128 encryption.

The trade-off is capital expense and RF engineering. You buy, place, and maintain the gateways. In a dense urban building with concrete between floors, a private LoRaWAN network can require careful gateway placement to hear every meter.

The Comparison Table

Criterion	NB-IoT	LoRaWAN
Network	Licensed cellular carrier (SIM per meter)	Unlicensed ISM, your own gateways
Link budget	164 dB	~157 dB typical
Basement penetration	Through 2-3 concrete levels	Best where a gateway sits nearby
Reliability under concrete	Packet delivery >0.96 at 30 dB attenuation	Drops below 0.85 above 20 dB
Cost model	~$2-5/mo SIM per meter	Gateway capex, no SIM fees
Data ownership	Carrier network	Private network
Security	SIM authentication + carrier security	AES-128 + private data control
Best building type	High-rise urban, deep basements, dense blocks	Garden-style, campus, owner-controlled sites

The cost row deserves its own look, since gateway capex and SIM opex behave very differently at 500 units versus 5,000. Our total cost of ownership analysis works through both models with real numbers.

In-Building Coverage: The Criterion That Decides Everything

The radio choice for a submetering deployment is usually decided not by the meter, but by where the meter physically lives. Concrete is the enemy of wireless signals, and apartments put their meters exactly where concrete is thickest.

Basements, Meter Closets, and Cast-Iron Covers

In a University of South Africa field study conducted with Rand Water, researchers buried test meters under concrete and measured packet delivery for both standards. NB-IoT maintained delivery ratios above 0.96 even under 30 dB of concrete attenuation. LoRaWAN reliability fell below 0.85 once attenuation exceeded 20 dB.

For a building, that is the difference between a basement full of readable meters and a basement full of blind spots. When meters sit in shared risers, stairwells, and below-grade mechanical rooms, the licensed cellular path has a measurable penetration advantage. This is the same physics our in-building coverage validation and RF planning guide documents for underground and concrete environments.

High-Rise vs Garden-Style: Where Each Protocol Wins

Building geometry determines the winner more than any spec sheet.

A dense urban high-rise puts meters in deep basements, shared risers, and interior unit closets, with slab between floors. Here NB-IoT’s penetration and lack of on-site infrastructure make it the pragmatic default. No gateway placement to engineer, no coverage gap on the lower floors.

A garden-style community or campus spreads units over acres, often with meters in exterior utility boxes and shallow crawl spaces. Here LoRaWAN shines. One rooftop or pole-mounted gateway hears a whole property, with no SIM fees and data kept on a private network.

The rule of thumb: basements and dense urban blocks lean NB-IoT; garden-style and campus sites where you control the gateways lean LoRaWAN. Your riser layout and basement depth matter more than any vendor’s roadmap.

The Complete Submetering Architecture: From Meter to Billing

The property-management guides stop at “call a billing provider.” The architecture underneath matters, because it determines whether your readings arrive reliably, on schedule, and in the format your billing software expects.

Unit-Level Meters and Where They Go

Submeters mount at the unit entry point, typically in the utility closet, bathroom, or kitchen supply line. Residential submetering uses small-bore meters in the DN15 to DN25 range, sized to the unit’s peak flow. A 100% capture installation meters every unit, giving you complete, auditable consumption data for billing.

For new builds, inline meters with ultrasonic sensing are the common choice. They have no moving parts, measure low flows that mechanical meters miss, and run 10 to 20 years on battery. Black Ant’s small-diameter ultrasonic water meters for residential submetering cover the DN15 to DN25 range with NB-IoT and LoRaWAN options and built-in tamper detection.

Concentrators, Data Terminals, and BEMS Integration

Meters don’t each talk to the internet directly. They aggregate. On a LoRaWAN network, gateways collect hundreds of meters and forward to the network server. In dense buildings, wired buses like M-Bus and RS485 gather meters locally, then a concentrator backhauls the batch over a single uplink.

Black Ant’s centralized meter readers aggregate up to 1,024 sub-meter points per unit, reading M-Bus and RS485 meters on schedule and pushing anomaly alerts. Where a building mixes protocols, IoT data collection terminals take multi-protocol inputs and uplink over NB-IoT or LoRaWAN, folding the whole fleet into one head-end.

From there the data feeds property management software or a building energy management system, which correlates water against HVAC for whole-building reporting.

From Consumption Data to the Tenant Invoice

The billing path is a simple handoff: meter reads on schedule, concentrator or network server normalizes them, billing software converts readings to charges at the approved utility rate, and the tenant invoice goes out with the rent statement.

Many owners outsource this to Read-Bill-Collect (RBC) providers, who handle metering, billing, and collections for a fee. Whether you run billing in-house or with an RBC partner, the requirement is the same: clean, timestamped, tamper-evident reads you can defend in a dispute.

Fair Billing, Tenant Privacy, and Regulatory Compliance

Submetering makes money only if it’s done lawfully, and the rules have teeth. Owners who charge more than the utility rate, or who treat consumption data carelessly, face fee caps, penalties, and lawsuits.

The No-Profit Rule and State-by-State Requirements

Across most U.S. jurisdictions, a landlord can’t profit from water resale. You may pass through the utility’s rate and a capped service fee, but no markup. The caps vary: Arizona allows up to $8 per month per unit for mobile homes, Texas caps the service charge at 9% of the bill, and Massachusetts and Kansas permit no service fee at all.

A few requirements appear in nearly every state:

• Disclose submetering and billing terms in the lease before move-in.
• Charge the same rate the utility charges, with only the permitted fee.
• Bill common-area water separately and transparently, not hidden inside unit charges.
• Maintain meter accuracy and provide a dispute process for tenants.

Check your state’s utility code, and require the same disclosure discipline from any Read-Bill-Collect provider you hire.

EU EED and GDPR: Consumption Data Is Personal Data

In the European Union, the analysis is different and stricter. Under the GDPR, unit-level consumption data linked to a tenant is personal data. That classification carries real obligations.

The landlord is the data controller, deciding why and how the data is processed. The metering or billing provider is a data processor, acting on the controller’s instructions. The two must sign a data processing agreement (DPA). Data must be minimized, retained only as long as needed, and protected with encryption and role-based access.

If your portfolio touches Europe, put the DPA and data-minimization policy in place before the first meter ships. The technical layer matters too; the security layers behind smart water meter data cover encryption, key management, and firmware patching in detail.

Compliance Checklist for the Buyer

Run this list before you sign anything.

• Confirm submetering is permitted, or required, in your jurisdiction and that you hold the right permits.
• Cap your service charge at the legal maximum, or at zero where the law allows no fee.
• Disclose the arrangement in every lease, with rates and billing dates spelled out.
• Allocate common-area consumption separately and document the method.
• If in the EU, classify unit data as personal data, sign a DPA with your provider, and encrypt it.
• Require MID or local metrology approval on every meter you install.

Leak Detection: The Hidden ROI of Unit-Level Metering

The conservation numbers justify submetering. The leak economics make it urgent. Every property manager has a running-toilet story, and the meters finally turn it into a work order.

Running Toilets and Event-Based Monitoring

Toilets account for up to 50% of a building’s water waste and up to 75% of apartment-unit leaks. A single constant-running toilet can waste as much as 75,000 gallons in a month. On flat-rate billing, that waste is simply absorbed. With a submeter and continuous flow monitoring, it becomes an alert.

The technique is event-based monitoring. A smart water meter logs flow continuously, so a toilet that runs for 14 hours instead of a 60-second flush stands out as a duration anomaly. The system flags the unit, the facility team isolates the fixture, and the fix happens in days instead of months.

Consider Dana, who manages a 40-unit building in Los Angeles and learned this the hard way. Her flat-rate tenants had no reason to report drips, and two running toilets went unnoticed for a quarter, costing the building an estimated $900 in wasted water. After submetering, the platform flagged both leaks within a week of installation, the toilets were rebuilt, and her next water bill dropped 12%. Her building now catches a leak in days, not quarters.

The evidence at scale is compelling. In a Pacific Institute pilot across 8 affordable multifamily properties in Los Angeles, 1,198 toilet leak sensors found that 51% of toilet water was lost to leaks. Proactive detection cut water use by 11% and water and wastewater costs by 12%.

From Alert to Shut-Off: Flood Prevention and Insurance

The same continuous flow data that catches running toilets also catches burst pipes and stuck valves. Alerts escalate by severity: a duration anomaly triggers a work order, a catastrophic flow spike can trigger an automatic shut-off valve. Some insurers now require leak detection on metered multi-tenant buildings, and a documented leak-response history can lower premiums.

The takeaway is simple. A submetering system doesn’t just bill tenants fairly. It gives the building a nervous system, one that finds the leaks quietly bleeding money and stops them.

How to Choose a Building Submetering IoT Water Meter: A Decision Framework for Building Owners

Here is the framework we use when advising property owners, facility managers, and submetering providers. Work through it in order.

1. Map the building. Classify each structure: garden-style or high-rise, basement depth, riser layout, and where meters will sit. This single step decides more than any vendor presentation.
2. Decide who owns the network. If you want zero on-site infrastructure and per-meter SIM simplicity, NB-IoT. If you want to own the gateways, avoid SIM fees, and keep data private, LoRaWAN.
3. Choose retrofit or new build. New construction gets inline ultrasonic submeters. For existing buildings, weigh full replacement against clamp-on meters, or against a camera direct-reading retrofit that reads existing mechanical meters optically and transmits over NB-IoT, with no plumbing changes.
4. Define the billing and compliance path. Confirm your jurisdiction’s rate caps, disclosure rules, and any EU data obligations before you tender.
5. Specify the procurement language. Write the radio and band support (868 MHz EU, 915 MHz US, 470 to 510 MHz China), gateway density, head-end integration, and certifications, CE, RoHS, MID where required, IP68, and battery life, into the RFP.

For mixed portfolios, where some buildings favor NB-IoT and others LoRaWAN, you don’t have to pick one. A hybrid NB-IoT and LoRaWAN building deployment lets you match each building to the right radio and manage the whole fleet on one platform.

Choose the Right Connectivity for Your Building

A building submetering IoT water meter system is the fastest way to make water billing fair, cut consumption 15 to 30%, and surface the running-toilet leaks that cost buildings thousands a year. The connectivity decision is not about which radio is “better.” It’s about where your meters physically live: NB-IoT for basements and dense urban high-rises, LoRaWAN for garden-style and campus sites where you control the gateways.

Both radios are proven. The right choice is a function of building geometry, network ownership, and jurisdiction, not vendor preference. With the building map, the network decision, and the compliance checklist in hand, you can specify a system with confidence instead of relying on a provider’s pitch.

Black Ant builds the full stack on both sides of the decision: ultrasonic water meters with NB-IoT or LoRaWAN modules, centralized meter readers, IoT data collection terminals, and BEMS integration. If you want a connectivity review for your building portfolio, send us your floor plans and meter locations. Our engineering team will recommend the architecture that matches your buildings, not our catalog. Start the conversation on our website or contact our OEM team.