Wealth Management Applications: Designing Client Intake

A wealth management application should reflect the service, account type and review process it supports. Customization is useful when it clarifies the information needed, not when it adds sales language or asks every client every possible question.

Start from a data and evidence map

List each field, why it is collected and where it is used. Identify which questions determine later questions and which require supporting documents. Separate a client’s answer from a fact checked by staff or another source.

For example, the legal name, contact name and authorized signer may refer to different people or entities. A clear form labels those roles instead of putting them into one name field.

Make conditional paths understandable

Use conditional questions to avoid irrelevant requests, but test every path. If a client changes an earlier answer, determine what happens to previously entered information and whether an attachment remains applicable. Hidden fields should not carry stale values into a review.

Explain why a requested document is needed and what makes it usable. Give an applicant a practical way to correct an error without creating a second, disconnected application.

Connect signatures to the reviewed version

Record which declarations and document versions the applicant accepted. If information changes after signing, the process must determine whether a new acknowledgment or review is needed. A completed signature and a completed account review are different states.

Keep a stable application identifier across the form, attachments and downstream system. Staff should not have to join records using an email address alone.

Test and govern changes

Use fictional records to test different client types, missing information and correction requests. Inspect the mobile view and the reviewer export. A successful submission should produce a coherent record, not just a confirmation email.

Approve template changes with the people who use the evidence. Document field changes and migration effects. This is general application-design guidance; it does not describe a currently offered Under application platform.