August 29, 2026 · The Key Bot
27 Questions to Ask on a Traffic Control Software Demo
Vendor demos are choreographed to show strengths. These are the questions that surface the gaps — on rentals, daily tickets, offline use, seats, data ownership, and what happens when the crew is standing in a field with no signal.

Software demos are sales presentations, and good ones are built to be persuasive. That is not a criticism — it is the job. But it means the burden of finding out what the product cannot do sits entirely with you, and generic buyer advice ("look for good reporting") does not get there.
These are the questions that actually separate platforms for a traffic control company. Ask them on the call, and ask for the answer to be demonstrated rather than described.
Start by making them build your job
Before anything else, one request that is worth more than the rest combined.
"Can you build one of our real jobs right now — quote, dispatch, daily ticket, invoice — using our rate sheet and our device list?"
Bring a real one. A three-day utility closure, two crews, a mix of rented devices left on site and devices returned nightly, a customer who requires a signed ticket per day.
Almost every gap surfaces here. The rate sheet does not model your unit structure. Devices cannot be both inventory and rentable. The daily ticket cannot capture what your customer requires. The invoice cannot combine labour, equipment on rent, and a mobilisation charge. Each of those is a workaround you will live with for years, and each is invisible in a scripted demo.
Rentals and equipment
The area where general field service platforms most often fail this trade, because plumbing and HVAC software has no reason to model an asset that sits on a customer's site for six weeks.
Can a device be rented rather than consumed — billed by day, week, and month? Recurring rental billing is the commercial core of barricade work.
Can I see, right now, which devices are on which job site? Not a count of what left the yard — a location-by-location answer.
Can I assemble kits and dispatch them as one unit while keeping the individual device counts?
What happens when a device is damaged, lost, or stolen on a job? Is there a path from that event to a charge on the customer's invoice, or does someone email the office? See charging for damaged and lost devices.
Can I run more than one yard, with transfers between them? If you have two, this is not optional — multi-yard operations break single-location inventory models quickly.
Does the same record carry the bid quantity, the loaded quantity, and the returned quantity? That comparison is how you find out whether your takeoffs are light or your devices are walking.
Daily tickets, which are your money
The daily ticket is the document a payment dispute turns on. Treat this section as a commercial evaluation, not a features one.
Can the crew capture a customer signature in the field, and is it GPS-stamped and time-stamped?
Can the ticket carry photos, and how many before it becomes slow on a phone?
Can the ticket template be configured to what our customers actually require? Some primes specify their own format.
What happens to a ticket started with no signal and finished later? See offline, below.
If a customer disputes a ticket eleven months later, what can I produce, and is the signature image still attached? Preventing daily ticket disputes is largely a question of what evidence survives.
Does an approved ticket flow into an invoice without re-keying?
Offline, and the phone in the crew's pocket
The question that decides adoption, and the one demos are least equipped to answer honestly because the demo has good signal.
What exactly works with no connectivity? Ask for specifics: can they open the job, clock in, complete the ticket, capture a signature, take photos? "It syncs when you get back" is not the same as "it works offline."
What happens when two crew members edit the same job offline and both reconnect?
How large is the offline cache, and what happens on a phone that is nearly full?
Can I put this on a crew member's actual phone today? Then do it — outdoors, in sun, and let a real crew member try it rather than the project manager. Offline-first field apps covers why this is not an edge case in a trade that works rural corridors.
Money, asked precisely
Do not accept plan prices. Ask for your number.
What is the total monthly cost at our headcount — say six office and thirty-four field — including every seat?
Is there a cheaper field-only or mobile-only seat, and what does it not include? This is frequently the difference between covering the whole crew and rationing accounts.
What is the one-time implementation or setup fee, and precisely what does it cover — data migration, configuration, training, and how many hours of each?
Which of the features you just showed me are paid add-ons?
What are the payment processing rates for card and for ACH, and can I bring my own merchant account? At conventional rates this is often a larger annual number than the subscription itself.
What is the price on renewal? Ask directly whether the quoted rate is promotional.
Do some of this homework before the call, because it changes what you can push on. Vendors differ sharply in how much they publish. Jobber publishes its plan prices, the number of users included in each, additional users at $29 a month, and its payment processing rates, and Housecall Pro publishes plan prices along with per-additional-user rates that differ by plan. Others do not publish figures at all — ServiceTitan presents its tiers behind a "Request Pricing" button and describes a per-technician model, and FieldPulse describes a seat-based model with full-access and field-only seats without listing prices. Prices accessed August 29, 2026; check the source before relying on any figure.
Where pricing is published you can arrive with the arithmetic already done at your headcount. Where it is not, the demo is the pricing conversation, and you should ask for the quote in a comparable shape: base, seats included, marginal office seat, marginal field seat, setup, add-ons.
The full arithmetic is in total cost of ownership, and the structural question of per-seat versus flat-tier in per-user versus flat-tier pricing.
Accounting, permits, and the seams
What syncs with QuickBooks Online, in which direction, and what happens when an invoice is edited on either side? A one-way push creates a reconciliation task forever — see QuickBooks integration.
Can the job record carry the permit, its conditions, and its expiry? For companies working across municipalities, this is multi-jurisdiction permit tracking and it is a real constraint on dispatch.
Can it hold crew certifications with expiry dates, and warn before dispatching someone whose card has lapsed? In states with mandatory flagger certification, that is a compliance control rather than a nicety.
Can a customer see their own jobs and tickets without emailing us? Customer portals remove a surprising volume of phone calls.
Leaving, support, and the awkward ones
What can I export, in what format, and does it include signature images and ticket photos?
How long are records retained? If retention is shorter than your dispute window, the platform is deleting your evidence on schedule.
What is the notice period, and is month-to-month available?
Who answers support, in what hours, and what happens at 4 a.m. when a crew cannot clock in? Night and emergency work is normal in this trade; business-hours-only support is a real constraint.
Can I talk to a traffic control or barricade company using this today? Not a general field service reference — this trade. A vendor with none is not disqualified, but you should know it.
What are you worst at for a company like ours? The answer is diagnostic either way. A vendor who names a real limitation is more trustworthy than one who does not, and the limitation named is usually the one you were about to discover.
Then run a pilot anyway
No demo predicts adoption. Whatever the answers, put one real crew on real jobs for two weeks before committing the fleet — that is the whole subject of rolling out software to your crews.
Non-adoption is the expensive failure: you pay the subscription and keep the spreadsheet running underneath. A pilot costs two weeks and tells you what a hundred demo questions cannot.
If you want to run this list against us, our pricing is published without a sales call and the features page covers the rental, ticket, and inventory questions above. Ask the awkward ones anyway.
Frequently asked questions
What is the single most useful question to ask on a software demo?+
Ask the salesperson to build one of your real jobs, live, from quote to signed ticket to invoice, using your rate sheet and your device list. Almost every gap that matters shows up in that ten minutes, and no amount of feature-list review substitutes for it.
Why do field service demos look better than the product?+
Because demo data is clean, the network is good, the account has every module enabled, and the workflow shown is the one the product handles best. None of those conditions hold on your jobs, which is why the questions worth asking are the ones that change those conditions.
What should I ask about pricing on the call?+
Ask for the number at your actual headcount, not the plan price — base, seats included, marginal cost per office user and per field user, setup or implementation fee, payment processing rates, and which of the features just demonstrated are paid add-ons.
How do I test whether the field app is usable?+
Put it on a real crew member's actual phone, outdoors, and have them complete a ticket. Not the salesperson's device, not indoors, not the project manager. If it fails that test it will fail in the field, and a platform the crews do not use is the most expensive outcome available.
What should I ask about leaving?+
What exports, in what format, including signature images and ticket photos; how long records are retained; and what the notice period is. These are cheap questions before signing and expensive discoveries afterwards.