How Heat Maps Can Improve Process Serving Routes (and When a Pin Map Is Enough)
Article version in Mike's voice for Process Server Daily.
When you're serving 30 or 40 papers in a day, the route is the job. Every wasted mile is a serve you didn't get to.
I built my process serving company in Redding, up in Northern California, and I know how fast a day falls apart when you drive across the county twice. Heat maps are one tool people talk about for fixing that. They can help. They can also be a lot of work for very little payoff, depending on how many jobs you run.
Here's how I'd think about them. I'm not an attorney, and this isn't legal advice. This is about running your day.
What a heat map actually is
A heat map takes a pile of points on a map and shows where they bunch up. Tableau calls this a density map. It groups overlapping marks and colors them by how many are in the group. Esri, the company behind ArcGIS, describes its heat map as a smooth surface of relative density, from cool where points are sparse to hot where they're packed together.
For a process server, the points can be whatever you track:
Addresses of jobs you were given
Addresses where an attempt succeeded
Addresses where you made three attempts and still came up empty
Where your rush jobs come from
Red is busy and blue or green is quiet. The map is only as good as the question you ask it. "Where do my jobs come from?" is one map. "Where do my failed attempts pile up?" is a different map, and usually a more useful one.
Where a heat map helps
It shows you your real territory. You may think you work the whole county. A map of last year's jobs might show that most of your work sits in three zip codes. That tells you where to base yourself, where to buy lunch and where another server could cover the edges for you.
It helps you group serves. If six jobs landed in one neighborhood, do them in one trip. That sounds obvious, but when jobs come in one at a time across a week, nobody sees the cluster until it's on a map.
It shows you where attempts fail. A cluster of hard addresses can mean gated communities, apartment buildings with locked entries or a part of town where nobody opens the door. Knowing that ahead of time changes when you go and what you bring.
It helps with dispatch. If you run more than one server, a map shows who is closest to a new job and where one server is carrying too much while another sits idle.
The map doesn't tell you when to go
A heat map tells you where. It doesn't tell you when, and timing is half the battle.
DreamBuilt Software, which makes process serving software, suggests that for a residential address you assume the people work nine to five on weekdays and are home on weekends. Its advice is a first attempt at 7 PM or later, then a weekend morning if that fails. It also says to adjust if your client tells you the person works second or third shift.
Proofser's guide says there's no universal best time, and that three attempts at 1:50, 2:05 and 2:20 PM are technically different times but test almost the same window. Real variety means a morning, an evening and a weekend, when that's lawful, safe and appropriate. Check your own state's rules, including any limits on Sunday service.
That's where my stalking method comes in. I know the word isn't great. Before I left the office, I wanted to know: Do they work? What time do they work? What kind of car do they drive? And do you have a picture of them? A map shows you the neighborhood. That kind of homework tells you when somebody will be standing in the doorway.
The best setup uses both. The map groups your stops. The homework picks the hour.
How to make one without spending a fortune
You don't need a big system to start. Here's the simple path.
Pull your data. Export your jobs with the address, the date, the time of each attempt and the result. If you've been tracking this in a spreadsheet, you're already halfway there.
Turn addresses into coordinates. A map tool needs latitude and longitude, or at least addresses it can recognize. Tableau says a density map works best when location data is precise.
Pick one question. Don't map everything on day one. Start with failed attempts or with where jobs cluster.
Look at it, then change one thing. Move your route, change your attempt times or shift which server covers which area. Then check again next month.
A few tools people use:
Tableau. Choose the Density mark type on a map of latitude and longitude. Tableau recalculates the density as you zoom or filter. It's a good fit if you like dashboards.
ArcGIS Pro. It has heat map symbology for point layers. Esri's own documentation says a heat map works best with a large number of points that overlap, and that sparse points are better drawn with an aggregation method. Its Density toolset needs the Spatial Analyst license. This is heavy software meant for GIS pros and probably more than a solo server needs.
deck.gl on top of Google Maps. If someone is building a custom tool, note that Google's own Heatmap Layer was deprecated in May 2025 and was decommissioned in the May 20, 2026 release of the Maps JavaScript API. Google points developers to the deck.gl HeatmapLayer as a replacement. Older articles that tell you to use Google Maps Platform's heat map layer are out of date.
Be honest about your size
This is where I'd push back on the hype. Both Tableau and Esri say heat maps work best with a lot of overlapping points. If you do 40 jobs a month, a heat map is mostly a colored blob. A plain map with a pin for each job will show you the same clusters, and you can build it in an afternoon.
If you do hundreds or thousands of jobs a year, or you dispatch to several servers, a density view starts to earn its keep. Pick the tool that fits the volume you have.
Watch your data
A map made from bad data lies to you. If addresses were typed wrong, if attempts were logged an hour after the fact or if a bad geocode drops a pin in the wrong town, your red zone could be a mistake.
Also remember what's on that map. These are people's home addresses tied to legal papers. Keep the file on a device you control, don't paste screenshots into public places and don't share it with people who don't need it. Keep your records the way you would keep a file for a court. I took a date and time stamped photograph of every single posting when I served eviction notices, because your records are what you stand on if anyone questions your work.
Don't let the map replace showing up
I once had a guy at a gas station in Redding throw the packet back at me, and it cut my head. The city police cited me for trespass. I didn't show up to the court date. Years later, a Shasta County bench warrant turned up when a permit application came back.
No map would have saved me from that. If you get a court date, you show up. Software can plan your day. It can't do your job or keep your record clean.
An attorney once told me a server has "one job, serve the paper, and that's it. Sign the proof of service, maybe, right? And communicate status." Routes, maps and tools all exist to do that one job better.
Where Mighty Process Server fits
I'll be straight about this one. Mighty Process Server doesn't list a heat map as a feature today, and GPS verified attempts and routing are coming with the app, not live yet. I won't tell you otherwise.
What's live today helps with the work around the route. You can create a job, upload the documents, and the AI fills in case details like case numbers, court details, servee names and addresses from the PDFs. You check what it pulled and assign a server. Clean address data going in makes any map you build later more trustworthy. The Affidavit Generator handles the paperwork when you're done.
Premium is $97 a month and adds the Dispatch Board, the open Bid Board and customers and accounting. Enterprise is $247 a month and adds Auto Dispatch. You can also sign up for a free Mighty Process Server account and get up to 25 free jobs every month. You never have to upgrade to a paid plan.
Want to talk through it? You can book a call here: https://mightyautomation.com/book/mps
Be safe out there.
A short checklist
Decide what question you want the map to answer.
Clean up your addresses and log every attempt with a date and time.
Start with a pin map. Move to a heat map when your volume is high enough that the pins overlap.
Group nearby jobs, then pick the hour for each one based on what you know about the person.
Vary your attempt times in a way that actually tests different windows.
Protect the data, because it's full of home addresses.
FAQ
What is a heat map in process serving?
It's a map that uses color to show where your points, such as jobs or failed attempts, are concentrated. Hot colors mean many points close together and cool colors mean few.
Do I need a heat map to route my serves?
No. If you have a small number of jobs, a pin map shows the same clusters. Tableau and Esri both say heat maps work best with many overlapping points.
Can Google Maps still make a heat map?
Not with its old Heatmap Layer. Google decommissioned it in the May 20, 2026 release of the Maps JavaScript API and recommends the deck.gl HeatmapLayer.
What's the best time of day to serve someone at home?
There's no universal answer. One software vendor suggests 7 PM or later for a first attempt on a residence, then a weekend morning. Another says it depends on the person's schedule, the location and what you've already tried. Follow your state's rules.
Does Mighty Process Server have a heat map?
Not today. GPS verified attempts and routing are coming with the app.
Sources
Tableau Help, "Maps that Show Density or Trends": https://help.tableau.com/current/pro/desktop/en-us/maps_howto_heatmap.htm
Tableau, "The Density Mark type brings a new kind of heatmap to Tableau": https://www.tableau.com/blog/density-mark-type-brings-new-kind-heatmap-tableau-98488
Esri, "Heat map symbology," ArcGIS Pro documentation: https://doc.esri.com/en/arcgis-pro/latest/help/mapping/layer-properties/heat-map.html
Esri Support, "How to create heat maps in ArcGIS Pro using the Density toolset": https://support.esri.com/en-us/knowledge-base/how-to-create-heat-maps-in-arcgis-pro-using-the-density-000021710
Google Maps Platform, Deprecations (Heatmap Layer unavailable as of May 2026): https://developers.google.com/maps/deprecations
Google Maps JavaScript API Release Notes, version 3.65.1c, May 20, 2026: https://developers.google.com/maps/documentation/javascript/releases
deck.gl, HeatmapLayer: https://deck.gl/docs/api-reference/aggregation-layers/heatmap-layer
DreamBuilt Software, "The Best Time of Day to Serve": https://www.dbsinfo.com/Articles/The-Best-Time-Of-Day-To-Serve
Proofser, "How Attempt Timing Affects Process Serving Due Diligence": https://proofser.com/learning-center/process-serving-attempt-timing/
Mighty Process Server, pricing and FAQs: https://mightyprocessserver.com/pricing-plan
Stay sharp. Stay informed. Live Mighty!
Read the full article at www.mightyprocessserver.com
This article is published by Process Server Daily, powered by MightyAutomation.ai, the leader in legal support intelligence.
