We are updating the "Overview" tab of the Claim Status Tool so that Veterans can see more details about their claim as it's being processed. Most importantly, we are moving from 5 "phases" to 8, and we are changing the names of some of those phases.
We have already collaborated with @laurwill on the content in the design itself. For this ticket, we specifically want to ensure that we track all changes to sitewide content where we currently mention the Claim Status Tool and the different phases.
Note: We work on nearly every OCTO product and manage all unauthenticated content on VA.gov, so we will need to prioritize intake requests based on overall workload and VA and OCTO priorities.
Is this work tied to a Congressional mandate, change in law or policy, or upcoming event with a specific deadline?
[ ] Yes
[x] No
[ ] I’m not sure
Where are you at in your timeline?
Tell us briefly about what you're working on now (such as initial discovery, wireframing, or usability research planning) and add any known dates for upcoming milestones or deadlines.
We just completed a Midpoint Review for this work. OCTO leadership expects us to ship this in June.
Will you release this new product incrementally (for example, release to 25% of users to start)?
[x] Yes
[ ] No
*Note: **If you check yes, we’ll reach out to discuss details about the content in the react widget. We use these widgets to display entry points for new products to a certain percentage of users who visit our static pages. Please refer to this GitHub reference for dynamic content.
[ ] I acknowledge that if I change the launch to be incremental, or change it from incremental to 100%, I must notify CAIA of this change as there is additional work involved that may impact deadlines.
Collaboration cycle
Which phases of the collaboration cycle have you completed?
Select all that apply.
[ ] Design intent
[x] Midpoint review
[ ] Staging
[ ] None. This initiative isn’t going through the collaboration cycle.
Collaboration cycle ticket
If you’re going through the collaboration cycle, provide your ticket number and link:
Provide links to any supporting artifacts that can help us better understand your initiative and begin collaboration. Include artifacts like your product outline, user flows, mockups and prototypes, or any draft content.
[ ] Post a link to this issue in the #sitewide-content-sitewide-content-accessibility-ia slack channel and tag @Terry Nichols, and we’ll then acknowledge receipt. We'll then review the artifacts in more detail and work with you to determine timing for collaboration. Depending on the work, we may schedule a kickoff meeting to better understand how we'll partner together.
[ ] Review the remaining next steps in the VFS team tasks section here.
[ ] If you also need engineering support from the public websites team, fill out their intake request form as well: Open a public websites intake request
Content, accessibility, information architecture (CAIA) new initiative collaboration request
Use this ticket to request collaboration on a new initiative with the sitewide content, accessibility, and information architecture (CAIA) team.
About your team
Benefits Management ToolsClaim Status ToolAbout your initiative
Which of these descriptions best fits the work we’ll partner on?
Select all that apply.
insert descriptionWhat's the nature of your initiative and desired outcomes?
Full context in this ticket.
We are updating the "Overview" tab of the Claim Status Tool so that Veterans can see more details about their claim as it's being processed. Most importantly, we are moving from 5 "phases" to 8, and we are changing the names of some of those phases.
We have already collaborated with @laurwill on the content in the design itself. For this ticket, we specifically want to ensure that we track all changes to sitewide content where we currently mention the Claim Status Tool and the different phases.
Examples include:
Collaboration timeframe
Note: We work on nearly every OCTO product and manage all unauthenticated content on VA.gov, so we will need to prioritize intake requests based on overall workload and VA and OCTO priorities.
Is this work tied to a Congressional mandate, change in law or policy, or upcoming event with a specific deadline?
Where are you at in your timeline?
Tell us briefly about what you're working on now (such as initial discovery, wireframing, or usability research planning) and add any known dates for upcoming milestones or deadlines.
We just completed a Midpoint Review for this work. OCTO leadership expects us to ship this in June.
Will you release this new product incrementally (for example, release to 25% of users to start)?
[x] Yes
[ ] No
*Note: **If you check yes, we’ll reach out to discuss details about the content in the react widget. We use these widgets to display entry points for new products to a certain percentage of users who visit our static pages. Please refer to this GitHub reference for dynamic content.
[ ] I acknowledge that if I change the launch to be incremental, or change it from incremental to 100%, I must notify CAIA of this change as there is additional work involved that may impact deadlines.
Collaboration cycle
Which phases of the collaboration cycle have you completed?
Select all that apply.
Collaboration cycle ticket
If you’re going through the collaboration cycle, provide your ticket number and link:
Supporting artifacts
Provide links to any supporting artifacts that can help us better understand your initiative and begin collaboration. Include artifacts like your product outline, user flows, mockups and prototypes, or any draft content.
Next steps
@Terry Nichols, and we’ll then acknowledge receipt. We'll then review the artifacts in more detail and work with you to determine timing for collaboration. Depending on the work, we may schedule a kickoff meeting to better understand how we'll partner together.Suggest an addition or update to the design system team