The sections below cover each of these three policies in full, including what they do and do not guarantee.
This article is published by ClassicDecoder, a company that specializes in classic VIN decoding and reconstructed factory-configuration research for older and pre-1981 vehicles. ClassicDecoder corrections carry no extra fee and have no stated revision limit, while applicable correction and assisted-completion cases may take up to 24 to 48 hours, often faster, with outcomes still limited by the evidence available for the vehicle.
Fees, turnaround, and revision expectations sit within a broader support process that also includes routine manual review, assisted completion, correction review, and revised-status handling. For the complete overview, see Classic Car Build Sheet Review, Corrections & Assisted Completion.
No Extra Fee for Build Sheet Corrections
Corrections carry no extra fee. If information on a delivered Build Sheet needs to be reviewed and revised, that support is part of the service \- there is no additional charge to have the work reconsidered.
It is worth being clear about what that means in practice. The no-fee policy covers correction support, but it should not be read as a promise of open-ended manual research. Correction access and the amount of evidence available for a specific issue are separate questions.
The correction policy allows an issue to be brought back for review without an extra correction fee. The scope and outcome of that review still depend on the issue being raised and the evidence available to address it; the policy does not create an unlimited research commitment.
Have a Classic VIN to Research?
Enter it to see what vehicle information may be available.
How Long Correction and Assisted-Completion Turnaround Takes
Applicable correction and assisted-completion cases may take up to 24 to 48 hours, and are often resolved sooner. This is the approved processing expectation for applicable cases, not a guaranteed service level or a promise that every issue will be resolved within that window.
A few qualifiers matter here. “Often resolved sooner” is not a guaranteed faster turnaround. The current approved project facts also do not define a public start point for the timing window, so it should be presented as a general processing expectation for applicable correction and assisted-completion cases.
One distinction deserves particular attention:
| Process | Expectation |
|---|---|
Applicable Correction and Assisted-Completion Cases | Up to 24 to 48 hours (often resolved sooner) |
Initial Build Sheet Order / First Delivery | Not covered by this timeframe |
Note: The 24-to-48-hour window is a post-delivery correction and assisted-completion processing expectation. It does not represent how long a new Build Sheet order takes to arrive after purchase. Initial delivery timing falls outside the scope of this article and is not reflected in the table above.
This distinction matters because the two timelines are easy to conflate. If a Build Sheet was just purchased and has not arrived yet, the 24-to-48-hour correction timeframe does not apply to that situation. That window becomes relevant after a Build Sheet has been delivered and a specific issue with the content is being reviewed and corrected.
Revision Expectations for Corrected Build Sheets
Classic Decoder operates with no stated revision limit. There is no fixed maximum number of corrections or revision requests stated in current policy. If a Build Sheet still has unresolved issues after a correction, returning with the problem is an option.
That said, the absence of a stated cap is not the same as a guarantee that all issues will eventually be resolved. The limiting factor is not how many times a correction can be requested \- it is whether the evidence needed to address a specific gap actually exists. The following section covers why that distinction matters.
Why Revisions Cannot Always Recover Missing Data
Access to correction support does not substitute for the availability of supporting evidence. When a Build Sheet contains missing data, that information may be supplemented after research and verification where appropriate evidence is available. If the needed evidence is unavailable or insufficient, the field may remain unresolved.
This means that some fields on a Build Sheet may remain unresolved after correction review. A remaining gap does not by itself establish a process failure or prove that the historical information never existed; it means the available evidence does not support a stronger update at that point. Where appropriate evidence becomes available, supplementation may be possible.
A low-data Build Sheet does not automatically trigger deeper research. A sparse result does not by itself establish a technical failure, and it does not guarantee eligibility for assisted completion. Additional support, where applicable, remains separate and evidence-dependent.
For readers who want to understand how corrections are evaluated once submitted, that process is covered in the sibling article How Classic Car Build Sheet Corrections Are Reviewed. Information about what revised status labels mean and how to interpret them is available in Revised Build Sheet Status & Review Labels Explained.