Burnt Screening
Talk to team Start screening
Application fees

Tenant screening fees need market-aware pricing.

Applicant-paid screening is familiar, but fee caps and local rules mean pricing should be presented with caveats and configurable payer models.

  • 01Choose payer model
  • 02Show package scope
  • 03Respect local limits
  • 04Scale billing terms
Start screeningBook a demo
Partner-check context
Burnt dashboard showing tenant screening package and payer model context
Keep partner checks inside the workflow. Credit, background, eviction, consent, criteria, and support context stay attached to the same applicant package.
Short answer

How much can landlords charge for tenant screening?

Tenant screening fees depend on who pays, what modules are included, and which state or local rules apply. Burnt can support applicant-paid, operator-paid, and portfolio pricing patterns while keeping package scope and legal caveats visible.

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

Package module list

Verified

Applicant-paid or operator-paid model

Verified

Market-specific fee caveat

Review

Portfolio billing context

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

Choose modules

Decide which application and screening checks the package includes.

02

Choose payer

Select applicant-paid, operator-paid, or portfolio billing based on market and business model.

03

Apply local limits

Review state and local fee restrictions before charging applicants.

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