ASSESS — Diagnose Risk, Prescribe Better Choices | Pillar 4 of 5 | IDEAL Framework by Jimmy Ng
A
Pillar 4 of 5 Criteria-Based Diagnosis • Explainable • Audit-Ready

ASSESS — Diagnose Risk, Prescribe Better Choices

The rental market is not short on applications. It is short on a system that can read information properly, verify what is real, and explain why a decision was made. Landlords cannot safely screen 20, 30, or 50 files by instinct. Newcomers cannot prove their worth through a process that only understands one type of history. Software builders cannot fix this by shipping another isolated tool. ASSESS turns raw files into a diagnosis, a result band, and a documented next step.

50
Applications can arrive faster than a landlord can verify them properly.
5
Diagnosis bands replace pass/fail thinking with explainable pathways.
0
Times “we had a bad feeling” has stood up as a real process standard.
1
Published rubric. Same order. Same method. Every applicant.
100%
Assessment depends on upstream identity, data, and engagement quality.

Abstract

Canada is building housing. Listings can rise and vacancy can soften, but the rental system still breaks because most participants do not trust the screening process. Landlords do not know what is real. Renters do not know how they are being judged. Property managers are buried in fragmented tools. Software teams keep optimizing small steps inside a workflow that is structurally broken.

ASSESS exists because screening is not supposed to be a mystery. It is supposed to be a disciplined decision process. The job is not to punish uncertainty. The job is to convert uncertainty into a published criterion, a verification step, a diagnosis band, or a documented pathway.

This is why ASSESS does not end with “approved” or “rejected.” It starts with diagnosis. Is this a strong match? A match with conditions? A review case? A file that is not ready yet? Or a file that should not proceed because the risk is too high and the facts do not support trust?


01 — The IDEAL Logic Chain: Why ASSESS Needs Everything Before It

ASSESS does not work in isolation. It needs verified identity, organized data, and clear communication upstream. Without those, you are not assessing a file. You are assessing fragments, stories, and assumptions.

I
If we cannot confirm the person, nothing downstream is reliable.
D
If the file is scattered, the assessor works from incomplete evidence.
E
If delivery is fragmented, key facts arrive late or never arrive at all.
A
Assess
Diagnose risk, explain the result, prescribe the right next step.
L
Safe, seamless, rewardable execution begins only after the match is clear.
The dependency is absolute. If IDENTIFY did not confirm the person is real, the documents may be fake. If DATA did not organize the file, the assessor is working from fragments. If ENGAGE did not deliver information properly, the result is distorted before assessment even begins.

02 — Five Diagnosis Bands, Not One Blind Score

Most screening systems pretend the job is simple: pass or fail, green or red, approved or rejected. Real life is not that clean. A strong file and a dangerous file should never be treated the same as a thin file, a newcomer file, or a borderline file with stabilizers available.

ASSESS uses bands because a diagnosis should tell the next person what the result means and what to do next. The point is not just classification. The point is prescription.

Band 1 — Strong Match
Proceed

The file is verified, the criteria are met, and there are no material red flags requiring delay.

  • Identity and key evidence confirmed.
  • Capacity, payment history, and fit align with published criteria.
  • Move forward to LEASE.
Band 2 — Match with Conditions
Proceed Carefully

The file is generally sound, but one or more neutral conditions should be completed or documented before move-in.

  • Example: guarantor, reserve proof, insurance confirmation, or corrected document source.
  • Conditions must be neutral, published, and applied consistently.
  • The result is not a hidden rejection. It is a managed path.
Band 3 — Review Required
Hold & Verify

The file may become acceptable, but material questions remain unanswered.

  • Verification is incomplete or contradictory.
  • Context matters and more evidence is needed.
  • The decision is paused, not guessed.
Band 4 — Not Yet Ready
Build the File

The applicant may still become a future match, but the current file is too thin or too unstable to proceed now.

  • Common with newcomers, students, or recent transition cases.
  • Offer a documented pathway: stronger records, more reserves, verified history, rent reporting, or time.
  • This creates a trust-building road instead of an unexplained dead end.
Band 5 — Do Not Proceed
Stop

The file does not support trust. The risk is too high, the facts do not line up, or fraud indicators remain unresolved.

  • Identity mismatch, fabricated references, falsified income, non-cooperation, or unresolvable contradictions.
  • The reason must still be documented by criterion and evidence.
  • Even “no” decisions require a real process.
The band is not the end of the process. It is the beginning of the next correct action. Good assessment does not just sort people. It tells the system what should happen next, and why.

03 — The Real Trust Gap: Why Current Systems Fail Both Sides

The rental market has a trust crisis that more apps, more uploads, and more dashboards have not solved. Landlords do not need more volume. Renters do not need more opacity. Property managers do not need more tabs. Builders do not need another scoring widget sitting on top of bad intake.

🏠
The Landlord’s Problem
Fifty applications arrive. Half look polished. A few are probably real. A few are probably fake. References may be friends. Pay stubs may be generated. There is not enough time to manually do full diligence on all of them, so instinct quietly takes over.
ASSESS fix: published criteria + verification gates reduce volume into comparable, documented files.
🌍
The Newcomer’s Problem
The person may have good income, real history, and responsible habits, but their proof comes from another country, another language, or another system. The file looks unfamiliar, so the person is treated as risky.
ASSESS fix: thin local history is translated into neutral stabilizers, not automatic exclusion.
📉
The Investor’s Problem
After one or two bad experiences, landlords start screening harder, slower, and more emotionally. Good renters get rejected. Vacancies last longer. Costs go up. Trust falls further.
ASSESS fix: repeatable decisions reduce overreaction, delay, and inconsistent picks.
💻
The Builder’s Problem
Many proptech products solve one screen inside the workflow. Few solve the decision architecture. Without the full intake-to-decision chain, software can speed up a broken process instead of repairing it.
ASSESS fix: build tools against a decision standard, not around isolated product features.
A hospital does not triage a patient by vibes. It records identity, symptoms, observations, history, and changes over time. Housing needs the same discipline. Screening is not supposed to be guesswork. Jimmy Ng, IDEAL Framework

04 — The Core Mechanism: Criteria → Evidence → Verification → Diagnosis → Prescription

ASSESS converts screening into an auditable workflow. The output is not a mystery score. It is a defensible decision note tied to neutral criteria, verified facts, and a documented next step.

ASSESS workflow (audit-grade) 1. Publish neutral criteria before reviewing any file 2. Collect only what is needed — privacy discipline matters 3. Verify evidence — identity, documents, references, source authority 4. Apply the same rubric in the same order to every applicant 5. Translate uncertainty into a band, not a guess 6. Write a decision note — timestamped, explainable, reviewable 7. Prescribe the next step — proceed, proceed with conditions, hold, build file, or stop
Key principle. “We just had a bad feeling” is not a process. “The file entered Band 3 because employment verification remained incomplete and the rent-to-income ratio sat outside the published guideline without stabilizers” is a process.

05 — Information Overload: The Hidden Assessment Failure

A landlord reviewing 50 applications is not making 50 careful decisions. They are making fast judgments under fatigue. Pages of bank records, PDFs, screenshots, texts, email threads, and verbal notes do not produce diligence by themselves. They produce overload.

ProblemWhat HappensASSESS Response
Too many pagesThe assessor skims, misses contradictions, and relies on first impression.Use a structured summary with verification flags before scoring any file.
Inconsistent formatsOne applicant sends PDFs, one sends screenshots, one sends fragments by text.DATA standardizes the file before review.
Unverifiable claimsReferences, income, and employer details look complete but are theatre.Claims are not scored until they are verified at source.
No time for due diligenceThe landlord chooses the fastest responder or the smoothest story.ENGAGE reduces friction; ASSESS reduces cognitive load.
The paradox. More information does not automatically create better decisions. Without structure, it usually creates worse decisions with more false confidence.

06 — Fakes Are Everywhere: Why Verification Comes Before Assessment

This is the foundational insight of ASSESS: you cannot assess what you have not verified. In today’s market, the fake file is often cleaner, faster, and more convincing than the real one.

  • Fake pay stubs can be generated in minutes and often look better than genuine payroll records.
  • Fake references often rely on friendly phone numbers rather than actual landlords or employers.
  • Synthetic identities blend real and fabricated information to pass superficial checks.
  • Fake authority appears when the person leasing the property does not actually have the right to do so.
  • Story quality is a poor proxy for truth. Fraud rings are good storytellers.
The uncomfortable truth. In an informal process, a polished fraud application can outperform a legitimate newcomer, student, or variable-income renter because the fake file is optimized for appearance while the real file reflects real life.

This is why IDENTIFY is a hard prerequisite and DATA is a hard discipline. ASSESS starts only after those gates are respected.


07 — ASSESS Decision Lab: Same Rubric, Every Applicant

This interactive example demonstrates how ASSESS generates an explainable result. The numbers are illustrative, but the design principle is fixed: same criteria, same order, same logic, every time.

Decision Lab — Illustrative Criteria + Five-Band Result
Adjust inputs to see how the decision note changes without becoming a black box.

Transparent Rubric

Publish the rubric. Version it. Apply it consistently.
Capacity
Income versus rent obligations. Ratio is a signal, not the whole story.
35%
Verified History
Payment behaviour, reference quality, stability, and confirmation at source.
25%
Documentation Integrity
How complete, coherent, and verifiable the file really is.
20%
Context & Stabilizers
Guarantor, reserves, rent insurance, strong work verification, portable history.
15%
Property Fit
Neutral realities tied to the unit, building, and lease conditions.
5%
Rule. If a criterion cannot be described in neutral language and applied to every applicant consistently, it should not decide the outcome.

Explainable Generator

The note below is written as a process explanation, not a personality judgment.
31%
74
67
2
82

Assessment Result

Band 3 — Review Required
Calculating...
Decision Note Example Output
Loading...

08 — Context Rules: Thin File Does Not Mean Bad Tenant

Modern applicants include newcomers, students, gig workers, remote workers, contract professionals, separated households, and people rebuilding after disruption. Many can be excellent tenants with limited local history. ASSESS turns uncertainty into controlled steps instead of automatic rejection.

SignalCommon FailureASSESS Response
Thin Canadian creditAuto-reject.Request stabilizers: reserves, guarantor, verified employment, or portable payment proof.
Variable incomeAssume instability.Use income history, consistency, reserves, and source verification.
Foreign documentsIgnore or dismiss them.Translate into verifiable equivalents instead of treating unfamiliar as false.
Strong storyApprove on narrative.Story remains secondary until the file is verified.
Automated risk flagBlack-box rejection.Every flag must map to a neutral criterion or a verification step.
Translation rule. Every risk signal must become one of four things: a verification step, a published condition, a diagnosis band, or a documented stop. If it becomes a gut feeling, the system has failed.

09 — Optional Supports: Rent Reporting, Insurance, and Trust-Building Tools

Good assessment does not require every applicant to have the same kind of proof. But it can use optional tools to reduce uncertainty and build trust over time. These tools should support the process. They should not become hidden gatekeeping devices.

Rent Reporting

Rent reporting can help renters turn good payment behaviour into portable evidence. In the IDEAL logic, that belongs to the long-term trust rail: the system should reward people who pay on time and keep their commitments. This is especially important for people who have been responsible tenants but have no useful record to carry forward.

Rent Insurance and Rent-Loss Insurance

Insurance can be part of a responsible risk strategy for landlords and investors, especially where thin files, variable income, or local unfamiliarity create hesitation. But insurance should be used carefully. It is not a substitute for verification. It does not fix fake identity, fabricated documents, or a broken intake process.

Stabilizers, Not Punishment

A guarantor, reserve proof, employer verification, insurance confirmation, or documented rent history can all operate as stabilizers. The purpose is not to punish the person. The purpose is to convert uncertainty into a safer, explainable path.

Design rule for builders. Treat rent reporting, rent insurance, and rent-loss insurance as optional supports that can improve a file or help a future file, not as silent auto-reject switches hidden behind a score.

10 — Review Workflow: Fair Process, Documented

A structured review path reduces conflict and strengthens fairness. If an applicant later claims the process was arbitrary, the file should show that the same rubric was used, the missing evidence was identified clearly, and the person had a defined opportunity to respond.

  1. Reason provided. Explain the band or barrier in neutral process language.
  2. Review window. Set a time-limited path to submit missing or corrected evidence.
  3. Evidence submission. New proof is stored in the DATA ledger.
  4. Re-assessment. The same rubric is applied again. No moving goalposts.
  5. Timestamped note. The updated outcome is documented and retained.
Critical. A review path is only fair if it uses the same published method. If you invent a new standard during review, the process becomes arbitrary again.
Criteria that cannot be applied consistently to every applicant should not drive decisions. Consistency is both the legal protection and the moral foundation. Jimmy Ng, IDEAL Framework

11 — Next on the IDEAL Rail: LEASE

ASSESS confirms that the match is right and the file is clean enough to proceed. Now LEASE turns the decision into a living relationship: payment automation, evidence-grade records, reward loops, and habits that make doing the right thing easier than doing the wrong thing.

I
Verified
D
Organized
E
Delivered
A
Assess
Diagnosed
L
Make it safe, seamless, and rewardable

References

Use this section as the public evidence base for legal, privacy, and process design guardrails.

  • 1. British Columbia Human Rights Code, RSBC 1996, c. 210. Source
  • 2. BC Human Rights Tribunal — housing complaints and process guidance. Source
  • 3. Personal Information Protection Act (BC). Source
  • 4. Office of the Information and Privacy Commissioner for British Columbia. Source
  • 5. Residential Tenancy Branch — Government of British Columbia. Source
  • 6. IDEAL Framework — Home. Source
  • 7. IDEAL Framework — IDEAL Explained. Source
  • 8. IDEAL Framework — Generations Research. Source
  • 9. IDEAL Framework — IDENTIFY. Source
  • 10. IDEAL Framework — DATA. Source
  • 11. IDEAL Framework — ENGAGE. Source
  • 12. IDEAL Framework — LEASE. Source

IDEAL Framework is an evidence-based research initiative developed by Jimmy Ng. This page is educational content designed to support safer process design, fairer rental decisions, and better tool building.

Jimmy Ng, Research Founder of the IDEAL Framework
Jimmy Ng
Research Founder, IDEAL Framework Lab. Building evidence-backed trust systems for Canadian rental housing because the old model is broken, and going back is not the answer.
Explore All Five Pillars