Prepare a task, not just a feature list
Choose one ordinary working day and one event that complicates it. Examples include a driver changing trucks, a dispatcher replacing a vehicle or the office investigating an unassigned movement. Write down who performs each task and what that person needs to see when it is finished.
Factor ELD is the provider of the product discussed here. The questions below are a practical meeting agenda, not an independent ranking of vendors. Ask other suppliers the same questions when comparing proposals.
- Bring truck and engine details, connector information and the phones or tablets you intend to use.
- Identify the driver, dispatcher and log-review roles that need access.
- Describe the current logging method and any records that must remain accessible during a transition.
- List optional tools you want discussed separately from the ELD workflow, such as tracking, IFTA reporting or cameras.
Ask to see the workflow from both sides
| Ask the presenter | Record the useful result |
|---|---|
| How does the driver select the correct truck? | The vehicle identifier shown, the connection check and the procedure for a wrong assignment |
| How does the driver review a log? | The date range, event details and steps that require the driver’s own review |
| What does the office see when a driver raises a record question? | The office role, relevant record and method of communicating the outcome |
| What happens during our chosen truck-change scenario? | Which steps were demonstrated and which require a test using the fleet’s equipment |
| How will a driver find help? | The support route, the details to provide and the procedure if the usual phone is unavailable |
The published Factor FRS manual describes driver logs and office review screens. Use documentation as a reference, then ask the presenter to identify the exact device, app and version in the proposal. A screen in a manual is not a demonstration of every current configuration.
Separate what was shown from what still needs proof
For each requirement, use one of three notes: shown in this demo, needs a vehicle test or awaiting a written answer. Add the equipment and app version used. Avoid a single “yes” column that treats a sales statement and an observed result as equivalent evidence.
For example, seeing a truck-selection screen answers an interface question. It does not settle whether the proposed cable works with every engine in a mixed fleet. That belongs in a representative vehicle test with an agreed pass condition.
Likewise, a demonstration of an optional camera or tracking tool does not establish that it is included in your ELD price. Ask for the hardware, subscriptions, installation responsibilities, support scope and any additional charges in the written offer. Verify current terms instead of copying a price from an old comparison.
End with a short action list
- Identify the configuration the team recommends and the configurations still unresolved.
- Assign a person and due date for each open product or commercial question.
- Agree which vehicle and driver tasks would be included in a pilot, if a pilot is the next step.
- Keep the observed results and the written proposal together so your decision can be reviewed later.
A supplier demonstration is a short evaluation meeting. A fleet rollout plan covers training, responsibilities and deployment across the business; it should not be squeezed into the demo checklist. Start with our registered-device guide for checks against the FMCSA list, or discuss a small-fleet setup with Factor ELD.
Demo-planning questions
Does a successful demo prove that the system works in every truck?
No. Record exactly what was shown and which equipment was used. Different engines, connections, mobile devices or work patterns may need separate acceptance checks before a wider rollout.
Should every possible feature be covered in the first meeting?
Prioritize the tasks that determine whether the proposed setup fits your fleet. Put less urgent options on a follow-up list so there is enough time to inspect the core driver and office workflow.