Start with one shared request
Name the account holder, representative, purpose, affected account relationship, requested actions, exclusions, and end date before anything is sent. This gives every later step the same boundary.
Passage field note
A clearer operating model for financial POA requests
Separate what each person supplies from what the institution reviews and decides.
Keep different decisions separate
An identity result says who someone appears to be. A document review records what was examined. A representative chooses whether to accept responsibility. The institution alone records what it will accept.
Make the next action obvious
Each person should see the current status, what they need to do, what will be saved, who can see it, and how to recover. Long activity histories should support the task rather than obscure it.
Preserve later changes
A revocation, withdrawal, or expiration should update the current status without rewriting the original decision. That distinction makes the record easier to operate and explain.
See the workflow in practice.
Use sample information to experience the request from the institution and participant sides.