You give a command
Describe the client task, review or operational outcome.

ADIAL is configured to your people, permissions, templates, compliance settings and approved systems. Ask for the work in plain language and ADIAL coordinates the authorised tools and specialist capabilities behind it.
Your single command point
You do not need to search across disconnected tools, log into several platforms or work out which capability to use. Tell ADIAL what you need. It gathers approved context, coordinates the permitted workflow and returns the result, questions and evidence in one place.
ADIAL only accesses systems, data and actions approved for the user and workflow. Sensitive updates, advice decisions and final approvals remain with authorised people.
Describe the client task, review or operational outcome.
Uses approved data, Xplan workflows, templates, tools and controls.
The completed outcome, gaps, source evidence, status and required approvals are returned for review.
Service catalogue
Choose your role to see the practical work ADIAL can prepare, coordinate and track.
FOR ADVISERS
Tell ADIAL what needs to be prepared so you can focus on the client, the strategy and the professional decisions.
Summarise the client record, previous advice, product position, open commitments, service history, likely discussion points and information gaps before the meeting.
Try: “Prepare me for tomorrow’s meeting and show the three decisions or missing facts I need to address.”Extract approved information, structure it against required fields, identify conflicts and prepare validated entries for Xplan or another approved system.
Try: “Update the client record from these approved documents and show me every field that needs confirmation.”Turn meeting notes, transcripts and correspondence into an articulate file note with decisions, scope, actions, owners and unresolved questions.
Try: “Prepare the file note from today’s meeting and create the follow-up actions.”Populate the fact find, reconcile it with approved source data, flag missing or inconsistent facts and prepare confirmed information for controlled entry into Xplan.
Try: “Complete the fact find, add the confirmed data to Xplan and return the gaps.”Assemble the facts, assumptions, scope and supporting evidence required for approved Xplan wizards, then route questions and outputs for human review.
Try: “Prepare the Xplan wizard for this advice scope and tell me which inputs are still missing.”Use the Xplan merged SOA, approved templates, research, modelling outputs and adviser direction to prepare a client-specific SOA with the required rationale, alternatives and disclosures.
Try: “Build the tailored SOA from the Xplan merge and this approved strategy brief.”Review required sections, evidence, consistency, client-specific wording, source links and defined compliance rules; return findings and corrections for a qualified person.
Try: “Audit this SOA against our approved standard and give me the issues by severity.”Coordinate approved product research, comparisons, modelling inputs and client-specific advantages and trade-offs into a review-ready evidence pack.
Try: “Prepare the comparison pack and identify the trade-offs that need adviser judgement.”Coordinate authorities, applications, provider follow-ups, outstanding evidence, client communications and completion status.
Try: “Show me every open implementation action for this client and draft the next follow-ups.”Coordinate welcome steps, document requests, progress updates, review preparation, ongoing service promises and proactive follow-ups so clients know what is happening and why it matters.
Try: “Show me which clients have not heard from us this quarter and prepare the right next contact for each one.”FOR PRACTICES
Give your team one place to tell ADIAL what needs to happen while keeping client work, service commitments, handoffs and quality controls visible.
Show active cases, accountable owners, blocked tasks, deadlines and the next action.
Try: “Show today’s blocked advice cases and who needs to act.”Surface bottlenecks, ageing work and handoff pressure before service standards are affected.
Try: “Which team member can take the next three SOAs?”Monitor reviews, follow-ups, implementation work and agreed service actions across the practice.
Try: “List overdue annual-review actions and draft the internal task plan.”Run approved checks and route incomplete, inconsistent or sensitive work for the right human review.
Try: “Run the pre-handoff checks on every advice file due this week.”FOR PARAPLANNERS
Tell ADIAL to standardise intake and production while applying the correct adviser, firm and licensee settings to each case.
Assemble adviser instructions, authorities, file locations, advice scope and missing inputs.
Try: “Triage this brief and send me only the questions that stop production.”Reconcile fact find data, research inputs, modelling dependencies and conflicting information.
Try: “Validate the inputs and prepare the Xplan data query list.”Prepare tailored SOAs and ROAs using the approved template, terminology, evidence and licensee rules.
Try: “Build the SOA for this client using Firm A’s approved template and review rules.”Coordinate checks, source links, versions, adviser feedback and final handoff evidence.
Try: “Complete QA and prepare the adviser review pack with open issues first.”FOR AFSLs + LICENSEES
Tell ADIAL to coordinate pre-vetting, file review, exceptions and network oversight using approved standards with traceable evidence.
Check defined mandatory sections, evidence, consistency, client-specific wording, approved-product requirements and escalation triggers.
Try: “Pre-vet this SOA and return the findings by risk level and clause.”Assess defined file-note requirements, scope, client discussions, consent, decisions, actions and gaps requiring reviewer judgement.
Try: “Review the file note against our approved standard and show unsupported advice elements.”Organise the sample, source evidence, findings, severity, responsible owner, reviewer decision and completion status.
Try: “Build the file-review pack and identify missing evidence before reviewer allocation.”Make the correct SOA structures, review rules, evidence expectations and approval points available inside each authorised workflow.
Try: “Apply the current licensee SOA standard to all new pre-vet workflows.”Route exceptions, assign owners and due dates, preserve responses and evidence completion or escalation.
Try: “Show overdue high-risk findings and the evidence still required for closure.”Monitor recurring review findings, evidence gaps, remediation, control performance and operational risk across authorised practices.
Try: “Summarise this quarter’s recurring SOA findings and link each trend to the underlying files.”FOR INSTITUTIONS
Deploy ADIAL by business unit, role or workflow while preserving identity, permissions, local variation, oversight and change control.
Define what each agent may read, prepare, propose, update or escalate.
Prepare records, route tasks, standardise handoffs and surface missing evidence.
Connect results to sources, versions, tests, approvals, exceptions and remediation.
Monitor workflow outcomes, control performance, service levels and approved change.
We will map the systems, data, controls, human approvals and outputs needed to make it work safely.
Design how we use ADIAL