Free AI tool · no signup

AI Route & Day Planner

Paste your day's jobs in any format, a spreadsheet dump, a WhatsApp list, rough notes with time windows, and get a clustered, sequenced dispatch plan per crew, with a ready Google Maps route link for each.

, optional; puts your company name, logo, and local pricing on the result

How it works

1

Paste the day's jobs, spreadsheet rows, notes, any format. Mention crews and time windows.

2

The AI extracts every stop, clusters by geography, and sequences each crew's day.

3

Get arrival-time tables, conflict flags, and a Google Maps route link per crew.

What this free AI route planner does, and what it doesn't

It turns a messy list of the day's jobs into a plan for each crew: which jobs go to which crew, in what order, at roughly what time, with a Google Maps directions link per crew. It reads the list the way a dispatcher would, so a spreadsheet paste, a WhatsApp message or rough notes all work.

It is a planner, not a navigation app. Drive times are estimates from the geography of your city, so the Maps link is where you check live traffic. It does not save routes, send them to your technicians or change during the day. You get three free runs a day, with no signup.

A worked example: two crews, six jobs

Take the sample on this page: two landscaping crews leaving the same shop, two mulch jobs, two sod installs, a sprinkler repair where the customer is only home from 8 to 10 am, and an estimate visit that can happen any time. Crew 1 has the mulch blower truck and crew 2 has the sod cutter.

The planner settles the hard constraints first. Equipment decides most of it: the mulch jobs go to crew 1 and the sod jobs to crew 2. Then the time window: the sprinkler repair has to start before 10 am, so it is pinned early on whichever crew can reach it in time. Only then does it sort by geography, putting nearby jobs together and dropping the flexible estimate visit where it costs the least driving.

Anything that does not fit the day is listed under conflicts with the reason, instead of being quietly dropped, and every assumption it made, such as a job's duration, is listed so you can correct it and run it again.

How to get a better plan

The plan is only as good as what you tell it. These details change the result most:

  • Where each crew starts, and when the day starts and ends
  • How long each job takes, even roughly ("~2 hrs")
  • Any time window the customer gave you
  • Equipment, vehicles or skills that only one crew has
  • Full street addresses with the city, one job per line

A free route planner vs route planning in dispatch software

A free planner is useful for planning one day. Once routes change during the day, the work moves into dispatch software:

This free plannerRoute planning in Fieldproxy
Where jobs come fromYou paste a listJobs are already on the map as they are booked
Drive timesEstimated from geographyCalculated on the road network
Changes during the dayRun it againThe day reshuffles when a job runs long or cancels
TechniciansYou send them the linkThe route is on their phone app
CustomersNot informedGet their arrival time
RulesTyped in each timeSkills, areas, time windows and SLAs set once

Signs you have outgrown a free route planner

  • You re-plan more than once a day because jobs move
  • Jobs need a particular skill or certification, not just the nearest crew
  • Customers keep calling to ask when the technician will arrive
  • You need proof of when each visit happened

You just trialed the dispatch_map + scheduler agent widget

One run here. Every job, inside Fieldproxy.

Here, you pasted a list and got one day's plan. Inside Fieldproxy, the dispatch board runs this continuously, on live drive times, all day.

  1. 1

    Jobs land with addresses already on the map, no pasting; the scheduler agent slots them as they arrive.

  2. 2

    Routes build on real road-network drive times, not estimates, and respect every window and skill constraint you've set.

  3. 3

    A tech runs long or a customer cancels, the rest of the day reshuffles itself and everyone's phone updates.

  4. 4

    Customers get live ETAs automatically, so fewer 'where's my tech' calls reach the office.

  5. 5

    Your dispatcher stops being a human traveling-salesman solver and starts managing exceptions.

dispatch_map + scheduler agent

See it embedded in your own workflow.

This page runs the widget once, on what you typed. The product runs it on every job, wired to your customers, price book, and techs, the result files itself and the next step kicks off automatically.

Frequently asked questions

How accurate are the drive times?

Sequences come from real geographic reasoning about your city; drive estimates are honest approximations. Each crew's Google Maps link gives you the live-traffic timing for the exact ordered route.

Can it handle constraints, time windows, equipment, crew skills?

Yes, say it in plain words ('customer only home 8-10', 'crew 1 has the mulch truck') and it pins those first, then optimizes geography around them. Anything that can't fit gets flagged, not silently dropped.

Is this the same AI as in Fieldproxy?

Same capability. Inside Fieldproxy, the dispatch board does this live on real drive-time data, jobs come in, the scheduler agent slots them, and reshuffles when a tech runs long or cancels.