What does the auto-filled report demo show?
It sets a paper trip log beside a log that a platform fills from records. You type a sample day of trips: places, times and distances. The tool builds the report from them and marks every field as filled by the platform or written by hand.
Then you say which fields your own log has and which sources you would have in place. The tool counts the entries that stay by hand and estimates the writing time you would save from the seconds you enter.
Everything is sample data. When a Tracom device sends position records to your tracking platform, the platform can build a report from them, and this page only shows the idea. It reads no device and shows no result from your own fleet.
Paper log or auto-filled log: what changes?
The log can hold the same fields in both cases. What changes is who writes each one and where the value comes from.
Paper log
Written by hand
- Who writes a field
- A person, one field at a time
- When
- Often at the end of the shift
- Who checks
- A supervisor reads and compares
Auto-filled log
Filled from records
- Who writes a field
- The platform where a source exists, a person for the rest
- When
- As the records arrive
- Who checks
- A supervisor still reads the report
Which fields can fill themselves?
The table gives the typical source of each field of a trip log. These are assumptions that the Tracom team can edit, not a list of what a given device does.
| Field | Written | Typical source | Without that source |
|---|---|---|---|
| Driver | Once a day | Sensor or ID reader | By hand |
| Vehicle | Once a day | Position records | By hand |
| Departure place | Every trip | Position records | By hand |
| Departure time | Every trip | Position records | By hand |
| Arrival place | Every trip | Position records | By hand |
| Arrival time | Every trip | Position records | By hand |
| Distance | Every trip | Position records | By hand |
| Break time | Once a day | Position records | By hand |
| Load carried | Once a day | Sensor or ID reader | By hand |
| Driving events | Once a day | Camera events | By hand |
| Purpose of the trip | Every trip | A person | Always by hand |
How does a record reach the report?
The path is short. The vehicle moves, the tracker records, the platform builds the report. Sensors and cameras add their own records, and a person writes what no record holds.
How is the time estimated?
The tool counts entries and multiplies. A day field is one entry. A trip field is one entry for every trip of the sample day.
A share of 60 % or more is read as most of the log, 30 % to 59 % as part of it, and below 30 % as little. These thresholds are typical and can be edited.
Worked example: a day of 4 trips
A vehicle makes 4 trips with 272 km and a full paper log of 11 fields. The figures are examples.
| Item | Value |
|---|---|
| Sample day | 4 trips, 272 km, 5 h 45 min of driving and 2 h 10 min between trips |
| Entries | 5 day fields + 6 trip fields × 4 trips = 29 entries |
| Position records only | 7 fields and 22 entries have a source, 76 % |
| Plus sensor or ID reader | 24 entries, 83 % |
| Plus camera events | 25 entries, 86 % |
| Time at 15 s per entry | 22 × 15 s = 5.5 min a day, × 22 days × 10 vehicles ÷ 60 = 20.2 h a month |
| Left by hand | 7 entries with position records only: 1.75 min a day |
The purpose of each trip stays by hand in every case, because no record holds it. Your own log, trips and seconds will give other numbers.
Mistakes to avoid when you compare paper and automatic
- Counting a field as filled before its source exists. A field that needs a sensor stays by hand until the sensor is installed and working.
- Using a best-case time. Time a few real entries with a stopwatch and enter your own seconds.
- Forgetting the review. A filled report still needs a person to read it.
- Comparing different forms. Use the fields your log really has, not a longer ideal one.
- Reading a demo as a result. This page shows the idea on sample data. It says nothing about your fleet.
Assumptions and limits
The demo knows nothing about any device. The source given to each field, the seconds per entry and the thresholds are typical values that you or the Tracom team can edit. The sample day is typed by you, so the totals show how the arithmetic works, not how your fleet runs. A real report depends on the devices fitted, the sensors installed, the platform settings and the quality of the records. Rules on trip logs and driver records differ by country, so check the current official text for your market.