Impervious Surface Data for Stormwater Billing and Fee Audits

Say a 42,000-account utility has 128.4 million billable square feet on a continuous area tariff of $7.35 per 3,000-square-foot ERU each month. Assume no credits or minimum charges, fractional ERUs without unit rounding, and a full year of billing for accepted changes. A 2% annual surface change, split between 1,716,000 added square feet and 852,000 removed square feet, changes annual billing by $25,401.60 net. Charging for the additions while overlooking the removals leaves $25,048.80 a year in unsupported charges.

The reconciliation has to work in both directions. A new loading apron belongs in the review queue. So does a parking pad replaced with vegetation. The billing manager needs to know which account changes and see the dated evidence behind the proposed fee.

Asset Search by PorchRocket reviews visible surfaces against property records and your search rules, then returns the account-level changes in your agreed format. The job is to give a GIS lead and a billing supervisor the same evidence for the same decision, including the properties that need a field check.

The three areas a billing record needs

A billing review needs three separate quantities: the parcel’s gross area, its mapped impervious area, and the area chargeable under the local fee policy.

Gross area is the parcel’s total area. Mapped impervious area is the identified surface coverage. If the map shows a paved strip inside the parcel but the adopted fee policy excludes that category, preserve the measured strip in the inventory and record its billing treatment separately so the next reviewer can reproduce the exclusion without redrawing the site.

The EPA’s explanation of impervious surfaces and runoff describes why this matters: hard surfaces reduce infiltration and increase surface runoff. It also distinguishes total impervious area from effective impervious area connected to stream channels. A map showing pavement does not settle the drainage connection or a credit application.

Start the mapping specification with the utility’s definitions. Raleigh’s impervious-surface examples include roofs and parking lots. Its list also covers gravel patios and artificial turf, along with typical slatted decks. A search rule that recognizes only dark asphalt and large roofs would miss categories that city lists.

Before measuring the first neighborhood, I would ask billing staff to approve a surface dictionary. Use marked examples to show where each surface begins and which borderline categories need more than a picture to settle. Give each category a treatment: include, exclude or refer for review. Attach the controlling policy and its effective date.

That dictionary should also distinguish the observed surface from its billing treatment. A reviewer can record that a paved pad exists while leaving its eligibility for a reduction undecided. Preserve the observation when the policy answer changes.

For the broader search process, the guide to asset inventory from aerial imagery explains how reviewed observations become site records. Stormwater billing adds the account relationship and the adopted fee calculation to that inventory.

ERUs and tiers in current utility fee schedules

Raleigh and nearby utilities use different billing units or residential tiers, so a November 2026 fee audit must start with the property’s own utility schedule.

An equivalent residential unit, or ERU, expresses chargeable area in the unit adopted by that utility. The name and size are local choices. A residential tier assigns a charge to a band of area instead of pricing each added square foot continuously.

Utility example	Published basis current in November 2026	What the reconciliation must preserve
Durham	Effective July 1, 2026, apartments and nonresidential properties pay $11.80 monthly per 2,400-square-foot ERU.	The property’s class and the locally adopted ERU treatment.
Raleigh	July 2026 commercial rate: $8.47 monthly per 2,260-square-foot Single Family Equivalent Unit, or SFEU.	The SFEU denominator and separate residential tier rules.
Charlotte	Four detached single-family tiers: below 2,000; 2,000 to 2,999; 3,000 to 4,999; and 5,000 or more square feet.	Whether a correction crosses a tier boundary.
Philadelphia	Nonresidential charges combine gross-area and impervious-area components, with factors based on 500-square-foot units rounded up.	Two area fields and their separate charge components.

Save the old tariff. When an appeal concerns a previous billing period, the reviewer should be able to pair the accepted area for that period with the rate that applied then, without replacing either value with the numbers on the utility’s current web page.

Do not carry a rule across jurisdictions because the properties look alike. Two warehouses with matching paved areas can have different unit sizes, account allocations or credit records. For a portfolio owner, group the audit by utility first, then by property.

How to calculate an ERU and a corrected stormwater fee

Divide approved billable impervious area by the utility’s adopted unit size, then apply its rounding rule, rate and any separately approved credits.

The calculation has four stages:

1. Determine the approved chargeable area for the property and period.
2. Convert that area to billing units under the local formula.
3. Calculate each applicable charge component using the effective tariff.
4. Apply approved credits, allocations and other adjustments in the prescribed order.

Keep the intermediate values. A customer service representative should be able to reproduce the proposed charge without tracing a spreadsheet through six hidden tabs.

Using Raleigh’s published July 2026 commercial formula, a property with 47,460 square feet has 47,460 / 2,260 = 21 SFEUs. Its monthly area charge is 21 x $8.47 = $177.87. An approved removal of 6,780 square feet leaves 40,680 square feet, or 18 SFEUs, and a $152.46 monthly area charge. The difference is $25.41 a month before any other applicable adjustment.

Whole units make that example easy to follow. In the working record, retain measurement precision until the utility’s prescribed rounding stage, and show the unrounded value beside the rounded factor so someone reviewing a disputed bill can tell whether the difference came from the measurement or the calculation. Philadelphia’s published method, for example, rounds each 500-square-foot area factor upward. A continuous formula copied from another city would produce a different result.

For tiered accounts, calculate the old and proposed tier instead. An area reduction inside one unchanged band can produce zero fee reduction. It still deserves an accurate record. Separate the physical change from the dollar change so the GIS team does not have to distort a measurement to explain the bill.

I would require a fee worksheet for every approved adjustment, including zero-dollar corrections. Its last line should identify the billing period when the accepted change takes effect.

Why impervious surface maps drift from billing records

A stormwater billing dataset goes stale when the surface map, parcel records and customer accounts describe different dates or different ownership arrangements.

Construction is one source of drift. Durham reports that its inventory gains an average of 2.5 million impervious square feet annually through construction and redevelopment. That is a local observation, separate from the 2% planning assumption in the opening model.

There are also deliberate differences between a working map and a billing baseline. Gaithersburg’s published mapping process describes imagery updates every one to two years, with interim updates from as-built drawings, approved site plans and field surveys. Its yearly fee uses conditions as of January 1. A newer observation needs to be assigned to the correct billing year.

Arlington County’s billed impervious-area dataset explicitly identifies itself as a static snapshot for the current tax year, excluding later updates. That is a helpful operating distinction: preserve what generated the bill while reviewing what has changed since.

Capture the dates separately. Record the two observations and the review approval alongside the proposed billing effective date, then add a construction completion date only when supporting records establish it; the date a surface first appears in an image should remain an observation date in the file.

I would also keep an account exception queue beside the surface queue. Put unmatched parcels and unresolved account allocations there. Otherwise a finished map can sit in the GIS department while billing staff work from the previous export.

Reconcile new roofs and pavement against removed surfaces

A two-direction reconciliation records every accepted addition and removal separately, then calculates the net area change for each billing relationship.

Keep the offsets visible. If a redevelopment adds a loading apron on one side of the parcel and removes an old parking pad on the other, the customer service record should show both changes even when their areas happen to cancel out and the bill stays the same.

Require the area balance to read: previous mapped area + accepted additions - accepted removals + signed mapping corrections = proposed mapped area. A signed correction is positive for previously understated coverage and negative for overstated coverage. Keep boundary and classification corrections separate from physical changes, with their own reason codes.

Observed change	Question the reviewer should settle	Evidence to attach
Building extension over a former planted strip	How much newly covered area falls within the billing parcel?	Earlier and later dated views, marked footprint and parcel reference.
New roof over an existing paved loading area	Was that ground footprint already included?	The former paved polygon and the proposed surface classification.
Building removed with a slab remaining	What chargeable surface remains after demolition?	A dated view of the remaining pad and a field question if its treatment is unclear.
Parking pad replaced with vegetation	Has the surface been removed, and what replaced it?	Before-and-after boundaries and supporting site records.
Parcel line moved across an unchanged lot	Is this an allocation correction instead of new development?	Previous and current parcel relationships.

These are review instructions, so set their final treatment with the utility’s experts. For an overlapping roof and paved footprint, require one agreed method for preventing duplicate area. For restored ground, ask what documentation establishes the replacement condition under that utility’s policy.

Return the rejects too. When a reviewer finds that a seemingly new paved area was already included in the billed total, attach the old record and the reason for rejection to the candidate so the next refresh does not send someone back to investigate the same strip.

For runoff-management features connected to the site, maintain a separate stormwater pond inventory. Link those asset identifiers to the account without adding a pond’s visible footprint to impervious area by default.

How should you handle parcels and shared accounts?

Use a parcel-to-account crosswalk that preserves shared sites and historical parcel identifiers, rather than assigning every polygon to the nearest mailing address.

The crosswalk is a table connecting the physical property to the customer record that receives the charge. Give each relationship a start date and, when replaced, an end date. Retain the prior parcel identifier after a split or consolidation.

Philadelphia provides a clear example of why this matters. Its appeals process includes changes to charge allocations among multiple water accounts on one property. The city’s published default allocation divides the parcel charge equally, subject to its per-account minimum. An owner can request another allocation through Form A-1. An area change and an allocation change are separate requests.

Reconcile the parcel first. Trace the approved parcel charge through the account allocation, then record any minimum-charge adjustments separately. In Philadelphia, a nonresidential account whose allocated share falls below the minimum is charged the minimum. That can make the sum of account bills exceed the unadjusted parcel charge. Show that difference on the worksheet alongside final bill rounding.

Avoid using an owner name as the sole join between files. Require stable parcel and account identifiers, and send uncertain matches for review. Keep the recorded owner in its own field so a change in the billing contact does not erase the property history.

Start with the invoices. For a portfolio appeal, ask the owner to mark shared sites and recently changed parcel numbers on an account schedule before ordering new measurements, because a disagreement over square footage will remain unresolved if the two parties are discussing different pieces of land.

Tie drainage assets to that schedule when they support a separate question. A culvert and drainage inventory can supply asset references for a follow-up inspection. It should not substitute for the billing allocation approved for the property.

Evidence that settles a stormwater fee appeal

A persuasive fee appeal identifies one billing error, quantifies the requested correction and gives the utility dated evidence it can check.

The Philadelphia stormwater appeals process accepts requests concerning area determinations and property classifications, among other billing issues. Most requests use Form A; revised charge allocations use Form A-1. The department performs technical review and can request more information or a site visit before issuing its decision.

Mark the disputed boundary. An area appeal should let a reviewer compare the billed footprint with the requested footprint on one dated view, while an assignment appeal should identify the surface in question and show which parcel-account relationship the owner is asking the utility to correct. Include the previous charge calculation and the calculation being requested.

I would organize the packet in this order:

• The property identifier, utility account and billing period under review.
• A short statement of the error and the requested correction.
• A marked map with dates and a surface-area worksheet.
• Supporting records required by that utility, followed by any unresolved field question.

Keep a copy of what was submitted and the utility’s written disposition. Then check the next affected bill against the approved decision. Approval and implementation are different checkpoints in the workflow.

A sample appeal request can stay short: “Account [number] includes the marked parking pad. The attached dated records show its removal and replacement condition. Please review the chargeable area from [old total] to [requested total] and confirm the effective billing period.”

The same standard applies to increases. I would have the reviewer explain the added surface using the account’s marked view and fee worksheet, then have the billing supervisor approve the effective period under the utility’s notice procedures before the record enters a production import.

The deliverable is an answer to the disputed measurement or account relationship. Keep any request for a runoff-management credit in its own track.

Stormwater credits require their own records

An area correction fixes the bill’s measurement or assignment; Philadelphia’s separate credit process rewards approved practices and site conditions that manage runoff.

Keep a credit register beside the surface inventory. Record the qualifying practice, its identifier, the approved credit and the part of the charge it affects. Add the effective date and renewal requirements. Link the supporting documents directly to that record.

Philadelphia’s stormwater credit requirements illustrate the difference. Its application process includes approved record drawings and a recorded operations and maintenance agreement after construction. Credits expire four years from their effective date, and the owner must submit a renewal application at least 30 days before expiration. Inspection and maintenance records support renewal.

Attach the approved drawing. If the unresolved question is whether a visible feature matches an approved runoff-management practice, send the inspector that drawing and the specific point to verify, then record the inspection finding beside the credit application so a later renewal review can follow the decision.

During reconciliation, test how an accepted area change affects the existing credit. A removed surface might change the area associated with a practice. A newly mapped extension might need its own review. Send either case to the staff responsible for credit decisions.

For a property owner, separate an appeal budget from a retrofit budget. Correcting the area calculation addresses the bill’s inputs. Installing or maintaining a qualifying practice has its own scope and operating costs. Use the current utility rules to evaluate that work before authorizing construction.

The file should preserve both the measured surface and the approved credit history. A credit renewal decision should be traceable without rebuilding the property’s geometry from scratch.

What should an account-level change file include?

An import-ready change file should connect each reviewed surface difference to a parcel, an account, dated evidence and an approval decision.

Agree on the fields before the pilot begins. Have the GIS lead and billing supervisor approve one sample row together. Test that row in a staging copy of the destination system before measuring a larger territory.

Field group	Requested contents	Purpose at review or import
Identifiers	Investigation ID, parcel ID, account ID and relationship ID.	Join the finding to the correct property and account.
Location and ownership	Site location, parcel geometry reference and owner information.	Check identity and route ownership exceptions.
Baseline	Prior billed area, mapped area, unit count and baseline date.	Reproduce the existing charge.
Change quantities	Added area, removed area and boundary or classification corrections.	Explain the difference without hiding offsetting changes.
Proposed outcome	Proposed area, units, fee difference and proposed effective period.	Prepare an approval decision under the utility’s rules.
Evidence	Dated views, marked boundaries, observation notes and record references.	Support review and later customer questions.
Review status	Fits, rejects with a reason, or unresolved with the field check needed.	Preserve every candidate’s disposition.
Authorization	Reviewer, decision date, approved values and import batch reference.	Distinguish a proposal from a posted billing change.

Asset Search scopes the search rules with your experts and reviews every candidate before delivery. For this job, define a fit as a supported candidate for the agreed reconciliation question. Utility staff retain the approval step for a charge change.

Delivery can be CSV, Excel or GIS-ready files, with the account fields arranged for the agreed import. Agree on blank values. In a delivery that mixes accepted changes with unresolved accounts, a missing area must lead to an exception rather than being read as zero, so ask the pilot team to demonstrate how each status travels through the import before you approve the file layout.

Test retrieval after import. Give a billing employee an unfamiliar account and ask them to find the dated view and approved worksheet from its history without help from the analyst who prepared the batch; make that exercise part of accepting the pilot.

Accuracy checks before a billing import

Validate the measured areas separately from account matching and fee calculations, using an independent review set that includes removals and unchanged properties.

First, have utility staff approve reference examples before production review starts. Include ordinary roofs and lots, followed by the surfaces that require local judgment. Record the agreed treatment of each example in the surface dictionary.

Next, reserve properties that the production reviewer has not used to settle the search rules. Check their results independently. Report the mistakes by type: missed addition, unsupported removal, duplicate footprint, wrong parcel or incorrect charge calculation. A single accuracy percentage conceals which problem billing staff will inherit.

Check account relationships independently of geometry. A perfectly drawn parking area assigned to the wrong customer is still a failed billing record. Require every proposed adjustment to reconcile to the approved parcel-account crosswalk.

Run arithmetic checks across the batch. Previous area plus additions minus removals should match the proposed area after documented corrections. Proposed unit counts should follow the correct property class and tariff version. Credits and allocations should reproduce the approved final charge.

I would hold unresolved records outside the import batch. Give each one a specific action and an owner: verify the replacement surface, inspect the boundary in question or confirm the shared-account allocation. Return the resolution to the same investigation record.

For field checks, group visits by territory. The route density calculator can help compare travel assumptions when planning that work. Budget the travel time alongside the inspection time, and record how many unresolved accounts each route settles.

Finally, test the approved batch in staging and compare totals before posting. Retain an export of the prior approved values. Ask billing staff to check selected customer bills after the change has run through the billing cycle.

The annual value of a 2% surface change

Under the opening utility’s assumptions, reconciling 2,568,000 changed square feet produces a net annual billing adjustment of $25,401.60 before credits.

The assumed unit in that model is 3,000 square feet and the monthly rate is $7.35. Annual area value is therefore $7.35 x 12 / 3,000 = $0.0294 per chargeable square foot. All accepted changes receive a full 12 months at that rate for the comparison.

The additions produce 1,716,000 x $0.0294 = $50,450.40 in annual charges. The removals reduce annual charges by 852,000 x $0.0294 = $25,048.80. Net annual adjustment is $25,401.60.

Do not report $50,450.40 as the net result. Show the downward adjustments beside it, with the accounts receiving those corrections. That report lets finance see the revenue effect and lets customer service identify the corrected overcharges.

Sensitivity	Annual surface area changed	Added area	Removed area	Annual upward adjustments	Annual downward adjustments	Net annual adjustment
Low: 1%	1,284,000 sq. ft.	858,000 sq. ft.	426,000 sq. ft.	$25,225.20	$12,524.40	$12,700.80
Base: 2%	2,568,000 sq. ft.	1,716,000 sq. ft.	852,000 sq. ft.	$50,450.40	$25,048.80	$25,401.60
High: 3%	3,852,000 sq. ft.	2,574,000 sq. ft.	1,278,000 sq. ft.	$75,675.60	$37,573.20	$38,102.40

The table holds the addition-to-removal mix constant and shows cents so each net equals additions minus removals. The changed area is the sum of added and removed area, not net growth. Calculate each account under its own tariff before summing a production result. Tier boundaries and approved credits require that account-level calculation.

If the base correction persists for five years with an unchanged rate and no further surface changes, its undiscounted cumulative net billing effect is 5 x $25,401.60 = $127,008. Let finance choose the comparison period. Keep expected future construction outside the value assigned to corrections already accepted.

For a property owner, the same model values an accepted 9,600-square-foot removal at $282.24 a year, or $1,411.20 over five unchanged years. Compare that saving with the effort needed to document the correction before commissioning a portfolio-wide appeal.

Cost per reviewed account and a pilot decision rule

Judge a reconciliation pilot by accepted account corrections and staff hours saved, then compare that value with the quoted investigation scope.

Count the denominator carefully. Count investigated accounts separately from corrected accounts. Then count the corrections posted to billing. Keep unresolved accounts visible in the pilot report even when they generate no immediate fee adjustment.

For the labor model, assume a 240-account pilot to test the workflow. Select groups with likely additions, possible removals and no expected change. Add shared-account cases. A deliberately selected test group is good for finding workflow failures; use a representative sample if finance also wants to estimate territory-wide change rates.

For the labor comparison, assign 45 minutes per account to manual assembly and review, compared with 18 minutes to review an evidence-ready record. At an internal loaded labor cost of $46 an hour, 240 manual reviews cost 180 hours x $46 = $8,280. The shorter review costs 72 hours x $46 = $3,312, leaving 108 hours for exceptions or another review batch. At 18 minutes per account, the same 180 hours cover 600 reviews, or 360 more than the manual route. Review capacity is 600 / 240 = 2.5 times as large. Labor per reviewed account falls from $8,280 / 240 = $34.50 to $3,312 / 240 = $13.80, a $20.70 difference. Across the pilot, that is $4,968 in staff capacity.

That compares assembly and review labor only. Add field travel and import work to both routes, then add the scoped investigation quote to the proposed route. Track measured pilot hours in place of the planning times before expanding.

For the utility-wide value calculation, separately assume 600 accepted account corrections carry the base model’s $25,401.60 annual net adjustment. That count is a planning input, not a correction rate inferred from the pilot or its review capacity. The annual mean is $25,401.60 / 600 = $42.336, displayed as $42.34 per corrected account. Using the unrounded mean, five unchanged years equal $211.68 per corrected account. Show upward and downward values separately alongside that average.

I would approve expansion when the conservative net billing adjustment over the chosen period exceeds the investigation quote plus internal implementation costs, and the pilot passes the account and calculation checks. Report corrected overcharges as customer savings; do not add them to utility revenue gains. A program focused on fixing overbilling can instead be approved against its accuracy and customer-service objectives. Give staff hours saved their own line so finance can distinguish added capacity from cash savings.

For a fixed reconciliation, per completed investigation is the clearest Asset Search buying model. Define the evidence and disposition required for an investigation to be accepted as finished. Ongoing territorial review fits a subscription after the first account baseline is working.

How to run a stormwater billing reconciliation step by step

Run the first reconciliation in eight steps, from an approved billing baseline through a controlled import and a check of the next bill.

1. Freeze the starting records. Export the billed area, unit count, tariff version and approved credits for the selected accounts. Retain the parcel-account relationships and the effective billing dates.
2. Approve the surface rules. Have utility billing and GIS staff settle included surfaces, exceptions, measurement units and rounding. Use marked examples, including a removed building with a remaining slab.
3. Scope the Asset Search pilot. Submit the service area, account sample and reconciliation question through Asset Search for impervious surfaces. Request dated before-and-after evidence, both additions and removals, and fits, rejects and unresolved dispositions in your import format.
4. Test the account joins. Check split parcels and shared accounts before calculating fees. Resolve unmatched identifiers in a separate queue. Approve one sample output row with the billing supervisor.
5. Review the evidence in both directions. Accept supported additions and removals under the same rules. Keep observed area separate from proposed billing treatment and existing credit decisions.
6. Resolve the field questions. Assign each unresolved record one deciding check and a responsible staff member. Group visits by area, then return the result and date to the investigation record.
7. Approve the billing batch. Calculate the old and proposed charges under the applicable tariff. Apply the utility’s notice and effective-date procedures, test the file in staging and retain the approval record.
8. Check the posted outcome. Reconcile the accepted batch to the posted records and inspect selected bills. Record upward corrections and downward corrections separately. Set the next review date for remaining exceptions.

For a first-month schedule, use the opening week for the baseline and surface rules. Schedule the pilot’s delivery with PorchRocket, then reserve the following week for output and account-join review. Use the remaining time for exceptions and import testing. Set the production date from the utility’s billing calendar after the pilot establishes the workload.

Rate consultants bidding this work can use the government service contracts guide to plan the public procurement process. Bid Control by PorchRocket brings public opportunities, bid papers and addenda together so the consultant can evaluate the required scope before preparing a response.

A refresh cycle that protects the next bill

Maintain a rolling change queue for review and a frozen billing snapshot for each cycle, with a named owner for every unresolved account.

I would start with quarterly exception reviews and an annual reconciliation timed to the billing baseline, adjusting those intervals to the utility’s workload and adopted rules. Set review triggers around the evidence your program receives. Route completed site records and accepted customer corrections into the queue between broader imagery reviews. Keep the proposed change out of the billed snapshot until the approval process assigns its effective period.

Asset Search can monitor a territory and return observed changes with before-and-after dates as new imagery becomes available. When the search requirement changes, the service can re-answer previously reviewed sites, often using the evidence already collected. That is valuable when a utility revises the question it needs answered about a surface category.

Make the refresh report small enough for someone to work. For each account, show what changed, why it matters to the agreed search rule and what decision remains. Include removals in every edition. Return rejected candidates with reasons so staff do not repeatedly investigate the same surface.

Keep program measures tied to the workflow: accepted corrections per review hour, unresolved accounts by age, and the share of approved changes verified on bills. Report customer-requested corrections beside changes found through territorial review. A backlog of approved records waiting for import deserves the billing manager’s attention.

For a contractor who only wants properties with paved parking areas, the self-serve parking-lot property lists are the narrower starting point in Ground Control. Utility reconciliation calls for a custom investigation built around measured changes and account evidence.

Assign responsibility for the next edition before closing the first batch. Put the baseline date, open field checks and import decisions in the handover record. The next reviewer should be able to continue from that file.

Reconcile accounts with Asset Search

The fastest way to start a stormwater surface reconciliation is to scope an Asset Search by PorchRocket pilot around your accounts, local surface rules and required evidence. The service cross-references aerial and satellite views with property records and public data, then returns every candidate’s disposition. Fits carry supporting observations; rejects carry reasons; unresolved records identify the field check that settles the question. Start with a small paid pilot credited toward the full order. Buy a defined reconciliation per completed investigation, then use a subscription for ongoing change monitoring.

For a stormwater billing scope, ask for these six deliverables:

• A parcel-and-account schedule aligned with your baseline and selected service area.
• Separate additions and removals, with the observed facts behind each proposed correction.
• Dated views and record references that billing staff can retrieve during an appeal.
• Owner information and a reviewed disposition for every candidate, including rejected changes.
• An unresolved queue with the deciding field check recorded for each account.
• CSV, Excel or GIS-ready delivery arranged for the agreed import, followed by refresh editions when requested.

Tell us what to find: describe the territory, billing question and file your team needs. PorchRocket returns a scope and quote, with no software to learn or imagery to buy.

Give billing staff a correction they can explain from the account record.