-
Notifications
You must be signed in to change notification settings - Fork 214
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create representatives.md #98897
Open
megzehn
wants to merge
10
commits into
master
Choose a base branch
from
megzehn-patch-representatives
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Create representatives.md #98897
Changes from 8 commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
60cd4b1
Create representatives.md
megzehn ea7b3f4
Update representatives.md
megzehn fa7f384
Update representatives.md
megzehn 6c07dca
Update representatives.md
megzehn 1d94e32
Update representatives.md
megzehn 48c0378
Update representatives.md
megzehn 1237731
Update representatives.md
megzehn 75c8971
Update representatives.md
megzehn 850b36e
Update representatives.md
megzehn bcfc976
Update representatives.md (#99081)
aprocik1 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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,118 @@ | ||
# VA content brief for representatives | ||
|
||
The sitewide content team created this content brief. It's for teams who are designing forms or products that involve representatives acting on behalf of a claimant or applicant. | ||
|
||
**Have questions or feedback on this brief or want to add something?** | ||
- Send us a slack in #sitewide-content-ia. | ||
|
||
## Sections | ||
|
||
- [Overview](#overview) | ||
- [Related terminology](#related-terminology) | ||
- [Content considerations specific to sign in and identity verification](#content-considerations-specific-to-representatives) | ||
- [Organic SEO and VA.gov search](#organic-seo-and-va.gov-search) | ||
- [Content-specific research findings](#content-specific-research-findings) | ||
- [Content pages related to this topic](#content-pages-related-to-this-topic) | ||
- [Other notes](#other-notes) | ||
|
||
## Overview | ||
|
||
Speaking plainly, compassionately, and consistently across VA helps us build trust with Veterans, service members, and their family members. As we continue to move toward an omnichannel experience and multilingual content, consistency becomes even more important. | ||
|
||
This brief will help your team create content for your product that aligns with the VA.gov voice and content standards and that uses consistent language about representatives--people signing and acting on behalf of Veterans, service members, and family members. It will also help us all track content decisions so we can all stay aligned from discovery through post-launch iterations. This is a living document. | ||
|
||
[Read our top 10 plain language standards in the VA.gov content style guide for more](https://design.va.gov/content-style-guide/content-principles/plain-language) | ||
|
||
## Related terminology | ||
|
||
**accredited representative** | ||
|
||
We use this term to refer to a person or organization who's authorized to provide help with VA benefit claims to Veterans and service members, as well as their dependents and survivors. In order for an accredited representative to sign for someone else, the claimant or the representative must submit VA Form 21-22 or VA Form 21-22a. | ||
|
||
Note on usage: Use "VA accredited representative" in the first instance. After that, "accredited representative" is OK. Lowercase, and define on first appropriate instance as “a person or organization who's authorized to help with VA benefit forms.” Include the definition in another sentence, as a parenthetical, or set off with commas. | ||
|
||
**alternate signer** | ||
|
||
We use this term for a person who's certified to sign certain VA forms or applications for a claimant. A person can certify as an alternate signer by submitting VA Form 21-0972. | ||
|
||
**applicant** | ||
|
||
We sometimes use this term to refer to 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 applicant”). Go to [Claims and applications](https://design.va.gov/content-style-guide/specific-topics-and-programs/claims-and-applications) for more guidance related to this word. In general, don't use "non-Veteran." | ||
|
||
**claimant** | ||
|
||
We sometimes use this term to refer to the person with the claim—-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.” When possible, use specific plain language instead, like “Veteran’s spouse” or “Veteran’s child.” Go to [Claims and applications](https://design.va.gov/content-style-guide/specific-topics-and-programs/claims-and-applications) for more guidance related to this word. In general, don't use "non-Veteran." | ||
|
||
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.” | ||
|
||
**court-appointed guardian or legal conservator** | ||
|
||
We use this term in the identity space. | ||
|
||
**fiduciary** | ||
|
||
We use this term for a person with legal permission to receive benefit payments and make financial decisions on behalf of a Veteran. | ||
|
||
**form submitter** | ||
|
||
We use this term, mostly internally, to refer to the person who's submitting the term. Don't use "form respondent." | ||
|
||
**next of kin** | ||
|
||
We use this term in specific forms and contexts to refer to people, often relatives, who can legally make certain types of decisions for a Veteran and act as a point of contact. Next of kin can represent a Veteran's wishes for care, medical documentation, and benefits, if needed. | ||
|
||
**power of attorney** | ||
|
||
We use this term to refer to the legal document that gives someone the permission to act on behalf of a Veteran in specific circumstances. We say that a person “has power of attorney” to describe their legal permissions. We don’t say that a person “is a power of attorney.” Since this term can mean many things depending on the context, we recommend replacing it with more specific terms, like "VA accredited representative," when appropriate. Don't use the initialism POA. | ||
|
||
Here are some types of power of attorney and related VA forms: | ||
- “Durable power of attorney for health care” is permission to make health care decisions on behalf of a Veteran. | ||
- VA Form 10-0137 gives this permission | ||
|
||
- “Power of attorney for VA purposes” is limited permission for accredited representatives to communicate with VA on behalf of a Veteran in the context of benefit applications. | ||
- VA Form 21-22 gives this permission for VSOs (and VSO representatives) | ||
- VA Form 21-22a gives this permission for accredited attorneys and claims agents | ||
|
||
**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”). Go to [Claims and applications](https://design.va.gov/content-style-guide/specific-topics-and-programs/claims-and-applications) for more guidance related to this word. | ||
|
||
**third-party representative** | ||
|
||
We use this general term for any person or organization with permission to act and communicate with VA on behalf of a Veteran. This includes accredited representatives, people with legal power of attorney, and fiduciaries. In most cases, we need to use more specific terms to describe the permissions a person has. | ||
|
||
**Veterans Service Organization (VSO)** | ||
|
||
We use this term for organizations accredited by VA to help someone with their VA claim or application. We no longer use the term “Veterans Service Officer.” You can use “VSO representative” after spelling out the acronym VSO once on a page. | ||
|
||
**Veterans Service Organization (VSO) representative** | ||
|
||
We use this term for individual representatives who belong to an accredited Veterans Service Organization (VSO). We no longer use the term “Veterans Service Officer.” You can use “VSO representative” after spelling out the acronym VSO once on a page. | ||
|
||
### Retired terms | ||
|
||
**form respondent** | ||
|
||
Use "form submitter." | ||
|
||
**Veterans Service Officer (VSO)** or **Veterans Service Representative (VSR)** | ||
|
||
Use “Veterans Service Organization representative” or “VSO representative.” VA’s Office of General Counsel accredits the organization, not the individual. | ||
|
||
|
||
## Content considerations specific to representatives | ||
|
||
Third-party representatives act or communicate **on behalf of** a Veteran — they don’t act **as** the Veteran. | ||
|
||
|
||
## Content-specific research findings | ||
|
||
|
||
**Content strategy-related findings** | ||
|
||
|
||
## Content pages related to this topic | ||
|
||
- [VA accredited representatives FAQs]((https://www.va.gov/resources/va-accredited-representative-faqs/) | ||
|
||
## Other notes |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"who's certified to sign certain VA forms on behalf of someone else. For example, signing a disability claim on behalf of a Veteran."
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm trying to keep "form" as the general term for the thing they're signing, and avoid making "claimant" the only term for the person if it might be broader than that. Does this work?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, that's a lot better. Thank you!!