As of July 29, 2026. The moment LTB orders became public data on July 24, one question went live in every landlord forum and every tenant advocacy meeting at once: can a landlord look up a prospective tenant's Board history — and act on what they find?
The honest answer has two halves, and everyone selling you one half is selling you trouble. Yes, you can read a public order — publishing them was a transparency decision, and no statute makes a reader a lawbreaker. And no, nothing about rental decisions loosened that day — the Human Rights Code governs every application outcome exactly as it did on July 23, the authorized screening package remains both the legal template and the better predictor, and order-based screening imports five specific risks the authorized tools don't. This guide walks all of it: what lawful screening looks like, where the new archive fits and doesn't, and the process that keeps a file defensible. One thing before anything else: this is general information, not legal advice — on this topic more than most.
The Tenant Screening Checklist
The authorized package run the same way every time — what you may ask, the consents to collect, the together rule, the grounds that never enter a file, and the public-orders-era sequence. One page, updated.
Get Free PDF →What screening is supposed to look like
Start where the law starts. Ontario's framework — the Residential Tenancies Act's application rules and Ontario Regulation 290/98 under the Human Rights Code — authorizes a specific toolkit: income information, credit checks (with the applicant's written consent, per the Consumer Reporting Act), credit references, rental history, and guarantees.
And inside that toolkit sits the rule that carries the Code's whole philosophy in one sentence. Per the Ontario Human Rights Commission's guidance: income information may be sought and considered only if the landlord also seeks and considers the applicant's credit references and rental history — the package weighed together, never income alone as a threshold. No single number decides. The guardrails follow the same logic: a first-time renter's missing rental history cannot be counted against them; income ratios like 30–35 per cent are guidelines, and rigid automatic cutoffs create Code risk; no Social Insurance Number can be demanded; ID is viewed, not retained; medical information stays out entirely, except where a tenant initiates an accommodation request.
Behind all of it, the protected grounds in housing: race, ancestry, place of origin, colour, ethnic origin, citizenship, creed, sex, sexual orientation, gender identity and expression, age, marital status, family status, disability — and the one that matters most for what follows, receipt of public assistance, protected in housing by name.
It's worth saying why the package works, beyond its legality: it triangulates. Credit shows how obligations were handled across years and creditors; references show how a tenancy actually ran; income shows current capacity; and the together rule forces them to be read against each other, so no single bad quarter — or single good number — decides. That's not bureaucratic caution; it's better prediction, and it's the standard any new data source should have to beat.
The two halves of the LTB-orders question
Half one: reading is lawful. The Board's final orders are public by design as of July 24 — published under an open licence that invites reuse — and the Code regulates decisions, not visibility. Nobody becomes a lawbreaker by reading a public document.
Half two: deciding is exactly as regulated as it was. Nothing in the release amended the Code, the regulation, or the application rules. A rejection that engages a protected ground — directly, or through a proxy that selects on its correlates — is as actionable with public data as it ever was with gossip — and in one way more so, because a public-data trail timestamps exactly what was looked up and when, where gossip never left a receipt. The question that matters was never "may I look." It's "what happens to my decision-making when I do" — and that's where the five risks live.
💡 For landlords: Before reading further, ask the operational question — what would an order tell you that the authorized package doesn't? If your honest answer is "how they behaved in a dispute," note that this is exactly the judgment the risks below complicate most: disputes are where rights get exercised, circumstances get adjudicated out of context, and names get confused.
The five risks the authorized tools don't have
1. Identity error. The catalogue is a CSV with no date of birth and no verification layer — a name is not an identity. An applicant who shares a name with a respondent in three arrears orders can be rejected for a stranger's history, and the wrong-person rejection is both the most concrete harm available and the most straightforward complaint file imaginable.
2. Penalizing rights-exercise. Some Board histories are T-applications — tenants who filed maintenance claims or harassment claims, including ones they won. Screening those applicants out is the practice the public "blacklisting" critique names explicitly; it invites Code exposure wherever it proxies protected grounds; it's the pattern most likely to draw complaints and coverage; and it cuts directly against the transparency purpose the publication serves. A tenant whose only order is a vindication should not read, in your process, as a risk.
3. Proxy discrimination. The Code catches indirect and constructive discrimination — no intent required. Order histories correlate with protected grounds, and an arrears-heavy filter lands hardest on recipients of public assistance. "I never asked about assistance" is not a defence to a filter that selects on its correlates.
4. The archive's structural bias. Settled and withdrawn files are invisible; the newest months are absent on the publication lag; the backfill is partial. The data systematically over-shows the adjudicated and hides the resolved — treating it as a complete record is factually wrong before it's legally risky. Note who the bias flatters and who it doesn't: a landlord-tenant pair who resolved an arrears file sensibly at mediation leave no trace, while the same dispute pushed to a hearing leaves a permanent public order — the archive punishes the adjudicated path, not the worse tenant.
5. One order is an episode, not a character. Files settle for a hundred reasons; circumstances change; the order says what happened once, not what happens next. The authorized package predicts a tenancy; an order narrates a moment.
If Board history enters a file at all — the defensible sequence
The order of operations, if history is going to touch a file at all: run the authorized package first — application, consents, credit, references, rental history, income, together. Only then, if Board history surfaces — disclosed by the applicant, or via a screening service — verify identity beyond a name-match; the catalogue won't do it for you. Read the actual order — the reasons, not the existence; our lookup guide covers the mechanics. Give the applicant the chance to explain — the same courtesy the credit system is legally built around — consumer-reporting law assumes disputed entries get explained and corrected, and a screening habit that grants Board records less process than credit records is hard to defend out loud. Decide on the package, and document the non-discriminatory basis. And never automate a history threshold.
Using a third-party screening service? Ask two questions before relying on one: how does it verify identity, and how does it handle consent — consumer-reporting rules may apply to a service even where reading a public order alone wouldn't, and that's a question to put to the provider, not a detail to assume.
Two worked files show the sequence earning its keep. The explained order: an applicant discloses an L1 from 2023 — job loss, arrears, a settlement honoured, the tenancy continued two more years. The order alone said "arrears"; the explanation said "recovered"; the package — current income, strong references, rebuilt credit — said yes. That's the process working. The defensible no: a poor current-landlord reference, thin credit, unverifiable income. That's a no on the authorized package alone — and it's the stronger file for never having touched Board history at all.
💡 For property managers: If screening is delegated to your firm, the process is your liability surface. Write the sequence into the SOP, train the identity-verification step, log the explanation opportunity, and audit any filter quarterly for proxy patterns. "The service did it" is not a defence you want to test.
For tenants: the same archive, your side of it
The application, from your chair: you can be asked for the toolkit above — income (weighed with everything else), consent to a credit check, references, rental history, possibly a guarantor. You cannot be asked anything probing a protected ground — family status, nationality, creed and the rest — nor for medical information outside an accommodation you raise, nor for a SIN as a requirement, and a missing rental history cannot count against you if you've never rented before.
And the archive is yours too — a counter-move the criticism under-weights. Pull your own orders first: twenty minutes with the catalogue tells you exactly what a landlord could find, lets you flag an error to the LTB where the record is wrong (a missing or misattributed order goes to [email protected], per the dataset's own instructions), and turns a surprise into a story you tell on your own terms — an explained order beats a discovered one every time.
💡 For tenants: If you suspect an order-based rejection: ask for the basis in writing, keep every message, and know that where a protected ground is engaged, the Human Rights Tribunal of Ontario route exists — and a lookup-followed-by-rejection paper trail is unusually discoverable. If your Board history is a claim you filed — especially one you won — that history is your rights working, and this guide's whole point is that a fair process should read it that way.
The honest recommendation — and what to watch
Said plainly, because someone should: for most small landlords, the package you were always allowed to use is stronger than the archive you just gained — more predictive, more defensible, already built for consent and explanation, and cheaper than the time tribunal research takes to do honestly — a proper order review means downloading the report, verifying identity, reading full reasons, and offering an explanation round; done right it's an hour per applicant, and done fast it's every risk on the list. The archive's best screening use may turn out to be the tenant's own: the pre-explained order, the corrected record, the surprise defused.
What to watch from here: Ontario Human Rights Commission commentary on order-based screening (none yet — expect it, and we'll cover it when it lands); the first tribunal complaints arising from order lookups, which seem likelier than not within the year given how discoverable the pattern is — a projection, plainly flagged as one; third-party tools' verification practices as they proliferate on the open licence; and the backfill's growth, which changes what "having history" even means as older files surface.
💡 Consistent process is a records problem: the same application, the same consents, the same sequence, the same documentation, every time — that's what Tenon10's screening workflow standardizes, so the file you keep is the file you'd want read back. Free for up to 3 units, tenants free on every tier. Create a free account or see current plans.
The Tenant Screening Checklist
The authorized package run the same way every time — what you may ask, the consents to collect, the together rule, the grounds that never enter a file, and the public-orders-era sequence. One page, updated.
Get Free PDF →Key takeaways
- Both halves are true: reading a public order is lawful, and every rental decision is as regulated as it was on July 23.
- The authorized package — credit, references, rental history, income, together — is the legal template and the better predictor.
- The together rule is the philosophy: no single number decides — and order-screening tempts single-datum decisions.
- The five risks: identity error, rights-exercise penalties, proxy discrimination, the archive's structural bias, and the episode-not-character problem — compounding in automation.
- If history enters a file: late, verified, read in full, explained, documented — never automated.
- Tenants: pull your own orders first, pre-explain where history exists, and know the missing-history rule protects first-time renters by name.
The archive changed. The law didn't.
Yes, you can read the Board's orders now — that's what publishing them meant, and pretending otherwise helps no one. And no, nothing about the decisions you make with them loosened at all: the Code stands exactly where it stood, the authorized package remains the tool the law actually built for this job, and the five risks above are the honest price of reaching past it. Screen with the package, weigh it together, hear the applicant, write the basis down — and if that sounds like what fair screening always was, that's the point. This is general information, not legal advice; for a live dispute or a close call, a lawyer or a community legal clinic is the right next step. As of July 29, 2026 — updated when the OHRC weighs in.
One process. Every applicant. Documented.
Applications, consents, and screening records that run identically every time — the consistency the Code expects, built in. Free for up to 3 units.
Free for up to 3 units • Tenants always free • See current plans
Related resources
- LTB Orders Are Now Public — what the release actually is, and how to read an order well.
- Tenant Screening and the Human Rights Code — the standing evergreen on the application itself.
- Bill 60 and Bill 97, Six Months In — the modernization season this release arrived in.
Frequently asked questions
Is it legal to look up a tenant's LTB history?
Reading a public order isn't prohibited — the orders were published as open data on July 24, 2026. What the law governs is rental decisions: the Human Rights Code applies to every application outcome exactly as before, and rejections that engage protected grounds — directly or by proxy — are actionable regardless of where the information came from.
Can a landlord reject me because of an LTB order?
Not on a basis that engages a protected ground under the Code — and a fair process should verify identity, read the actual order, and let you explain. If you suspect an order-based rejection, ask for the basis in writing, document everything, and know the Human Rights Tribunal of Ontario route exists where a protected ground is engaged. This is general information, not legal advice.
What can landlords legally ask on a rental application in Ontario?
The authorized package: income information, credit checks (with written consent), credit references, rental history, and guarantees — with income considered only alongside credit references and rental history, weighed together. Off-limits: protected-ground probing (family status, nationality, medical information outside accommodation), SIN demands, and holding a first-time renter's missing history against them.
Do income ratios like 30% disqualify an applicant?
No — ratios are guidelines, not legal thresholds, and rigid automatic cutoffs create Human Rights Code risk. The regulation's structure requires the package weighed whole.
Should landlords use LTB orders for screening at all?
For most small landlords, the honest answer is that the authorized package predicts better and defends better. If Board history enters a file at all, the defensible sequence is: package first, identity verified beyond a name-match, the actual order read, the applicant heard, the decision documented — and never an automated history threshold.
