This is the Identify problem in plain language. The issue was not simply that the listing looked convincing. The issue was that the system allowed money and trust to move faster than verification.
A person can copy photos. A person can copy wording. A person can sound polite, professional, even urgent. But if the person has not been verified — and if their authority over the property has not been verified — the relationship begins on an unproven foundation.
The First Question in Renting
Every rental transaction should begin with one simple question: Are we real?
For tenants, that means: Is this landlord, owner, or property manager real? Are they authorized to lease this unit? Is this listing legitimate?
For landlords and property managers, that means: Is this applicant the real person behind the documents? Is the ID genuine? Is the person signing the same person who was screened?
The rental market does not fail only when bad people appear. It fails when the system cannot distinguish a real person from a fabricated one before money, access, or legal obligation begins. — Jimmy Ng, IDEAL Framework
Why Canada, Why Now
Canada’s rental market now operates in a high-friction environment: more digital interaction, more platform dependency, more cross-border movement, and more document-based decision-making. That would already raise risk. But fraud tools are improving faster than the average landlord, tenant, or small operator can adapt.
This is why the IDEAL Framework does not start with marketing, applications, screening scores, or digital signatures. It starts with identity. Because if the person is unverified, then the documents, the communication, and the lease all inherit that uncertainty.
The Triage Rule
In a hospital, triage starts by identifying the patient. Before treatment, before medication, before surgery, the staff must know who is in front of them. Are the records attached to the right person? Is the history accurate? Are there language barriers, missing records, or urgent risks that change how the next step should happen?
Renting now faces a similar problem. If you do not know who the person is, you cannot safely decide what data to collect, what level of access to give, what promises to rely on, or what risk you are actually carrying.
That is why Identify must come first. Not because it solves everything. But because without it, nothing after it is stable.
Who This Protects
Protection from ghost landlords and fake listings
- Verify the person asking for money is real.
- Verify the person has authority over the property.
- Reduce the chance of giving documents to the wrong party.
- Reduce the chance of losing deposits before move-in.
Protection from fabricated identities and false documents
- Verify the applicant behind the application.
- Confirm the signer matches the screened person.
- Reduce occupancy, payment, and safety risk.
- Start the file with a defensible first step.
Operational control and audit readiness
- Set one standard instead of ad hoc judgment.
- Create repeatable intake across staff and portfolios.
- Reduce team inconsistency and missed red flags.
- Strengthen incident response when disputes happen.
The identity layer your product should not skip
- Know where your tool fits in the rental chain.
- Stop treating identity as a side feature or addon.
- Design safer data intake and safer workflow branching.
- Build trust infrastructure, not just convenience features.
In other words, Identify is not only about stopping bad actors. It is about giving good actors a safer starting point. A real system must protect both sides before the relationship becomes expensive, emotional, or hard to unwind.
When Identity Fails
The failure patterns are repetitive. The names and cities change, but the underlying breakdown stays the same.
| Failure Pattern | What It Looks Like | Why It Matters |
|---|---|---|
| Ghost landlord | Someone advertises a unit they do not own or control. | Tenant sends money or documents to a stranger. |
| Fabricated tenant identity | A real-looking application is backed by altered or mismatched identity evidence. | Landlord makes a legal and financial decision on false input. |
| Signing mismatch | The person who signs is not clearly the person who was screened. | The lease becomes harder to enforce and defend. |
| Authority gap | The person communicating cannot prove they are authorized to lease the property. | Trust is misplaced before the first step is even valid. |
Mutual Verification, Not One-Sided Verification
One of the biggest problems in renting is that verification is often imagined as something only tenants must endure. That is too narrow for today’s risk environment. A modern rental process must verify both directions.
What tenants should verify
- The person leasing the property is a real person or legitimate business.
- The person has authority to lease the unit.
- The property details match what is being offered.
- The request for deposit or documents comes after legitimacy is established, not before.
What landlords and property managers should verify
- The applicant is a real, live person connected to the identity being presented.
- The application details are consistent with the identity record.
- The person moving in is the person who was screened.
- The verification event is stored, timestamped, and reviewable.
The IDEAL 4-Layer Identity Model
Good identity verification is layered. One document check alone is no longer enough. A durable Identify process should answer four different questions.
Identity Proofing
Is the credential real enough to rely on? This is the document and record validation layer.
Liveness & Match
Is a real live person present, and do they match the credential being used?
Authority Proof
Even if the identity is real, does this person actually have the right to lease, manage, sign, or collect?
Recorded Verification Event
Was the verification stored with time, method, and outcome so the step can be proven later?
This is the difference between looking secure and being secure. The rental industry has too many visual checks and too few recorded verification events.
If you cannot show the proof, you do not have the step. — IDEAL Framework principle
For Software and App Builders
For product teams, Identify should not be treated as a login problem, a simple KYC widget, or a box to tick before the “real” workflow starts. In renting, Identify is the workflow gate that determines whether the platform is collecting, routing, and acting on trustworthy input.
If your tool helps landlords, tenants, property managers, marketplaces, payments, leasing, maintenance, or screening, then your product is already participating in trust delivery. The question is whether it does so explicitly and safely.
Record who was checked, how they were checked, when they were checked, and whether the result can be reviewed later.
A real person is not automatically an authorized landlord, manager, owner, or signer. The product should treat those as different proofs.
Do not allow document upload, deposit requests, lease issuance, key handoff, or sensitive data collection until verification conditions are met.
The output of Identify should become the first trusted record in the file that the next pillar can inherit safely.
Privacy and Fairness Still Matter
Strong identity verification does not mean careless data collection. It means collecting only what is necessary, at the right moment, for a clear purpose, with proper controls.
It also does not mean using identity as an excuse for arbitrary exclusion. A safer system must still be fair, proportionate, and understandable. The goal is not to create a harsher market. The goal is to create a more trustworthy one.
Good Identify practice should be:
- Purpose-limited — only collect what the step actually needs.
- Sequenced — verify before more data is requested.
- Recorded — keep an auditable trail of what was done.
- Access-controlled — not every staff member should see every detail.
- Explainable — the workflow should be understandable to ordinary users.
Operational Checklist
If you manage property, build tools, or advise housing operations, this is the practical standard to aim for.
No deposit, no key, no code, no signed lease workflow until the identity gate is cleared.
Do not stop at “this is a real person.” Ask whether they are authorized to act in this transaction.
The verification step should leave a timestamped record that can be reviewed, exported, and defended later.
If one team member verifies one way and another member improvises, the process is already unstable.
The verified identity event should become the first trusted record inside the unified applicant or tenancy file.
How Identify Connects to the Rest of IDEAL
The IDEAL Framework is a chain, not a menu. The output of Identify becomes the trusted input for everything else.
| Pillar | What Identify Makes Possible |
|---|---|
| Data | You can now collect and store documents against a verified person instead of an unproven identity. |
| Engage | Communication can now be attributed to verified parties in one defendable timeline. |
| Assess | Decisions can now be made on more trustworthy input and applied more consistently. |
| Lease | The lease is now anchored to verified people and a more stable evidence chain. |
This is why Pillar 2 comes next. Once the first gate is real, the file can become real too.

References
- CBC News — “35 people in Kitchener, Ont., out total of $40K, say police about one rental scam.”
cbc.ca/news/canada/kitchener-waterloo/rental-scam-kitchener-1.7327746 - TransUnion Canada Newsroom — 2025 fraud trends coverage and Canadian business fraud-loss findings.
newsroom.transunion.ca/?h=1&t=FraudTrends - IDEAL Framework — Home page and cross-page research framing for the five-pillar trust infrastructure.
idealframework.com - IDEAL Framework — “IDEAL Explained” evidence page.
idealframework.com/idealexplained - IDEAL Framework — “Generations Research” historical trust analysis.
idealframework.com/generations_research