Veterans are often told that help is available, but finding the correct place can still depend on knowing the right program name, searching the right website, interpreting unfamiliar facility categories, and verifying that a map listing is current.

That is a serious usability problem. A veteran may know the need - health care, counseling, benefits assistance, education support, employment help, a cemetery, or pre-discharge services - without knowing the exact name of the office that provides it.

A resource is not truly accessible merely because its address exists somewhere online. It must be discoverable at the moment and place where the veteran can act on it.

The veteran is expected to know what to search before the search begins

Traditional directories are organized around institutional terminology. The user may need to distinguish a medical center from a community-based clinic, a Vet Center from a benefits office, a Veteran Readiness and Employment site from a regional office, or a VetSuccess on Campus location from the university’s own veteran services.

A person who does not know that a program exists cannot reliably search for its name. The same is true for a transitioning service member who has never used VA services, a veteran who recently moved, a caregiver helping someone else, or a traveler outside the home region.

This creates a discoverability paradox: the veteran must already understand the resource system in order to use the tool that is supposed to help them understand the resource system.

General-purpose phone maps are useful but not authoritative directories

Apple Maps, Google Maps, and other navigation tools are valuable for routing. Their business and place listings are assembled for a broad public purpose, not specifically to represent the full VA facility ecosystem.

A listing may be missing, duplicated, categorized too broadly, placed at the wrong entrance, associated with an old name, or left active after a program changes. Updates can depend on public submissions, business-owner claims, third-party feeds, and the mapping provider’s review process. The map may show a destination without explaining whether it is a clinic, Vet Center, benefits office, campus site, cemetery, or pre-discharge location.

This does not make general-purpose maps unreliable in every case. It means they should not be asked to serve as the sole source of truth for a specialized federal resource network.

Static directories become separated from the veteran’s current context

A web directory can contain accurate information and still create friction. The veteran may need to open a browser, select a state, enter a ZIP code, choose a facility type, interpret the results, copy an address, and reopen that address in a navigation app.

The directory does not necessarily remain present in the veteran’s daily workflow. It may not surface a nearby resource unless the person intentionally returns to the site and performs the search again.

For outreach, that distinction is important. Passive proximity can reveal a resource the veteran did not know to request. Search can only return what the veteran thought to ask for.

A location listing can be accurate and still fail to create engagement

Many resource tools stop after displaying a name, address, and phone number. That is useful, but it leaves the veteran to complete every next step in a different system.

The person may need directions, a place to meet a peer, an event at the facility, a reminder, or a way to remain connected to a local community. When the facility record cannot participate in those later actions, it remains a static answer rather than an engagement point.

What a better veteran facility tool should do

A veteran-centered facility layer should begin with an official source, update in a repeatable way, surface places based on the veteran’s current area, explain the type of location in plain language, and remain useful after discovery.

• Use official VA facility records rather than relying only on public map listings.

• Synchronize records idempotently so updates do not create duplicates.

• Deactivate stale records within the synchronized region.

• Skip incomplete records that lack the information required for mapping.

• Show nearby facilities without requiring the veteran to know the exact program name.

• Separate official public-service locations from paid partner promotions.

• Allow the user to hide the VA facility layer.

• Connect the facility to directions, CheckIns, meetups, and group events.

How SOCYiD builds an official-source VA facility layer

SOCYiD synchronizes facility records from the U.S. Department of Veterans Affairs Facilities API. The process can page through the nationwide inventory or synchronize a defined region by latitude, longitude, and radius.

Each record is upserted using the VA source and external facility identifier. Re-running the sync updates the existing location instead of creating a duplicate. Records no longer returned within the synchronized area can be reconciled and deactivated. Entries missing a usable name, address, or coordinates are skipped rather than displayed as incomplete map points.

This architecture does not make every underlying record permanently correct. It creates a repeatable path from the official source into the app and a way to reconcile change.

The nearby list removes the need to know the program name

When a veteran opens SOCYiD and permits location use, the app can show VA facilities within the nearby radius, sorted nearest first with distance displayed. The user does not have to begin by choosing a state, memorizing a facility name, or knowing the administrative category.

The person can see what is physically near the current location, open the facility record, view the address, and hand the destination to the phone’s navigation system for routing.

This is not a replacement for route guidance. SOCYiD supplies the official-source destination and context; the navigation app still performs turn-by-turn directions.

The facility inventory reflects more than hospitals and clinics

At the time of drafting in July 2026, SOCYiD contained 2,574 active VA facility records. The inventory included 214 Vet Centers, 141 national cemeteries, 117 Veteran Readiness and Employment offices, 91 VetSuccess on Campus sites, regional benefits offices, pre-discharge locations, health facilities, and other official facility types.

Those records appeared alongside 860 manual or partner CheckIn locations, for 3,434 total locations in the platform at that time. Counts will change as the official source and the SOCYiD inventory are synchronized.

Friendly category labels such as VA Health Facility, VA Benefits Office, Vet Center, and VA Cemetery help translate technical or missing classifications into terms a user can understand.

VA facilities are not treated as paid advertisements

The VA records are configured as non-paying CheckIn locations. They do not display a partner discount pill or paid-perk language. They can use the VA seal and a facility category while remaining distinct from commercial CheckIn partners.

The home screen can preserve the user’s choice to show or hide VA facilities. The resource layer is available without forcing every user to view it, and the listing should not imply that VA officially sponsors SOCYiD unless a separate relationship exists.

The important difference begins after the facility is found

Because VA facilities are ordinary location records inside the SOCYiD CheckIn system, they can participate in the same workflows as other declared places. A facility can be selected for a one-to-one meetup, a solo CheckIn, an arrival-confirmed interaction, or a SOCYiD Group event.

This changes the role of the listing. The facility is no longer only an address returned by a search. It can become the place where a peer meets another veteran, where an outreach group schedules an event, where a student receives a reminder, or where a Watcher receives an optional arrival update.

The facility record becomes a bridge between discovery and participation.

Examples of discovery without prior knowledge

A transitioning service member near a pre-discharge site

The service member may not know the formal name of the program or where it operates. Nearby-first discovery can surface the official location without requiring that vocabulary first.

A college student near a VetSuccess on Campus location

The student may know there are veteran resources on campus but not know the VSOC program name. The facility can appear based on proximity and later serve as a group event venue or community anchor.

A veteran traveling outside the home region

A veteran away from home can see nearby official VA locations without rebuilding a search around an unfamiliar city or county.

A family planning a cemetery visit

A national cemetery can be surfaced as an official location, opened for its address, and passed to the phone’s navigation app. The listing does not guarantee hours, eligibility, or service arrangements, which should be confirmed through official channels.

What the feature does not claim

A location record cannot determine whether the veteran is eligible for a service, whether walk-ins are accepted, whether the office is open, whether a specific appointment is available, or whether the facility is the correct place for an emergency.

Phone GPS can also be inaccurate, especially indoors, around tall buildings, or when the device has a stale reading. Straight-line distance does not equal driving distance. The veteran should confirm time-sensitive services, hours, eligibility, and emergency instructions through the responsible official channel.

• The listing does not replace VA.gov or official facility communications.

• The listing does not guarantee that every service is offered at every location.

• The listing does not guarantee hours, appointments, or walk-in availability.

• The listing does not replace 911, the Veterans Crisis Line, or emergency medical guidance.

• The listing does not imply official VA endorsement of SOCYiD.

Frequently asked questions

Where does SOCYiD get the VA facility information?

The facility sync uses the U.S. Department of Veterans Affairs Facilities API and stores the official source identifier with each record so later synchronizations can update rather than duplicate it.

How many VA facilities are in the app?

The live inventory provided for this draft was 2,574 active VA facilities in July 2026. The count should be presented with an as-of date because official records and synchronized inventory can change.

Do veterans have to search for a facility name?

No. With location permission, the app can show nearby VA facilities sorted by distance, allowing discovery before the user knows the exact program or office name.

Does SOCYiD replace Google Maps, Apple Maps, or VA.gov?

No. SOCYiD can surface the official-source destination and connect it to app workflows. A phone mapping service can still provide navigation, and official VA channels remain responsible for authoritative service, hours, appointment, and eligibility information.

Are VA facilities paid placements?

No. The described records are non-paying CheckIn locations and do not receive partner-discount or paid-perk treatment.

Can I hide VA facilities?

Yes. The app can persist the user’s preference to show or hide the VA facility layer.

The better resource-discovery default

The old default assumes the veteran knows the program, finds the correct directory, interprets the category, copies the address, and opens a separate navigation tool.

A better default begins with the veteran’s current context: show the official resources nearby, explain what kind of place each one is, preserve the choice to hide the layer, and connect the destination to the next action.

SOCYiD uses official-source facility data to make that transition from “a resource exists” to “this is the resource near you and here is what you can do next.”

Back to the Trust Lab