The multi-asset dispatch test: five questions before you trust one board

If you rent one thing, dispatch software is a solved problem. The trouble starts the day you rent a second and a third. Roll-offs, portable toilets, fencing, equipment: each has its own rental clock, its own route, its own idea of what "done" means. Most tools were built for one of those and bolt the rest on later.

This is a test you can run in an afternoon against any tool you already use or any demo a vendor gives you. Five questions. Each one exposes a seam that a single-asset tool tends to paper over. You are not looking for a perfect score. You are looking for where the cracks are, so you know what a second spreadsheet is quietly costing you.

Why one asset type is easy and three is hard

A tool built for one asset type only has to model one story. A dumpster gets dropped, sits, and gets pulled. A service visit shows up, does the work, and leaves. Simple.

Multi-asset breaks that. A roll-off is on a site for a week. A porta-john is serviced every Friday for three months. A skid steer goes out Monday and comes back whenever the job ends. Same office, same drivers, three completely different clocks. A board that only understands one of them will force the other two into shapes that do not fit, and the mismatch leaks out as double entry, missed pickups, and assets nobody can find.

Question 1: Can one board show every asset type at once?

Open the schedule and look for today. Can you see the roll-offs, the toilets, and the equipment on the same screen, at the same time, without switching modes or filtering down to one type?

If every asset type lives on its own tab, you do not have one board. You have three boards in a trench coat. The dispatcher's real job, seeing that the same truck and the same driver are committed across asset types, is exactly the view those tabs hide.

Question 2: Does the schedule understand duration, not just a visit?

Book a two-week rental. Watch what the calendar does.

A visit-based tool drops a single dot on the day you scheduled it and forgets the asset exists until the next visit. A rental-aware tool holds the asset for the whole span, so it knows the unit is committed the entire two weeks, not just on drop-off day. That difference is the whole game for utilization. If the schedule cannot see that a unit is out, it cannot tell you what is free to rent tomorrow.

Question 3: What happens when an asset is out for two weeks?

Follow that same rental across its life. Can you answer, from the board alone:

• Which specific unit is on that site right now?
• When is it due back?
• Is it overdue, and does anyone get flagged if it is?

If the answer to "where is unit 214" is "let me call the driver," the asset is not really on the board. It was scheduled once and then fell off the edge of the system. That gap is where rented assets quietly go missing and where you keep buying units you already own.

Question 4: Can a driver run a mixed route without switching apps?

Look at it from the truck. A driver's day is rarely one asset type. It is a dumpster swap, then a toilet service, then an equipment pickup, in whatever order the map makes sense.

Hand the driver the app and ask: is that mixed day one clean list, in route order, or does the toilet service live in a different app than the roll-off swap? Every app switch is a place a stop gets skipped and a place the office loses visibility. A route is a route, no matter what is on the truck.

Question 5: When you add a new asset type, is it a setting or a rebuild?

This is the one that predicts your next three years. Ask the vendor to add an asset type you do not rent yet, live, on the call.

If it is a field you fill in, the tool was built for many asset types from the start. If it needs a new module, a services call, or a "that is on the roadmap," the tool was built for one type and everything else is an add-on. You will feel that every time your business changes, which for a growing operator is constantly.

How to run the test

You do not need a lab. Use a normal week:

1. Pick a real day that has at least two asset types on it.
2. Try to answer questions 1 through 4 using only the tool, no phone calls.
3. Save question 5 for the next vendor demo, and make them do it live.

Write down where you had to leave the tool to get an answer. Every one of those moments is a seam, and every seam is a spreadsheet, a text thread, or a phone call doing the job the software was supposed to do.

The honest takeaway

No tool passes all five perfectly, and a vendor who claims otherwise is selling. The point of the test is not a grade. It is a map of where your current setup makes you the integration layer, holding three systems together with your own attention.

Take these five questions to whatever you are evaluating next, including us. The seams do not lie, and once you can name them, you can decide which ones are worth paying to close.