SprayBossPro Blog — Program Management

How to Track Pre-Emergent and Post-Emergent Programs Separately in One System

A customer enrolled in a full weed control program may receive both pre-emergent applications (spring and fall) and post-emergent treatments (multiple rounds across the growing season) under the same account. These are distinct service types with different products, different scheduling logic, different compliance fields, and different customer communication requirements. Tracking them under the same service type in a shared scheduling queue creates confusion in compliance logs, inaccurate round numbers, and incorrect SMS messages. They need to be tracked separately — even when they're serving the same customer.

Why Combined Tracking Fails

When pre-emergent and post-emergent are treated as one service type, several problems emerge. Round numbering breaks: a customer who received pre-emergent in March and three post-emergent visits by July shouldn't show "Round 4" on their next post-emergent — the pre-emergent wasn't part of the post-emergent sequence. Compliance logs for the two service types require different fields: pre-emergent often uses granular application tracked by sq ft per bag; post-emergent is typically liquid tracked by gallons applied at a specific rate per 1,000 sq ft. Putting both in one log type produces incomplete records for both.

SMS templates also differ. The re-entry interval for a granular pre-emergent is typically "water in within 48 hours" plus a short REI. The post-emergent SMS instructs the customer to stay off the lawn until dry, provides the REI, and may include watering instructions specific to the post-emergent product. A single template that covers both will be wrong for at least one of them on every send.

Service Type Configuration in Purpose-Built Software

In purpose-built weed control software, each service type is configured independently: separate waiting list entries, separate scheduling intervals, separate compliance log templates, and separate SMS alert templates. A customer enrolled in both pre-emergent and post-emergent programs has two separate service queues on their account. When pre-emergent season opens, their pre-emergent entry appears in the pre-emergent waiting list. When a post-emergent round is due, the post-emergent entry appears in the post-emergent queue. The dispatcher sees them as distinct services, routes them appropriately, and the compliance log for each visit captures the data specific to that service type.

Managing Both Programs for the Same Customer

When a customer has both programs active, some visits will be combination visits — particularly when a spring pre-emergent coincides with a post-emergent that's also due. The system needs to show both services due for that customer so the technician can address both in a single stop. This combination visibility — "This stop has a pre-emergent AND a post-emergent due" — should be clear on the dispatcher's view and the technician's mobile stop card.

The compliance log for that stop should produce two separate records: one for the pre-emergent application (product, rate, granular area covered) and one for the post-emergent application (product, EPA reg number, liquid rate, area sprayed, conditions). Both records must be independently complete for compliance purposes.

The Waiting List View Across Both Programs

On any given routing day, the waiting list should clearly separate pre-emergent and post-emergent pending accounts. A dispatcher who sees 80 pre-emergent accounts and 35 post-emergent accounts due this week understands the work differently than one looking at 115 undifferentiated "weed control" stops. The service type breakdown drives routing decisions: pre-emergent accounts get prioritized based on window urgency; post-emergent accounts are routed by geographic density and days overdue.

For the field logging details that make separate compliance records work correctly per service type, see How to Log EPA Reg Numbers for Weed Control Products in the Field.