When business in this market requires an initial fleet size review, procurement judgments should return to the current contract and specific vehicles. Historical orders and verbal responses serve only to identify what to check. Current release decisions must still be based on this order's records.
This guide breaks the initial fleet size review into three inputs: current workload, vehicle availability, and repair downtime. First examine the relationship between tasks and available vehicles, then identify which conditions remain estimates. Do not base a conclusion for the entire batch on unconfirmed data.
This article provides internal checking methods for local fleet procurement teams. The return, reinspection, and release actions described here do not replace regulatory judgment in the destination country. When statutory obligations are involved, current requirements must still be checked and input obtained from the responsible local party.
Base fleet sizing on workload and vehicles
When estimating initial fleet size, first consolidate current workload records, then use vehicle availability status to count the vehicles that can actually be deployed. Do not expand the fleet if the relationship between tasks and available vehicles does not add up. Exclude vehicles out of service for repairs from the available count. Address repair downtime individually; one conclusion cannot cover the entire batch.
List unconfirmed repair, staffing, or route conditions separately rather than presenting estimates as fixed demand. If the source, version, and subject of vehicle availability records are inconsistent, have the operations records administrator obtain evidence again before updating the estimate. Return records that cannot be located directly through this order's index for completion.
Fleet size review steps
| What to check | When you can proceed | When you must pause | Who is responsible |
|---|---|---|---|
| Current workload records | This order's index directly locates the current workload records | Identify and fix the scope of subjects affected by the current workload records | Fleet requirements lead |
| Vehicle availability | The source, version, and subject of the vehicle availability records are consistent | Have the responsible person obtain evidence again when vehicle availability cannot be verified | Operations records administrator |
| Repair downtime | Repair downtime records explain the boundaries between partial approval and the status of the entire batch | Address repair downtime individually; do not use one conclusion to cover the entire batch | Fleet requirements lead |
| Initial fleet size decision page | The initial fleet size decision page records the reasons for adoption and the effective time | Keep the initial fleet size decision page at its original status and notify the person taking over | Replenishment decision-maker |
Separate execution from approval when completing the table. The business lead proposes requirements, the executing role records results, and the decision-maker confirms subsequent arrangements using the same set of materials. Keep their views under the same order index. Each return must specify the missing input and who must provide it.
Keep only inquiry records when registration is involved
When checking vehicle registration or inspection status in Paraguay, start with the local DINATRAN official services portal. The page is only an inquiry starting point and does not approve the initial fleet size. Retain the original question, full response, and applicable period. If the responding party is unclear, keep the item pending verification and exclude it from the estimate.
How to Hand Off and Review the Initial Fleet Size Decision
The initial fleet size decision page records the reasons for adoption and the effective time. After vehicles return to service or workload or availability changes, first review whether the original fleet size is affected, then decide whether to adjust it. Retain the previous version when updating, document the reason for the change, and notify the role taking over.
Recalculate the next order using the workload and available vehicles at that time instead of reusing this batch's figures. The calculation approach and record fields can be reused across batches.
Final checks on fleet size before handoff
Limit this review to the same set of tasks and vehicles. Update the initial fleet size decision page only when the current workload records, vehicle availability, repair downtime, and initial fleet size decision page align. Start initial fleet sizing with the relationship between tasks and available vehicles. List unconfirmed repair, staffing, or route conditions separately rather than presenting estimates as fixed demand.
The initial fleet size decision page must clearly state the scope of the conclusion, unresolved fields, and the person taking over. The guidance set out here reflects Starvia's own approach to managing orders internally, and it is not intended to take the place of judgment exercised by local professionals.
FAQ
What if a supplier's template uses different fields from our form in a Paraguay project?
If field names differ but refer to the same content, first document the mapping in the comparison notes, then record the information using your fields. Return fields with different meanings or unclear sources to the original provider. A supplier template must not directly overwrite your records. Retain the version and date of each comparison.
In a Paraguay project, how can a dealer spot-check whether initial fleet size decision records are usable?
Check three items: whether workload records can be traced to this order, whether vehicle availability records include complete sources and dates, and whether vehicles out of service for repairs are listed separately. The records are usable only when all three align. If any item is missing, return them for completion so the next role does not continue estimating with unconfirmed information.
In a Paraguay project, why retain the original records after vehicles out of service for repairs return to use?
Return-to-service records must show when a vehicle was taken out of service, why, and when and in what condition it returned to use. This supports the decision to count it as available again. Without the original records, a later return-to-service explanation cannot be verified. Retain both the out-of-service and restored statuses and link them to the initial fleet size decision page.
Who is responsible for retaining communication records in a Paraguay project?
The operations records administrator retains original communications and materials, the fleet requirements lead retains the calculation approach, and the replenishment decision-maker retains the initial fleet size decision page. Each role keeps records only within its own scope. Verbal conclusions must be traceable to an original record row. Communications without a traceable source must not be included in the decision.
Regarding initial fleet size in a Paraguayan 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: Paraguay DINATRAN official services portal; Starvia procurement FAQ. This article provides order recordkeeping and communication methods for fleet procurement in Paraguay. 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.