Paraplanning Quality Assurance: A Checklist for Advice Practices

Quality is an operating system—not a final inspection

Quality spans factual accuracy, completeness, reproducible calculations, current research, consistency, appropriate escalation, controlled templates, secure handling, timely flow and an audit trail. A document can be beautifully formatted and still contain the wrong assumption, an unsupported strategy or an implementation inconsistency.

Build controls at intake, production, technical review, adviser review, release and post-completion learning. Final inspection is late and expensive: it discovers defects after the practice has already spent most of the production effort.

Accountability does not move with the task

ASIC says advice licensees may outsource administrative functions, advice support and paraplanning, while retaining responsibility for complying with their obligations. Its guidance points to due skill and care in provider selection, ongoing performance monitoring and appropriate action when a provider breaches service levels or relevant obligations.

The authorised advice function retains client-specific strategy judgement, approval of material assumptions, assessment of suitability, substantive review and final release. A paraplanner or outsourced team can assemble evidence, research, model and draft within an approved lane—but a provider QA stamp cannot approve personal advice.

ASIC’s offshore review is a control warning—not a prohibition

ASIC’s October 2025 work examined 10 selected advice licensees using offshore providers through intermediaries and engaged with six intermediaries. The principal offshore functions included paraplanning and administration. ASIC was concerned that most licensees reviewed lacked adequate arrangements for assessment, appointment and ongoing monitoring.

That targeted sample is not a population-wide estimate and does not show that offshore work caused poor advice. It does show why a practice needs its own evidence of roles, access, monitoring, incidents, performance and remediation rather than relying on broad provider assurances.

Gate incomplete work before production

The first QA decision is whether the file is ready to start. Confirm the client and entity structure, scope, authorised adviser, source documents, strategy instruction, assumptions, complexity, due date, approved template and escalation contacts. Record contradictions rather than choosing the most convenient value.

A red brief should not enter the production queue. Pausing at intake is not poor service; it prevents silent assumptions, false turnaround reporting and expensive downstream reconstruction.

• Unique file ID and named authorised adviser
• Explicit work scope and required output
• Current, legible source evidence
• Documented objectives, constraints and strategy instruction
• Approved assumptions, template and research sources
• Complexity and enhanced-review triggers
• Named technical, advice, compliance and security escalation contacts

Separate four different review jobs

Self-QA asks whether the preparer followed the brief, reconciled data and completed the approved checklist. Operational QA checks completeness, process, template control and handover evidence. Technical review tests research, calculations, product detail and internal consistency. Adviser review applies professional judgement to the client’s circumstances, strategy, suitability, explanation and final release.

Compliance review may add independent testing or examine particular regulatory and licensee controls, but it should not be treated as the first place basic production problems are found. Naming each layer prevents duplicated work and stops an operational checker from being mistaken for the advice decision-maker.

Review source evidence before prose

Reconcile names, dates, ownership, balances, liabilities, income, policies, product details and fees against current attributable sources. If the fact-find, platform record and provider statement conflict, log and escalate the discrepancy before modelling or drafting.

A reviewer should be able to trace every material input to its source and determine which version was used. Typed recollection should not silently displace an approved source document.

Make calculations reproducible

Record material inputs, assumptions, model version, time periods, fee treatment and scenario logic. Independently check material calculations and confirm that tables, graphs and narrative use the same outputs.

Higher-risk matters—such as major replacements, complex entities, insurance changes, novel strategies or files affected by a known model defect—may justify enhanced independent technical review. The appropriate intensity is a practice and licensee decision based on evidence and risk.

Test the document as one connected system

Research, modelling, strategy instructions, recommendations, fees, risks, disadvantages, replacement implications and implementation steps should agree. Check that the correct client, product, entity and version appear in every relevant section and attachment.

Internal inconsistency is particularly dangerous because each individual paragraph may appear reasonable. Cross-check the recommendation against the implementation form, fee table, projections, risks and file note—not merely against the preceding page.

Use a severity model that protects the client

Classify corrections by potential impact, not by who made them or how embarrassing they feel. A minor formatting issue differs from a material calculation or incorrect fee; an unsuitable recommendation, wrong-client release or unauthorised data access requires immediate containment and escalation.

Define severity locally with the compliance function. Major or critical matters should stop release, preserve evidence and trigger the applicable advice, compliance, privacy or security pathway. Never allow a blended quality percentage to hide a critical event.

• Minor: presentation issue without impact on meaning or control
• Moderate: clarity, completeness or process weakness requiring correction
• Major: could affect facts, calculations, fees, implementation, disclosure or client understanding
• Critical: actual or likely serious client harm, unsuitable advice, systemic failure or serious privacy/security concern

Find the origin—not just the person who found it

Code incomplete sources, ambiguous instructions, obsolete templates, transcription errors, research gaps, model defects, internal inconsistency, technical errors, advice-judgement issues, compliance gaps, undocumented reviewer preferences and system failures separately.

Origin, detection and containment failure may belong to different parts of the workflow. This makes coaching fairer and exposes upstream changes that can prevent recurrence across every file.

Measure accepted output and hidden effort

Raw file count and fastest turnaround are poor standalone measures. Track first-pass acceptance, material rework, defect severity, repeat defects, reviewer minutes, clarification, complete-brief rate, median cycle time, on-time completion and access exceptions together.

Segment results by work type and complexity. Agree definitions before measuring: first-pass acceptance should exclude files needing material paraplanning rework, and the production clock should begin only when a brief is accepted as complete. No authoritative Australian benchmark was identified for these measures, so compare the practice with its own baseline rather than a marketing average.

Close every material defect loop

Contain the issue, preserve evidence, classify severity and root cause, assign an owner and determine whether wider files, templates, access or systems may be affected. Correct the file and the control that allowed the issue—not merely the visible wording.

Verify the fix through re-sampling. If the defect recurs, reopen the action. Trends should update briefs, SOPs, templates, training, access design and provider-performance discussions so QA becomes a learning system.

• Detect and contain
• Classify defect, severity and detection point
• Assess materiality and required escalation
• Identify evidence-based root cause
• Correct the affected work and prevent recurrence
• Assign owner, due date and approval evidence
• Test effectiveness and reopen if necessary
• Report trends and update the operating system

Interrogate provider quality claims

Words such as ‘rigorous QA’, ‘fast turnaround’ and ‘high quality’ have little decision value without definitions. Ask who reviews each file, what their authority is, which checklist and template version apply, how defects are classified, when the service clock starts and how adviser rewrite time is measured.

A managed model can add recruitment, role matching, onboarding, operational QA, coaching, scorecards and continuity to the individual resource. Those elements must be confirmed in the actual service scope. Certifications and guarantees can inform due diligence, but they do not prove advice quality or remove active licensee oversight.

• Who reviews this work, and independently of whom?
• What constitutes a material defect or first-pass acceptance?
• How are incomplete briefs and changed scope recorded?
• Which results are segmented by complexity and work type?
• How are repeat defects coached and verified as resolved?
• What evidence can the practice retain for monitoring?
• How are access, incidents, leave, replacement and exit handled?

When a practice is not ready to scale

Outsourcing will export inconsistency when no one can define a finished file, templates are uncontrolled, every reviewer applies hidden preferences, the licensee has not approved the arrangement or no internal owner has time to review and improve it.

That is an implementation requirement—not an argument against outsourcing. Start by documenting one repeatable workflow, one complete-brief standard, one reviewer and one scorecard. A managed discovery and controlled pilot can expose the gaps before a larger team amplifies them.

The practical quality standard

The goal is not zero comments. It is dependable, reviewer-ready work with traceable inputs, visible assumptions, appropriate escalation and fewer repeated material corrections. Adviser review should become more focused on professional judgement, never reduced to an automatic approval click.

For an outsourced engagement, buy and govern the production system around the person: clear scope, controlled intake, relevant capability, layered QA, measurable feedback and continuity. That is how support becomes usable capacity while responsibility remains where it belongs.