What Is a Tenancy Database in Queensland Real Estate? Definition and Agent Guide

A tenancy database is a privately operated register used by Queensland property managers and lessors to record adverse tenancy history — most commonly rent arrears exceeding the bond, property damage, or termination on the grounds of objectionable or repeated breaches. In Queensland, the Residential Tenancies and Rooming Accommodation Act 2008 (RTRA Act) regulates the use of tenancy databases by agents, lessors and database operators. These are not government systems. Tenancy databases are registers run by privately owned companies. A tenancy database is a record that holds personal information about someone who has lived in a rental property, and can include information used for past, present, or future rental agreements. The RTA does not operate or maintain information on tenancy databases. For any Queensland property manager, knowing both how to use these databases and when the law prohibits you from using them is non-negotiable.

How a Tenancy Database Works in Queensland Real Estate

A tenancy database, sometimes called a “blacklist”, contains information about tenants and is used by rental providers such as real estate agents and landlords to screen potential tenants. These databases are usually run by private companies, who charge a fee for access to the information. The three most prominent providers operating in Queensland are TICA (Tenancy Information Centre Australasia), the National Tenancy Database (NTD), and Trading Reference Australia. In Queensland, many real estate agents use the TICA database, and many agents and lessors are members of TICA.

The database framework sits within Chapter 9 of the RTRA Act, which the Act dedicates entirely to information about tenants. The relevant part — Part 3 of Chapter 9 — governs tenancy databases specifically, with key provisions running from sections 457F through 464 covering definitions, notice obligations, listing restrictions, data quality requirements, access rights, and QCAT applications. The use of such databases in Queensland is governed by the RTRA Act as well as the Commonwealth Privacy Act 1988. There are strict rules about information that can be stored on a database.

There are two distinct database types agents need to understand. The database rules under the RTRA Act apply to all external tenancy databases, but do not apply to internal databases kept by a real estate agent or housing provider. An agency’s own internal blacklist — notes kept in a property management system that are never shared externally — falls outside the regulated regime. Once information is disclosed to a third-party commercial operator, however, all of the Act’s listing, notice, and data quality obligations apply in full. Agents who conflate the two regimes and apply external-database rules loosely to their own records, or vice versa, routinely expose their principals to liability.

When an application comes in and an agent runs a database check, specific notice obligations are triggered immediately. If the lessor or agent uses a tenancy database, they are legally obliged, within 7 days after accessing the database, to provide the applicant with written notice as to the fact there is personal information about the applicant listed in the tenancy database (section 458B of the RTRA Act). This is not discretionary — the 7-day window starts from the moment the search is run, not from the moment you decide to decline the application.

Why a Tenancy Database Matters for Queensland Agents

Tenancy databases hold information about the tenancy history of tenants. They are often used by real estate agents and lessors to decide a tenant’s suitability when assessing tenancy applications. In a competitive Queensland rental market, where multiple applications may arrive for a single property within 24 hours of listing, a tenancy database check is a core due-diligence step. A verified adverse listing — one that meets the RTRA Act’s criteria — gives a property manager and their lessor-client material information about prospective risk. An unlawful or sloppy listing, on the other hand, creates serious legal exposure for the agent who made it.

The consequences of a database listing for a tenant are significant. If an agent or lessor alleges a tenant has breached their tenancy obligations and lists them on a tenancy database, that tenant may find it difficult to rent a property. That gravity is precisely why the Act imposes strict pre-conditions on listing. A property manager who lists someone outside those conditions is not merely bending the rules — they are potentially destroying a person’s ability to secure housing, exposing themselves and their agency to QCAT applications and financial penalties, and undermining the professional standards that the RTRA Act exists to protect.

Breaches of the RTRA Act’s database requirements carry a maximum penalty of between 20 penalty units and 40 penalty units. Anyone who does not comply with a QCAT order faces a maximum fine of 50 penalty units. QCAT can also order compensation be paid to a person affected by the non-compliance. At current Queensland penalty unit values, a 50-unit fine for an individual is a material sum — but the reputational damage to a property management business that ends up subject to a published QCAT decision is the greater long-term cost.

It is also worth noting what tenancy databases cannot do. The tenancy database provisions of the Act and Regulations do not apply to social housing databases (section 458 of the RTRA Act). A social housing database is a separate database kept for the purpose of providing housing services under the Housing Act 2003 (Qld). Agents placing applicants in community or social housing, or assisting clients who have social housing connections, need to recognise that an entirely separate information regime applies to those providers.

Legal Requirements and Lawful Grounds for Listing

This is where most compliance errors originate. The RTRA Act and the Residential Tenancies and Rooming Accommodation Regulation 2025 (Qld) together prescribe exactly who can be listed, for what reasons, and only after what procedures. Every element is mandatory.

Who can be listed

Only tenants named on the tenancy agreement can be listed on a tenancy database (section 459 of the RTRA Act). Tenants can only be listed on a database after the tenancy agreement has ended. There must be a valid reason for the listing (section 459 of the RTRA Act). This last point deserves emphasis: the tenancy must have concluded before any listing can be made. An agent who attempts to list a current tenant — even a seriously defaulting one — is acting outside the law.

Approved grounds for listing

A tenant can only be listed on a tenancy database for an approved reason, which are set out in the Residential Tenancies and Rooming Accommodation Regulation 2025 (Qld). The approved grounds under the Regulation are:

• Debt exceeding the bond: Where the tenancy has ended and the amount owed exceeds the rental bond, and either the tenant was served a Notice to Remedy Breach (Form 11) for rent arrears and failed to remedy it; money owed under a conciliation agreement or QCAT order was not paid on time; or the tenant abandoned the property (unless the matter is subject to a current QCAT determination). If no rental bond has been paid, a tenant cannot be listed unless the amount owing is more than one week’s rent.
• Objectionable behaviour: Where QCAT has terminated the tenancy agreement for that reason.
• Repeated breaches: Where QCAT has terminated the tenancy agreement for that reason.

The debt threshold is critical and frequently misapplied. An outstanding amount that falls at or below the bond paid is not a lawful basis for listing. This was a deliberate legislative amendment to prevent agents from listing tenants for relatively minor end-of-tenancy disputes — the kind that should properly be resolved through the RTA’s dispute resolution service rather than a permanent adverse record.

Domestic and family violence exemptions

A tenant who has experienced domestic and family violence should not be listed if the breach is the result of the actions of a person using violence. This protection is not optional. An agent who lists a tenant for damage caused by a domestic violence perpetrator — whether that perpetrator is the other co-tenant, a former partner, or a third party acting with violence — is in breach of the Act. A tenant under the agreement who was a perpetrator of domestic or family violence can be listed on a tenancy database if there are grounds — meaning the protection runs to victims, not perpetrators. Agents managing vacated properties where DFV is a factor must assess circumstances carefully before any listing decision is made.

The pre-listing notice requirement

The listing must be accurate, complete, and not misleading. Landlords and agents are required to notify tenants in writing before listing them and provide them with 14 days to object to the listing (section 459(2) of the RTRA Act). This proposed-listing notice is not a formality — it is a procedural condition precedent to a lawful listing. Sometimes, listings are found to be unlawful. A listing is unlawful if it is not made for a lawful reason, or procedural requirements are not adhered to — for example, where the listing is not “proposed” to the tenant before it is made.

However, if the tenant moves out and does not provide forwarding details, the tenant may not receive notice of the proposed listing. The Act requires that reasonable steps be taken to notify the tenant. Where a forwarding address is genuinely not available, agents should document every step taken to attempt notification — this contemporaneous record is your protection if the listing is later challenged.

What Queensland Agents Need to Know About Tenancy Database Compliance

Data quality obligations don’t end at listing

Once a listing is made, the agent’s obligations continue. A tenancy database company and the person who makes a listing are both responsible for ensuring the quality of personal information on a database. If a debt has been paid by a defaulting tenant, the listing must be removed from the database. If a property manager becomes aware that information they have listed is inaccurate, incomplete or ambiguous, they must let the database operator know in writing within 7 days how to amend it. The same applies for removing out-of-date information. They must also keep records of these notifications for a year.

This ongoing obligation catches agents out repeatedly. A listing made lawfully at the time of the tenancy’s end may become inaccurate — if the former tenant subsequently pays the outstanding debt, settles via conciliation, or if the QCAT matter underpinning the listing is overturned. The agent carries a positive duty to update or remove. Failing to act on newly available information is itself a breach of the Act, separate from the original listing decision.

The database owner must amend or remove the information within 14 days of being notified. All listings must be removed after 3 years. In practice, tenancy database operators automatically remove listings after three years. It is uncommon for a listing to remain after the three-year period.

Providing information to applicants who are listed

When running a database check on a prospective tenant and finding a listing, the agent’s disclosure obligation is immediate. If a rental provider finds a person on a database, they are required to advise the person within 7 days of the information about the person that is stored on it, who listed the information, how and in what circumstances the person can have the information amended or removed, and how the applicant can obtain the information.

Applicants also have the right to access their own listing. A rental provider or database operator must provide a person with a copy of information held about the person on the database within 14 days of a request by the person. A fee may be charged for access, but it must be reasonable and must not apply to the initial lodgement of the request — the Act separates the act of requesting from the production of the information.

Tenant dispute rights agents must understand

Queensland agents need to be familiar with the QCAT pathways available to tenants, because these pathways flow directly back to the agent or agency that made the listing.

If the tenant believes there has been a breach in the listing process — an unlawful listing that does not meet the approved criteria under section 459 of the RTRA Act — the tenant must apply to QCAT within six months of becoming aware of the breach (section 460 of the RTRA Act). There is no time limit to dispute an inaccurate, incomplete, out of date, ambiguous, unjust listing, or a listing causing extreme hardship (section 461 of the RTRA Act). The distinction matters: a procedurally unlawful listing (wrong grounds, no prior notice) carries a 6-month limitation window for challenge; a listing that is simply wrong on the facts has no limitation period at all.

A person can apply to QCAT for an order to prohibit a rental provider from listing information about them on a database, or to have information listed on a database amended or removed. QCAT can also order compensation to be paid, and non-compliance with a tribunal order is a separate, more serious offence carrying penalty fines up to 50 units.

Application disclosure: telling applicants which databases you use

Before a tenancy is agreed, agents have a disclosure obligation that precedes any search. When an applicant applies for a tenancy, the agent or lessor must advise them which tenancy databases they use, the reasons they use the databases, and how they can contact the database operator. This obligation is contained in section 458A of the Act (notice of usual use of a database). It applies at the application stage — before any search is run and before any listing is found. Agents who only mention database use after discovering an adverse listing are not complying with the Act.

What This Means for Queensland Agents

The tenancy database framework under the RTRA Act is one of the more technically demanding areas of Queensland property management compliance. The obligations run in both directions — what you must do before listing, what you must do after — and each step carries its own timeframe and documentary requirement.

The practical rules that matter most in day-to-day property management are these. A listing can only be made after the tenancy ends. The outstanding debt must exceed the bond. You must give written notice to the former tenant and allow 14 days before listing. The information must be accurate and must remain accurate — which means you carry a positive duty to correct or remove a listing if circumstances change. If a listed debt is paid, the listing must come down. The 7-year retention rule for personal information collected during a tenancy applies separately and concurrently with these database obligations.

If a rental provider lists information on a database and becomes aware the information is inaccurate, incomplete, ambiguous or out of date, the rental provider must notify the database operator of this within 7 days, and advise the operator of how the information must be amended or that it must be removed. The operator must amend or remove the information within 14 days.

For principals running multi-agent teams, the risk management implication is clear: database listing decisions should never be left to a single junior team member acting without oversight. The combination of mandatory pre-listing notice, prescribed grounds, post-listing data quality obligations, and the absence of a limitation period for inaccuracy disputes means that a poorly made listing can resurface years later. Building a documented internal workflow for every listing decision — grounds confirmed, notice sent and recorded, 14-day objection period respected — is the only defensible approach.

The RTA does not operate tenancy databases and cannot resolve disputes about their content. Complaints about unlawful listings go to QCAT, and complaints about Privacy Act compliance can also be directed to the Office of the Australian Information Commissioner. Agents working with the full legislative framework — Chapter 9 of the RTRA Act together with the Residential Tenancies and Rooming Accommodation Regulation 2025 (Qld) and the Commonwealth Privacy Act 1988 — are the ones who avoid tribunal proceedings and protect both their clients and their licence.