Skip to main content
U.S. flag

An official website of the United States government

Dot gov

The .gov means it’s official.
Federal government websites often end in .gov or .mil. Before sharing sensitive information, make sure you’re on a federal government site.

Https

The site is secure.
The https:// ensures that you are connecting to the official website and that any information you provide is encrypted and transmitted securely.

Templates

Introduction

Use: Deployed
The form introduction page gives users information about what they can expect before they submit an online application. This page also provides users with steps on how to apply.

About

The introduction page introduces the process that the user is about to embark on to apply to a benefit or service or to complete an ancillary form. This page sets clear expectations on the process and may provide details on when they can expect a decision on their application. This page also gives users ways to get help, as well as important information about that specific form or benefit.

Users can navigate to a form’s introduction page either from within VA.gov or through an online search. Since users can navigate to this page from outside VA.gov, it’s recommended that this page include some basic benefit eligibility information or a link back to the VA.gov benefit eligibility page.

Variations

There are 2 versions of the Introduction page:

  1. Application: The application template is intended for introduction pages that start an application for a benefit or service.
  2. Non-application: The non-application template is intended for introduction pages that start a standard form flow. In other words, an online form that is not for an application for a benefit or service. Typically these are for ancillary forms related to a benefit or service.

Example - Application

Unauthenticated

An example of an introduction page for unauthenticated users.
Anatomy of the Introduction page for unauthenticated users.

The introduction form page for unauthenticated users consists of:

  1. H1 Plain language title of benefit
  2. VA Paper form title
  3. Save work in-progress alert
  4. Process list
  5. Sign-in
  6. OMB Information
  7. Need help

Authenticated

An example of an introduction page for unauthenticated users.
Anatomy of the Introduction page for authenticated users.

The introduction form page for authenticated users consists of:

  1. H1 Plain language title of benefit
  2. VA Paper form title
  3. Prefill alert
  4. Start form link
  5. Process list
  6. Start form link
  7. OMB Information
  8. Need help

Instances of this template in production

Structure - Application

Title

The plain language title of a form makes it clear to the user the benefit they are applying for. The title is limited to 52 characters. For example:

File for [name of benefit]

or

Apply for [name of benefit]

VA Paper form title

The VA paper form title appears in a subtitle under the title in the following format:

Full PDF form title (VA Form FormNumber)

For example:

Authorize the release of non-VA medical information to VA

Authorization to disclose information to the Department of Veterans Affairs (VA Forms 21-4142 and 21-4142a)

Save work in progress alert

The Save work in progress in message uses the Alert - Informational component and encourages users to sign-in in order to save their progress while completing a form.

The message content is captured in engagement messages.

This alert gives users the option to start the form without signing in, excluding the Disability Compensation form where users are required to sign in.

An example of save work in progress alert.
An example of a save work in progress alert used in the Introduction page.

Prefill alert

The Prefill alert uses the Alert - Informational component and informs users who are signed-in that their progress will be saved while completing a form.

The message content is captured in engagement messages.

The Start form link is an action link that navigates the user to the first main form page.

Process list

Process list, describes the steps the user should take to apply.

The headings start with action words and are short/concise. We’ve made these consistent across forms.

Prepare

These steps tells the user what they need to fill out the form (Social Security number, bank information, military history, spouse information, etc). This bullet can also include some basic eligibility information or a link back to the VA.gov benefit eligibility page.

An example of the Prepare step.
An example of a Prepare step from the application to use transferred education benefits.

Depending on the type of benefit, we sometimes include an Alert - Informational with specific information about that benefit.

This is an optional component and should only be used if there is important benefit or part of the application process to call out to the applicant.

An example of a disability ratings alert.
An example of an optional alert used in the Prepare step. This example is from the 21-526EZ form for disability compensation.

Apply

The is standard langauge we use across forms:

Complete this [benefits] form. After submitting the form, you’ll get a confirmation message. You can print this page for your records.

VA review

The step tells applicants how much time it takes VA to review their application. The content under this heading depends on what type of benefit an applicant is applying for.

Some examples:

Health care benefits form intro page

We process health care claims within a week.

Education forms intro page

We usually process claims within 30 days. We’ll let you know by mail if we need more information.

We process applications in the order we receive them. The amount of time it takes to process your claim depends on how many injuries or disabilities you claim and how long it takes us to gather evidence needed to decide your claim.

Decision

This step tells users when they’ll be informed about the status of their application (if denied or approved) and the next steps. It also sets the user’s expectation for how long it takes to receive a response.

Sign-in

A Button - Primary that reads “Sign in to start your application” and opens a modal allowing a user to authenticate. The button is paired with a link which reads “Start your application without signing in” and allows the user to start the application process without authenticating.

OMB information

OMB information is a component that appears at the bottom of the page. The information to fill the component is taken from the paper form (or provided by a VA stakeholder).

Need help

The Need help component is a footer that appears on the bottom of every page of the form. This content lets users know how to get additional help with the form or the benefits.

An example of a need help footer for forms pages.
An example of a Need help component used on all forms pages.

Example - Non-application

Unauthenticated

An example of a non-application introduction page for unauthenticated users.
Layout of the non-application introduction page for unauthenticated users.

The non-application introduction page for unauthenticated users consists of the same elements as the application intro page with some notable distinctions:

  1. The Sign-in to save work in-progress alert appears towards the bottom of the page and is the only call-to-action to start the form. Note that there are two variations of this Alert: Pre-fill and no-pre-fill.
  2. A What to know before you fill out this form section is added.

Authenticated

An example of a non-application introduction page for authenticated users.
Example of the non-application introduction page for authenticated users.

Instances of this template in production

Structure - Non-application

The structure of the non-application into template uses the same elements as the application version with the addition of on new section.

Sign-in to save work in-progress alert

There are two variations of this alert:

  1. Pre-fill sign-in
  2. No pre-fill sign-in

What to know before you fill out this form

  • A 2-5 bulleted list of things people should know before filling out the form. This could include information such as when submitting a form is unnecessary or if there are time limits to be aware of, etc.
  • If an additional list with separate information is useful here, you may add a second h2.
Edit this page in GitHub (Permissions required)
Last updated: Mar 29, 2024