Structured intake keeps the chosen commercial path intact
Identity and documents
Passport upload, address details, and supporting verification documents.
Portal-native upload cards replace fragmented email attachments and should later support review states and replacement uploads.
The future vault should reopen pending uploads with review state and replacement controls.
Identity uploads require file-type checks, completeness checks, and review-state visibility.
Primary identity artifact with later review state and replacement path.
Only mandatory if review or compliance requests address confirmation.
Additional identity context can be attached without falling back to email.
The client should upload identity and support files directly into TAVALIS, not through scattered mail attachments.
Each artifact should show whether it is prepared, conditional, accepted, or requires replacement.
Customer-visible document slots should later surface the safe projection of reviewed artifacts and issued records.
Legacy ShareFile remains acceptable as a bridge, but the customer-facing truth should converge into TAVALIS.
Primary identity artifact with later review-state and replacement handling.
Only required when review or compliance explicitly asks for it.
Summary pack that bridges intake completion into signature and order handoff.