How to Plan a Multi-Stop Mystery Shopping Route Without Losing Money on Gas

Every mystery shopper hits this math problem eventually. You have six assignments spread across town, each with its own pay, deadline and time window, and the order you visit them in can be the difference between a genuinely good day and one where half your fee went to gas.

Here is how to actually plan it, instead of working down a list in the order the jobs came in.

Start with constraints, not distance

The instinct is to sort stops by what is closest first. That is the wrong first filter. Start with time windows. Any stop that only accepts visits between, say, 10am and 2pm has to anchor your route, because missing that window usually means losing the assignment entirely. Distance is a secondary optimization once the hard deadlines are locked in.

The reason this ordering matters is asymmetry of consequences. A badly optimized route costs you twenty minutes and a few dollars of gas. A missed time window costs you the entire fee, and sometimes your standing with that scheduler. Optimize the cheap thing second.

The anchor and fill method

Do it in this order every time and it stops being a puzzle:

1. List every stop with its window. Write the actual clock times, not "morning."
2. Find your hard anchors. Any stop with a window shorter than about three hours is an anchor. It is going in a fixed slot and everything else moves around it.
3. Place the anchors in time order and check they are geographically survivable. Two anchors an hour apart with windows that overlap by thirty minutes is an impossible day. Better to find that out now than at 1:40pm.
4. Fill the gaps with flexible stops, choosing whichever unrestricted stop sits closest to the line between two anchors.
5. Put the loosest stop last, ideally the one nearest home, so the thing that slips when the day runs long is the thing that can slip.

A worked example

Six stops, one day. The raw list looks like this:

Two anchors: the north fuel audit, which closes at 10am, and the lunch shop, which has a two hour window in the middle of the day and cannot move. Everything else is fill.

The route writes itself once the anchors are down. North fuel audit first thing, because its window closes earliest. Downtown bank next, since it opens at 9am and sits between the north side and the lunch shop. Lunch at 11:30am. Then west for the retail and fuel pair, which are close to each other and unrestricted. Pharmacy last because it is two minutes from home and the day can absorb losing it.

Sorting that same list by distance instead would have put the two west stops early, stranded you across town at 11:15am, and cost you the $25 lunch shop plus its reimbursement.

Group by direction, not by company

It is tempting to knock out all your IPSOS shops, then all your LiveShopper shops, because it is mentally tidy. But if IPSOS Job A is across town from IPSOS Job B, you have just doubled your driving for no reason. Group by geography and let the payer be irrelevant to the route order. A payments view that keeps each company straight regardless of visit order means there is no downside to interleaving.

The only legitimate reason to cluster by company is a shared report deadline. If one company wants everything submitted within twelve hours and another allows forty eight, that changes what you can safely leave for tomorrow night, not what order you drive in.

Do not trust straight line distance

Two stops that look close on a map can still be twenty minutes apart if they are on opposite sides of a highway with no easy crossing. Rivers, rail lines, one way grids and divided roads all lie on a map at the zoom level you plan at.

If you are planning by hand, add a buffer of roughly a fifth to a quarter more time than the straight line distance suggests, and more than that downtown. Or use a tool that pulls real drive times from a routing engine rather than guessing, which is the entire reason routing engines exist.

Build in time on site and report time

A route that only accounts for driving will blow its schedule by early afternoon. If a fuel station audit reliably takes you eighteen minutes and a sit down restaurant shop takes forty five, those numbers need to be in the plan. Otherwise "arrive by 2pm" quietly becomes "arrive by 2:40pm" three stops in.

The bigger omission is report writing. A day of six shops is not six shops, it is six shops plus however long the reports take, and reports are the part shoppers consistently underestimate. A narrative report with ten required photos is not a five minute job. If you are planning a full route, block the report time on the same calendar you planned the driving on, because it is the same day's work.

Track your own real numbers for a month: actual minutes on site and actual minutes per report, by company. Most shoppers who do this discover they have been optimistic on both, and once you are planning from your own measured figures instead of your impression of them, the whole day gets more accurate.

The human parts of the day

Routes planned on paper tend to assume a machine is driving them. Leave room for:

• Fuel. A fill up is ten minutes you did not schedule, and on a long route you will need one.
• Food. If none of your shops are dining shops, you still have to eat.
• Bathrooms and parking. Downtown parking alone can be a reliable fifteen minutes.
• A location that is closed, under construction, or simply not where the address says. This happens often enough to plan for, not often enough to plan around.

A day with no slack is a day where the first surprise cascades into every stop after it.

When the route breaks mid day

It will. The useful question is what you do at 12:30pm when a stop takes twice as long as planned.

Re-plan from where you are, not from the original list. The stops behind you are sunk. Ask which remaining stop has the earliest closing window, go there, and treat everything else as newly flexible. The instinct is to try to catch up by rushing the original order, which is how a shopper ends up doing a sloppy audit and getting a report kicked back, turning a late day into an unpaid one.

If something genuinely has to drop, drop by value per remaining minute rather than by fee. A $32 audit forty minutes away is worth less to the rest of your day than two $14 stops that are close together.

The gas money math that actually matters

At current mileage rates, an inefficient route does not just cost time, it eats directly into what you keep per shop. A route that is fifteen miles longer than it needed to be, at even a modest per mile cost, can wipe out the margin on a low paying stop entirely.

This is why the stops that look "not worth it" on paper often are not the problem. A $12 pharmacy shop is a bad job as a standalone errand and a perfectly good one when it is four minutes off a route you were already driving. The fee is not what makes a stop profitable. Its position is.

Where this gets hard to do manually

Everything above is doable with a notebook and a maps app for a three stop day. It stops being doable once you are running eight to ten stops with mixed time windows, several companies and a mix of report deadlines, and it stops being doable entirely when something changes at 11am and you need the whole order recomputed while sitting in a parking lot.

That is why route optimization exists as a category of tool rather than as a nice to have. The arithmetic is not hard. Doing it eight times a day, under time pressure, with the correct drive times, is.