The specification sheet revision history must show what changed. Each time a new sheet arrives, record its revision number, date, and changes before deciding which version to adopt. Retain previous versions, and ensure the revision index links back to the originals so sales, procurement, and acceptance teams do not each use a different version.
The version-recording and change-checking methods in this article are our operational recommendations. They do not represent the procedures of Bolivia's customs or registration authorities. Follow current official instructions for specific declaration requirements.
Log the revision number and changes on a new version
Whenever a new specification sheet arrives, register it alongside the original. Enter the revision number, date, person proposing the revision, and changed fields in the revision index. Retain the previous original without overwriting or deleting it. For fields such as color, accessories, powertrain, or delivery contents, update only the affected portions. Unchanged items should continue to reference their existing supporting records.
If only the date or filename has changed and the content has not been checked, do not mark the new version as adopted. Identify the version's source and applicable vehicles before checking the changes.
When old and new versions conflict, record the differences using a revision index that allows retrieval of the originals. Do not choose a version based on verbal statements in a chat.
Who Records the Revision History and Signs Off on Adoption?
| Aspect Requiring Verification | Standard for Advancing | Circumstances That Halt Progress | Accountable Role |
|---|---|---|---|
| Specification sheet revision index | The index records the revision number, date, and applicable vehicles and links back to the original | Stop citing the version if its source is missing from the index | Vehicle documentation administrator |
| Change comparison record | The record lists the fields changed in each version and their before-and-after contents | Do not assess adoption until every difference is listed | Document reviewer |
| Adopted-version and excluded-item record | The record identifies the adopted version and items not included | Do not sign off on adoption until excluded items are listed | Vehicle documentation administrator |
| Release sign-off record | The sign-off scope matches the currently adopted version and identifies the applicable vehicles | Suspend the affected commitments if actual vehicle documentation differs from the adopted version | Order release approver |
Keep recording, review, and adoption separate. The vehicle documentation administrator maintains the revision index, the document reviewer checks the changes, and the order release approver signs off only on the currently adopted version.
Before confirming specifications with a customer, sales and order staff should review the currently adopted version together. If actual vehicle documentation differs from that version, create a discrepancy record and suspend the affected commitments. Do not overwrite old files to make the conflict disappear.
Make the Revision History Usable During Handovers
During subsequent handovers, use the revision index to retrieve the originals. Every role should find the same adopted version and the same revision history. That history must explain what changed, who proposed it, and when it was adopted. Return any incomplete entries for additional information instead of passing along assumptions as conclusions.
When checking Bolivia's current import requirements, you can start by opening the Bolivia Customs import services portal to verify the inquiry channel. Record the inquiry date and scope of the response.
Telling downstream teams a version changed
When the adopted version changes, first list the affected orders and roles, then update the adoption entry in the index accordingly. External communications should cite only the latest adopted version. When withdrawing statements based on an older version, record the reason and date.
Keep specification sheet revision histories in separate files for each order. The next inquiry batch may reuse the checking criteria and record fields, but not the conclusions about which version was adopted for this batch's vehicles. Start the final recheck with the revision index. Close the order only when the revision number, date, changes, and adoption record all correspond within the same index.
FAQ
For a Bolivia order, should we keep the old specification sheet after a new one arrives?
Yes. Move the old version into the historical section of the revision index without deleting or overwriting it. After recording the new version's revision number, date, and changes, retain both versions side by side so the originals can be retrieved through the index for later checks.
For a Bolivia order, does a specification sheet with only a changed filename count as a new version?
It does not count as an adopted new version. First check whether the content changed. Until that check is complete, retain the existing status and mark it as pending review. A change to the date or filename alone does not justify marking a new version as adopted.
For a Bolivia order, whose version should we use if sales and procurement receive different sheets?
Return to the revision index to find the currently adopted version. Identify whose copy matches the adoption record, then update the other team's materials. If neither version can be traced to its original, return them to the party that supplied them to clarify the revision numbers and dates.
What should we do if the actual vehicle configuration does not match the adopted version?
First suspend the affected commitments, record the differences, and check the actual vehicle documentation and the source of the adopted version. Update the adoption record after determining which version is supported by evidence. Do not overwrite old files to remove the conflict. If the discrepancy affects delivery contents, first tell sales and order staff to stop making the affected external commitments. Resume them only after the check results are entered in the revision index.
If a Bolivian order turns on the specification sheet revision history, submit the vehicle or order identifier, available materials, and questions through the Starvia contact page or WhatsApp. Then use this article's table to review the available vehicle supply and export documentation item by item. Sources: Bolivia Customs vehicle import guidance; Starvia procurement FAQ. This article provides order-recording and communication methods for vehicle documentation in Bolivia. It does not constitute local legal, tax, customs clearance, or technical conclusions, nor does it guarantee market access, delivery times, warranty coverage, selling prices, or business results. Information checked on: 2026-09-07.