If operation record fields remain only in chat histories, people taking over later will struggle to determine what was observed at the time. Linking original materials, review comments, and handling results makes decisions for local orders easier to trace.
This guide divides operation record fields into four areas: vehicle identity, task start and end, driver and route, and issues and downtime. Records must let dispatchers see where a vehicle went, who used it, and whether any unresolved issues remain. A general status page alone is insufficient.
The evidence fields and stopping conditions listed here for operation records support order management and are our operational recommendations. Local legal, tax, registration, and technical requirements are governed by official information and professional advice valid at the time of publication.
Open records with destinations and users
Link each operation record to the vehicle identity fields first, then record task start and end details, the driver, and the route. If a record lacks the destination or user, dispatchers cannot dispatch a vehicle based on that row. List information unsupported by the vehicle identity fields separately and do not upgrade the status.
If a vehicle develops an issue or is taken out of service, document the observed condition, time, and sign-off role in the issue and out-of-service status fields. Keep it on hold if the status has no sign-off. If the same vehicle has multiple task segments on the same day, record them on separate rows by start and end time. Do not combine different routes into one record or put vague conclusions in the driver and route fields.
If a record's vehicle, time, or personnel do not match the actual vehicle situation, return it for additional information before proceeding. Do not fill it in based on speculation. Withdraw references to a task start and end record if it does not match the current subject.
Who records, pauses, or authorizes
| Subject requiring verification | Benchmark that must be satisfied to proceed | Scenario obliging a halt | Owning function |
|---|---|---|---|
| Vehicle identity fields | The actual holder completes the vehicle identity fields | List information unsupported by the vehicle identity fields separately | Fleet requirements lead |
| Task start and end records | The next role can independently verify task start and end records | Withdraw references when task start and end records do not match the current subject | Operations records administrator |
| Driver and route | Driver and route fields are not replaced with vague conclusions | Return driver and route matters to a role authorized to make the judgment | Fleet requirements lead |
| Issue and out-of-service status | Issue and out-of-service status is shared with all affected roles | Keep the hold in place if issue and out-of-service status has no sign-off | Replenishment decision-maker |
Use one row per vehicle when completing the table, updating the destination, user, and issue status together. The business lead proposes requirements, the executing role records results, and the decision-maker confirms subsequent arrangements using the same set of materials. No role may draw conclusions on behalf of another professional role.
When a status changes from pending verification to approved, it must be traceable to a document, reviewer, and date. An issue without sign-off is not automatically cleared when records are handed over.
Resolve Outstanding Issues Before Handing Off Records
At handoff, the actual holder completes the vehicle identity fields, and the next role independently reviews task start and end records. List the discovery time, affected scope, and receiving role for unresolved issues. Address the issues before releasing the vehicle, and identify on the handoff page who will continue each segment.
Keep original materials and review comments in the same record row instead of creating a vague new entry. If records differ from the supplier's account, first return the discrepancy to the provider for its basis and date, then decide which version to adopt.
Extract Only Verified Fields for Reviews and Quote Requests
When using operation records for a review or quote request, extract only fields that can be checked repeatedly, such as vehicle identity, task start and end details, and issue status. Keep case-specific notes and unsigned content in the original record. When one record is used for dispatch, statistics, or replenishment decisions, note each citation date separately. After an update in one place, update the versions of all other references as well.
Before reusing the record structure for the next batch, remove this order's customer personal information and temporary arrangements. Retain fields that can prevent similar gaps.
Final check of operation record fields
Limit this review to the same vehicle and time period. Update issue and out-of-service status only when vehicle identity fields, task start and end records, driver and route details, and issue and out-of-service status align. Operation records must let dispatchers see where the vehicle went, who used it, and whether unresolved issues remain. If fields are missing, suspend only the related statistics; do not guess the itinerary.
Issue and out-of-service status records must clearly state the scope of the conclusion, unresolved fields, and the person taking over. This recommendation for internal order management at Starvia does not substitute for the judgment of local professionals.
FAQ
Why should operation records have separate identifiers for each vehicle in a Colombia project?
Each record can belong to only one vehicle. Its destination, user, and issues must be linked to the vehicle identity fields to determine whether that vehicle can currently be dispatched. If multiple vehicles share an identifier or are combined into one record, issue and out-of-service statuses cannot be located. Split them into individual vehicle rows before continuing.
In a Colombia project, does access to an external webpage or supplier materials mean they apply to this order?
No. First check whether the materials' vehicle version and date match this order, then decide whether to cite them. Only fields with traceable sources that refer to the correct subject may enter the record. Return webpage or verbal information whose applicable subject is unclear for supplementation. Do not enter it in vehicle identity or task start and end rows.
In a Colombia project, which should be changed first when operation records and a supplier's conclusion disagree?
Change neither at first. Identify the differences in vehicle identity and task start and end fields, return them to the provider for each account's basis and date, then adopt a traceable version. Keep unresolved differences in the corresponding rows. Overwriting one version based on a majority opinion or a later-arriving version extends the conclusion beyond its support.
Which records are worth including in a review after a Colombia order is complete?
Include fields that can be checked repeatedly: vehicle identity, task periods, routes, issue types, and handling results. Keep case-specific notes, customer personal information, and unsigned statuses in the original order. Review conclusions should only improve the definitions of record fields for the next batch; they do not directly change the current order's release status.
For a second opinion on operation record fields in a Colombian order, submit the vehicle or order identifier, available materials, and questions requiring confirmation through the Starvia contact page or WhatsApp. Then use this article's checklist to review available vehicle sources and export documentation item by item. References: Colombia SIC consumer protection topic page; Starvia procurement FAQ. This article provides order recordkeeping and communication methods for fleet procurement in Colombia. It does not constitute local legal, tax, customs clearance, or technical conclusions, nor does it guarantee market entry, delivery timelines, warranties, selling prices, or business results. Materials checked on: 2026-09-07.