This bill directs the Department of Veterans Affairs to build explicit tracking and reporting for appeals and remanded claims, give the Board of Veterans’ Appeals a formal aggregation authority, expand certain powers of the Court of Appeals for Veterans Claims, and require an independent assessment of whether the Board should issue precedential decisions.
Practically, the measure is a framework of transparency, docket-management tools, and outside study intended to shorten time-to-resolution and reduce repeat remands. For counsel, advocates, and VA managers it creates new data streams, procedural hooks (aggregation, limited remands, tolling for class-related matters), and deadlines they will need to incorporate into litigation and case-management practices.
At a Glance
What It Does
Requires new annual reports on remand pendency and Board motion outcomes; creates a statutory duty to track specific claim categories in a VA database; gives the Board explicit authority to aggregate appeals with common questions; expands the Court of Appeals for Veterans Claims’ tools (class-related supplemental jurisdiction and limited remands); and directs an FFRDC study on giving the Board precedential authority.
Who It Affects
Veterans with remanded or pending appeals, VA Veterans Benefits Administration adjudicators and managers, the Board of Veterans’ Appeals, the Court of Appeals for Veterans Claims, veterans service organizations and attorneys representing classes or multiple claimants.
Why It Matters
The bill shifts the appeals ecosystem from opaque queueing toward measurable workflows and centralized resolution tools. That promises faster system fixes but also concentrates decision‑making and could prompt more aggregate litigation and rule‑development at the Court level.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The bill amends Title 38 to force explicit measurement and public reporting of how long remanded claims sit with the VA and how the Board’s procedural motions resolve. It revises section 5109B to require an annual report that covers average remand pendency at the agency, outcomes of motions for earlier Board consideration under section 7107(b) (with reasons), and a breakdown of Board dismissals that flags deaths and whether a dismissal followed a suicide.
The first of these reports is due within one year of enactment.
Separately, the Secretary must issue guidelines within a year describing the evidence claimants may submit with a motion to advance a case on the Board docket. The bill then creates a new statutory duty (section 5109C) requiring the VA to use technology to track and maintain information on a set of defined case categories — for example, claims that are “continuously pursued” under existing notice-and-notification rules, claims sitting unassigned in the National Work Queue, claims remanded by the Board, and cases awaiting Board hearings.
The tracking duty explicitly includes monitoring when VBA adjudicators fail to comply with Board remand instructions, and the VA must report that information annually.On Board operations, the bill adds an explicit aggregation power so the Chairman may consolidate appeals that share common legal or factual questions. Aggregation is defined broadly to include joinder, consolidation, intervention, and other multiparty procedures.
The Board must report every five years on how often aggregation has been used and whether it improved efficiency. The bill also requires the Secretary, through a Board member, to ensure “substantial compliance” with Board remands, but allows the agency of original jurisdiction to waive that requirement when subsequent evidence resolves the issue or when a remand was unnecessary; the waiver must be documented in the Board’s decision.At the court level, the bill expands the Court of Appeals for Veterans Claims’ role in class-related matters by granting supplemental jurisdiction over claims that match a class-certification request and by tolling certain administrative filing deadlines for class members.
The Court also gains a defined limited-remand tool: it may return a narrow question to the Board when the Board failed to address an issue raised or failed to provide adequate reasons and bases. The Court must write rules about how parties request limited remands, the Board’s time to respond, when the Court may act sua sponte, and required notice; the Court retains jurisdiction and stays while the Board resolves the remanded question.Finally, the Secretary must seek an FFRDC to assess whether the Board can feasibly issue precedential decisions and to evaluate aggregation practices.
The bill sets a fast timeline for that procurement and requires the Secretary to share the assessment with Congress and to develop implementing policies within set windows after receiving the FFRDC report. The Chairman of the Board must also conduct a separate study identifying common questions of law or fact (with optional AI assistance) and report the findings within a year.
The Five Things You Need to Know
The bill amends section 5109B to force an annual remand‑pendency report that must show the average time remanded claims remain with the Secretary.
It creates new section 5109C requiring VA to track defined claim categories — including unassigned National Work Queue claims, remanded matters, and claims continuously pursued under existing notice rules — and to report annually.
The Board Chair may aggregate appeals that share common legal or factual questions and must report every five years on instances of aggregation and its impact on efficiency.
The Court of Appeals for Veterans Claims gets supplemental jurisdiction tied to class‑certification requests, a 60‑day administrative window for class members to request review, and authority to order limited remands while retaining and staying the case.
The Secretary must seek an FFRDC assessment on whether the Board can issue precedential decisions and, after receiving the assessment, publish it to Congress and develop policies to implement the recommendations within specified deadlines.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Annual remand and Board-motion reporting (amend 5109B)
This provision rewrites 5109B to add an annual-report obligation. The report must include average pendency after Board remands, counts of cases advanced by 7107(b) motions broken down by grants/denials and stated reasons, and counts of Board dismissals including whether dismissals followed an appellant's death and whether a death was suicide. The Secretary must deliver the first report within one year of enactment, creating a recurring congressional oversight mechanism tied directly to remand performance.
Guidelines for motions to advance cases on Board docket
Within one year the Secretary, in consultation with the Board and VA General Counsel, must issue guidelines describing when and how the Board should advance a case on motion under 7107(b)(3), and what evidence may accompany such motions. Practically, this standardizes the evidentiary threshold for early consideration and gives advocates a predictable checklist to support advancement requests.
VA tracking requirement for specific claim categories
The bill inserts a new section (5109C) mandating technology-enabled tracking of several discrete populations: continuously pursued claims under 5104C/5110; claims in the National Work Queue not yet assigned; claims given expedited treatment; remanded claims; pending Board hearings; adjudicator noncompliance with Board remands; certain supplemental claims; and first notices of beneficiary deaths (flagged by fiduciary status). The Secretary must report annually on the tracked data, forcing internal case‑flow transparency and a public accounting of both operational bottlenecks and alleged noncompliance.
Board aggregation authority and remand compliance
This strand authorizes the Board Chairman to aggregate appeals that share common questions of law or fact and defines aggregation broadly to include joinder and class-like procedures. It also adds a substantial-compliance requirement: the Secretary, acting through a Board member, must ensure VBA respects Board remands, subject to a narrow waiver if new evidence resolves the issue or if the remand was unnecessary. The Board must include any waiver determination in its decisions, and the Secretary must report on aggregation every five years.
Expanded Court jurisdiction and limited‑remand process (amend 7252)
The bill revises 7252 to grant the Court supplemental jurisdiction over claims that fit a class‑certification request and that are in certain pre-final stages with the agency, provides a 60‑day administrative-review window for class members, and tolls appeal deadlines when appropriate. It also gives the Court explicit power to issue limited remands to the Board to address unaddressed issues or inadequate reasons and bases, requires the Court to make rules for that process, and instructs the Court to retain jurisdiction and stay while the Board resolves the remanded question.
Study of common questions and use of AI
The Board Chairman must study the recurring legal and factual questions the Board faces and report to congressional veterans committees within a year. The bill explicitly permits the use of artificial intelligence and other technology in that study, signaling an openness to automated case analysis to guide potential precedential development or internal guidance.
FFRDC assessment on precedential authority and implementation timeline
The Secretary must seek an agreement with an FFRDC to assess whether the Board can issue precedential decisions, consult stakeholders, and recommend aggregation rules. The bill imposes procurement and reporting timelines — 30 days to seek an agreement, reporting/briefing requirements if negotiations stall after 180 days, delivery of the assessment, and a requirement that the Secretary publish the assessment and begin developing implementing policies within 90 days and complete those policies within six months.
This bill is one of many.
Codify tracks hundreds of bills on Veterans across all five countries.
Explore Veterans in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- Veterans with remanded or long-pending appeals — increased visibility into remand pendency and new procedural tools (docket advancement, aggregation) aim to shorten time to final decisions.
- Survivors and families — the requirement to track first‑notice-of‑death data (including fiduciary assignment and suicide disaggregation) provides better information for estate, fiduciary, and mortality oversight.
- Veterans service organizations and systemic counsel — aggregation authority and the Court’s expanded class‑related jurisdiction create clearer paths for multi‑claim strategies and systemic relief.
- Board and Court decisionmakers — aggregation and limited‑remand authority give institutional tools for resolving common legal questions once rather than repeatedly across many appeals.
Who Bears the Cost
- Department of Veterans Affairs (VBA and Board) — must fund IT upgrades, ongoing data collection, annual and quinquennial reports, and additional policy development work required by the bill.
- VBA adjudicators and managers — increased documentation, tracking duties, and exposure to remand‑compliance review will add workload and may prompt rework of adjudication processes.
- The Court of Appeals for Veterans Claims — new rulemaking, administration of limited remands, and supplemental jurisdiction over class-related matters will increase procedural load and case-management complexity.
- Taxpayers/appropriators — the bill creates multiple unfunded or underfunded obligations (FFRDC contract, IT systems, staffing for reporting) that Congress will likely need to fund through appropriations.
Key Issues
The Core Tension
The central dilemma is speed and systemic correction versus individualized accuracy and administrative capacity: the bill pushes the VA and its tribunals to resolve common legal issues faster and more transparently, but doing so concentrates decisionmaking, increases procedural burdens, and risks turning case‑level nuance into blunt institutional fixes without guaranteed resource support or consensus on definitions and thresholds.
The bill trades measurement and centralization for added procedural complexity. Tracking remand pendency and noncompliance creates visibility, but it also produces a new set of metrics that can drive process changes, litigation, and political oversight without guaranteeing quicker resolutions for complicated claims.
Aggregation and expanded court tools can speed resolution of legal questions but risk flattening individualized factual determinations into multi‑party dispositions that may not fit every claimant's circumstances.
Implementation raises thorny operational questions. Building a reliable tracking system that meaningfully captures ‘continuously pursued’ claims, remand compliance, and National Work Queue status requires precise definitions, stable data mappings, and funding.
The substantial‑compliance requirement for remands is intended to curb repeat remands, yet it creates a litigation axis: agencies may over‑use the waiver when new evidence appears, or litigants may dispute whether the waiver was appropriate. Commissioning an FFRDC avoids internal bias in assessing precedential authority, but timelines for procurement and delivery are tight and the Secretary’s obligation to implement recommendations could collide with resource limits and stakeholder disagreement.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.