A structured intake should feel guided, resumable, and operationally clean.
This page now acts as the intake hub: each step has its own preview state, clear checkpoint model, and a dedicated entry path for the later portal-native flow.
Structured work starts here without losing the commercial context
Intake is the first real customer workspace inside TAVALIS. Public pages explain scope, but structured customer work should start here — before protected portal modules open.
The customer should understand service lane, package scope and commercial posture before entering structured work.
Customer data should move into guided intake instead of scattered email or PDFs.
The finish step should connect review, signature, checkout and the accountable order state.
After activation, the customer should continue with status, documents, tasks, messages and billing visibility inside the portal.
Captures the legal setup baseline before downstream review and filing work begins.
Captures beneficial ownership, responsible party and tax-relevant person data in one accountable structure.
Keeps required files and identity evidence attached to the intake record instead of email threads.
Connects summary, consent, signature and payment readiness into one final accountable transition.
Owners and responsible parties
This step establishes the beneficial ownership, responsible party, and tax-relevant person data needed for the later operational path.
Owners added
Responsible party identified
Tax data prepared
Owners can be added across multiple sessions without losing partial structure.
Ownership totals, responsible party logic, and tax-relevant person data stay under validation watch.
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.