Building a Chronological Timeline from a VA C-file

Why Chronology Is a Regulatory Requirement, Not a Convenience

A chronological timeline is not an organizational preference. VA's own rating framework requires it. 38 CFR § 4.1^[1] states that each disability must be viewed in relation to its history, because ratings may require adjustment over time as laws change, medical knowledge advances, and the veteran's condition evolves. 38 CFR § 4.2^[2] goes further: the rating specialist must interpret examination reports in light of the whole recorded history, reconciling different reports into a consistent picture.

That is the regulatory standard VA applies. If the firm is not working from an ordered, date-anchored record, it is working with less clarity than the standard demands. A timeline built from the C-file is how the firm meets that standard on its own terms before a decision is made.

What Documents Anchor the Timeline

The C-file is requested using VA Form 20-10206, the Freedom of Information Act and Privacy Act request form. VA Form 20-10206^[3] A complete C-file should contain every document VA has associated with the veteran's claim under their VA file number, which tracks the claim through VA's compensation system and ties all evidence to the record. VA.gov – Request Personal Records^[4]

The documents that carry the most chronological weight:

• Service treatment records (STRs). These establish the in-service period, any documented injuries or diagnoses, and the baseline medical picture at separation. They are the starting point for any direct service connection theory.
• Claim receipt dates. The date VA received the claim controls the effective date analysis under 38 CFR § 3.400^[5]. Every claim in the file needs a confirmed receipt date pinned to the record.
• Rating decisions. Each decision establishes what VA found, what it denied, and when. The sequence of decisions shows the rating history for each condition and tells you whether there is a prior final decision on the issue.
• C&P exam reports. These carry the date of the exam, the examiner's findings, and often a nexus opinion. The date of the exam relative to the claim and the rating decision matters for adequacy review.
• Private medical records. The date these were submitted to VA or associated with the file affects both the evidentiary record and, in some cases, the effective date analysis.

Each of these document types gets its own segment in the case record. Date, document type, source, and a brief note on relevance. That is the raw input for the timeline.

• Service treatment records (STRs). These establish the in-service period, any documented injuries or diagnoses, and the baseline medical picture at separation. They are the starting point for any direct service connection theory. For a structured approach to extracting and auditing the STR segment before building the timeline, including how to identify missing records and map in-service events to claimed conditions, see the STR review guide.

How to Sequence the C-file Chronologically

C-files arrive in no reliable order. VA does not organize them for the firm. Documents are often misfiled, duplicated, or missing dates entirely. The sequencing step is purely structural work: pull every document, assign it a date, and order the case record accordingly.

C-files arrive in no reliable order. VA does not organize them for the firm. Documents are often misfiled, duplicated, or missing dates entirely. The sequencing step is purely structural work: pull every document, assign it a date, and order the case record accordingly. That work depends on separating the file into discrete document categories before sequencing begins, because a C&P exam report filed in the STR segment will skew the event timeline and obscure the gaps the attorney needs to see.

The practical approach for staff:

Start with the documents that carry hard dates: separation papers (DD-214), claim receipts, and rating decisions. These create fixed anchors across the timeline. Then place STRs within the in-service period, using the date of treatment rather than the date the record was created. C&P exam reports go on their exam date. Private records go on their treatment date, not the date submitted.

Undated documents are a common problem. When a record has no date, note it as undated and record the date it was associated with the claims file if that metadata is available. Flag it for attorney review. Do not guess at a date.

Misfiled records are another. A document that appears in the C-file under the wrong veteran's name or claim number needs to be flagged immediately and kept separate from the working record until the firm can confirm it belongs to the case.

Once the documents are ordered, the timeline reveals the actual sequence of events: when symptoms first appeared in the record, when claims were filed, when VA acted, when evidence was submitted, and where the gaps are. That sequence is what drives claim analysis.

Related guides

VA C-file Workup ChecklistA structured C-file workup turns a raw claims file into a cited case record. This checklist covers document segmentation, chronology, conditions, exams, and evidence gaps.

Effective Date Arguments the Timeline Unlocks

Effective date errors are among the most financially significant problems in a VA file, and they are invisible without a timeline. Two provisions create the most consequential arguments.

Under 38 CFR § 3.400^[5], the effective date of an award is the date VA received the claim or the date entitlement arose, whichever is later. That sounds straightforward. In practice, firms often find that VA used the wrong claim date, applied the wrong event as the entitlement date, or failed to account for an earlier informal claim.

Under 38 CFR § 3.156(c)^[6], if VA later receives or associates official service department records that existed but were not in the file when VA first decided the claim, VA must reconsider the claim. An award made on that reconsideration is effective on the date entitlement arose or the date VA received the previously decided claim, whichever is later. This provision can shift the effective date back by years.

The timeline is what surfaces both arguments. If STRs are present in the current C-file but were missing from earlier decisions, the firm can see that directly in the chronological record. The gap between when the records should have been associated and when they actually appear in the file is the factual basis for a 3.156(c) argument. Without the timeline, that gap is invisible.

Claim status under 38 CFR § 3.160^[7] also matters here. Whether a prior claim was complete, final, or pending affects which dates are operative. The timeline should note the status of each claim at the time of each decision.

Attorney judgment is required to interpret what these dates mean for the argument and any submission. The timeline gives the attorney the factual sequence. The strategic call is theirs.

Service Connection Theory and the Chronological Record

Service connection theory depends on three points in time: the in-service event or exposure, the current diagnosis, and the medical nexus connecting them. The timeline shows whether the record actually supports all three.

A direct service connection theory requires an in-service event documented in the STRs, a current diagnosis, and a nexus opinion linking them. The timeline tells the firm whether the STRs document the event and how close in time the post-service symptoms appear in the medical record. A large gap between separation and the first documented diagnosis is a problem to address in the evidence strategy, not ignore.

Secondary service connection requires a service-connected condition and evidence that it caused or aggravated the secondary condition. The chronological record shows the sequence of diagnoses and whether the medical record supports a causal relationship.

Presumptive theories depend on the in-service period. If the veteran served in a covered period or location, the timeline confirms when service began and ended and whether the diagnosis falls within the applicable window.

Whatever the theory, the chronology also tells the attorney what evidence is currently missing. A nexus opinion that predates a significant change in the veteran's condition, an STR that mentions symptoms but no diagnosis, a diagnosis that appears without any documented in-service precipitant: all of these are visible in the sequence and require a decision about what to develop.

Spotting Duty-to-Assist Failures in the Timeline

VA has a duty to assist claimants in developing their claims. M21-1, Part III, Subpart i, Chapter 2^[8] covers VA's duty to obtain records and maintain the development process. That duty has limits and exceptions, but where VA failed to fulfill it, the failure can support an appeal argument.

The timeline makes duty-to-assist failures visible. Four patterns to flag:

Missing STRs. If the veteran reports in-service treatment and no corresponding STR appears in the file, that is a gap. The timeline shows the in-service period and what the record actually contains. If VA decided the claim without those records in the file, that decision may rest on an incomplete record.

Unanswered record requests. The C-file should reflect VA's development activity: requests sent, responses received, and any follow-up. A gap in that activity, visible in the timeline as a period of no VA action during a pending claim, may show that VA did not pursue records it should have.

C&P exam adequacy. The timeline shows when the C&P exam occurred relative to the claim and rating decision. An exam that predates significant medical evidence, or that was conducted under a theory inconsistent with the claim, is a potential adequacy problem. Per 38 CFR § 4.2^[2], the examiner must account for the whole recorded history. If the exam predates records that changed the picture, or if the examiner clearly did not review the full file, the firm has a factual basis for challenging the exam's adequacy.

Periods of service not covered. Some veterans served in multiple periods or locations. If the timeline shows a period of service with no corresponding records in the file, that gap needs to be flagged before the claim or appeal is submitted.

These findings go into the case record as attorney review items. The attorney decides whether they support an argument and what to do with them.

Using the Timeline to Set Appeal Strategy

The sequence of decisions and evidence entries determines which appeal lane is available and what the strongest argument is at each stage. That is not a general observation. It is a direct consequence of how the AMA appeal system works.

A Supplemental Claim requires new and relevant evidence. The timeline tells the attorney whether such evidence exists and when it entered the record relative to the prior decision. If the evidence was already in the file before the decision, it is not new. If it was submitted after, its date of receipt relative to the decision controls whether it qualifies.

A direct appeal to the Board requires no new evidence but limits the Board to the record at the time of the appealed decision. The timeline tells the attorney exactly what was in that record and when.

The sequence of prior rating decisions also sets the rating ceiling history. If the veteran received a 30 percent rating that was later reduced, the timeline shows when the reduction occurred, whether VA followed the reduction procedures, and whether the veteran was at that rating long enough to trigger stabilization protections. A reduction made without the required findings under the applicable regulations is a separate issue the timeline can surface.

Chronology also drives CUE arguments. A clear and unmistakable error claim requires showing that VA made a legal or factual error on the face of the record at the time of the decision. The timeline is the record. Without it, there is no CUE analysis.

Staff Work Versus Attorney Judgment in Timeline Review

Building the timeline is staff work. Interpreting it is not.

A paralegal or case coordinator can pull the C-file, segment documents by type, assign dates, order the sequence, flag undated records, and note gaps in the evidence or VA's development activity. That work product goes into the case record and becomes the foundation for attorney review. Source documents attach to the case, dates get pinned to events, and gaps surface as flagged items before the file reaches the attorney.

What requires attorney judgment: deciding which service connection theory is viable given the chronological record, identifying which gaps are material and how to address them, determining whether the timeline supports an earlier effective date argument under 3.156(c) or an error in a prior decision, and selecting the appeal lane and argument that best fits the sequence.

The distinction matters for workflow design. If the attorney is reviewing raw documents to find the dates, that is a resource allocation problem. If staff has already structured the chronological record and flagged the issues, the attorney can focus on the calls that require their expertise.

The goal is a case record where the timeline is visible, sourced, and current before the attorney ever opens the file.