Check the file before using its totals
A fleet report can arrive intact and still look different after a spreadsheet interprets its columns. Before using a download to compare vehicles or periods, confirm the file format, reporting scope and column definitions with the provider. Keep an untouched original and work on a separate review copy. A visible difference is a reason to investigate, not immediate proof that a vehicle record or tracking platform is wrong.
For a fleet management software evaluation in India, include the handover to your actual reporting team. Ask which report and export formats are available for the proposed deployment, then demonstrate the complete path from the approved report to the tool your team uses. This article checks that handover; the existing timestamp article remains the reference for measurement and receipt times.
Preview identifiers as text
Microsoft explains that Excel can remove initial zeros or reinterpret long numeric strings during import. If a column is an identifier rather than a quantity, inspect its type before loading it. Its support guidance describes importing through From Text/CSV and choosing text for relevant columns; the controls available depend on the Excel edition. Consult the linked instructions for your version rather than changing a whole computer’s settings for one file.
Fictional example: reference 0042 and reference 42 should not be assumed interchangeable. Ask how the export identifies a vehicle and compare the received value with the imported cell. A display format that adds zeros later does not establish what the original identifier was. Preserve the source reference and document any approved transformation instead of guessing which vehicle a changed value represents.
Write down the date order and time zone
A date such as 03/04/2026 is ambiguous without a declared date order. Confirm whether the column uses day-month-year, month-day-year or an explicit format, and check a sample with the provider. Identify the time zone and the reporting day’s start and end separately. Do not assume a downloaded file and an on-screen report use identical settings.
Samsara’s API documentation provides one vendor-specific example: its timestamp responses use UTC. That is not a description of SafarTrak exports. Fictional boundary example: 00:15 on 23 October in India at UTC+05:30 is 18:45 UTC on 22 October. Both labels describe the same instant, but their calendar dates differ. Agree the intended reporting boundary before counting rows by day; confirm the actual format in your own deployment.
Keep units and missing values visible
For every quantity, retain the unit and the meaning of the field. Ask whether a duration is seconds, minutes, hours or formatted text, and whether a distance is kilometres or another unit. In a fictional duration example, 1.5 hours means 90 minutes; the text 01:30 needs a declared hours-and-minutes interpretation before a comparison. Do not infer the unit from the size of the number.
Keep a missing observation distinct from a recorded zero. Ask how unavailable readings, unassigned references and incomplete periods appear in the export, and whether a spreadsheet filter removes them. Record any exclusions beside a total. The existing data-quality acceptance Guide covers missing and delayed evidence; this article does not change those definitions or provide a new algorithm for filling gaps.
Reconcile a small sample before the whole file
Choose approved demonstration records and compare the source report, untouched export and imported review copy side by side. Check one identifier, an unambiguous date, a midnight boundary where relevant, one duration and one missing value. Record the observed values and the explanation for any difference. Keep private driver details, customer locations and real operational files within the organisation’s controlled records.
Then compare the selected vehicle group, date range, row count and a defined total. Ask whether one row represents a trip, event, interval or vehicle summary, and whether later records can revise the file. A matching row count alone does not prove that every value was interpreted correctly. Preserve the filter and import choices so another reviewer can reproduce the comparison.
Bring an export-review brief to the demo
The blank worksheet below separates the intended task, source report, vehicle scope, date order, time zone, identifier type, units, missing-data treatment, import method and evidence owner. Complete it with the provider using non-sensitive sample records. Leave an unanswered field open rather than treating it as a supported feature or inventing a value.
Use the SafarTrak platform page to discuss which reports and records your team needs and how the proposed workflow can be demonstrated. Confirm formats and limitations for your actual setup. No CSV export, spreadsheet connector, API access, scheduled delivery or automatic reconciliation is promised here. The existing report-access article covers who should receive a file; this article focuses on preserving its meaning when it is opened.
Sources and further reading
Microsoft guidance explains spreadsheet import behaviour. Samsara documents its own API timestamp format; neither establishes SafarTrak export or integration capabilities. All examples below are fictional.
BRING IT TO YOUR FLEET
Start with your vehicles.
Ask the right questions.
Share your vehicle mix, existing devices and required signals with the SafarTrak team.
Discuss fleet software and report requirementsDiscuss your deployment
