-
Notifications
You must be signed in to change notification settings - Fork 67
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'main' into 3452-font-token-update
- Loading branch information
Showing
2 changed files
with
60 additions
and
1 deletion.
There are no files selected for viewing
59 changes: 59 additions & 0 deletions
59
src/_content-style-guide/specific-topics-and-programs/claims-and-applications.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,59 @@ | ||
--- | ||
layout: content-style-guide | ||
permalink: /content-style-guide/specific-topics-and-programs/claims-and-applications | ||
has-parent: /content-style-guide/specific-topics-and-programs/ | ||
title: Claims and applications | ||
intro-text: "The information on this page will help you use consistent language about claims and applications across communication channels." | ||
anchors: | ||
- anchor: Considerations | ||
- anchor: Related terms | ||
- anchor: Resources | ||
--- | ||
|
||
## Considerations | ||
|
||
- We use the terms "claim" and "application" intentionally, and they often aren't interchangeable. We also use other related terms like "request" and "authorization" to refer to other types of VA forms. | ||
- In reusable content that appears in many types of applications, requests, and static pages (like an alert), use the general term "form" instead of "claim," "application," or "request" to avoid confusion. | ||
Like this: "Thank you for submitting your form on VA.gov" | ||
Not this: "Thank you for submitting your application on VA.gov" | ||
- Updated standards can take time to implement across all content on VA.gov pages and interactive forms and tools. Existing content on VA.gov, including the claims status tool, may not always reflect the latest decisions documented here. If you have questions about any content, feel free to ask the content and information architecture (CAIA) team. | ||
|
||
**Note:** We're working on style guidance for additional types of VA forms and for how to refer to different people involved in submitting forms, like third-party representatives. Check back soon. | ||
|
||
## Related terms | ||
|
||
**application** (noun) and **apply** (verb) | ||
: We use this term in the context of someone submitting an initial application for benefits. In general, a Veteran will "apply" for any non-disability benefit (including pension and DIC benefits) and "file a claim" for disability. | ||
|
||
**claim** (noun) and **file a claim** (verb) | ||
: In most cases we use this term in the context of someone filing a disability claim. We also use this term in the context of reimbursement and after someone applies for a benefit and has been judged eligible. For example, a Veteran may file a travel reimbursement claim or a life insurance claim. We use this term to reflect that Veterans who are filing for disability-or filing a claim for reimbursement-have a right to that compensation. | ||
|
||
**claimant** and **applicant** | ||
: We sometimes use this term to refer to the person with the claim or the person applying for the benefit—especially if the person is not a Veteran, or if they are not the person submitting the form (for example: "I'm signing for the claimant"). Always define the term on the first instance as "person with the claim" or "person applying for this benefit." When possible, use specific plain language instead, like "Veteran's spouse" or "Veteran's child." | ||
|
||
Like this: "I'm the spouse, dependent, survivor, or caregiver of a Veteran, and I have an existing claim." | ||
Not this: "I'm a non-Veteran claimant." | ||
|
||
**claim exam** | ||
: We use claim exams to determine if a Veteran has a service-connected disability. We also use claim exams to rate that disability. | ||
: - Note: This term is evolving. For now, on first mention on a page, use “VA claim exam (also known as a compensation and pension, or C&P, exam).” After first mention, use “VA claim exam” or “claim exam.” | ||
|
||
**file** (noun) | ||
: We use this term to refer to the actual file a Veteran is uploading from their device. These may not be “documents” as in .doc. They could be .pdf, .jpg, .png, or other file types. | ||
: - Note: Button text on file upload screens should say "Upload file," not "Upload document" or "Upload evidence." | ||
|
||
**document** | ||
: We use this term to refer to the digital or paper item a Veteran is submitting as evidence. | ||
: - Note: File input screens in form flows should use "document" in the screen header. For example, "Upload your supporting documents." | ||
|
||
**evidence** | ||
: We use evidence to refer to all documents and information you submit to support your claim or application. We define evidence as “supporting documents or information.” Supporting documents and other information become evidence when they get attached to a claim or application. | ||
|
||
**sponsor** | ||
: We use this word in forms and other content to refer to the Veteran who earned the benefits that a family member may be using. It's OK to use the word sponsor but lead with the plain language definition. | ||
|
||
Example: the Veteran you're connected to (called your "sponsor") | ||
|
||
## Resources | ||
|
||
- [Check your VA claim, decision review, or appeal status](https://www.va.gov/claim-or-appeal-status/) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters