Skip to main content
Public Manuals
Step-by-step guidance for RentMatrix users and day-to-day workflows.
Audience: Operations teams

Application Review

What is this?

The Application Review module is where you evaluate tenant applications submitted from your listings. It centralizes applicant details, screening reports, and documents so you can approve or reject with clear documentation.

When should I use it?

Use this module when:

  • A tenant application is submitted.
  • Screening and background checks are available.
  • You are ready to approve or deny.
  • You need to document a rejection reason.

Prerequisites

Before review, ensure you have:

  • Permission to review applications.
  • Completed submitted application.
  • Completed screening reports.
  • Clear and lawful review criteria.

Flow diagram

Step-by-step instructions

  1. From sidebar, click Applications.
  2. Select applicant name or application ID.
  3. Review personal info, income and employment, rental history, and screening data.
  4. Approve if criteria is met, or reject if criteria is not met.
  5. If rejecting, select a specific lawful reason.
  6. Confirm decision.

Example scenario

Situation: Applicant credit score is 620 while minimum required is 650.

Solution in Rent Matrix:

  1. Open the application.
  2. Confirm score from credit tab.
  3. Click Reject Application.
  4. Select reason Credit score below minimum requirement.
  5. Confirm rejection.

Common mistakes / FAQs

  • Mistake: Delayed reviews causing loss of good applicants.
    • Solution: Set SLA to review within 24 to 48 hours.
  • Mistake: Vague or subjective rejection reasons.
    • Solution: Use objective system reasons tied to policy.
  • FAQ: Can I approve exceptions?
    • Answer: Yes, but document the exception clearly.
  • FAQ: What happens after approve?
    • Answer: Workflow usually moves to lease signing steps.

Pro tips

  • Define tenant criteria before reviewing applications.
  • Use internal notes for close calls.
  • Batch pending reviews at scheduled times.
  • Verify adverse action communication behavior in your setup.