When a Bolivian customer wants to compare demonstrator-vehicle records from tasks at different altitudes, each record must first explain what happened at the time. Instrument-panel photographs without direction, load, or en-route arrangements offer little support for a procurement decision. Records can help raise questions, but one trip alone cannot establish a conclusion about the vehicle.
The US Department of Energy's electric-vehicle overview discusses the relationship between driving conditions and real-world range. This article does not use that material to estimate range in Bolivia; it addresses only how customers should preserve the conditions of their own observations.
Treat a Complete Task as the Unit of Record
Before departure, record the task's start and end points, primary purpose, and whether it includes a return trip. Note detours, waiting stops, and driver changes separately so that different tasks are not later treated as repeat tests of the same route.
If altitude information comes from a map or device, preserve the tool's name and the location where the reading was taken. When reliable information is unavailable, state that it was not recorded rather than adding a figure based on assumptions about the city. If tools give different readings, retain the sources side by side instead of arbitrarily choosing a favorable figure.
Candidate identities can be checked in the Starvia Automotive vehicle catalog; a configuration name in the catalog does not mean it was verified on this route.
Preserve Essential Context Beside Each Data Point
Recorders should separate information shown directly by the vehicle from their own calculations. A photograph of the instrument panel's remaining-value display records only the value shown at that moment; it cannot be rewritten as a promise that a later task can be completed.
| Record point | Context to preserve | Question it can answer later |
|---|---|---|
| Departure preparation | Occupants, cargo, and vehicle settings | Whether the burden was similar on both tasks |
| Trip changes | Detours, waiting, and extra temporary tasks | Why the observations cannot be compared directly |
| Energy replenishment | Actual method and original supporting record | Whether start and end records are complete |
| Route-section observation | Road surface, direction, and visible weather | Whether another observation under the same conditions is needed |
| Abnormality | Original alert, location, and actions taken | Whether performance comparison should stop |
Conditions not covered by the table may be added as notes. Never guess speed, temperature, load, or altitude simply to fill the record; a missing field is itself information reviewers need to know.
Identify Differences That Cannot Be Attributed Before Comparing
If the uphill task carries passengers and cargo while the return task is empty, describe each purpose separately rather than attributing the entire difference to altitude. Driving style, route direction, and cabin power use also belong in the discussion.
Observers may identify factors requiring further verification, but "what was observed" and "why it happened" should occupy separate fields. Without diagnostic data, do not attribute a warning or consumption change to a particular component failure.
Any task involving a safety abnormality should first be referred to qualified personnel rather than continued simply to complete the data. Records from before and after repair should also be clearly distinguished because the object of comparison may have changed.
Use Only Explainable Records in the Procurement Meeting
Classify the material as having sufficient conditions, missing conditions, or unresolved safety issues. The first group may support discussion of suitability for the current task; incomplete records provide clues only; safety concerns must not be diluted with averages.
The customer can use this classification to decide what further observation is needed or adjust vehicle assignments. Do not combine records from different drivers, loads, and routes into one overall performance conclusion merely to create a unified ranking.
Retain original images, the name of the person completing the record, and reasons for revisions. Later corrections should show what changed, protecting customer data and preventing sales staff from misusing obsolete excerpts.
FAQ
Can instrument-panel photographs from only the start and end be compared?
First add the task context and energy changes. If they cannot be reconstructed, state that the record has limited uses.
What if there is no reliable altitude reading?
Retain the actual location and state that the altitude was not verified. Do not fill it in from experience.
Does a round trip on the same route have identical conditions?
Direction, load, driver, and stopping arrangements must also be considered; the route name alone is insufficient.
Can a favorable record be described as local range?
No. It reflects only observations of a specific vehicle under the recorded conditions and is not a general promise.
When organizing cross-altitude requirements, provide the original task sheet and candidate configuration through the Starvia Automotive contact page or WhatsApp to discuss specific documentation needs.
Information checked on: 2026-09-04. The Department of Energy material supports only basic electric-vehicle concepts; this article publishes no Bolivian road-test or range figures.