This article covers four aspects of post-generation support: what routine verification covers and how it differs from deeper research, when assisted completion applies and what it can offer, how the correction and revision policy works including fees and timing, and what to expect from future evidence-status labels on your Build Sheet. Each of these topics has a dedicated section below, with deeper operational details available in the linked child articles.
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. Its Classic Decoder Build Sheet is a reconstructed research product, and this guide explains the current review, correction, assisted-completion, and revision policies that apply when a report needs additional attention.
These support processes sit within the broader Classic Decoder Build Sheet workflow. For the overall explanation of what the product is, how factory-configuration research works, and what the reconstructed Build Sheet can and cannot establish, see Classic Car Build Sheet.
What Routine Manual Verification Actually Covers
Routine manual verification is the baseline review every Classic Decoder order receives. At this stage, the completed Build Sheet is checked for errors, such as inconsistencies or obvious data problems, before it reaches you. This review is a standard part of the process, applied across all orders.
What routine verification does not do is independently authenticate each field by consulting original manufacturer records, cross-referencing multiple archival sources, or conducting a historical investigation. Those are categorically different activities. Understanding this distinction matters because the word “manual” can easily be read as more comprehensive than it actually is.
Deeper manual research is a separate process, distinct in purpose and scope from the error-check layer. It is not automatic, and it should not be assumed to occur on every order. These two processes serve different functions and should not be treated as interchangeable.
Have a Classic VIN to Research?
Enter it to see what vehicle information may be available.
Routine Verification vs. Deeper Research at a Glance
The contrast below captures the key differences between these two process types.
Routine Manual Verification
Applied to every Classic Decoder order- Covers error-checking of the completed Build Sheet
- Does not constitute independent authentication of individual fields
- Does not include comprehensive historical investigation of sources
Deeper Manual Research
- A distinct process, separate from routine verification
- Not automatic and not included as a standard component of every order
- Not triggered simply because a Build Sheet was delivered
- Not activated by sparse data alone
The practical implication is straightforward: receiving a Build Sheet, including one with complete data, does not mean every field has been independently authenticated through historical research. Routine verification is the error-check layer. Deeper research is something different. For more on how the review and deeper research process works, see How Classic Car Build Sheet Review & Assisted Completion Works.
When Assisted Completion Applies and What It Can Offer
Assisted completion is additional support that may be used in applicable cases where further research and verification can supplement Build Sheet information. The key word is “may.” Whether missing data can be added to your Build Sheet depends on whether supporting evidence is available. Assisted completion is not a guaranteed service, and it does not activate automatically.
When a Build Sheet has gaps, those fields may be supplemented where evidence permits. If appropriate evidence exists, the missing information can potentially be added through a subsequent review. If evidence is not available, the gap remains. The process is conditional on what the historical record supports, not on how much you want the information or how many times a revision is requested.
Owner-supplied information is one type of input that can feed the correction process. If you have documentation or records that speak to your vehicle’s original configuration, that information can be submitted as part of a correction. How owner-supplied information is handled and evaluated is covered in detail in the child article on corrections.
Note on sparse or low-data Build Sheets: A Build Sheet that returns limited information can reflect limits in the available historical evidence rather than a technical failure. A low-data report does not automatically trigger deeper manual research or assisted completion. It reflects what the available evidence supports for that vehicle.
For submission steps and a fuller explanation of how owner-supplied information is handled, see How Classic Car Build Sheet Corrections Are Reviewed.
Correction and Revision Policy — Fees and Turnaround Times
Corrections to your Classic Decoder Build Sheet carry no extra fee. There is no stated revision limit. These are current correction-policy terms and do not imply unlimited manual research or guaranteed successful revisions.
For applicable correction and assistance cases, turnaround is up to 24 to 48 hours, often faster. This window covers corrections and assisted-completion reviews, not the initial delivery of your Build Sheet.
One boundary deserves clear attention: the absence of a stated revision limit does not mean that missing historical data can always be recovered, regardless of how many times a revision is submitted. The revision policy removes cost and repetition as barriers, but it does not change what evidence exists for a given vehicle. If the historical record does not contain information about a particular option or specification, no number of revisions will produce that data. Supplementation is possible where evidence permits, and that conditionality does not disappear because the revision policy is generous.
To put it plainly: corrections are included at no additional cost, and there is no stated revision limit, but those terms do not guarantee that every issue can be resolved. Evidence availability remains the governing factor for what can actually be added.
For detailed information on the correction fee structure and revision process, see Build Sheet Correction Fees, Turnaround & Revision Times.
Review-Status Labels Coming to Your Build Sheet
Current Classic Decoder Build Sheets do not universally display field-level provenance markers. There is no system in place today that attaches a visible evidence-source label to each individual field on your report. If you are looking for such indicators on a Build Sheet you have already received, they are not currently a universal feature of the product.
Looking ahead, three evidence-status labels are planned as future terminology for Build Sheet governance: Revised, Owner Confirmed, and Manual Reviewed. Their exact scope and placement, including whether they apply at the field, report, or workflow level, should not be assumed from the label names alone. They represent a planned future state, not a description of what current reports universally display.
The distinction between current and planned matters here. These label names should not be read as confirming that your existing Build Sheet carries them. If and when these labels are deployed, their exact meaning, scope, and application should be read according to the product state at that time. For those definitions, see Revised Build Sheet Status & Review Labels Explained.