App Developers in San Antonio Who Read the Aquifer Before the Route

Updated November 2026 · Written and maintained by the Progression Agency strategy team

A landscape crew pulls up to a house on the North Side on a Tuesday to run and test the sprinklers, but under SAWS drought rules the last digit of that address points to a different day. One wrong day can put a water waste charge on the customer’s bill. San Antonio’s watering rules change with the Edwards Aquifer, stage by stage, and the day for each property follows the last digit of its address. App developers in San Antonio building for crews and property managers have to put those rules inside the route. Progression is based in New York, builds for South Texas businesses remotely, and offers on-site sessions on request.

A crew truck on the wrong day

A crew gets to a house early on a Tuesday. The route sheet on the dash says the sprinkler check is due, and nothing on the sheet says the day for this address is a different one. The card below is hypothetical, and it shows how one printed route can put a customer on the wrong side of a rule.

The sheet is the problem, not the crew. A paper route lists stops in an order that made sense last week, and it cannot know that the stage changed on Monday. An app can hold each property’s designated day, the stage and the hours, and flag the stop before the truck leaves the yard.

• Put each property’s designated day in its record, not in a note.
• Show a warning when the day, the stage or the hour does not fit.
• Let the office change the stage in one place.

What app developers in San Antonio build from the SAWS rules

The San Antonio Water System uses watering rules set by city ordinance. The rules limit water use according to specific levels of the Edwards Aquifer, and during drought stages the day for each property is set by the last number of its street address. The stage sets the frequency and the hours. Read the SAWS drought restrictions page for the current text, since the rules and the stage can change.

SAWS also says the rules apply to all its customers, inside and outside city limits. A crew that works on both sides of the line follows one set of rules, and the app does not need a separate mode for each.

What can the app not decide?

The app does not set the stage and does not interpret the ordinance. It holds what SAWS publishes, applies it to each stop and shows the people who plan the route what it did. Questions about a rule go to SAWS.

Who sees what in the app?

The office sees the stage, the week’s changes and the log. The crew sees today’s stops, the day and the hours for each. The customer sees notices the office approves.

Ten properties, every stage

Here is one route of ten properties, run through each stage. Each row gives the aquifer trigger, how often and when watering is allowed, what the app schedules, what it blocks and what it tells the customer. The rules are SAWS’s, taken from its page; the behavior is how a scheduling app can follow them.

The address digit as a field, not a note

Store the last number of the street address as its own field on every property, and let the app work out the day from it. A note in a free text box will be missed, and a day typed by hand can be wrong. Confirm the day for each number with SAWS, and let the office load it once.

• Make the digit a required field.
• Take the weekday for each digit from SAWS and show where it came from.
• Re-check the digit when an address is edited.

Medians and entryways with no street address

SAWS says areas without a street address, such as medians and neighborhood entryways, water on Wednesday during drought stages. A route that includes common areas needs a property type for them, so the app does not look for a digit that is not there.

• Create a type for areas with no street address.
• Set its day to Wednesday under drought stages.
• Show the type on the stop so a crew sees why.

Stage 4 and every other week

Stage 4 allows landscape watering only once every other week, and the City Manager may declare it in consultation with the SAWS president. The app needs a week counter for each property, so it can tell which week is the on week. Five stops one week and five the next is one way a route can stay balanced.

• Keep an on week flag on every property.
• Show the flag on the route and on the customer notice.
• Let the office rebalance the weeks when it switches the stage.

What a build like this costs

A scheduling app for a landscape or irrigation crew is a small to mid size project. Cost follows the number of users, the maps, the customer notices, the integrations with billing and the log. Progression quotes after a written scope, with a free proposal first. The bands below are published market figures, from the typical low to the published high.

These bands do not include maps, messaging fees or SAWS data work. For what drives app prices in general, see app development cost.

When the stage changes overnight

Stages move with the aquifer’s ten day rolling average. On August 3, 2026, Texas Public Radio reported that SAWS would end Stage 3 on August 4 after rain lifted the average above the trigger. The surcharge for single family households ended with it, and the once a week schedule by address stayed the same.

That example shows two kinds of change. One is a rule that ends, and the other is a rule that stays. An app should take the stage as a setting the office changes, and should never guess it from a gauge or from the news. Check SAWS for the stage in effect at any time.

What changes on the route?

In a move up a stage, hours and days may shrink and stops move. In a move down, the hours may widen, though SAWS says leaving a stage can be considered 15 days after the aquifer is above the trigger. The app should show the office both the new route and the old one.

• Keep the date each stage began in the log.
• Show a preview before the new route reaches a crew.
• Keep old routes for a week in case of a question.

Hand work and system work on the same route

A crew does more than run sprinklers. It pulls weeds, trims shrubs, checks heads and replaces filters. The rules restrict irrigation, so the app should separate tasks that use the system from tasks that do not.

Mark each task as one or the other. A stop with only hand work can happen on any day, and a stop that needs the sprinklers has to wait for the designated day. This is plain scheduling advice, and the app reads no more of the ordinance than SAWS’s page says.

• Tag each task as system work or hand work.
• Let hand work fill the days between system visits.
• Show a crew which tasks wait for the designated day.

The water waste charge and the customer’s bill

SAWS no longer issues municipal court citations. Instead, a water waste charge appears on the customer’s bill. The first charge for a single family or small commercial site is $137, and a one hour online course can waive it. Later charges are higher, and SAWS says high use commercial irrigation customers face higher charges too.

The charge lands on the customer, so the crew’s record matters. A log that shows what ran, on which zone, at what time and by whom answers a question quickly. SAWS also says violations are witnessed and documented in person by trained staff, and that a customer can review the evidence and appeal.

• Log every zone started, with the time and the person.
• Keep the log for a full season at least.
• Share the log with the customer on request.

What should the app tell a customer?

The day, the window and the stage, in plain words. If a visit is moved, say why. If a charge arrives, the customer should be able to see the log and the office can point to the record.

Surcharges for the biggest outdoor users

SAWS says its Stage 3 surcharge applies only to the top 5% of water users. For single family accounts it was $10.37 per thousand gallons above 20,000 gallons a month, and in Stage 4 the threshold drops to 12,000 gallons. Commercial irrigation surcharges vary with use and meter size, and SAWS can answer those questions.

A property manager’s view can show usage next to the threshold, so a manager sees a month’s use before the bill. The app displays what the customer enters or what an integration brings in. It does not predict a bill, and it sends rate questions to SAWS.

• Show each account’s monthly use beside the threshold.
• Warn the office when an account is close.
• Link the rate question to SAWS.

The office screen for a stage change

One person in the office should be able to change the stage in one place. The screen below holds the switch, a preview of the week’s changes and the notices waiting to go out.

The six cards above are the parts of the screen. Our app development agency page explains how apps like this are scoped. For work on the search side in the same city, SEO in San Antonio has its own page.

What does the crew see at the start of the day?

A crew lead opens the route and sees today’s stops, each with its designated day, its window and its tasks. A stop that cannot run today is greyed out with the reason, and a stop that can is first in line.

• Today’s stops come first, in route order.
• A greyed stop shows the reason in plain words.
• A banner shows the stage and the date it began.

Can a crew change a stop?

A crew can note a problem and ask the office to move a stop. Only the office changes a day or a stage, so the record stays the same for everyone.

What if the signal drops in the field?

The route should work without a connection and send its log when the phone has signal again. The time of each start stays as it was entered.

Related services and guides

Pages that sit beside this route:

• App development agency
• App development cost
• App development company in Texas
• App development company in Houston

Frequently asked questions