Skip to content
ProDispatch.
ProductFor ownersPricingResourcesAbout
Book a call

Free download / Vendor-neutral switching checklist

Before you switch dispatch tools: the checklist.

Most operators get burned by the same mistakes when they change dispatch software. Here is how you avoid them.

7 sections, printable59 checks1,292 words, start to finishFree with your email

Before the gate

What this is.

We wrote this because a tool switch tends to go wrong the same few ways: three days of job history lost, a driver at a site with no gate code, two weeks untangling invoices. The software was fine. The process was not. This list exists so you do not learn it the hard way.

Vendor-neutral, and useful no matter which tool you choose. ProDispatch published it because we want operators asking hard questions of every vendor, including us.

This is not a shipping-product pitch.

What is inside

The whole checklist, section by section.

7 sections, listed below with what each one holds. Every count on this page is read out of the document itself, so what you see here is what lands when you unlock it.

Contents7 sections / 59 checks / 1,292 words
01Before you start: what is actually in your current system?20 checks. Most operators underestimate how much data lives in their current tool until they try to leave.
02Export your data before you cancel7 checks. Do this while your account is still active.
03Questions to ask every vendor you evaluate17 checks. These questions separate tools built for multi-asset operators from tools that were built for one asset type and stretched to cover the rest.
04Run a parallel period4 checks. Do not cut over cold.
05Migration day checklist6 checks.
06What will actually bite youRecurring schedules.
07Five things that must be true before you commit5 checks.

Sample

Read a section before you decide.

This is section 4 of 7, reproduced from the checklist exactly as it appears in the document. Nothing in the box was rewritten for this page.

The rest is the same shape: 7 sections and about 1,292 words in total. If the box below is not worth an email address to you, the other sections will not change that, and that is a fair answer.

Section 4 of 7

Run a parallel period

Do not cut over cold. Run the old tool and the new tool in parallel for at least two weeks.

  • Pick a subset of jobs or one asset type to run through the new tool first
  • Verify that jobs entered in the new tool produce the correct output: the driver gets the right address, the customer gets notified if expected, completed jobs flow to billing
  • Confirm your drivers know what they are doing in the new field app before you go live
  • Check that accounting does not have a gap (old jobs in the old tool, new jobs in the new tool, nothing falling between)

Do not cancel your old tool until the parallel period is clean.

Reproduced from the checklist. The other 6 sections follow the same format.

You get your data out first

The full export list, run while your old account is still active, which is the mistake most operators make in the other order.

You get the vendor questions

Grouped by what actually breaks: asset types, the field app with no signal, customer comms, migration, accounting, support.

You get the traps in advance

Recurring schedules, gate codes, pending invoices, job photos, messaging numbers, auto-renewal. The six that bite on migration day.

Get the checklist.

Free, printable, yours to keep. The email is the whole ask: no truck count, no company name, nothing else is collected here.

Your address goes on the founding-operator list, which is how the founder reaches operators directly. Reply to any message to come off it. The checklist stays yours either way.

More free downloads

Five more, same deal.

Each one is a landing page like this: contents shown up front, one email, document unlocked. Take what applies to your yard.

The dead-zone auditMap every spot on your routes where the field app fails, in one afternoon, using nothing but your drivers and airplane mode.Read the page
The multi-asset operator workflow auditA one-page self-audit for operators running two or more asset types out of one business. See whether your dispatch setup is quietly costing you jobs, hours, and drivers.Read the page
The offline-first field app guideThe plain-English guide to what offline-first really means, why offline-tolerant is not the same thing, and the five-minute airplane-mode test to run on any app before you trust it.Read the page
What to charge: a pricing framework for multi-asset operatorsStop pricing off gut and the cheapest shop in the county. Build your number from your own costs, in an afternoon.Read the page
The customer-comms swipe fileThe texts and emails that stop the "where is my driver" calls. Copy, fill in the blanks, send.Read the page

No email required

Rather have a number now?

The tools run in the browser and show the result first, with no gate in front of it. Bring your truck count and ten honest minutes.

Cost calculatorRevenue leakIdle-asset utilizationWindshield timeOverlap checkerOperation scorecard
ProDispatch.Built in Texas.
hello@prodispatchapp.comLegal