Feature
Screening and compliant decision support
ResidentAxis runs the screening workflow — consent, orders, payer, decision, adverse-action reminder — and leaves the reporting to a consumer reporting agency you contract. It does not make decisions for you.
The problem
Screening is a regulated step wrapped in a convenience feature.
The risk is rarely the report itself; it is consent that was never captured, a decision without a reason, and an adverse-action notice nobody sent. The workflow around the report is what protects an operator.
- Consent is a checkbox in a PDF that nobody can find six months later.
- The same report is ordered twice because the first is not attached to the application.
- Denials are communicated verbally, with no adverse-action record.
- Owners want to pay for screening on some properties and not on others.
The workflow
Consent → order → result → decision → notice
- Capture consent per party
Each applicant and guarantor consents individually; stale consent blocks an order until refreshed.
- Choose the order and the payer
Credit, criminal, eviction or full. Applicant-paid, owner-paid or management-company-paid — owner and PM-paid orders book an expense automatically.
- Run through the provider interface
Orders go to whichever consumer reporting agency you have configured. Results attach to the application; SSNs are never stored — only the provider’s order reference.
- Record the decision
Approve, deny or conditionally approve with a reason. The decision, the income check and any flags are stored with the application and audited.
- Adverse action
A denial surfaces the adverse-action step so the operator sends the notice their counsel has approved.
Illustrative screening card. The provider name and result content depend on the CRA you configure.
Capabilities
What is built, what needs configuration, what is planned
Each row is a real capability in the current build. Labels are derived from the codebase and its test suites, not from a roadmap deck.
How to read the labels
- Built
- Implemented in the current build and covered by its test suite.
- With configured integration
- Implemented; a live outcome requires a provider you configure (keys, contract, or credentials).
- Pilot
- Implemented in part and enabled per pilot customer with tuning.
- Planned
- On the roadmap. Not sold or promised today.
-
Consent gates and adverse-action reminders
BuiltPer-party consent capture with staleness checks before an order can run; a denial surfaces the adverse-action step for the operator.
-
Screening orders through a pluggable provider
With configured integrationCredit, criminal, eviction and full checks are ordered per applicant, with payer choice (applicant, owner or management company). Live reports require a consumer-reporting-agency integration you contract and configure; the build ships a deterministic mock.
-
Structured decision record
BuiltIncome qualification, duplicate flags and the decision reason are recorded with the application and audited.
By role
What each party gets
Leasing agents
Cannot order without consent; cannot lose a report; cannot forget the notice.
Property managers
A defensible record of who decided what, when, and on what basis.
Owners
Pay for screening where they choose to, with the expense booked automatically.
Configuration and pilot notes
Before you rely on it
Things that are set up per operator during a pilot, or that depend on a provider you contract.
- Live screening requires a contract with a consumer reporting agency (for example TransUnion SmartMove, Experian or another CRA) and its credentials in your configuration. Permissible purpose, applicant consent and adverse-action notices are the operator’s responsibility under the FCRA.
- The current build ships a deterministic mock provider for demos and pilots without a CRA contract.
- Decision criteria and notice templates are configured per operator and should be reviewed by counsel.
Questions about this area
Does ResidentAxis provide credit or background reports itself?
No. ResidentAxis is not a consumer reporting agency. It runs the workflow around reports supplied by a CRA you contract and configure.
Does the platform recommend approving or denying an applicant?
No. It records income qualification and flags you configure, and stores the decision a person makes. There is no automated scoring of applicants.
Is applicant data such as SSN stored?
No. Only the provider’s order reference is stored. See the security page for the data inventory.
Related
Connected areas
Leasing & applicants
Applications, households, offers, approval to lease, renewals.
Learn moreLeases & e-signatures
Template-built leases, rules-based review, locked terms, native signing.
Learn moreAPI, integrations & security
Scoped API keys, webhooks, row-level isolation, audit, MFA.
Learn moreSee screening & decisions on your portfolio.
A pilot starts with a discovery call and your CSV exports. We reply within two business days.