A 90-Day Onboarding Plan for a New Paraplanner

Why 90 days is a framework—not a productivity promise

A 90-day structure creates three useful management checkpoints, but it is not evidence that every paraplanner should be independent by a fixed date. File complexity, prior experience, systems, licensee requirements, brief quality and reviewer consistency all affect progression.

General organisational research supports structured and supported on-the-job learning, but the evidence is not specific to Australian paraplanning and does not establish a universal time-to-productivity. Treat each stage as an evidence gate: progress, remediate, narrow scope or stop.

Before day one: make the practice ready

Do not make the new paraplanner discover the role by trial and error. Before access is granted, approve the work scope, excluded tasks, reviewers, escalation route, templates, complete-brief standard and communication rhythm. For an outsourced arrangement, complete the applicable provider, contract, privacy, security and licensee approvals first.

Create a compact onboarding pack: one annotated gold-standard file, a current template register, an assumption guide, a file-complexity rubric, an intake checklist and examples of acceptable escalation. If two advisers prefer different approaches, resolve or document the difference before expecting the paraplanner to infer it.

• Written role and responsibility boundaries
• Licensee and provider approvals where applicable
• Named reviewers and decision owners
• Current templates, examples and version control
• Work-ready intake checklist
• Privacy, security, access and incident arrangements
• Backup and offboarding owners

Define the operating lane

Paraplanning support can include file assembly, verified data entry, research compilation, controlled modelling, draft preparation, checklist-based quality checks and workflow records. The authorised advice function retains strategy judgement, approval of material assumptions, client suitability, substantive review and final release.

The role boundary should also state whether client or provider contact is allowed, which scripts or channels apply, what may be communicated, and which circumstances require immediate escalation. A managed provider can support the operating process, but cannot replace the practice’s or AFS licensee’s retained responsibilities.

Days 1–30: foundation and controlled practice

The first month is for safe operating habits, not independence theatre. Introduce the practice proposition, licensee framework, advice journey, systems, templates, source standards and escalation expectations. Use demonstrations, annotated examples and training cases before narrowly scoped live work.

Begin with file preparation and lower-complexity, repeatable tasks. Require the paraplanner to show source documents, assumptions, unanswered questions and self-check evidence. Hold short, frequent calibration sessions so feedback becomes a documented rule rather than a private preference.

• Days 1–10: access, security, workflow and knowledge checks
• Days 11–20: shadow files and supervised preparation
• Days 21–30: controlled live work within a narrow approved scope
• Day-30 gate: safe systems use, sound escalation and usable low-complexity work

The day-30 readiness gate

Progression should require evidence that mandatory induction is complete, approved systems are used safely, role boundaries are understood and low-complexity work can be returned with appropriate escalation. Any unresolved security event, unauthorised access or attempt to provide advice outside the approved role should stop progression.

Do not evaluate only completed volume. Early questions can be a positive control when they identify missing facts or unclear instructions before an error reaches the document. Assess whether questions are timely, relevant and increasingly informed.

Days 31–60: supervised production

The second month moves from learning the workflow to producing standard workpacks under structured review. Increase variety gradually, keep complexity labels visible and continue substantive review. Ask the paraplanner to explain material inputs, identify conflicts and perform self-QA before handback.

Run a dual feedback loop: the adviser or authorised reviewer addresses advice judgement and final suitability; the operational quality review addresses brief completion, calculations, consistency, template control and record evidence. Every recurring correction should update the preference log, SOP, template or training example.

• Use a representative but controlled standard-file mix
• Measure cycle time only from an accepted complete brief
• Separate provider defects from missing inputs and new reviewer preferences
• Track repeat defects to see whether feedback is being learned
• Day-60 gate: standard files require comments and correction—not reconstruction

The day-60 readiness gate

Before expanding scope, confirm that workpacks are submitted complete, self-QA is visible, feedback is applied, repeated defects are reducing and escalation remains timely. Reviewer confidence should support a defined next lane, not unlimited complexity.

If progress is behind, freeze new complexity. Conduct a file autopsy on recent rewrites, classify the root causes, provide targeted examples and set a dated remediation decision. Adding more volume to an unstable process makes the backlog larger, not the capability stronger.

Days 61–90: earned ownership

During the final phase, the paraplanner should establish a dependable rhythm for an agreed range of work—not become an unsupervised adviser. Move towards normal queue planning, proportionate operational QA and stable communication while retaining substantive review and approval with the appropriate authorised people.

Test continuity before declaring onboarding complete. A current SOP, work-in-progress board and controlled handover should allow an approved backup to understand the supported workflow without relying on private memory. The goal is resilient practice knowledge, not dependency on one person.

• Stable performance by approved work type and complexity
• Reviewer time and rework trends understood
• Current access remains proportionate
• Escalation occurs before silent assumptions
• Backup and handover arrangements tested
• Day-90 decision documented

Measure what buyers actually care about

Attendance, completed training modules and raw file count do not prove dependable capacity. Measure whether work is increasingly complete, correctly controlled and ready for substantive adviser review.

Agree definitions before collecting data. ‘First-pass acceptance’ should mean accepted without material paraplanning rework, not a document that merely entered review. ‘Cycle time’ should begin when the brief is accepted as complete, so missing information is not confused with production time.

• First-pass acceptance by work type and complexity
• Material rework and defect severity
• Reviewer minutes per file
• Clarification rate and recurring missing inputs
• Cycle time from complete brief to reviewer-ready submission
• Repeat-defect trend
• Correct and timely escalation
• Access reviews and continuity coverage

Classify the cause before coaching the person

Not every correction is a paraplanner performance problem. Separate incomplete input data, an ambiguous adviser brief, an outdated template, a technical paraplanning defect, a compliance-process gap, an undocumented reviewer preference, a system issue and an external delay.

This classification protects both quality and fairness. It prevents the practice from repeatedly coaching a person for an error created upstream, while making genuine skill or process gaps visible enough to address.

Internal and managed onboarding share the same control objective

Internal and outsourced paraplanners both need role clarity, appropriate access, practice knowledge, quality review, feedback and escalation. Offshore delivery adds fact-specific provider, privacy, cross-border, security and continuity considerations; it does not make the underlying onboarding principles different.

A managed arrangement can potentially reduce coordination by supplying agreed recruitment, workforce supervision, reporting, quality support or continuity mechanisms. Those services must be verified in the actual provider scope. The practice and licensee still retain responsibility for advice governance, provider oversight, access approval and substantive review.

What each party owns

The practice defines its file standard, work scope, reviewers and operating priorities. The AFS licensee establishes and oversees the applicable governance framework. A managed provider supplies the contracted workforce and service-management mechanisms. The paraplanner follows the approved process, self-checks work, asks questions and escalates exceptions.

Responsibility matrices are useful operational tools, but they do not transfer statutory obligations. Names, evidence and due dates should sit beside each responsibility so that ‘shared’ does not become ‘nobody’.

Questions practices ask about the first 90 days

Should a new paraplanner produce a complex SOA independently by day 90? Not automatically. Independence applies only to the approved preparation lane and remains subject to appropriate review; complexity should expand when evidence supports it.

What if two advisers review differently? Create one core file standard and explicitly document permitted adviser variations. Do not make the paraplanner reverse-engineer preferences from conflicting mark-ups.

What if a previous outsourced arrangement failed? Diagnose incomplete briefs, changing templates, missing calibration, skill mismatch, access delays and reviewer inconsistency before assuming the location caused the failure.

Where can AI help? Approved automation may assist bounded preparation or formatting tasks, but it does not remove the need for verified source information, role boundaries, human judgement, quality control and accountable records.

How do we know onboarding worked? At day 90, the practice should be able to show the approved work lane, quality and reviewer-effort trends, current access, sound escalation, documented knowledge and a clear continuation decision.

The day-90 decision

Finish with a written decision: continue the current scope, expand selected work types, remediate a defined gap, restrict access or responsibility, replace the resource through the agreed process, or exit. Record the evidence and the next review date.

A properly managed onboarding process makes that decision easier because expectations, feedback and controls are visible from the beginning. It turns outsourcing from a staffing transaction into dependable capacity built around the practice’s way of working.