Burnt Screening
Talk to team Start screening
Screening laws

Tenant screening laws vary. Your workflow should show that.

National screening rules, fair-housing expectations, and local fee or criminal-history restrictions can all affect how teams configure rental application workflows.

  • 01Show the boundary
  • 02Support consistent review
  • 03Adapt by market
  • 04Use reviewed criteria
Start screeningBook a demo
Partner-check context
Burnt compliance workflow for tenant screening policy and review context
Keep partner checks inside the workflow. Credit, background, eviction, consent, criteria, and support context stay attached to the same applicant package.
Short answer

What tenant screening laws should landlords know?

Tenant screening laws can include FCRA obligations for consumer reports, fair-housing rules, applicant consent, adverse-action requirements, and state or local limits on fees or screening criteria. Burnt helps organize the workflow, but operators should configure policies with counsel.

Trust record

What should stay visible in the record.

Trust content should support the product workflow by making consent, partner boundaries, and review context easy to inspect.

Verified

Configured policy by property or market

Verified

Package and fee model context

Verified

Consumer-report partner boundary

Review

Audit trail for review

Trust and compliance

Built around consent, criteria, and reviewable records.

Trust content should help buyers and applicants understand the workflow without taking attention away from the screening product itself.

Applicant consent

Screening begins with applicant authorization, clear package context, and a record of what the applicant completed.

FCRA partner modules

Credit, background, and eviction checks are presented as partner-powered modules with the right decision boundary made explicit.

Adverse-action context

Operators can keep report status, criteria, and applicant-support context together when consumer reports affect decisions.

Fair-housing consistency

Teams can organize packages and criteria by property or market so reviewers are not improvising applicant-by-applicant.

How it works

From application link to reviewable result.

01

Map markets

Identify where screening fees, criminal-history review, income criteria, or timing rules differ.

02

Configure consistently

Use packages and criteria that reflect the policy for each property.

03

Review periodically

Update workflows as laws, partner coverage, and portfolio requirements change.

Use cases

Designed for real rental workflows.

Whether you run one unit or a national portfolio, each workflow keeps the answer focused and the next step clear.

Next pages

Keep exploring the screening workflow.

Compliance

Build tenant screening workflows with applicant consent, criteria display, adverse-action context, audit trails, and FCRA-regulated partner modules.

Trust

How Burnt handles applicant consent, source verification, partner screening modules, data boundaries, support paths, and tenant screening decision context.

Applicant support

Applicant support for Burnt tenant screening: what to expect, how consent works, where report questions go, and how applicants get help.

Report disputes

How tenant screening report questions, adverse-action notices, and consumer-report disputes should be routed when Burnt partner modules are used.

Reporting partners

How Burnt presents partner-powered credit, background, and eviction modules while keeping consumer-reporting agency boundaries clear.

Adverse action

A practical guide to adverse-action context for tenant screening workflows that use credit, background, eviction, or other consumer-report modules.
FAQ

Questions this page answers.

Tenant Screening by Burnt

Send the link. Guide the renter. Review one package.

Launch with screening links or talk through a portfolio workflow with the Burnt team.

Start screeningTalk to team