The bill adds a new section to 38 U.S.C. creating a Veterans Experience Office (VEO) inside the Department of Veterans Affairs’ Office of the Secretary and tasks a Chief Veterans Experience Officer with coordinating customer-experience strategy across the Department. The office will collect veteran-derived data, require other VA components to report customer-experience metrics, assess customer-facing information and sites, and provide strategic guidance to increase satisfaction and usage of benefits and services.
The measure sets a yearly reporting chain—first from the Chief to the Secretary, then from the Secretary to Congress with disaggregated feedback and analyses of reasons veterans do not use benefits—and includes privacy limits, a prohibition on expanding VA FTEs, reimbursement mechanics for shared services, and a statutory sunset in 2028. It also orders a Comptroller General review of the VA’s feedback methods and tools, including VSignals and trust-scores.
At a Glance
What It Does
Establishes a Veterans Experience Office headed by a Chief Veterans Experience Officer who reports to the VA Secretary and coordinates customer-experience strategy, data collection, and improvement activities across VA. The office will gather veteran-derived feedback, require periodic reporting from other VA entities, assess websites and service channels, and produce annual summaries for the Secretary and Congress.
Who It Affects
VA central leadership and line program offices that administer benefits and services, VA digital and customer service teams that manage websites and surveys, veterans and beneficiaries as the source of data and the intended beneficiaries of improved service design, and GAO, which must audit the Office’s methods.
Why It Matters
This creates a single, Secretary-level function charged with turning service feedback into policy and operational change, institutionalizing data-driven decisionmaking at VA. The bill also mandates external review of VA’s feedback tools, signaling congressional interest in the validity of metrics such as trust-scores and VSignals.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The bill inserts a new statutory section into title 38 to form a Veterans Experience Office (VEO) under the VA Secretary. The Secretary appoints a Chief Veterans Experience Officer to lead the Office; the Chief reports directly to the Secretary and is responsible for steering the Department’s overall customer-experience strategy and preventing duplicative efforts across VA units.
The statute frames the Office as the centralized steward of customer-experience policy rather than a program-delivery unit.
The Office’s operational role centers on collecting veteran-derived data to measure satisfaction and service usage, and on requiring other VA organizations to deliver routine reports on customer-experience metrics and improvement plans. The bill directs the Office to assess VA’s customer-facing content—websites and other information channels—and to advise where design and communication changes could increase take-up of benefits and services, including outreach to veterans who are eligible but not using available programs.Reporting is structured in two steps: the Chief submits an annual summary of the collected metrics to the Secretary; then the Secretary has 180 days to transmit an annual summary and analysis to Congress.
The required congressional report must disaggregate feedback by benefit and include demographic information of respondents, identify reasons veterans do not use benefits (eligibility, awareness, technology, time, and other factors), and provide an analysis of possible remedies.On resources, the Secretary must give the Office sufficient staff, access, and non-PII information to do its work; the Office cannot receive personal data without appropriate consent. VA offices may reimburse the Office for services at cost-recovery rates if reimbursement does not impair those offices’ statutory duties, but the statute explicitly prohibits increasing the Department’s authorized full-time headcount.
Finally, the Office’s authorities and reporting obligations end on September 30, 2028, and the Comptroller General must complete a review—within 540 days of enactment—evaluating the VA’s feedback methodologies, including VSignals and trust-scores, and submit findings to the Veterans’ Affairs committees.
The Five Things You Need to Know
The bill creates 38 U.S.C. §325 establishing a Veterans Experience Office within the Office of the Secretary, led by a Chief Veterans Experience Officer appointed by the Secretary.
The Office can require other VA organizations to report customer-experience metrics, action plans, and improvement efforts on a regular basis to the Chief.
Annual reporting is two-tiered: the Chief sends a summary to the Secretary, who then has 180 days to deliver an analysis to Congress with disaggregated feedback and demographic data.
The Office may not receive personally identifiable information without individual consent, may be reimbursed for services by other VA offices at cost, and cannot increase VA’s authorized FTEs.
The Office’s authorities expire September 30, 2028, and the Comptroller General must review VA’s feedback tools and methodology (including VSignals and trust-scores) within 540 days of enactment.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Creates the Veterans Experience Office under the Secretary
This subsection formally establishes the Office as part of the Secretary’s Office, giving it statutory existence and situating it at the Department’s senior level. Making the Office a statutory entity increases its visibility and obligates the Secretary to provide it access and resources—an important change from a temporary or informal unit.
Chief Veterans Experience Officer: appointment and reporting
The Secretary appoints the Chief from qualified candidates and the Chief reports directly to the Secretary. That reporting line gives the Chief authority to coordinate across VA but does not create a new competitive-exam civil service post; appointment authority remains with the Secretary, which preserves executive control over the role.
Core functions: strategy, coordination, data collection, and assessments
This subsection lists the Office’s substantive duties: set customer-experience strategy and policy, prevent duplication by coordinating with other offices, collect veteran-derived data for policymaking, advise on outreach to non‑users, and assess the helpfulness and accuracy of customer-facing materials. The language grants the Office policymaking influence (strategy and guidance) rather than direct operational control of benefit delivery.
Annual reporting: summaries, disaggregation, and reasons for non-use
The reporting framework requires the Chief to compile data summaries each year for the Secretary, who must then report to Congress within 180 days. The congressional report must break feedback down by benefit or service, include relevant demographic data, list potential reasons veterans don’t use benefits (eligibility, awareness, technology, time, and other reasons), and analyze how to address those barriers—tying feedback into actionable recommendations.
Staffing, funding mechanics, privacy rule, FTE cap, and sunset
The Secretary must ensure the Office has necessary staff and access to customer-experience information but the Office may not receive PII without consent. Other VA organizations may reimburse the Office at cost for services provided, provided such charges do not interfere with statutory duties; however, the statute bars any increase in the Department’s authorized full-time employee count. Finally, the statute sunsets on September 30, 2028, limiting the Office to a finite trial window.
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 and beneficiaries — gain a centralized function focused on improving clarity, access, and design of benefits and services through data-driven recommendations and website/content assessments.
- VA program managers and service designers — receive consolidated customer-experience metrics and analyses that can guide redesign, outreach, and prioritization of investments to raise service usage.
- Congress and oversight offices — obtain regular, disaggregated reporting linking user feedback to specific benefits, enabling more targeted legislative and budgeting decisions.
- Veteran service organizations and advocates — get access to richer, aggregated feedback and analyses that can strengthen advocacy and outreach strategies.
- VA digital, communications, and customer service teams — receive prioritized assessments on where websites and materials are confusing or inaccurate, helping target fixes that improve uptake.
Who Bears the Cost
- Line VA offices and program components — must prepare and deliver recurring customer-experience metrics and action plans, imposing staff time and reporting burden.
- VA finance and shared-service units — may need to absorb or account for reimbursements to the Office and implement cost-recovery arrangements, complicating internal budgeting.
- IT and privacy teams — must implement data access controls and consent mechanisms so the Office can use veteran-derived data without violating privacy rules, increasing technical workload.
- The Chief’s office — will require sustained internal resources and political backing to influence operational units, which may divert attention from other priorities within the Secretary’s Office.
- Congressional committees and staff — must review and act on the new, complex data packages and the GAO report, adding oversight responsibilities without dedicated appropriations attached to the statute.
Key Issues
The Core Tension
The bill’s central dilemma is between centralizing customer-experience authority to drive coherent, data-driven improvements and preserving operational autonomy and privacy constraints at the program level: giving the Office power to collect and standardize feedback improves policymaking, but without clear access rights, stable resourcing, and validated metrics, the Office risks becoming a reporting hub that documents problems without the means to fix them—or it could impose reporting burdens that divert resources from service delivery.
Several implementation questions could limit the Office’s effectiveness. First, the statute requires veteran-derived data but also constrains access to personally identifiable information without consent; that balance protects privacy but may prevent linking survey responses to administrative records needed to diagnose problems for particular subpopulations.
Second, the cost-recovery and non‑FTE provisions make the Office effectively a coordination function without guaranteed new headcount, which risks under-resourcing the very activities—data analytics, survey design, outreach—needed to produce high-quality insights. Third, the Office’s authority to require reporting is clear in text but enforcement is not: the bill does not create penalties or incentives, so compliance may depend on internal leadership and agency culture.
The bill also leans on new and existing metrics such as trust-scores and VSignals; these tools are still evolving and their methodological validity varies. The required GAO review acknowledges that issue, but the statute does not prescribe standards for measurement quality or address how to pivot if those tools prove unreliable.
Finally, the statutory sunset truncates the window to institutionalize changes; useful reforms in service delivery often require sustained investment and multi-year IT projects, so a fixed 2028 termination could undermine long-term transformation or create uncertainty about whether to invest now.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.