Ad Hoc vs Dedicated Paraplanner: Which Model Fits Your Practice?

First, define what you are buying

Ad hoc paraplanning is support requested for a particular need without permanently reserved capacity. It may be priced per file, hour or task bundle. Dedicated paraplanning reserves a named person or stable allocation for a practice, either full-time or part-time. A hybrid model combines a core allocation with flexible overflow.

Labels are not enough. A proposal should state the allocation, included tasks, work location, priority rules, turnaround basis, reviewer responsibilities, backup cover, systems access and exit process. ‘Dedicated’ may otherwise mean anything from a full-time named person to priority access to a shared pool.

• Ad hoc or per-file: capacity purchased when required
• Dedicated: a stable resource or allocation reserved for the practice
• Hybrid: core reserved capacity plus planned overflow
• Managed offshore: the provider adds recruitment, HR and service-management layers
• Direct remote engagement: the practice carries more employment, continuity and management responsibility

Why capacity planning matters

ASIC reported 15,663 advisers on its register at 1 March 2024. FAAA later reported 15,127 advisers at 12 March 2026, compared with almost 29,000 at the start of 2019. The definitions and dates differ, so these figures should not be combined as a single official series; they do, however, illustrate sustained workforce pressure.

There is no reliable current national benchmark for the proportion of Australian advice practices using outsourced paraplanning, typical provider prices, document turnaround, first-pass acceptance or offshore savings. Any provider claiming a universal crossover point should therefore be tested against your own files and workflow data.

When ad hoc support is the better fit

Ad hoc support is most useful when demand is irregular, a practice needs short-term surge capacity, a team member is absent, or the practice wants to test a provider on a narrow workflow before making a larger commitment. It can also suit discrete, standardised packages where the inputs and acceptance criteria are clear.

The trade-off is repeated context. Each allocation may need fresh briefing, clarification and review, and queue position may be less predictable. A low per-file quote can become expensive if adviser and operations time spent packaging, chasing and correcting work is excluded.

• Irregular new-advice files or seasonal peaks
• Temporary backlog or leave cover
• A controlled pilot of one repeatable file type
• Clearly bounded tasks with complete source material
• A practice not yet ready to manage reserved capacity

What can break in a per-file queue

A per-file model becomes operationally noisy when the writer changes, each job rebuilds practice context, or incoming files are not work-ready. Turnaround may look acceptable while adviser time is absorbed by repeated explanations, status chasing and inconsistent corrections.

That does not make ad hoc support a poor model. It makes briefing discipline and queue transparency essential. A good ad hoc service should define what counts as a complete brief, how complexity is classified, where the file sits, what acceptance means and how feedback carries into the next allocation.

• Changing writers and inconsistent document voice
• Repeated explanation of templates and reviewer preferences
• Unclear queue position during demand peaks
• Per-file charges that exclude coordination and rework
• Feedback that remains attached to one file instead of improving the system

When dedicated support is the better fit

Dedicated support is generally better aligned to a stable or growing workload, recurring task patterns and workflows where knowledge of the practice’s systems, templates and reviewer preferences can compound over time. Reserved capacity can make planning more predictable and create a regular rhythm for training and quality calibration.

The trade-off is commitment and management. Capacity can be underused when the pipeline falls, and a named person can become a key-person dependency if documentation and backup cover are weak. Familiarity is not a control: adviser review, access governance and performance evidence remain necessary.

• A reliable prepared backlog
• Recurring advice-production tasks and systems
• A need for retained practice knowledge
• Management capacity for coaching and weekly planning
• Documented leave cover, cross-training and transition arrangements

What dedicated capacity actually buys

Dedicated support should buy more than attendance. Its value is reserved time, continuity and the opportunity to turn repeated feedback into retained practice knowledge. The resource can learn the current templates, file conventions, escalation preferences and working rhythm instead of reconstructing them for every job.

The commercial test is whether that familiarity reduces clarification, repeated briefing and material rework while improving capacity predictability. A named person without documented processes, quality calibration or backup remains a fragile arrangement rather than a mature dedicated model.

• Reserved capacity with defined priority rules
• A shared knowledge base rather than memory alone
• Regular calibration using coded feedback
• Visibility of utilisation and accepted output
• Backup coverage and an orderly transition path

Do not confuse delivery model with location

A dedicated paraplanner may be onshore or offshore. An offshore paraplanner may be directly engaged or supplied through a managed provider. Ad hoc work can also be completed in either location. These dimensions affect different risks and should be assessed separately.

ASIC’s 2025 review of 10 advice licensees found governance and monitoring gaps in offshore-provider arrangements and emphasised that licensee obligations remain. The review does not show that one commercial model or location is inherently safer. It shows why selection, access control, monitoring, review and corrective action must be demonstrable in every model.

Compare total cost per accepted output

Provider price is only one component. Add internal briefing time, clarification, substantive review, correction, workflow administration, technology, security oversight and unused reserved capacity. Then divide the total by outputs accepted at the required standard.

A dedicated model may have a higher visible monthly commitment but lower repeated briefing cost. An ad hoc model may avoid idle capacity but incur more coordination per file. Neither advantage should be assumed—measure it.

• Total delivery cost = provider fees + attributable internal labour + systems and governance cost
• Cost per accepted output = total delivery cost ÷ outputs accepted at the required standard
• Capacity returned = previous internal task time − retained briefing, review and management time
• Track material rework separately from minor editorial corrections

Use workload shape, not a magic file count

Review at least three months of completed and incoming work. Record files by type and complexity, not just a monthly total. Ten near-identical review files can create a different capacity requirement from ten complex new-advice cases with incomplete information.

Calculate baseline demand, peak demand and volatility. Note how often work arrives complete, how long clarification takes, and how much reviewer capacity is genuinely available. A stable average can hide severe weekly peaks, while a volatile month may still contain a predictable core suitable for a hybrid model.

The hybrid option

A hybrid model can reserve enough capacity for the predictable base workload while directing peaks, unusual complexity or leave coverage to an approved overflow process. It often suits growing practices that can see a stable core but are not ready to reserve for peak demand.

Hybrid arrangements need stronger queue rules, not weaker ones. Define which work enters the core queue, what triggers overflow, whether both resources use the same templates and systems, and who owns quality across the handoff. Avoid accumulating multiple providers and access paths without a single operating model.

Managed outsourcing versus direct engagement

A managed provider and a directly engaged remote worker may appear similar because both can involve an individual working inside the practice’s systems. The operational responsibilities can be very different. With direct engagement, the practice typically carries more recruitment, onboarding, performance management, leave coverage, access administration and replacement work.

A managed service can add structure through recruitment, supervision, workflow controls, quality support, reporting, continuity and escalation—but only where those mechanisms are actually included and evidenced. Compare the service contract and operating process rather than assuming that the word ‘managed’ guarantees an outcome.

• Who recruits, supervises and manages performance?
• Who maintains the operating playbook and quality records?
• What happens during leave, overload or departure?
• Who administers access and supports incident response?
• What reporting and contractual accountability does the practice receive?

Governance requirements do not move with the work

Outsourcing does not remove the applicable responsibilities of the AFS licensee, relevant provider or practice. The arrangement should be approved within the licensee framework and supported by documented provider assessment, privacy analysis, access controls, incident handling, business continuity, record keeping and ongoing monitoring.

For overseas access to personal information, APP 8 and section 16C of the Privacy Act can be relevant. Whether a specific arrangement constitutes a cross-border disclosure is fact-specific. Map the people, systems, countries, recipients, downloads, backups and subprocessors rather than relying on where a server is hosted.

• Individual identities, MFA and least-privilege access
• A named Australian reviewer and clear release authority
• Documented data flows and approved work locations
• Quality records, access evidence and incident escalation
• Tested access revocation, backup and exit procedures

Run a controlled pilot

Start with a repeatable task or file type and a complete written brief. Use the same acceptance standard for every pilot file and apply 100% substantive review. Record every clarification, defect, turnaround delay and reviewer minute so the decision is based on evidence rather than impressions.

A practical pilot should test both service output and the practice’s ability to manage it. If files repeatedly arrive incomplete, reviewers are unavailable or instructions change informally, the pilot has identified internal workflow work that must be fixed before either model can scale.

Build a fair scorecard

Review quality, speed, effort, risk and continuity together. First-pass acceptance shows whether output reaches the agreed standard without substantive rework. Median cycle time is more useful than a single fastest file. Clarification rate reveals whether briefs and source packs are fit for purpose.

Include operational measures such as backlog age, on-time completion, reviewer hours, material defect rate, access exceptions and successful backup coverage. Agree definitions before the pilot so neither the practice nor provider can improve the result by changing what counts.

• First-pass acceptance rate
• Median cycle time from accepted brief to completed draft
• Clarifications per file and time blocked
• Internal review and management hours
• Material defects and repeated root causes
• Continuity performance during leave or demand peaks

Questions practices ask before changing models

Is there a universal file count at which dedicated becomes better? No. Public thresholds are provider rules of thumb, not Australian industry standards. File complexity, work readiness, reviewer time and volatility matter alongside volume.

Can we start ad hoc and convert later? Yes, if the operating model preserves instructions, examples, quality history and access decisions so the transition does not restart onboarding from zero.

What happens if a dedicated paraplanner leaves? The answer should exist before appointment: documented knowledge, current work status, access revocation, a named transition owner and an agreed backup or replacement process.

Does dedicated support remove adviser review? No. Familiarity may reduce avoidable rework, but the appropriate authorised people retain substantive review and release responsibilities.

Will AI make the model choice irrelevant? No. Automation can change individual tasks, but practices still need accountable inputs, exception handling, quality control, records and capacity for work that requires human context and judgement.

A practical decision rule

Choose ad hoc when demand is genuinely uncertain, work can be tightly packaged and flexibility is worth the repeated coordination. Choose dedicated when there is a stable queue, retained practice knowledge has real value and the business can actively manage reserved capacity. Choose hybrid when the core is predictable but peaks are not.

If task boundaries, briefing or access still need work, treat that as an implementation requirement—not a reason to abandon outsourcing. A structured discovery and pilot can define the workflow, establish the baseline and identify the right starting allocation before the practice scales.

Questions to ask before signing

Ask each provider to describe the actual service rather than the marketing label. Compare answers on the same written scenario and require clarity where claims depend on averages, exclusions or provider-measured results.

• Is the person named, reserved and prohibited from being reassigned without notice?
• What is included in a file, and how are complexity and revisions handled?
• How are queue priority and turnaround measured?
• Who performs quality review, and what evidence is retained?
• Where will work and data be accessed, and by whom?
• What leave, surge, incident and exit coverage is contractually defined?
• Which outcomes will we measure during the first 90 days?