State-by-State Tenancy Workflow Review

This State-by-State Tenancy Workflow Review explains how Leasily treats major Australian residential tenancy workflows at a public level. It is not legal advice and is not a substitute for current state legislation, prescribed forms, regulator guidance, tribunal practice, or advice about your facts.

Leasily may use state rules to show reminders, block higher-risk workflows, calculate timing guardrails, record evidence, or label a step as manual. That does not mean Leasily has completed the legal step for you.

• Automated guardrail: the product checks or blocks a timing/status condition before allowing a workflow to proceed.
• Reminder only: the product can show deadlines, nudges, or statuses, but the user generally needs to complete the legal step.
• Record keeping only: the product stores evidence, references, documents, or notes, but does not perform the legal act.
• Manual or review required: the user should complete the step outside Leasily or seek independent advice before acting.

• NSW: no-grounds landlord notice workflows are designed to be blocked in self-serve flows; bond, rent increase, entry, breach, condition report, disclosure, and renewal rules may be supported as guardrails or records.
• VIC: no-grounds landlord notice workflows are designed to be blocked in self-serve flows; rent increase timing, prescribed-reason notice periods, entry windows, bond records, and disclosures require careful state review.
• QLD: no-grounds landlord notice workflows are designed to be blocked; QLD-specific rent-increase, bond, breach, entry, minimum standards, and disclosure rules are treated as state-specific guardrails or records.
• WA: some no-grounds notice workflows may be available only where seeded rules permit them; bond, entry, rent increase, condition report, and disclosure records remain landlord-controlled.
• SA: no-grounds notice workflows may be available only where seeded rules permit them; bond deadlines and prescribed disclosures remain landlord-controlled and should be checked against current CBS guidance.
• TAS: no-grounds notice workflows may be available only where seeded rules permit them; condition report, breach, entry, bond, and renewal records require state-specific review.
• ACT: no-grounds landlord notice workflows are designed to be blocked; ACT-specific EER, bond, entry, rent increase, prescribed-reason termination, and disclosure records require careful review.
• NT: trust-account handling for bond money is treated as a manual responsibility; termination, rent increase, breach, and entry rules are state-specific and should be checked before action.

Bond features are generally reminder and record-keeping tools. Leasily can record payment status, authority state, lodgement evidence, proof references, refund status, and dispute evidence. Unless a product screen expressly says otherwise, landlords remain responsible for collecting, holding, lodging, refunding, and disputing bond money under the relevant state or territory law.

Leasily can apply state-specific timing guardrails for rent increase workflows and update future rent schedule records where a supported notice becomes effective. Users remain responsible for checking whether rent can be increased, whether prescribed wording or forms are required, and whether service has been validly completed.

Breach, termination, and entry workflows are legally sensitive. Leasily may block unsupported no-grounds or breach-based termination workflows, enforce minimum timing, require reasons, or keep audit records. Users remain responsible for the facts, prescribed form, service method, evidence, follow-up, and tribunal process.

Leasily may collect state-specific disclosure inputs, condition report timing information, renewal reminders, and related records. These are support tools. Landlords must check current state requirements and provide any prescribed documents, information statements, by-laws, safety disclosures, or government forms required outside the product if not expressly supported.

Tenancy laws change frequently. Leasily aims to keep product rules and public notices aligned with current product behaviour, but users should verify high-consequence decisions against official state or territory sources before acting.