Service periods
Track each meaningful period separately, including branch, component, dates, active-duty status, and the records attached to that period.
SERVICE & ELIGIBILITY FOUNDATION — FOUNDING PUBLIC BETA
Prior service, branch transfers, component changes, actual breaks in service, IRR or inactive periods, legal name changes, missing records, and different discharge characterizations can all change which records and service periods matter to a benefit decision.
Privacy note: This page does not ask for your name, former name, SSN, DoD ID, VA file number, or other identifying information. The quick check runs only in your browser and its answers are not sent to analytics.
The foundation is: Person → identity history → service periods → branch/component transitions → breaks in service → record sets → conflicts → eligibility facts → benefits.
A single global field such as “Branch,” “Years served,” or “Discharge” is not enough for people whose military history spans more than one period.
WHAT MDN TREATS SEPARATELY
Track each meaningful period separately, including branch, component, dates, active-duty status, and the records attached to that period.
Prior service in one branch followed by another should not be collapsed into the current branch.
Active, Reserve, Guard, AGR/active Reserve, IRR, and other statuses can have different service and eligibility consequences.
A civilian break is different from remaining in an inactive status. MDN should preserve both the gap and the status during the gap.
Records may exist under a former legal name, spelling, suffix, or other identity detail. MDN only needs to know that a continuity issue exists—not the actual former name.
Characterization belongs to the relevant period of service. A later discharge should not silently overwrite an earlier qualifying period.
Missing DD214s, NGB records, orders, reserve points, medical records, retirement documents, or conflicting dates should be flagged before personalization.
MDN can identify a mismatch and route the user; the responsible service, records custodian, VA, or correction board controls the actual correction.
LOCAL-ONLY QUICK CHECK
Choose Yes, No, or Unsure. You do not need to enter names, dates, units, or identifiers.
VA specifically explains that an honorable period of service may support eligibility even when a later period ended differently, and that a qualifying earlier period may exist even when no separate DD214 was issued at the end of that earlier term. That is why MDN will evaluate relevant service periods rather than treating the most recent discharge as the whole person.
OFFICIAL RECORD ROUTES
NARA says record requests rely on the complete name used while in service, branch, and dates of service, among other identifiers. MDN does not need those identifiers to flag a continuity issue.
Open NARA records guidance ↗Non-archival corrections generally route to the appropriate service personnel command; some changes require a service review or correction board.
Open correction guidance ↗VA explains how prior honorable service and separate periods can affect benefit eligibility and Character of Discharge review.
Open VA discharge/correction guidance ↗milConnect documents how service-reported information, name updates, and breaks between reported occupation codes can create inaccurate or incomplete downstream records.
Open milConnect VMET guidance ↗NEXT LAYER
The Benefits & Services Registry does not issue eligibility verdicts. It shows what factors need verification and where the official answer lives.