Fleet Equipment Demonstration Plan

Before a fleet-equipment demonstration, agree which purchase question the session must answer, which configuration and conditions represent the intended work, what the site and operator must have ready, and how observations will be accepted. A completed demonstration supports only the tasks and conditions actually observed. It does not, by itself, establish year-round suitability, annual savings or approval to buy.

This use case helps a fleet evaluator and equipment dealer answer: what evidence must this demonstration produce before we can advance our equipment decision? The output is a demonstration plan and a result record that preserve both successful observations and unanswered questions.

Start with the decision that remains unresolved

A demonstration becomes useful after the buyer has identified a real application. The equipment-dealer prospecting workflow covers whether a fleet has a replacement or expansion project. Here, the business has requested an evaluation of equipment for a stated job; the purchase remains undecided.

Separate three statements in the plan:

Observed fact: the offered specification, existing work record or site document, with its source and date.
Fit hypothesis: the equipment may perform a defined part of the buyer's work. State which uncertainty the demonstration can address.
Confirmed evaluation request: the buyer has asked for a particular demonstration and named the people who will review it. This establishes permission to plan that evaluation, not a purchase order.

Replace “show us the truck” with a bounded question. For example: can the offered configuration complete the buyer's agreed sample assignment and return within its stated availability window under the documented conditions? A separate question might concern whether the proposed replenishment arrangement fits the time available between assignments.

Keep those questions separate. A successful route observation does not answer a charging question that was never tested. A short operator familiarization session may be worthwhile, but should not be relabeled a representative duty-cycle evaluation.

Match the demonstration configuration to the proposed purchase

Record the demonstration unit's identifier and the offered configuration revision. List differences that could affect the question being evaluated: vehicle dimensions, powertrain or battery option, installed body or attachment, trailer pairing, and other application-specific specifications identified by the technical reviewer. Distinguish equipment actually fitted from equipment described in a sales proposal.

Freightliner's eCascadia specifications list different drive-axle and battery configurations and state that range varies with configuration, load, driver behavior and environmental conditions. The practical implication for an evaluator is to preserve the configuration and conditions behind a result. A model-family name is insufficient to transfer a result to another offered version.

The public eCascadia Driver's Manual, foreword also explains that its information does not apply to every vehicle and directs readers to the vehicle's specification information. That public edition is dated November 1, 2022; obtain the applicable current documentation for the actual unit through the manufacturer or dealer before an operational demonstration.

Classify each difference before the session:

Matches the intended configuration: retain the supporting specification reference.
Different, but irrelevant to a named observation: have the responsible reviewer explain why that particular observation remains useful.
Different and material: restrict the conclusion or arrange a representative unit.
Unknown: assign confirmation and hold the conclusion that depends on it.

An evaluator might accept an observation about a control layout while leaving range, payload or site compatibility unresolved. This is a narrower result than accepting the entire model. Do not silently average away configuration differences when comparing two demonstrations.

Establish site readiness and the permitted scope

Have the dealer's competent technical/operator representative and the buyer's site owner review the proposed activity before it is scheduled. The evaluation sheet should reference their accepted plan and applicable instructions; it should not attempt to replace them.

Confirm the actual location and route or work area, access arrangements, authorized operator, relevant familiarization, equipment availability, and the site resources required for the agreed scope. For a battery-electric truck, the relevant technical and facility reviewers must address any charging equipment and arrangement proposed for the session. Record who has confirmed each prerequisite and what remains pending.

Define the allowed activity, exclusions and authority to stop or revise it. Include the person responsible for handling an unexpected condition under the approved site and manufacturer procedures. An observer's desire to collect another data point must not expand the permitted operation. This article supplies no driving, loading, charging or maintenance procedure.

Use a prerequisite status with a practical consequence:

Ready: the responsible reviewer has accepted the prerequisite for this session.
Ready for a reduced scope: the revised plan expressly excludes the unavailable activity, and the resulting evidence limitation is recorded.
Not ready: the affected demonstration does not proceed until its prerequisite is resolved.

For example, a buyer's charging arrangement may be unavailable while another separately approved observation can proceed. Record charging as not observed, without treating the alternative session as a test of that arrangement. A demonstration at a dealer's facility also does not establish that the buyer's site is ready.

If the unit needs a separate technical assessment or service task before evaluation, use the equipment-service requirements sheet to scope that work. A demonstration approval is not an authorization for unspecified repairs.

Write the observation and acceptance rule before seeing the result

For each purchase question, record five things: the requirement, the observable event, the measurement source, the acceptable evidence and the reviewer. Use criteria supplied by the buyer and accepted by the responsible technical reviewers. There is no universal demonstration duration, minimum sample or performance threshold that suits every fleet.

For an assignment-time question, define the start and finish events and record all time within that interval. If waiting, loading or a detour occurs, preserve it as context rather than quietly removing inconvenient minutes. State whether the source is an observer's timestamp, an existing permitted trip record or another agreed method. Synchronize the time references used for comparison and retain their timezone.

For a resource-use question, identify what is measured and where. A vehicle display, a charger record and an electricity bill need not describe the same measurement boundary or interval. Record units, timestamps and source limitations. Do not convert an undocumented display change into a precise energy-cost claim.

Distinguish an observed result from a forecast. Volvo Trucks describes its Electric Performance Generator as a route simulation using terrain, ambient temperature and traffic information with the selected truck configuration and battery capacity. Such a modeled result can inform the evaluation questions, but it remains a model output; label it separately from measurements collected during the demonstration.

Choose an outcome for each question:

Supported within the observed scope: the pre-agreed evidence was obtained and met the stated criterion for that session.
Not supported in this session: a valid observation did not meet the criterion; record the condition and reviewer response.
Inconclusive: missing or unreliable evidence prevents the comparison.
Not observed: the activity or condition was outside the completed scope.

Keep “not observed” separate from failure. Equally, do not turn several favorable observations into a pass for an unanswered requirement. The person accepting the evidence should identify what decision it permits next: specification refinement, another evaluation, a commercial comparison or a purchase review.

Worked example: one usable result and two unresolved decisions

Fictional teaching example. The fleet, equipment labels, requirements, timestamps and observations below are invented. They describe no real manufacturer's performance, customer trial or operating recommendation.

Example Fleet is considering a battery-electric tractor for a recurring assignment. Its buyer asks for three findings: whether a sample assignment fits an agreed 150-minute availability window, whether the proposed charging arrangement fits the between-assignment window, and whether the evaluation supports the configuration in the purchase proposal.

The demonstration uses unit D-1 with battery configuration A. The proposal currently lists configuration B. The technical reviewer records that the difference prevents a range or energy-use conclusion about B. The fleet nevertheless wants a bounded observation of the assignment sequence using A. The site and operator representatives approve that reduced scope through their own process; this example does not prescribe how they operate the unit.

Before the session, the parties agree that the timing interval begins at release for the sample assignment and ends at return to the agreed location. It includes all waiting within that interval. They also agree to preserve the recorded route, load description, conditions and any deviations. The 150-minute window is this fictional buyer's business requirement, not a recommended operating limit.

The saved result record contains:

Timing: release at 10:05 and return at 12:17, on the same day and timezone, give 132 elapsed minutes. The record separately identifies 17 minutes waiting, included in the 132 minutes. The sample met the fictional 150-minute window by 18 minutes under those recorded conditions.
Replenishment: the buyer's proposed charging arrangement was unavailable and had been excluded from the reduced session. Result: not observed. No recharge-duration or between-assignment-readiness conclusion is accepted.
Configuration: D-1 used A; the proposal remains B. Result: configuration-specific performance unresolved for B. The evaluator does not transfer A's demonstration result to B.

The accepted conclusion is: “The documented sample assignment using D-1 was completed within this session's timing criterion. Evidence does not yet establish replenishment readiness or performance of the proposed B configuration.”

The buyer may advance the observed workflow to its next review while holding those two dependent conclusions. The dealer owns confirmation of a representative configuration; the facility reviewer owns readiness for the proposed charging observation. The next evaluation is scheduled only after the required prerequisites are resolved.

Do not calculate annual savings by multiplying the 18-minute difference by a year of assignments. That figure is unused time within a fictional availability window, not a measured improvement over an existing vehicle. The session supplies no matched cost baseline, annual operating distribution or long-term service evidence. A purchase review needs those separate inputs if they matter to the decision.

Copy this demonstration plan and result worksheet

Use one observation section per decision question. Short lines keep the record usable on a phone or in an existing shared document.

DEMONSTRATION BASELINE
Plan reference / revision / date:
Buyer / application / evaluation request:
Purchase question / decision currently held:
Proposed configuration / evidence reference:
Demo unit / actual configuration / evidence:
Material differences / technical reviewer:
Site or route / approved scope reference:
Operator / site owner / prerequisites:
Ready / reduced scope / not ready:
Allowed activities / exclusions:
Stop or scope-change authority:

OBSERVATION — repeat for each question
Buyer requirement / units / criterion:
Observable event / start and finish:
Evidence source / method / timezone:
Conditions to record / known limits:
Actual result / timestamps / reference:
Deviation / missing evidence / consequence:
Supported / not supported / inconclusive:
Not observed, if outside completed scope:
Acceptance reviewer / date / reasons:
Conclusion allowed / conclusion still held:

FOLLOW-UP
Open question / responsible person:
Required evidence / prerequisite:
Next decision / review date or trigger:
Purchase approval status, separately:

Before accepting the record, check that the physical configuration is identified, prerequisites were reviewed, the recorded activity stayed within scope, measurements retain their units and interval, and every material unknown has an owner. Preserve the original result if later evidence changes the conclusion; add the revised decision and its reason.

A favorable demonstration may lead to several separate commercial reviews. Maintenance offers can be compared using the fleet-service proposal guide. Equipment offered in trade needs its own identity and title evidence. Neither is resolved by a successful demonstration.

Frequently asked questions

Must the demonstration reproduce the entire duty cycle?

It must represent the conditions needed to answer its stated question. A limited session may support a particular workflow observation while leaving other routes, loads, weather or shifts unassessed. Identify the missing conditions and have the responsible evaluator decide what further evidence is needed before a broader conclusion.

Can a demonstration unit differ from the purchase configuration?

Yes, if the differences and resulting limits are explicit. Some observations may remain useful; others may not transfer. Have the technical reviewer identify which conclusions depend on the differing specification. Do not call a demonstration representative merely because both units share a model name.

What if a site prerequisite is missing on demonstration day?

Hold the affected activity or have the responsible parties approve a genuinely reduced scope. Record the missing prerequisite and the excluded observation. An alternative location or resource answers a different site question unless the reviewer establishes why its evidence applies.

Does completing the route prove the truck has enough range?

It establishes completion only for the documented configuration and session conditions. Preserve the evidence needed for that observation, and refer broader suitability to the responsible evaluator. One trip cannot by itself establish every intended load, season, contingency or operating pattern.

How should an inconclusive observation be handled?

Record exactly why it is inconclusive: missing timestamps, an unconfirmed configuration, a changed assignment or another named issue. Keep any valid partial evidence. Assign the smallest follow-up capable of resolving the decision, with prerequisites and ownership, instead of treating missing evidence as either success or failure.

Is accepting the demonstration record the same as approving purchase?

No. Accepting the record means the reviewer agrees with its observations, interpretation and limits. Specification approval, service support, commercial terms and purchasing authority remain part of the buyer's own decision process. State which next step the evidence supports and what remains unresolved.

Resolve the purchase question before booking the session

Take the proposed demonstration and write the one question whose answer could change the equipment decision. Confirm the necessary configuration, prerequisites, evidence and reviewer. If the session cannot answer it, narrow the promised result or change the evaluation plan before calling it an acceptance test.

By John Hauler, USDOTData's editorial persona. Primary sources reviewed October 16, 2026. The worksheet, decision method and fictional example are independent editorial analysis, not manufacturer operating instructions or a performance guarantee.

Fleet Equipment Demonstrations: Plan the Acceptance Evidence