Recurring service visits bring technicians back to the same customer locations. The effort those locations need can differ with the frequency and length of each visit. A service manager reviewing regions needs to know how that work is spread across the area.
The regional plan also affects which locations a technician visits on the same trip. That's a different question from arranging today's stops to shorten the trip.
Prepare recurring regional workload
Use one row per customer service location for the regional plan. Keep its customer ID, full address, current region, usual technician, job type, visit frequency, and expected service time. If a customer has several buildings, keep the service locations separate. You may need different trips to reach them even when one customer pays the bill.
Choose one planning period for the workload calculation. Mixing weekly visits at one location with monthly visits at another will give you totals that don't mean much. Use the same period across the whole customer list, and keep the period in the column name or workfile notes.
A useful workload field is the number of visits in a planning period multiplied by the expected minutes per visit. Calculate it in your source spreadsheet so the regions account for the time spent on service as well as the area covered.
For a simple arithmetic illustration, a location needing 4 visits a month at 45 minutes each contributes 180 service minutes a month. A site that needs 1 visit of 120 minutes adds 120 minutes. Each adds one customer to the count, but they need different amounts of service time. These are planning calculations, not measured travel savings.
Keep driving out of that service-time field. You'll inspect access and routes later. Combining an uncertain travel allowance with the service estimate makes it harder to see why one proposed region looks heavier than another.
Import the prepared customer data into Maptive and check the placement of the service addresses. Keep a list of technician bases too. A home base, a branch, and a parts depot may all matter, but decide which origin you are using for this regional plan before you compare areas.
Daily job records need their own IDs and dates. You can map those fields, but don't mix repeated visits into a customer-level workload total without accounting for them. Otherwise, a customer with several imported jobs may contribute the same monthly effort several times.
Build the technician regions
Balance the selected work measure
Open Map Tools, select Territories, and choose Create Territories. Select Auto Territory Builder and click Continue. Choose a boundary set, such as US Zip Codes, then click Continue again.
Choose Data Metrics and select the workload column you prepared. You must select at least one variable. If you use other variables, choose how much weight to give each one. Account count may help you inspect the result, but it shouldn't automatically carry the same weight as service minutes. Click Continue, choose the territory count, and click Continue. Enter a group name and select Generate Territory.
The builder produces the regions, a metric distribution graph, and boundary metrics. Review the workload spread first. Check whether one region contains much more service work than the others, then inspect the locations that cause that difference.
A small region can still need a large share of a technician’s time. Look for frequent service locations or unusually long visits before you move a boundary. If the estimate comes from weak job history, correct the estimate in the source data and rebuild. Changing the area won’t fix a wrong estimate.
Keep the first proposal available while you review changes. Use a clear group name that identifies the planning period and proposal, so an earlier region set doesn't get mistaken for the approved plan.
Preserve continuity and base access
Use Respect Previous Territories when the existing regional structure is worth keeping. It lets the build start from that structure while you review the new workload. This is useful when familiar customer relationships or established service days are part of the operating plan.
Respect Sales Rep Locations can use a separate map of technician bases, even though the control says sales reps. Select the location map and its naming column. The territory count comes from the number of those locations. The builder attempts to center territories around them, so inspect the result rather than assuming every technician's base is in the right place.
Optimize with Constraints lets you apply thresholds to variables you've already selected for territory creation. If a workload column wasn't selected earlier, you can't add a constraint to it at this stage. Go back and include the variable when it matters to the regional plan.
Next, look at the roads around each base and region edge. Neighboring ZIP codes may connect through an easy corridor, or they may require a long trip around a river or limited crossing. The region outline is a starting point for that access review. Test the customer locations on both sides before moving them.
Correct edge areas and exceptions
Click a territory or open its three-dot menu to edit it. Use Edit Territory for drawing or drag-and-drop changes, or Advanced Edit for boundary selection. Select the method, mark the area, and click Save. Choose Reassign the drawn area between territories, then Done, when the area should belong to one region. That choice removes the area from every other territory it overlaps.
Use Add the drawn area to an existing territory only when you mean to retain overlapping coverage. It preserves overlaps. For a region with one owner, that may make it look as though two technicians are in charge of the same area. Record the reason if shared coverage is intentional.
Complex boundaries may have too many points for vertex dragging. Use the available boundary-selection method instead of assuming every outline can be reshaped by dragging its corners.
If the work follows whole ZIP codes, you can adjust their manual fill assignments in Boundary Tool. Load the boundary set, choose Set Manual Fill, select On Click, On Hover, or Lasso Tool, and click Start. Select the boundaries, click Save, choose Add Boundaries to Existing Fill Group, and click Done. Moving them into an existing fill group removes them from their other fill groups. Check the customer records after the geographic change too.
For a base-access check, remember that Drive Time Polygon Tool assumes perfect driving conditions. It leaves out current and past traffic. Open it from Map Tools, enter the base address, set hours and minutes, and select Add Drive Time Polygon. Inspect the customer points near its edge. Use actual trip knowledge to review difficult roads or congested approaches before approving their assignment.
Treat trips across a boundary for special skills differently. Keep the recurring regional owner in one source field and the assigned technician for the specialist visit in another. Moving the whole area for one unusual job may spread out the usual route more than it needs to. Give the service planner an exception record with the job ID, required skill, and reason for the crossing.
Select one technician's eligible day
Open Map Tools and Filter Tool. On first use, choose Create Filters. If filters or grouping already exist, use the gear to configure them. Select Group beside the region or technician column, then select Date beside the service-day column. Add a job-type filter when it helps isolate the intended work.
Review the filtered job list before selecting the route. Confirm the job IDs, service date, technician assignment, and required work. An area group doesn't prove that a technician has the right qualification, parts, or access permission.
Watch for filters left over from an earlier check. A job-type restriction can remove valid stops from the day you're planning. Uncheck a filter's checkbox to disable it, then compare the resulting records with the intended job list.
Keep appointment commitments in the imported fields so the planner can review them. Maptive can map and filter those records, but it doesn't automatically match jobs to a technician’s skills or track live technician status. Check who can do the work in the service system before you approve the selected jobs for the day.
Compare separate regional routes
Order one region's stops
Add the selected locations through a marker's tools icon and Add to Route, or use Lasso & Fill Locations to collect a group. Close the lasso polygon, then check that the locations in the routing panel match the filtered job IDs. Include the depot or other required endpoint explicitly.
Arrange the first and last locations before optimization. Optimize Route keeps those endpoints fixed. If the technician must return to the depot, the route needs that return location at the end. Maptive supports up to 73 locations per route, so count the endpoints along with the jobs.
Click Get Directions for the proposed order. Then select Optimize Route and Add another directions instance to retain a comparison. Check that both instances contain the same eligible jobs and endpoints. A route with a missing stop can appear shorter for the wrong reason.
Review edge-area jobs in this comparison. If a few stops force repeated trips across the same corridor, review which region they belong to or which day to do the work. Confirm that the change still works for the jobs' frequency and appointment commitments before you adopt it.
Keep several routes on the same map
Use Clear Form, select the next region's stop set, and choose Add another directions instance for its route. Under Settings, choose Edit Route to change its name and color, then Save. Give each route a name that includes the technician or region and service date.
You can then inspect the regional routes together. Look for crossings caused by a misplaced edge account, a shared depot, or a legitimate specialist assignment. Review the cause before changing a territory. A shared starting point will naturally produce some common travel.
Compare the expected time on the jobs with the time spent driving. Two technicians with the same number of stops can have very different workdays. Add the expected time for the selected jobs in the planning workfile and check it against the route and the available shift.
Export the intended regional job list through the map's Export Data icon. Choose Export Filtered Data, select .xlsx, .tsv, .csv, or Clipboard, and click Export Now. Export Data Visible on Map follows the viewport, so it can leave out a job simply because you've zoomed into another part of the region. Check that the exported IDs match the selected route list.
Approve coverage and daily work separately
Keep an approved regional workfile with the boundary version, recurring owner, workload period, and specialist exceptions. Keep a separate daily job file with the selected jobs, route, and service commitments. The service planner still needs to approve skills, parts, site access, appointment windows, and actual time each job takes in the service system. Maptive doesn't schedule or dispatch technicians. When an edge assignment changes, update the recurring owner record and tell the daily planner which future visits it affects before releasing the next day's work.
