Fair Work (Digital Labour Platform Deactivation Code) Instrument 2024

The instrument rests on a small set of defined concepts that structure operator obligations and worker protections.

• Digital labour platform, digital labour platform operator, employee‑like worker and deactivated: these expressions are defined in the Fair Work Act 2009 and are incorporated into the instrument (s 5 note). The code applies to employee‑like workers who are “protected from unfair deactivation”, which requires meeting the Act’s regular work threshold (6 months) (s 4, note to s 7; s 18 clarifies regularity).

• Code process: a defined term meaning the procedural sequence set out in Part 2 that operators must follow for proposed deactivations (s 5). Part 2 structures the process in divisions: application, warnings, process for deactivation, and general matters (Divs 1-4).

• Deactivation warning, preliminary deactivation notice, final deactivation notice: these three notices are central. The deactivation warning (s 8) is an initial written warning describing the conduct or capacity issue and the consequences. If the operator proceeds, a preliminary deactivation notice (s 11) follows and must inform the worker that their access is being considered for termination, that they have a right to respond and to request a discussion, and of their right to appoint a non‑lawyer representative. If the operator decides to terminate, it must give a final deactivation notice detailing the reason, when termination takes effect (which may be immediate), and when/how final payments will be made (s 14(5)).

• Reasonable grounds / reasonable time / reasonable endeavours: the code repeatedly uses these standards instead of fixed timelines or bright‑line tests (see ss 7(1)(b), 9(1), 11(1)(c), 13(2), 15, 14(4)). That creates operator discretion and potential uncertainty about compliance measures.

• Valid reason: the instrument lists a non‑exhaustive set of matters that may constitute a valid reason for deactivation where they arise in the course of performing platform work (s 19). These include failure to meet platform obligations and contractual requirements (s 19(2)), health and safety misconduct (ss 19(3)-(5)), misuse of information (s 19(6)), fraud or deliberate damage (ss 19(7)-(8)), legal or regulatory referrals (ss 19(9)-(11)), licensing/accreditation or screening failures (ss 19(12)-(15)), and prolonged inactivity where required by law/regulator (s 19(16)). Section 19(17) expressly leaves the list non‑exclusive.

• Exceptions permitting immediate action: the code provides that a deactivation warning may not be required where, on reasonable grounds, immediate modification or suspension is warranted, or it is unreasonable to allow continued performance of work (s 9(1)). Examples include safety reasons, loss of licence, fraud, or referral to law enforcement (s 9 note/examples).

• Data and reinstatement: when access is reinstated or suspensions removed, the operator must ensure the worker has the same platform access and retains status or ranking no lower than before deactivation (s 21).

• Record keeping and privacy constraints: operators must retain records necessary to demonstrate compliance (s 22). The code displaces neither law enforcement directions nor obligations under the Privacy Act 1988; the instrument explicitly permits non‑disclosure where safety risk exists and refuses to require contravention of law enforcement directions or the Privacy Act (s 17).

These concepts shape the instrument’s mechanics: it is primarily a procedural code setting minimum steps and information duties for operators before removing access, while allowing exceptions and deferring many concrete standards to “reasonable” tests and existing statutory/regulatory regimes.

Primary regulated parties

• Digital labour platform operators: the instrument directly imposes operational obligations on platform operators when they are considering deactivation of a protected employee‑like worker (s 7(1)). Operators must develop procedures to issue warnings and notices (ss 8, 11, 14), maintain adequate records (s 22), provide access for discussions with human representatives (s 13(4)-(6)), and ensure platform communication features are available to workers (s 20).

• Employee‑like workers: the code protects workers who meet the Act’s “regular basis” threshold (noted in s 4 and elaborated in s 18). Such workers gain procedural rights: a deactivation warning (s 8) except in defined exceptions (s 9), a right to respond and request discussion (s 13), the right to appoint a non‑lawyer representative or support person (s 16), and the right to receive a final deactivation notice specifying reasons, timing and final payments (s 14(5)).

Secondary or connected parties

• Organisations providing support: the worker may seek assistance from a person who is not a lawyer, including a delegate or employee of an organisation (s 8(2)(c), s 16). Section 8 notes the term “organisation” is defined in the Act (see s 12 of the Act referenced in the instrument).

• Law enforcement and regulatory agencies: these bodies are explicitly recognised in the instrument as entities whose lawful directions and requests can constrain operator disclosure and can constitute grounds for removal (see definitions in s 5 and s 17(2), s 19(11)).

• Customers/clients and other workers: conduct relating to customers or other workers that falls within misuse of information, fraud, harassment or safety grounds can form valid reasons for deactivation (s 19(3), (6)-(8)).

Affected activities and business functions

• Platform safety and compliance teams: must be prepared to assess complaints or reports, apply “reasonable grounds”, and document decisions to demonstrate compliance (s 13(7)-(8), s 22).

• Product/engineering functions: may need to implement in‑platform notice delivery, ensure workers can access messages, and enable status/ranking restoration on reinstatement (ss 20, 21).

• Payroll and operations: required to specify final payments in final deactivation notices and follow through on payment timing and method (s 14(5)(d)).

Who pays and who decides

• Operators bear the compliance costs: designing and operating the notice and review process, retaining records, keeping human representatives available, and implementing technical reintegration of data and ranking on reinstatement (ss 11-14, 21, 22). Operators also decide whether deactivation is justified but must apply the code’s procedural steps and the “reasonable grounds” standard (s 14(4)).

• Workers bear costs in exercising rights: they must respond within the period specified, secure non‑lawyer support if desired, and preserve evidence of their work history to demonstrate that they are a protected worker (s 13(1)-(3), s 16, s 18). A worker excluded from the Act’s “protected” class (for example because the 6‑month regular work requirement is not met) does not trigger the code process and therefore faces a different deactivation regime under the Act.

Decision points with discretion

• Whether the worker is a “protected” worker (interaction of s 7 and s 18).

• Whether a matter amounts to “serious misconduct” (excludes the code process, s 7(2); note that “serious misconduct” is prescribed by regulation per the Act).

• Whether immediate suspension or non‑disclosure is justified on “reasonable grounds” (s 9, s 17).

• Whether the reason for termination is a “valid reason” and is established on reasonable grounds (s 14(4), s 19).

The instrument therefore allocates procedural protections to workers who meet thresholds and places the practical burden of documentary and procedural compliance on operators, subject to exceptions for safety, law enforcement directions and privacy obligations.

Operator duties

• Follow the code process when deactivation is contemplated for conduct or capacity reasons for a protected worker (s 7(1)). This includes adherence to Division 2 (deactivation warnings) and Division 3 (process for deactivation), except where s 7(2) (serious misconduct) or s 9 (exceptions) operate.

• Provide deactivation warnings in writing that specify the conduct or capacity reason, state the risk of deactivation and the conditions that could lead to it, and inform the worker that they may seek non‑lawyer assistance (s 8(1)-(3)). Warnings must provide sufficient information for a reasonable person in the worker’s position to understand (s 8(3)).

• Where Division 3 applies, give a preliminary deactivation notice specifying the reason, that termination is being considered, the worker’s right to respond and request a discussion with an operator representative within a reasonable period, and the right to appoint a non‑lawyer representative (s 11(1)-(2)).

• Make a human representative available for discussion when requested and consider the worker’s response and any discussion; make further inquiries reasonably warranted after consideration (s 13(4)-(8)).

• Notify the worker in writing as soon as reasonably practicable of the outcome, and where termination occurs give a final deactivation notice that states the decision, specifies reasons, the effective time and day (which may be immediate), and details about final payments (s 14(2), (5)).

• Where any modification or suspension of access occurs, notify the worker of when it takes effect and its consequences and do so in accordance with timing rules tied to the preliminary deactivation notice (s 12(3)-(4)).

• Use reasonable endeavours to ensure the process is carried out within a reasonable time frame and that workers have reasonable time to exercise response rights (s 15).

• Ensure written communications use the platform or a reasonable alternative and ensure workers have sufficient platform access to view and respond (s 20).

• On reinstatement, ensure the worker has the same access to platform data and a status/ranking no lower than before deactivation (s 21(2)(a)-(b)).

• Maintain records necessary to demonstrate compliance and retain them as long as reasonably necessary, subject to Privacy Act constraints (s 22).

Worker rights

• Receive a deactivation warning before deactivation in most cases (s 8), except where the operator reasonably considers immediate suspension is required or it is not reasonable to allow continued work (s 9).

• Receive clear, written preliminary and final notices, with sufficient information to understand the matters and to exercise response rights (ss 11(1)-(2), 14(5)-(6)).

• Right to respond in writing or orally within the period specified in the preliminary deactivation notice and to request a discussion with an operator representative (s 13(1)-(6)).

• Right to appoint a person other than a lawyer acting in a professional capacity for support or representation; that person may be a delegate or employee of an organisation (ss 8(2)(c), 16).

• If reinstated, right to the same access to performance data and status no lower than before deactivation (s 21).

• Implicit remedial pathway under the Fair Work Act: an employee‑like worker may seek relief by alleging unfair deactivation to the Fair Work Commission under the Act (s 4 notes referencing paragraph 536LF(c) of the Act).

Limits and qualifications

• Operators are not required to disclose information if disclosure may pose a risk to safety or security (s 17(1)).

• Operators are not required to contravene law enforcement or regulatory directions nor breach obligations under the Privacy Act (s 17(2)).

• The code process does not apply to deactivations for serious misconduct as defined by regulation (s 7(2)).

• Representation expressly excludes lawyers acting in a professional capacity (s 16(1)).

Standards for justification

• Before termination, the operator must be satisfied the reason is a “valid reason” and must consider on reasonable grounds that the reason has been established (s 14(4)). Section 19 gives illustrative categories of valid reasons but is non‑exhaustive (s 19(17)).

These duties and rights create a structured but flexible process: operators retain discretion in assessing “reasonable grounds” and “valid reasons”, while workers get procedural opportunities to respond and to be reinstated with data and status if the operator takes no further action.

The instrument itself is a code made under the Fair Work Act 2009 and does not specify standalone civil or criminal penalties within its text. Enforcement and remedies link back to the Fair Work Act and the Fair Work Commission, as indicated in the simplified outline (section 4) which states an employee‑like worker may be found to be unfairly deactivated if the Commission is satisfied the deactivation is not consistent with this Code (see paragraph 536LF(c) of the Act). The instrument therefore operates as a mandatory process whose non‑compliance can be central to statutory unfair deactivation claims under the Act.

Practical enforcement mechanisms and points

• Fair Work Commission claims: the instrument is designed to be the benchmark against which the Commission assesses whether deactivation was “unfair” under the Act (section 4). A worker alleging unfair deactivation would point to failures to follow the code process, missing notices, inadequate consideration of responses, or inadequate reinstatement (ss 8, 11, 13, 14, 21, 22).

• Evidential role of records: operators must make and keep records setting out worker data and the processes followed for deactivations (s 22). Those records are evidence for both operators to demonstrate compliance and for workers or regulators alleging breaches.

• Administrative and reputational enforcement: although not spelt out in the instrument, breaches can lead to Fair Work Commission orders, potential remedies under the Act, and reputational costs for platforms. The instrument’s requirement to specify final payments (s 14(5)(d)) ties operator conduct to wage settlement obligations; failure to pay could trigger separate Fair Work Act enforcement or other statutory claims.

Limits on enforcement

• The instrument defers to other legal obligations: it does not require contravention of law enforcement directions or privacy obligations (s 17(2)). If an operator claims a law enforcement direction prevented compliance with the code, that claim will weigh in a subsequent enforcement or unfair‑deactivation proceeding.

• Subjective standards and exceptions: many operative standards are “reasonable”, and the instrument allows exceptions such as immediate suspension for safety or regulatory reasons (s 9). These subjective tests create factual questions for adjudication rather than bright‑line statutory penalties for procedural lapses.

• No express pecuniary penalties in the instrument: the instrument does not create fixed monetary penalties or criminal offences for non‑compliance. Enforcement therefore proceeds through the statutory unfair‑deactivation regime and any other applicable provisions of the Fair Work Act for breaches of that Act.

What is required for a worker’s unfair‑deactivation case

• The worker would likely need to show they were a protected worker (regular basis for 6 months , s 18), that the operator proposed deactivation for a covered reason (conduct or capacity), and that the operator did not comply with the code’s process as required (ss 7-15). The operator’s records required by s 22 will be central evidence of compliance.

• The operator’s defence will focus on reasonable grounds for immediate suspension or deactivation (s 9), justification under valid reasons listed in s 19, and any law enforcement/privacy constraints under s 17.

The instrument thus creates procedural obligations that feed into the Act’s enforcement framework, with the Fair Work Commission positioned as the primary forum to adjudicate disputes about compliance with the Code and the fairness of deactivations.

The instrument is expressly situated within the broader statutory framework and cross‑references or defers to several other legal regimes.

Fair Work Act 2009

• Authority and enforcement: the instrument is made under the Fair Work Act 2009 (s 3) and implements the Digital Labour Platform Deactivation Code required by section 536LJ of the Act (s 4). Its primary enforcement route for deactivation disputes is via the unfair deactivation provisions of the Act (noted in s 4 referencing paragraph 536LF(c)).

Regulations defining serious misconduct

• The code excludes deactivations for “serious misconduct” from its process (s 7(2)), and notes that “serious misconduct” is prescribed by the regulations (s 7(2) note 2; references s 12 of the Act). Operators therefore must reconcile the instrument with any regulatory definition of serious misconduct that permits immediate deactivation without the code’s steps.

Privacy Act 1988

• The instrument recognises privacy obligations and limits disclosure requirements where a disclosure would contravene obligations under the Privacy Act (s 17(2)(b)). It also requires that records that are personal information be collected, used and disclosed only in accordance with the Privacy Act (s 22(3)). These cross‑references require operators to design record‑retention and disclosure procedures consistent with the Privacy Act.

Law enforcement and regulatory directions

• The instrument accepts that lawful directions from law enforcement or regulatory agencies can override disclosure obligations under the code and can constitute grounds for deactivation (s 17(2)(a), s 19(11)). Section 5 defines “law enforcement or regulatory agency” broadly to include AFP, state police and any other authority responsible for law enforcement of Commonwealth or State/Territory laws. Operators must therefore balance compliance with the code against directions from such agencies.

Industry codes and licensing regimes

• Section 19(10)-(16) treats failure to comply with mandatory industry codes, licensing, accreditation or screening as potentially valid reasons for deactivation. This creates direct interaction between platform policies and sectoral regulatory regimes (for example health, transport licensing, or other licenced services). Operators must therefore monitor applicable industry codes and regulatory requirements and ensure their platform rules and deactivation processes dovetail with those regimes.

Employment and contract law

• The instrument operates in the context of services contracts between workers and operators. Section 19(2)(a) explicitly includes failure to meet the requirements of the worker’s services contract as a potential valid reason for deactivation. The code therefore interacts with contract terms and any disputes about contractual interpretation or enforceability.

Motor vehicle and road safety laws

• Section 19(5) specifically contemplates unsafe driving practices by workers who drive as part of platform work. That creates an intersection with state/territory road rules and licensing requirements.

Other procedural and evidential laws

• The instrument’s record keeping and evidentiary role (s 22) mean that other statutory obligations (for example, taxation record‑keeping, insurance, or work health and safety incident reporting) will intersect with the same data and process flows.

Net effect

• The instrument is not an isolated code; it requires platforms to operate in coordination with existing privacy law, law enforcement directions, licensing and industry codes, regulatory or criminal referrals, and the statutory framework of the Fair Work Act. The code gives operators a framework but also requires them to determine how to implement the code alongside these other legal obligations and to document their decisions accordingly (s 17, s 19, s 22).

Original making and commencement

• The instrument was made by the Minister for Employment and Workplace Relations, Murray Watt, and is dated 3 December 2024 (prefatory material). Section 1 states the name of the instrument.

• Commencement is specified in section 2. Each provision of the instrument commences on the later of the day after registration and 25 February 2025. The commencement table in s 2(1) gives that specific detail and notes the table relates only to provisions as originally made.

Amendment metadata in the instrument

• Section 2(2) records that information in column 3 of the commencement table is not part of the instrument and may be edited in published versions; that is an administrative note about publication, not an operative amendment provision.

• Section 22(2) uses an operator’s subjective standard of “as long as the operator considers reasonably necessary” to keep records, rather than specifying a minimum statutory retention period. That drafting choice leaves the retention period open to change by operator policy or future regulation.

No further amendment history within the text

• The instrument itself contains no subsequent amendments or historical annotations of previous amendments; the instrument’s internal commencement table includes the standard note that it relates only to provisions “as originally made”. Users should consult the instrument as registered and any later registered instruments or amending regulations that alter the scope of “serious misconduct” in the Act or otherwise modify related provisions.

What future amendments might focus on

• Definition of “reasonable” standards: multiple provisions use “reasonable” without definition (ss 7(1)(b), 9(1), 11(1)(c), 13(2), 14(4), 15). Any amendment could either define specific timeframes and evidentiary thresholds or leave them to case law by the Fair Work Commission.

• Records retention: s 22(2) currently leaves retention length to operator judgment. Regulators or Parliament could specify minimum retention periods for auditability.

• Scope of representation: s 16 excludes lawyers acting in a professional capacity. An amendment could alter this by allowing legal representation or further specifying who may represent workers.

• Reinstatement mechanics: s 21 requires restoration of data and status but does not prescribe technical standards. Future amendment could set standards for algorithmic ranking restoration or dispute resolution around ranking.

To track amendments and commencement, practitioners should monitor the instrument’s registration details and any amending instruments or regulations under the Fair Work Act and related instruments that define “serious misconduct” or adjust procedural obligations.

The instrument itself, as a newly made code, contains no litigation history recorded in its text. It states its function as the Digital Labour Platform Deactivation Code under the Fair Work Act and indicates that unfair deactivation enquiries will be considered by the Fair Work Commission under the Act (s 4 referencing paragraph 536LF(c)). The instrument does not name any cases and contains no judicial or tribunal decisions.

What practitioners should expect

• Future litigation or Fair Work Commission proceedings: because the instrument provides procedural standards and many standards hinge on “reasonable grounds” or “reasonable time”, disputes are likely to arise that will be resolved by the Fair Work Commission and, potentially, by courts on questions of legal interpretation or jurisdictional error. Such disputes will create the case law that clarifies the boundaries of “reasonable” and the content of procedural fairness under the Code.

• Records and evidence: s 22 requires operators to make records of data and processes “to the extent that the operator considers reasonably necessary to demonstrate compliance”. Those records will be central evidence in any Commission application alleging unfair deactivation. Operators should expect that failure to produce contemporaneous notes, notices and logs will weaken their position in disputes.

• Intersection with law enforcement: where operators rely on law enforcement or regulatory directions to justify non‑disclosure or immediate suspension (s 17, s 9, s 19), disputes may involve balancing statutory directions, privacy obligations and the code. Parties may seek judicial review where a platform’s refusal to disclose is challenged as pretextual, or where a law enforcement direction is alleged to be improperly invoked.

• Reinstatement and algorithmic status: s 21 requires that reinstated workers receive the same access to data and retain no lower status or ranking. Litigation may test what “status or ranking” means in algorithmic platforms, and how operators must technically restore ranking or compensate where algorithmic effects persist.

Absent any cases named in the instrument, practitioners should treat litigation history as prospective: the instrument is designed to be testable through the existing unfair deactivation pathways of the Fair Work Act, and the practical contours of the Code will be clarified through Commission and court decisions as disputes arise.

The instrument contains several provisions that create compliance traps or practical ambiguities. These are concrete points operators, workers and advisers should watch.

“Reasonable” standards and timeliness

• The instrument repeatedly uses “reasonable grounds”, “reasonable time”, and “reasonable endeavours” (see ss 7(1)(b), 9(1), 11(1)(c), 13(2), 15). No objective timeframes are prescribed. Operators must therefore define and document internally what they consider reasonable. In disputes, the operator’s contemporaneous justification and adherence to any self‑imposed standards will be critical. Workers face uncertainty about how long they have to respond or when a decision will be made.

Immediate suspension and notice timing

• Section 12 permits modification or suspension either before or after a preliminary deactivation notice (s 12(2)). Section 12(4)(a) requires notification as part of the preliminary deactivation notice if suspension occurred before that notice was given, and s 12(4)(c) requires notification before the modification if it occurs after the preliminary notice. Practically, an operator that suspends access immediately for safety reasons must still provide the preliminary deactivation notice “as soon as reasonably practicable” (s 12(4)(a), s 11). Operators must reconcile immediate safety action with prompt post‑suspension notification.

Exception for serious misconduct

• The code does not apply where deactivation is for “serious misconduct” (s 7(2)), but “serious misconduct” is prescribed by regulation. Operators may be tempted to characterise conduct as “serious” to avoid process obligations. This is a factual question that will be tested in disputes. Operators should document the basis for any classification of “serious misconduct” against whatever regulatory definition applies.

Presumption of validity after non‑response to reports

• Section 13(9) sets a specific evidential consequence: where a preliminary notice follows a report/complaint and the worker’s response is inadequate or absent, and the report/complaint if true would be a valid reason, then termination is taken, for the purposes of subsection 14(4), to be termination for a valid reason the operator reasonably considers established. This places a strong evidentiary weight on reports and on workers’ timely responses. Workers who do not respond risk the operator being able to treat the matter as established.

Representation restrictions

• Workers may appoint a person other than a lawyer acting in a professional capacity for support or representation (s 16(1)). This prohibition on legal representation in the process is a potential surprise to workers who assume they can bring a lawyer to an operator meeting. It does not, however, limit a worker’s ability to seek legal remedies through the Fair Work Commission later.

Reinstatement of ranking and data

• Section 21 requires restoration of access to data and that a worker’s status or ranking is no lower than immediately before deactivation. For algorithmic platforms where rankings are influenced by ongoing activity, technical reinstatement may be complex. Operators must design technical measures to preserve and restore ranking metadata; failure to do so will be a breach even if access to the platform is restored.

Records retention ambiguity

• Section 22(2) leaves record retention periods to what the operator “considers reasonably necessary”. There is no minimum statutory period, but inadequate retention will blunt an operator’s ability to demonstrate compliance in a dispute. Practically, operators should adopt conservative retention policies to avoid evidentiary gaps.

Privacy and disclosure balance

• Section 17 allows operators to withhold information where disclosure may pose a risk to safety or security and disallows contravening lawful directions or the Privacy Act. However, operators who overuse safety or privacy claims to avoid disclosure risk being challenged for procedural unfairness. Operators must log the specific grounds for withholding information.

Final deactivation notice may be immediate

• The final deactivation notice must specify an effective time and day and may be immediate (s 14(5)(c)). Practitioners should note that immediate final termination is permissible where justified, but must still follow the code’s process unless exceptions apply.

Non‑exhaustive list of valid reasons

• Section 19 is non‑exhaustive (s 19(17)). That means operators can treat other conduct or capacity items as valid reasons, but must ensure their decision‑making complies with the “valid reason” and “reasonable grounds” standards in s 14(4).

In short, the instrument creates procedural protections but leaves substantial space for operator discretion. The quality of contemporaneous documentation, clearly articulated internal definitions of “reasonable” and prompt communication will determine the practical risk of disputes.

Checklist for digital labour platform operators

1. Classify workers and identify protected workers

   • Maintain records of worker activity to show whether a worker meets the Act’s “regular basis” threshold. Use the objective triggers in s 18: 60 hours of paid work per month on average, or paid work on average 3 days per week, and a 6‑month horizon noted in s 4. Document the methodology used to calculate averages.

2. Design notice templates and content

   • Prepare written templates for deactivation warnings (s 8), preliminary deactivation notices (s 11), and final deactivation notices (s 14(5)) that include all required elements: reasons; that termination is being considered; rights to respond and request discussion; right to appoint a non‑lawyer support person; timing for response; and final payment details. Ensure the content is sufficient to enable a reasonable person to understand the matters (ss 8(3), 11(2), 14(6)).

3. Define internal standards for “reasonable” and timelines

   • Adopt and publish internal standards for what constitutes “reasonable time” to respond and “reasonable grounds” for immediate action, and ensure consistent application and recordkeeping (s 15). Document how “reasonable” is applied to different categories (safety, licensing failure, fraud, etc.). These standards should be defensible and justifiable in subsequent Commission proceedings.

4. Implement a human review and discussion process

   • Ensure human representatives are available to take part in discussions when requested and have authority to consider worker responses and order further inquiries (s 13(4)-(8)). Maintain logs of discussions and the people involved, and note whether a support person participated (s 13(6)).

5. Establish suspension and modification protocols

   • Create protocols for immediate modification or suspension where safety, loss of licence, fraud, or regulatory referral justify it (s 9 examples, s 12). Ensure suspension notifications are issued in accordance with s 12(3)-(4) and that preliminary notices follow as soon as reasonably practicable.

6. Maintain evidentiary records

   • Keep contemporaneous records of the facts relied upon, reports/complaints, the worker’s response, the reasoning for decisions (including “reasonable grounds”), the notices sent, dates/times and the identities of decision‑makers (s 22). Set a conservative retention policy that documents why longer or shorter retention was chosen (s 22(2)). Ensure records that are personal information comply with the Privacy Act (s 22(3)).

7. Preserve and reinstate technical state

   • Architect platform systems to preserve pre‑deactivation status, ranking metadata and performance data so that reinstatement restores the same access and status no lower than before deactivation (s 21). Log the technical steps taken for reinstatement and the dates they occurred.

8. Coordination with law enforcement and privacy obligations

   • Create an escalation route to handle requests or directions from law enforcement and regulatory agencies (s 17(2)). Record the legal basis for complying with such directions and how they limit disclosure under the code.

9. Training and governance

   • Train safety, moderation, and operations staff on the code’s requirements, the list of potential valid reasons (s 19), the exceptions under s 9, and the process steps including when a deactivation warning may be skipped. Ensure decision‑makers understand the consequences under s 13(9) where the worker does not respond.

10. Payment and termination administration

    • Ensure final deactivation notices specify the timing and method of any final payments (s 14(5)(d)) and that payroll processes can effect those payments promptly.

Checklist for employee‑like workers and advisers

1. Track hours and days worked

   • Maintain contemporaneous records of hours and days worked through a platform to demonstrate whether you are a protected worker under s 18 and the Act’s 6‑month regularity threshold.

2. Monitor platform communications and respond promptly

   • Read deactivation warnings and preliminary deactivation notices and respond within the period specified to preserve the evidentiary record (s 13(1)-(3)). Both written and oral responses are permitted.

3. Use permitted representation

   • Appoint a non‑lawyer for support or representation if needed (s 16). Note that lawyers acting in a professional capacity are excluded from participation in the operator’s internal discussion process.

4. Preserve evidence

   • Keep copies of all notices, messages, screenshots, GPS or trip logs, and any communications with customers that relate to the issue in dispute.

5. Seek external remedies if needed

   • Where an operator does not follow the code, consider lodging an unfair deactivation claim with the Fair Work Commission under the Act (see s 4 note referencing paragraph 536LF(c)). Use the operator’s records under s 22 to support any claim; request copies where feasible and permitted.

Recommended practical controls and documentation

• Audit trail: timestamped logs of notices delivered, acknowledgements, and the worker’s access to communications will be critical in disputes.

• Pre‑defined decision matrices: for categories in s 19 (licence loss, safety, fraud, misuse of information, inactivity), specify what evidence will be required to justify suspension or termination and who can approve it.

• Privacy/Disclosure decision log: where an operator withholds disclosure citing safety or law enforcement, create a short decision memorandum explaining the reason and citing the relevant law/agency direction (s 17).

• Reinstatement testing: periodically test the platform’s ability to reinstate data and ranking exactly as required by s 21, and document the testing and any gaps.

• Templates and notice tracking: store templates and a register of notices provided with copies of the actual communications sent.

Following these steps will align operational practice with the instrument’s obligations, mitigate dispute risk and provide the documentary trail necessary to show compliance before the Fair Work Commission or other enforcement bodies.