How can a team organize a driving-for-dollars territory without covering the same streets twice?

A unit is the set of streets one driver covers in a single afternoon or evening. PropertyRadar's guide suggests groups of 30 properties or fewer when a drive follows a list of target properties. A street survey has no target list, so size the first units by street length and driving time, and resize them after the first drive.

Draw the units with lines every driver can see. The mobile app's Boundary layer draws ZIP Codes, counties, municipalities, census tracts and block groups over the map, and those lines look the same on every phone. When the shapes are too big for one session, the Draw Location Criteria tools cut a polygon, a rectangle or a radius around a point. Save each unit as its own named list, because drawn criteria aren't saved unless you make a list from them. An invited member can access the account's saved data, so every driver can work from the same unit names.

Define each unit by its boundary alone. A list built on criteria with monitoring turned on adds and removes properties as they start or stop matching, so a unit built that way can change between the day it is assigned and the day it is driven. Keep a filter such as tax delinquency in a separate list. Our answer on dynamic and static property lists covers how the two behave, and a team that hasn't decided how much of the territory to drive can size that first with a records filter ahead of the drive.

A street that divides two units gets driven twice when each driver assumes it is theirs, and it gets skipped when each assumes it belongs to the other. One rule applied everywhere settles it. A simple version is that the unit to the north or east owns the street, both sides. Draw the owning unit's polygon to take in the lots on both sides of the street, and stop the neighbor's polygon at the back of those lots.

Then check that every parcel belongs to exactly one unit. Export the territory and each unit list, and compare them on county and assessor parcel number. A parcel that appears in two unit lists is an overlap, and a parcel in the territory that appears in none is a gap. Matching totals don't settle the question, because an overlap in one place can cancel a gap in another.

Suppose a manager and four drivers split a territory into five units and revisit each one every six weeks. Each row of their record is one unit saved as a named list. Midway through the week of October 5, the record looks like the table below.

Every unit has one driver and a start and an end address. The status column holds the stopping address when a session ends early. The record can live in any shared spreadsheet, as long as its unit names match the saved lists.

Each driver needs a separate login, because the app sorts tracks by member. For a manager and four drivers, PropertyRadar's pricing page puts five logins on the Team plan at $324 a month. That is $249 billed monthly with three users included, plus two more at $37.50 each.

Before the drive, the Route option under Marketing Options takes a start and an end address and returns turn-by-turn directions the driver can save or print. To record, the driver opens Discover, then Explore, turns on GPS Tracks and taps the red circle. For each house worth a follow-up, the driver adds it to a static list from the property profile, attaches a photo and a dated note, and sets a Status so a teammate can pick it up. At the end of the unit, tapping the square brings up Stop Tracking, and Stop saves the track to the Tracks list.

If the track ran on past the unit, the driver trims it by swiping left on it, tapping the edit button and moving the Start Point and End Point sliders. Then the driver updates the status in the record, either as driven or with the last address reached. The manager needs to see that track, and drivers need to open the saved unit lists, so confirm both from each login during setup. If the manager's login doesn't show a driver's tracks, the driver shows the track at handoff.

A half-driven unit has a stopping point somewhere in the middle. If nobody writes it down, the streets on either side of it get driven again or skipped. The East 02 row above shows the fix. Driver 4 saved the track, wrote 2200 Orchard Rd in the status along with the date the unit will be finished, and will start the next track at that address. The same prompt that saves a track also offers Continue Tracking, which keeps the recording going if the square was tapped too soon.

The same driver should get the unit back first, since that driver knows which streets are done. If someone else has to finish it, the manager passes along the stopping address and the streets the first driver's track already covers. The revisit date is set from the day the unit is finished, so a partial drive doesn't count as the last full pass.

In the Tracks list, the View By section has a Member tab and a Month & Year tab, each with its own selector. The next morning, the manager opens each driver's track, compares it with the unit, and sets the revisit date in the record.

Two drivers' tracks on the same block are worth a question, since one driver may have been passing through to reach a unit. If both surveyed it, the block doesn't need another drive, and the manager corrects the boundary or the assignment that caused it. A street no track covers gets a question to the driver first, in case the recording was off. If it was missed, it goes first in the next round of assignments, along with any half-driven unit.

A track shows where the car went. Photos and notes show which houses a driver stopped to record, so the review covers both. It also helps when drivers record the same distress signals in the same words, so a note from one unit can be compared with a note from another.