Retained or project-based workplace advisory: choosing the right support model

The question of whether to retain a workplace adviser or engage one for a defined project rarely begins as a procurement question. It begins with an operating problem. A people-and-culture lead is absorbing complaint intake, award interpretation and manager coaching on top of a full role. A general manager has had three matters escalate in a quarter and no consistent standard applied to any of them. A board has approved a restructure and discovered that nobody internally has run one. A finance director is looking at advisory spend that arrived unplanned, invoice by invoice, with no way to say what it bought.

Those are different problems, and they do not have the same answer. Continuous low-volume demand and a one-off, high-consequence programme call for different arrangements. Choosing the wrong shape produces predictable outcomes: a retainer that quietly funds work nobody scoped, or a series of disconnected engagements that do not build a standard the organisation can apply itself.

This guide sets out how to diagnose which model fits, how to specify it, and how to govern it. No model is inherently superior. The correct choice depends on the nature and recurrence of the work, internal capability, the need for continuity, urgency, independence, the clarity of the intended outcome, information sensitivity, commercial control and how the arrangement will be reviewed and ended.

A retained arrangement buys defined access to defined capability for a defined period. It is an agreement about availability, continuity and scope — not an agreement to perform unlimited work. Its value lies in the adviser knowing the organisation: its instruments, its structure, its management culture, the history behind a particular team, and the standard already agreed for handling a complaint or a performance conversation.

Typical retained scope covers day-to-day questions and manager guidance, interpretation of awards, enterprise agreements, contracts and policies, early triage of complaints and grievances, review of correspondence and process steps before they issue, guidance on documentation standards, and periodic reporting on themes and emerging exposure.

It is not accurate to describe this as outsourced human resources. A retained adviser does not become the employer, does not assume the organisation's statutory duties, and does not make the decisions that management is accountable for. Recurring transactional administration — payroll processing, records administration, day-to-day people operations — is a different service with different scope, and should be described and contracted as such.

A project engagement is defined by an outcome rather than by availability. It has a stated objective, a scope with explicit inclusions and exclusions, stated assumptions and dependencies, milestones, a deliverable set and completion criteria. It ends when those criteria are met.

Work that can be scoped this way includes a workplace investigation, a facilitated mediation or conflict-resolution process, a restructure or redundancy programme, an enterprise bargaining round, a wage compliance review, a policy or contract framework rebuild, a culture or psychosocial review, and structured manager or contact officer training. Each has a shape, a defined end point and its own independence and confidentiality considerations.

The discipline of a project is that its boundaries are visible. Everyone can see what was agreed, what changed, what it cost and what was produced. That visibility is exactly what disappears when specialist work is absorbed into a general retainer without re-scoping.

The comparison below is not a scorecard. It is a set of dimensions to test against the organisation's actual demand pattern.

• Best fit — retained: recurring, unpredictable, lower-volume demand where continuity of knowledge matters. Project: a defined outcome with a clear beginning and end, or specialist work requiring separation from day-to-day advice.
• Scope — retained: a described category of work with stated inclusions, exclusions and an approval route for anything outside it. Project: an outcome specification with assumptions, dependencies and completion criteria.
• Access — retained: agreed access arrangements, authorised requesters and triage rules. Project: access defined by the project plan and its governance.
• Continuity — retained: institutional knowledge accumulates and standards persist between matters. Project: continuity is limited to the engagement unless handover is expressly designed.
• Deliverables — retained: advice, reviewed documents, guidance records and periodic reporting. Project: a specified set of outputs against milestones.
• Budget control — retained: predictable periodic cost, with the risk that unscoped work erodes the value of the fee. Project: cost tied to the outcome, with the risk that scope changes are absorbed informally.
• Change control — retained: needs a written route for out-of-scope requests and their approval. Project: needs a variation process that records scope, time and cost impact before work proceeds.
• Independence — retained: prior involvement in a matter may limit the adviser's ability to perform an independent role in it later. Project: independence can be assessed and preserved at the point of appointment.
• Review and exit — retained: scheduled review points, performance measures, renewal terms and notice. Project: closure against completion criteria, with records, evidence and handover specified in advance.

A retained arrangement suits an organisation with continuous but modest demand: enough questions arising each month that ad hoc engagement is inefficient, but not enough to justify additional internal specialist headcount. It suits managers who need a consistent standard applied across sites or business units, where the alternative is each manager improvising.

It also suits organisations where response timing matters — a stood-down employee, a complaint that has just landed, a resignation letter that alleges conduct — and where the cost of re-briefing a new adviser each time is real. Where an organisation is deliberately building internal capability, a retainer can be scoped around coaching and standard-setting rather than doing the work, with the volume of questions expected to fall as capability grows.

A project engagement suits work with a defined outcome, particularly where the outcome is high-consequence, time-bounded or requires specialist independence. A complaint that requires an externally appointed investigator, a redundancy and consultation programme, a wage compliance review or an enterprise bargaining round each have their own governance, evidence standard and end point.

It also suits organisations with capable internal teams who need depth on a specific question rather than ongoing support, and organisations that need a defensible record of what was done, by whom, against what scope. Where the work may later be examined — by a regulator, a court or tribunal, an insurer or a board — a defined engagement can produce a clearer, more reviewable record than an entry on a monthly advisory summary.

Where demand genuinely includes both recurring advisory work and defined, separable programmes of work, the answer may be both, and the discipline lies in separating them deliberately rather than allowing one to swallow the other. A hybrid model keeps a limited retained channel for day-to-day guidance, triage and standard-setting, and scopes specialist work — investigations, mediations, restructures, bargaining, systems and training programmes — as separate engagements with their own terms.

That separation does more than protect the budget. It makes the retainer measurable, because the recurring work is no longer inflated by project spikes. It makes each project reviewable on its own terms. And it forces an explicit decision about independence at the moment a specialist matter arises, rather than defaulting to whoever is already engaged.

The trigger for separation should be written down at the outset: for example, that any matter expected to require formal findings, a defined programme of work, or effort beyond an agreed threshold moves to a scoped engagement before work begins.

Work through the following before comparing proposals. The answers, taken together, indicate the shape of the arrangement more usefully than a pricing comparison alone.

• Demand pattern — is the work continuous and unpredictable, episodic and defined, or genuinely both? Look at the last twelve months rather than the last month.
• Internal capability and capacity — is the gap knowledge, bandwidth, or both? A capability gap points toward coaching and standard-setting; a capacity gap may point toward scoped delivery.
• Urgency and access — what actually has to be answered quickly, and what only feels urgent? Define the categories that warrant priority rather than assuming everything does.
• Continuity and organisational knowledge — how costly is re-briefing? Where history, instruments and structure are complex, continuity has measurable value.
• Independence and conflicts — will the work require someone with no prior involvement? Assess this per matter, not once at the start of the relationship.
• Deliverable certainty — can the intended outcome be described precisely enough to know when it is finished? If yes, scope it as a project. If not, define the access instead and re-scope when the outcome becomes clear.
• Information sensitivity — what information will the adviser hold, under what access controls, for how long, and how will it be transferred and returned or destroyed?
• Budget and commercial control — which model gives the organisation a defensible answer to what was bought, what it produced and what it should cost next year?

Under-specification at the outset can undermine an arrangement even where delivery is sound. The following should be agreed in writing before the first request is made.

• Purpose and scope — what the arrangement exists to achieve, described in operational terms, with the categories of work included and excluded.
• Authorised requesters — who may instruct the adviser, and who may not. Uncontrolled access is a cause of unmanaged cost and inconsistent advice.
• Triage and priority rules — how requests are categorised, who resolves competing priorities, and what information must accompany a request.
• Inclusions, exclusions and out-of-scope approval — the written route by which work outside scope is identified, quoted and approved before it starts.
• Service and access expectations — agreed availability and acknowledgement arrangements, expressed by category of request rather than as a universal response promise.
• Decision rights and escalation — an explicit statement that the adviser advises and the organisation decides, with named internal decision-makers and an escalation path.
• Conflicts and independence checks — how conflicts are identified at the outset and re-checked when each new matter arises, including actual and perceived conflicts arising from prior involvement.
• Confidentiality, privilege and information handling — what is confidential, how privilege will be considered where legal advice is required, and the access, storage, retention, transfer and destruction arrangements that apply.
• Records, evidence and handover — what the organisation retains, in what form, and what is handed over at review, renewal or exit so that internal knowledge does not leave with the adviser.
• Fees, expenses and change control — the fee basis, what is included, how expenses are treated, and how variations are recorded and approved.
• Review points, performance measures, renewal and exit — when the arrangement is reviewed, what it is measured against, how it renews and how either party ends it.

The failures below are design failures rather than delivery failures, and each is avoidable at the contracting stage.

• Vague scope. "Support as needed" is difficult to plan, price, measure or end well. It produces disputes about what the fee covered.
• Unlimited-access assumptions. Where anyone may instruct the adviser on anything, the organisation loses both cost control and consistency of advice.
• Using a retainer for major work. Absorbing an investigation, a restructure or a bargaining round into general advisory time distorts the retainer, obscures the true cost and weakens the record of that work.
• Fragmenting recurring work. Repeatedly re-engaging for the same category of question, with no continuity or standard, is expensive and produces inconsistent outcomes.
• Advisers as substitute decision-makers. An external adviser can frame options, test reasoning and document a process. Management remains accountable for the decision and for the organisation's obligations, and a record showing otherwise is difficult to defend.
• Independence assumed rather than protected. A general statement that an adviser is independent does not resolve a specific conflict arising from prior involvement in the matter.
• No usable internal record. If advice, reasoning and precedents live only with the adviser, the organisation builds no capability and faces a difficult handover.
• Measuring activity instead of outcomes. Counting calls and hours says little. Measure whether matters are resolved earlier, whether managers act more consistently, and whether recurring issues decline.

Engaging an adviser does not move accountability. Workplace obligations arise under legislation, modern awards, enterprise agreements, contracts and the organisation's own policies, and the employer remains responsible for meeting them. Where an award, agreement, policy or statute requires consultation about a change, that requirement is the employer's and is separate from the decision to engage external support. Engaging an adviser does not transfer or discharge any WHS/OHS duty applicable to the organisation or its officers under the legislation of the relevant jurisdiction, and depending on the jurisdiction and the circumstances duties may also be owed independently by other duty holders, including workers, other persons at the workplace and another business or undertaking involved in the work.

Two further points warrant deliberate treatment. Legal professional privilege is not created merely because work is confidential or performed by an external workplace adviser, and involving a lawyer does not make all project or investigation material privileged. Depending on the applicable law and the context, privilege generally concerns confidential communications or documents made for the dominant purpose of obtaining or giving legal advice, or for use in existing or reasonably anticipated litigation, and whether it applies is fact-specific. Where legal advice or privileged work is required, the purpose, the roles of those involved, the instructions and the information flows should be settled with legal counsel before work begins. AWS does not promise that particular material will be privileged. Second, privacy, employee-record and surveillance obligations differ between jurisdictions and contexts, so information-handling arrangements should be settled against the rules that actually apply to the organisation rather than assumed to be uniform.

Related governance work — contract and instrument review and contact officer role design — sits alongside this and may be better scoped as defined work than absorbed into general advisory time.

AWS works with employers under all three models. A retained workplace advisory arrangement is scoped around defined access, authorised requesters, triage categories and agreed reporting, with an explicit route for moving specialist matters into separate engagements. Project engagements cover investigations, mediation, restructure and consultation programmes, compliance reviews, policy and framework work, and training, each with stated scope, assumptions, milestones and completion criteria.

Where an organisation wants obligations, controls, evidence and actions held in one place across those engagements, that work can be supported through governance, risk and compliance arrangements and the Strobe platform, so the record remains with the organisation rather than with the adviser.

Independence is assessed matter by matter. Where prior advisory involvement would compromise an investigation or a mediation, that is identified before appointment and the work is allocated accordingly.

The organisations that get the most from external workplace support are not necessarily the ones that spend the most. They are the ones that have decided what they need external help for, what they intend to keep and build internally, how the arrangement will be governed, and how they will know whether it is working.

If the demand is continuous, define the access. If the outcome is definable, scope the project. If both are true, design the boundary between them rather than leaving it to accumulate. Then set the review point before the first request is made.

This article is general information about workplace practice in Australia. It is not legal advice, does not take account of any organisation's circumstances, and does not transfer any employer obligation to an adviser. To discuss which arrangement fits your organisation, contact AWS.