Form Submitter Pattern Question / Answers

[tbaker1026]

Current documentation:
Help users to identify who is filling out a form

This pattern helps VA forms figure out two important things:

• Who is filling out the form (the person typing or writing)
• Who the form is about (the person who will get the benefits)

Sometimes these are the same person. Sometimes they're different.

When to Use This Pattern
Use this pattern when your form can be filled out by:

• Veterans for themselves
• Claimant for themselves
• Family members / Alternate Signer for a Veteran or Claimant
• Third party filling out for a Veteran or Claimant

Please share your use cases, form name/ number, figma designs and the team you are on.

[eileen-coforma]

Pattern documentation has been released.

Provide examples, feedback, or ask questions.

Teams already using this pattern, please let us know which forms they are being used on. Thanks!

[chumpy]

Hi! posting on behalf of the Accredited Rep Crew. We're just seeing this so apologies for being late to the party. We have a sub application where accredited representatives login and authorize as accredited reps so they can submit forms on behalf of veterans and their dependents. I'm not sure how the pattern might apply to us since the third party is already known via logged in state and backend authorization as a rep but since our whole world revolves around third party form submission perhaps it's better late than never to let you know our use cases for this.

Currently we support 22-686c, 22-526ez, and 22-096.

Our figmas:

• 526ez
• 686c
• 096 ITF

686c and 526ez are live and ITF is releasing next week.

Our main slack channel is #benefits-accredited-rep-crew

Please let us know if you'd like anymore info. I guess our first question is, since we wouldn't want the rep to have to explicitly identify themselves (because we've already authorized them as a rep and they are in a rep-only space), does this pattern apply to us at all?

Thanks!