Sales Route Planning: How to Build Optimised Field Routes in Google Sheets

Sales route planning is the process of sequencing daily or weekly account visits geographically to reduce drive time and increase face-to-face selling hours. Instead of visiting accounts by alphabetical spreadsheet order, reps group stops into tight clusters, turning scattered driving across three counties into a single geographic sequence.

This workflow is built for field sales operations managers and reps who need to organise Salesforce territories without paying for dedicated routing software. You will get a live, colour-coded map of your territories and clear daily driving loops for your team.

Why spreadsheet sales route planning beats alphabetical sorting

Salesforce's State of Sales research consistently shows that field reps spend less than 30% of their time actively selling. The remaining 70% goes to administrative tasks, travel, and planning. A significant portion of this wasted time stems from poor route architecture. When a rep plans stops alphabetically from a standard CRM list, they lose up to an hour daily to unnecessary backtracking across their territory.

Sales route planning is the process of sequencing account visits to minimise drive time and maximise face-to-face selling hours. The core failure of traditional CRM data views is that they prioritise alphabetical or revenue-based sorting over geographic proximity. Reps naturally default to familiar accounts instead of nearby ones.

An efficient route plan flips this logic: it starts by mapping where accounts physically sit, then sequences stops into tight geographic clusters. By doing so, a rep covering a dense urban territory can realistically increase daily visits from four to seven. The prerequisite to achieving this efficiency is visual geographic data. You cannot spot geographic clusters in a standard spreadsheet row. Moving account data from an alphabetical list into a visual map is the mandatory first step to reclaiming those lost selling hours.

Step-by-step: Building a sales route in Google Sheets

Building an optimised route requires transitioning your CRM data from raw text to a visual map. Here is the exact workflow to sequence your accounts using Google Sheets and the InstaMaps add-on.

If you prefer not to type formulas manually, open the sidebar (Extensions > InstaMaps > Enable formulas) to insert them directly, or use the Build-the-workflow button to write entire formula chains automatically.

1. Export your Salesforce report: Filter accounts by owner, stage, or region. Export this list as a CSV and open it in a new Google Sheet. Ensure you have dedicated columns for street, city, and postcode.

2. Standardise the location data: CRM data is notoriously messy. Before mapping, combine your address fragments into a single, clean string. In cell D2, type =CLEAN_ADDRESS(A2:C50) (assuming A is street, B is city, and C is postcode) to process your entire dataset.

3. Generate coordinates: Maps require latitude and longitude. In cell E2, use =GEOCODE(D2:D50). The free tier provides 100 lookups per day (1,000 per day with a free email unlock), which easily covers a standard weekly export.

4. Render the live map: In cell F2, type =INSTAMAP(E2:E50, D2:D50). This generates a live, hosted shareable map URL that updates automatically whenever you add or remove rows in your sheet.

5. Isolate the viewport: Open the InstaMaps add-on from the Extensions menu and click 'Load Map'. The accounts appear as markers. Zoom into the specific region you are planning for that day.

6. Filter by priority: Use standard Google Sheets filtering to isolate high-priority accounts (for example, stage = 'Proposal'). The map instantly updates to show only those markers in your viewport.

7. Assign routes: Group 5 to 8 accounts that form a logical geographic loop. Copy these rows into a new sheet tab, prefix the tab name with 'layer_' (for example, layer_MondayRoute), and reload the map. Each tab becomes a colour-coded layer.

Worked example: Sequencing a 47-stop medical device farm

Consider a medical device rep managing a 47-account territory across Greater London. The rep has exported their Salesforce data into a Google Sheet, cleaned the addresses in column D (rows 2 through 48), and generated coordinates in column E using =GEOCODE().

Instead of manually scanning the map and guessing which hospitals are closest together, the rep uses formulas to mathematically sequence the stops. First, the rep identifies a tight cluster of 8 hospitals in South London for Tuesday's route. They paste these 8 specific addresses into cells D2 through D9 of a new tab.

To calculate the exact distance from their starting location to every other stop in that cluster, the rep uses =SORT_BY_DISTANCE(). In cell G2, they input =SORT_BY_DISTANCE(F2, $F$2:$F$9) to evaluate the geographic positions of all 8 stops.

Next, the rep sequences the actual driving order. In cell H2, they write =VISIT_ORDER(F2:F9). This function returns the most efficient numerical sequence to drive the stops, outputting numbers 1 through 8. The rep sorts their sheet by column H to finalise the driving hierarchy.

Finally, the rep needs the actual turn-by-turn navigation link. In cell I2, they type =ROUTE_LINK(D2:D9). This compiles the 8 addresses into a single clickable driving link. Because =ROUTE_LINK() uses Google Maps' official URL scheme, it is capped at a maximum of 11 stops. By restricting the formula to daily clusters, the rep turns a scattered list of hospitals into an ordered, navigable sequence in under 60 seconds.

Common sales route planning mistakes and metrics

Effective sales route planning requires more than just drawing lines between pins. Teams consistently make two operational errors: ignoring time-of-day constraints and overloading daily schedules.

Medical device reps know teaching hospitals are best visited before morning rounds start at 7 AM. Restaurant suppliers know owners are only reachable during the post-lunch lull between 2 PM and 4 PM. Your route must account for when contacts are actually available, not just where they are physically located. A perfectly optimised geographic loop fails entirely if it puts you at a restaurant at 11:30 AM.

Overloading routes is the second failure point. Scheduling eight consecutive meetings sounds highly productive until one meeting runs 20 minutes long, cascading delays through the entire afternoon. Most experienced field reps cap their day at 6 planned stops, leaving 2 flexible slots to absorb the unexpected without derailing the route.

To ensure your planning is actually working, track two primary metrics. First, look at drive time as a percentage of working hours. If a rep spends 40% of their day driving, they have a routing problem. The target is under 25% for urban territories and under 35% for rural routes. Second, track visits per day per rep. If structured geographic clustering moves a rep from 4 stops a day to 6, that is a 50% increase in face-to-face selling time with zero additional headcount cost.

The territory-to-route handoff

Territory planning is a quarterly manager exercise: balancing account distribution, patching coverage gaps, and defining boundaries. Route planning is a daily rep exercise: sequencing a specific set of stops to minimise drive time. Most workflows break at the handoff. A manager designs a balanced territory, exports a 500-row Salesforce report, and emails it. The rep receives a spreadsheet sorted alphabetically by company name, completely devoid of geographic logic.

InstaMaps bridges this gap directly in Google Sheets using tab prefixes. Instead of exporting and reformatting, the rep filters the manager's master tab and copies their assigned 47 accounts into a new tab named layer_MondayRoute. Because InstaMaps reads any tab with the 'layer_' prefix as a distinct map layer, the Monday route instantly plots as a separate colour on the map.

If a rep needs to prioritise urgent renewals, they copy those specific rows into layer_PriorityAccounts. The rep can then use =SORT_BY_DISTANCE(A2:A50, B1) to organise the stops, followed by =VISIT_ORDER(A2:A48) to number them logically. Finally, running =INSTAMAP() generates a live, hosted URL of their daily loop. This structure preserves the manager’s master data while giving the rep the geographic clustering they need to execute the day.

Limits and honest alternatives

InstaMaps does not auto-sequence stops based on live traffic data. It provides geographic visibility and mathematical sorting, but you still sequence the final route manually. If a cancellation frees up an hour, InstaMaps will not instantly recalculate the optimal path for the remaining stops.

Additionally, any tool relying on standard Google Maps URL schemes faces a hard technical limit. When you use the =ROUTE_LINK(A2:A12) formula to generate a turn-by-turn navigation link, Google Maps caps the journey at 11 stops (10 waypoints plus the destination). If your rep has 15 stops for the day, a single formula link will fail to plot the final four. You must split the route into two separate =ROUTE_LINK() formulas, or use =INSTAMAP() to view all 15 markers on a single interactive map instead.

When manual cluster planning fails-typically when field reps manage 15+ daily stops and need real-time re-sequencing as conditions change-enterprise tools fill the gap. Badger Maps ($49/user/month) handles multi-stop route optimisation natively. Salesforce Maps ($75/user/month) adds route optimisation on top of its full field execution platform. For teams needing daily auto-sequencing, those per-user subscriptions are the correct investment.

Who this workflow is for

This workflow is ideal for three specific users:

1. Solo field reps managing 20 to 50 weekly accounts who currently plot stops manually or cross-reference addresses in a spreadsheet.

2. Small field sales teams lacking the budget for $50 per-user-per-month mapping software. With a 100 lookups/day free tier (or 1,000/day with a free email unlock), you can map an entire territory at zero cost.

3. Sales operations managers who need to audit territory balance quarterly. By plotting 2,000 accounts using =GEOCODE(A2:A2000) and =INSTAMAP(), managers instantly spot geographic coverage gaps before assigning them.

Common Questions