That distinction matters from the start. The review step is what stands between a request and any change, and the outcome is always conditional on what the supporting evidence can establish.
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 correction process distinguishes owner-supplied information from independently supported historical evidence, so a correction request is reviewed against what the available evidence can actually establish rather than being accepted automatically.
Correction review is one part of the wider support process surrounding a reconstructed Build Sheet. For the broader explanation of routine review, assisted completion, revised information, fees, turnaround, and revision expectations, see Classic Car Build Sheet Review, Corrections & Assisted Completion.
What Happens Before a Correction Request Is Filed
Every Classic Decoder order receives routine manual verification or a manual double-check for errors. This baseline review is standard across orders, but it should not be described as a deep field-by-field authentication process.
What routine verification is not, however, is the same thing as a correction review. These are two distinct processes. The baseline check that happens on every order is not a deep, field-by-field investigation where each data point is independently authenticated. It’s a quality layer, not a research resolution.
A correction request enters a separate review context from routine verification. Current approved project facts do not define a universal step-by-step evidence-ranking workflow, so the safe boundary is that a requested change is reviewed and any revision must remain supported by appropriate evidence.
The correction request is also not the same as an accepted correction. Submitting one means the review begins; it doesn’t mean the change has been made. That’s the mediating step the rest of this article explains.
Have a Classic VIN to Research?
Enter it to see what vehicle information may be available.
How Classic Decoder Evaluates the Evidence in a Correction Request
A correction review is evidence-dependent, but current project facts do not establish one universal hierarchy for every evidence type. The essential distinction is that owner-supplied information must remain separate from independently supported historical evidence, and each source can support only the propositions within its actual authority.
Owner-supplied information is information provided by the vehicle owner in support of a correction. It may include statements or supporting materials supplied with the request. Its source should remain identifiable as owner-supplied, and it should not automatically be treated as independently verified historical fact.
Independently supported historical evidence is evidence from an external source that is authoritative for the specific proposition being reviewed, such as applicable archival or production documentation where available. The project facts do not authorize a universal evidence-ranking formula; source authority remains proposition-specific.
The table below shows the minimum distinction that should be preserved between owner-supplied information and independently supported historical evidence.
| Evidence Source | What It Can Establish | Safe Review Treatment |
|---|---|---|
Owner-supplied information | What the owner states, observes, or supplies within the material's actual scope | May inform review; does not independently establish historical factory configuration |
Independently supported historical evidence | Historical propositions within the source's exact authority and applicability | May support revision where applicable; no universal source hierarchy is asserted |
The practical implication is that owner-supplied information can inform a correction review without automatically becoming independently supported historical evidence. If separate authoritative evidence supports the same proposition, that support should remain distinguishable from the owner's contribution.
As an evidence-logic example, a current photo may support what is physically present on the vehicle today without by itself proving that the same feature was installed at the factory. A period or archival record may support a historical configuration claim if it is authoritative and applicable to that vehicle. These examples illustrate evidence scope, not a guaranteed Classic Decoder workflow or outcome.
The source of the evidence affects what the evidence can legitimately support. No source type should be upgraded beyond its actual applicability or treated as universally decisive.
What a Correction Review Can and Cannot Establish
When a correction review finds independent historical evidence that supports the change you’ve requested, the Build Sheet may be revised. But revised means something specific, and it’s worth being clear about what that is.
A revised Build Sheet is an updated reconstructed report. Revision does not change the document into an original factory-issued record, manufacturer certificate, or independently authenticated artifact. Any revised claim should remain bounded by the evidence supporting that change.
When owner-supplied information and historical evidence point in different directions, current project facts do not establish a universal rule for resolving that conflict or a current field-level label that must be applied. The safe treatment is to preserve the source distinction and avoid presenting an unresolved conflict as settled fact.
Missing data is a related situation. If your Build Sheet has fields where information wasn’t available in the original reconstruction, it may be possible to supplement those gaps if appropriate evidence surfaces during review. But this is a conditional possibility, not a guarantee. Recovery depends entirely on whether the right evidence exists to fill those gaps.
The project-approved future evidence labels are limited to Revised, Owner Confirmed, and Manual Reviewed. Current project materials do not establish a universal current field-level provenance system or the exact trigger and placement rules for those labels. For the current boundaries and future terminology, see the sibling article Revised Build Sheet Status & Review Labels Explained.
Correction Support: What the Policy Covers
Corrections carry no extra fee. This is a support-policy fact, not a guarantee that every requested change will be accepted or that unlimited manual research will be performed.
Applicable correction and assisted-completion cases may take up to 24 to 48 hours, and are often resolved faster. This timing does not apply to initial Build Sheet delivery and does not guarantee that every correction will be resolved within that window.
There is no stated revision limit. That wording should not be strengthened into unlimited research, unlimited successful revisions, or guaranteed eventual resolution. Each revision outcome remains evidence-dependent.
For full detail on fee conditions, turnaround policy, and related terms, see the sibling article “Build Sheet Correction Fees, Turnaround & Revision Times.”