Process overview
AdvisorOne is designed as a guided advisory workflow. Advisers collect information, run planning tools, review outputs, and approve final documents before client use.
- 1. Setup account and profile
- 2. Add and maintain client data
- 3. Run tools and document outputs
- 4. Review, approve, and maintain history
Step-by-step timeline
Step 1: Adviser account creation and sign-in
What the adviser does: Registers an AdviserOne account and signs in securely.
What is stored: Account identity, login details, and account metadata.
Why it is required: Needed to secure access and isolate adviser workspaces.
Next step: Complete practice and compliance profile details.
Step 2: Practice and compliance profile setup
What the adviser does: Captures FSP and compliance profile details in Settings.
What is stored: Practice profile, adviser contact details, compliance fields.
Why it is required: Used in generated disclosure and advice documentation.
Next step: Activate trial or subscription billing.
Step 3: Subscription or free-trial activation
What the adviser does: Completes trial or billing setup and confirms account activation.
What is stored: Subscription status, billing schedule, and payment references.
Why it is required: Enables ongoing platform access and billing controls.
Next step: Create a new client record.
Step 4: Create a new client
What the adviser does: Adds a client profile from the Clients workspace.
What is stored: Client identifier, core profile, timestamps, adviser ownership.
Why it is required: Creates the base record for all advice workflows.
Next step: Capture identity and contact details.
Step 5: Capture identity and contact information
What the adviser does: Records names, contact channels, and identification details.
What is stored: Client demographic and identity data.
Why it is required: Supports suitability, disclosure, and record-keeping obligations.
Next step: Record consent and required disclosures.
Step 6: Record consent and required disclosures
What the adviser does: Captures consent status and disclosure-related information.
What is stored: Consent indicators and compliance context fields.
Why it is required: Supports legal and compliance obligations in advisory workflows.
Next step: Capture financial and planning information.
Step 7: Capture financial planning inputs
What the adviser does: Captures income, expenses, assets, liabilities, dependants, policies, investments, estate data, and goals.
What is stored: Structured client financial and goal-planning data.
Why it is required: Powers calculations, needs analysis, and planning recommendations.
Next step: Save and manage the client record.
Step 8: Save, update, and manage the client record
What the adviser does: Maintains and updates client information as facts change.
What is stored: Current profile plus update timestamps and related records.
Why it is required: Ensures advice is based on current and accurate information.
Next step: Complete risk assessment.
Step 9: Complete the client risk assessment
What the adviser does: Assesses risk needs and relevant planning exposures.
What is stored: Risk-related inputs and outputs for advisory context.
Why it is required: Informs suitability and recommendation development.
Next step: Use planning tools.
Step 10: Use financial-planning tools
What the adviser does: Uses Estate Liquidity, Investment Analysis, Risk-Needs Analysis, Family-Income Provision, and Education Funding tools.
What is stored: Tool-specific assumptions, outputs, and planning records.
Why it is required: Supports analysis depth and quantifies client needs.
Next step: Review assumptions and shortfalls.
Step 11: Review assumptions, calculations, and shortfalls
What the adviser does: Checks assumptions, result realism, and identified gaps.
What is stored: Updated assumptions and reviewed calculation context.
Why it is required: Improves quality control before recommendations are drafted.
Next step: Record recommendation options.
Step 12: Record recommendations and possible product solutions
What the adviser does: Drafts potential recommendation paths and product options.
What is stored: Recommendation notes and implementation placeholders.
Why it is required: Forms the advisory narrative before document generation.
Next step: Generate an FNA.
Step 13: Generate a Financial Needs Analysis
What the adviser does: Creates the FNA document from reviewed data and assumptions.
What is stored: Generated FNA document and associated metadata.
Why it is required: Documents needs analysis and planning rationale.
Next step: Generate an ROA.
Step 14: Generate a Record of Advice
What the adviser does: Produces the ROA aligned to selected recommendations.
What is stored: Generated ROA record and reference links.
Why it is required: Captures recommended advice decisions for client engagement.
Next step: Review and approve generated documents.
Step 15: Review and approve generated outputs
What the adviser does: Validates all generated calculations and document content.
What is stored: Revision history and latest approved version context.
Why it is required: Adviser remains responsible for final accuracy and compliance.
Next step: Capture final disclosures and compliance context.
Step 16: Record disclosures and compliance information
What the adviser does: Captures disclosures, replacement advice, and compliance notes.
What is stored: Compliance records attached to the advisory workflow.
Why it is required: Supports regulated record-keeping and audit readiness.
Next step: Export and store completed documents.
Step 17: Export, download, or store completed documents
What the adviser does: Downloads or stores final advisory outputs for client records.
What is stored: Document files, links, and document-state metadata.
Why it is required: Enables client delivery and controlled document lifecycle.
Next step: Update records when circumstances change.
Step 18: Update records when client circumstances change
What the adviser does: Revisits client profile and planning assumptions over time.
What is stored: Updated client data and revised planning outputs.
Why it is required: Keeps advice relevant to changing client needs.
Next step: Conduct periodic reviews.
Step 19: Conduct future reviews and advice maintenance
What the adviser does: Performs periodic client reviews and refreshes recommendations.
What is stored: Ongoing review history and updated advisory documents.
Why it is required: Supports long-term client servicing and continuity.
Next step: Maintain audit-ready history.
Step 20: Maintain advice history
What the adviser does: Maintains a complete timeline of advisory decisions and outputs.
What is stored: Historical versions, records, and compliance context.
Why it is required: Supports defensible advice records and operational continuity.
Next step: Continue iterative planning cycle.
How client data is organised
Client records are organised per adviser workspace. Each client profile acts as the anchor for related planning data, tool outputs, generated documents, and updates over time.
- Core identity and contact profile
- Financial and planning inputs
- Tool outputs and assumptions
- Document records and status
- Review history and updates
Draft versus completed documents
Draft outputs are working versions that may still contain incomplete fields, provisional assumptions, or pending adviser review. Completed outputs are versions that the adviser has reviewed, approved, and accepted for client-facing use.
Adviser responsibility and regulated advice
AdvisorOne supports the advice process with data handling, calculations, and document generation, but does not independently provide regulated financial advice.
The adviser and FSP remain responsible for verifying all generated outputs, appropriateness of recommendations, and compliance with applicable legal and regulatory obligations.
Detailed guides coming soon
The following detailed documentation pages are planned for future release:
- Estate Liquidity deep-dive guide (placeholder)
- Investment Analysis assumptions guide (placeholder)
- Risk-Needs Analysis workflow guide (placeholder)
- Compliance document review checklist (placeholder)
- Subscription, retries, and account status matrix (placeholder)
Need help with a workflow?
If a workflow is unclear or a generated output does not match expectations, use theContact page and include the relevant category, client reference, and impacted step number.