Sample screening package

Show reviewers what is ready, pending, and worth a closer look.

A useful screening report is not a pile of PDFs. Burnt organizes applicant status, source-backed facts, partner report context, criteria notes, and exceptions into one reviewable package.

  • 01See what is ready
  • 02Trust source-backed facts
  • 03Keep reports in context
  • 04Spot exceptions
Screenings dashboard
Burnt tenant screening report dashboard with applicant package status and review context
Track every applicant in one queue. See who has not started, who is in progress, and who is ready for review without opening separate tools.
Short answer

What should a tenant screening report show?

A sample tenant screening report should show what was requested, what the applicant completed, which facts were verified at the source, which partner modules returned status, and what the property team should review next.

Screening workflow

The whole flow fits on one line.

Create the package, send the link, guide the renter, review the result. That simple path keeps screening understandable for applicants and manageable for teams.

01

Create the package

Choose application fields, verification modules, payer model, and property criteria.

02

Send the link

Invite the applicant by email, SMS, listing, dashboard action, or connected workflow.

03

Applicant completes

The renter consents, verifies identity, connects sources, and completes requested partner steps.

04

Review one package

Your team sees status, source-backed facts, partner context, exceptions, and notes together.

Product jobs

Clear work for the team. Clear steps for the renter.

The point is not just to run checks. The product has to help the buyer start screening, help the applicant finish, and help the reviewer understand what is ready.

Property team does

Confirm which modules were requested, completed, pending, or unavailable.

Applicant does

Compare source-backed income, employment, identity, and applicant details against the application.

Burnt returns

Use criteria notes, fallback evidence, and partner-report context to guide the next review step.

In the product

The package stays connected from invite to review.

Reviewers get status and exceptions in the dashboard. Renters get focused mobile steps. The handoff stays visible as the package moves forward.

Burnt operator dashboard showing screening list and applicant statuses
Review queue Property teams can scan applicant status before opening the full package.
Burnt invite renter flow for sending a tenant screening link
Screening link The applicant starts from one property-specific link instead of email threads.
Burnt applicant verification checklist on mobile
Applicant flow Mobile verification steps stay visible, ordered, and easier to complete.
Review signals

What your team can review.

Burnt keeps the screening output compact, scannable, and tied to the workflow your team actually uses.

Verified

Applicant invite and completion status

Verified

Income-to-rent and employment context

Verified

Identity, credit, background, and eviction module status

Review

Criteria notes and exception reasons

How it works

From application link to reviewable result.

01

Read package status

Confirm which modules were requested, completed, pending, or unavailable.

02

Review verified facts

Compare source-backed income, employment, identity, and applicant details against the application.

03

Handle exceptions

Use criteria notes, fallback evidence, and partner-report context to guide the next review step.

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.

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