0781 release plan

[jinaryu]

Context: The delivery team needs to design release plan for the 0781. The outdated 0781a/0781 will only be accepted until April 2025, but some users may have in progress forms past this due date. (Proposal in Mural)

Questions to answer

1. Would the user be required to answer the new questions before submitting or could they opt out?
2. Are any of the new questions conditional based on any existing questions from either the 526 or the 0781/a already done?
3. Do any of the new questions require any specific evidence uploads that may not have been addressed in the current flow?

Acceptance Criteria

• [ ] Completed release plan for new claims
• [ ] Completed release plan for claims with in progress 0781/0781a
• [ ] Completed relevant designs (Figma)

[jinaryu]

Transferring notes from Zenhub ticket:

Sources of truth

• It is technically feasible to prefill new 0781 with old 0781 info
• Taking down the old 0781/0781a wouldn't be the best use of time and resources (better use would be toward building the new 0781)

Proposal:

• because these dates are both way later than goal launch for the new online 0781 (12/2024), we should let in progress "old 0781/0781a" be submitted
• better use of resources in building new 0781 rather than this rather short interim period

Plan (modeled after TE's two step launch):

• turn on new 0781 questions for new forms, roll out over month (could this be faster to limit the number of folks who could start the old 0781/0781a?)
• turn on new 0781 for in progress forms, roll out over month
• before new 0781 launched if user is in old 0781, alert guiding to new PDF on first page they left off, then alert goes away (example sketch)
• after new 0781 launched if user is in old 0781, alert guiding to new 0781, and prefill info from the old form (example sketch)
• if user has already completed an old 0781/0781a, allow them to submit it (no redirection, unless it's past 4/2025)

[jinaryu]

Notes from 7/31 meeting:

• what if we turn the new 0781 on only for people who haven't started the form?
• TE experience: once someone is on the new version, we don't go back (not reverting versions and losing data)
• what about folks who have mental health conditions other than PTSD?
• what are the implications of having 2 0781s in the efolder?
• if you've started answering any 0781, offer an obvious choice "there's a new form. you can choose to submit what you have or use the new form"
• after april cutoff, user doesn't have a choice. we send everyone to new 0781
• no in progress forms in canary
• direct users if they want to do PDF at the "do you want to fill it out or PDF version"
• we don't want to throw away peopl's data

[jinaryu]

note to self: review Katherine's thread from pension example

[jinaryu]

List of 0781 updates:

1. move POW question to step 1
2. add 0781 screener question to step 2 conditions
3. add a new step (step 3: additional forms)
4. move additional disability benefits to step 3
5. move 0781 to step 3
6. remove 0781a pages
7. update 0781 questions
8. update step 4: supporting evidence (new treatment flow, add in 0781 supporting docs)
9. change footer to VEO one

How this affects release plan:

• Essentially, the 0781 update affects steps 1-4 of the form (most of the form)
• The form updates don't just affect people who have a 0781, but also those who don't (because there are updates to the evidence section)
• I think it makes sense to bump everyone to the beginning given this fact

Proposal

• new user: bump to first page of new form; turn on updates
• in progress user: bump to first page of new form; turn on updates; prefill new 0781 with old 0781 data
• user on review and submit (completed 0781): allow user to submit old 0781 (no redirect on 0781); don't turn on updates
• add info alerts about form updates to static page and form intro page

[jinaryu]

Notes from 9/5 sync - knowledge sharing with TE team TE figma link

• Designed two alerts - save in progress (didn't end up implementing d/t complications), and review & submit
• Can we use the save in progress form alert for 0781 updates? - yes that's reasonable (ME)
• Why was save in progress form alert not feasible? Something about the way the code was structured, placing it in this spot would require customizing (Christine could have more context); mainly the location of the banner
• TE release: at launch, only new users would see TE questions, in progress users would see the alert that says it's optional
• review & submit:
• RS: i don't think it's bad to bump people to the first page, but it'd be good to have something to reorient them to the new experience
• If they click back enough times, they would see this page
• Would the TE page still show up on the review & submit page? - ME guess is yes
• Do we even want an alert on review & submit? There's already a TE one.
• There's guidance on design system component for alert - don't stack alerts
• If they click the TE link, it'll take them back to TE (can we have this be a general link?)
• ME: general sentiment from emily - err on side of too many notifications than not letting people know
• JP: we need an alert if we bump them back explaining why we're bumping them back "we've made updates, but all your info is saved and prefilled. we just want to give you a chance to refill the new questions"