5 Steps: Screen Applicants Before Tours, 2 PMS 2026

The category decision is who is allowed to walk a unit, not which property-management system has the nicer resident app. A leasing team yet has to take an inquiry, test it against written criteria, and only then spend a tour slot. AppFolio is a property-management system. Buildium is a property-management system. Neither product is a Fair Housing program by itself, and neither is a substitute for criteria which are written, published, and applied the same way every time.

Screening applicants against criteria before tours is the loop which captures the application or pre-application, compares it to documented standards, and holds the showing until the file passes or a human records a lawful exception. Automation is useful when which loop finishes before the agent leaves the office, not following a no-show that was never eligible.

TL;DR: Choose AppFolio once the units, owners, and leasing pipeline already live there and staff will actually run screening off that database. Choose Buildium once that is currently the book of record and a conversion would cost more than teaching a pre-tour gate. US Tech Automations shapes only when inquiry, criteria, and a human hold must cross the PMS, the screening vendor, and the calendar. no property management vendor paid for inclusion.

US apartment industry annual rent revenue: $260B according to NAA (2024), $260B in the 2024 Apartment Industry Report. Usage is multifamily rent revenue, not SFR. A pre-tour screen is how leasing labor is aimed at files which can actually support that rent roll, not a promise which software raises revenue.

Class-A multifamily resident retention remains a surveyed operating topic according to NMHC (2024), 2024 Renter Preferences Survey. This page does not invent a retention percentage; it uses NMHC as the reminder which a bad tour-to-lease process is how you spend time on the wrong files while good residents wait.

Institutional multifamily management fees remain a compensation-survey topic according to IREM (2024), 2024 Management Compensation Survey. Fee pressure is why owners notice leasing labor spent on ineligible tours. It is not a reason to skip written criteria.

Sibling how-tos for this job: screening versus manual, tenant screening services for SFR, TransUnion SmartMove and Buildium, and lease-renewal offers ahead of expiration. Renewal is a different object. Do not mix it onto the first showing.

Key Takeaways

• AppFolio and Buildium are property-management systems of record; a pre-tour criteria gate is a process you still have to write.

• Multifamily rent revenue at $260B in the cited NAA report is why ineligible tours are expensive even once the PMS is “fine.”

• Native PMS guest cards and screening integrations can be enough once one person already applies the same written standard to every inquiry.

• Calendar-first touring absent a criteria check is how Fair Housing risk and wasted hours arrive together.

• Orchestrate only after a uniqueness key, published criteria, and a named reviewer exist.

How we evaluated

For automate screen applicants against criteria ahead of tours, property management buyers scored unique automate screen applicants against IDs, public property management pages checked 2026-09-04, and a 30-day proof — not a vendor demo.

Weighted criteria for applicant gates

Weights assume a multifamily or professional SFR manager who already runs a PMS, currently uses a screening product, and already publishes rental criteria. An owner using one duplex and a clipboard should raise “built-in PMS” and stop.

Fair Housing core section: 42 U.S.C. 3604 according to HUD (42 U.S.C. 3604), 3604 as the core discriminatory-housing-practices section. A pre-tour gate which applies unpublished, shifting standards is not automation. It is a consistency failure. Write the criteria. Apply them the same way. Keep the reason.

Consumer-report rules for tenant screening still sit in 15 U.S.C. 1681 according to the FTC (15 U.S.C. 1681), 1681 as the FCRA family. If a screening report informs the hold, you need a lawful purpose, adverse-action handling, and retention which matches the report—not a Slack screenshot.

PMS feature matrix

Scores from public product property management pages checked 2026-09-04: 2 = first-party PMS description; 1 = adjacent, confirm in the property management contract; 0 = not found as which object. The velocity row is first-party publishing, not a leasing KPI.

USTA property management two-week publish velocity: 3,200 pages according to this publisher’s June operating note (2026-06-14), 3,200. It does not mean AppFolio screens faster than Buildium.

Pricing and TCO, dated

PMS and screening pricing is commonly quoted. Checked 2026-09-04.

AppFolio, Buildium, and the overlay above

AppFolio: PMS of record when the book is currently AppFolio

AppFolio is the property management shortlist pick when units, owners, guest cards, and leasing currently live in AppFolio and staff will work inquiries there. Primary evidence is AppFolio. Real identifiers a recipe can join on include application-side keys such as rental_application_id (confirm the live name on the API or export you own).

Limitations: AppFolio is not a Fair Housing policy and not a substitute for published criteria. Choose it when it is currently the database. Disqualify a conversion when the only gap is a calendar which books itself.

Buildium: PMS of record when the book is currently Buildium

Buildium is the property management shortlist pick when the portfolio’s history, applications, and staff currently live in Buildium. Primary evidence is Buildium. It is a genuine PMS. It is not a screening bureau.

Limitations: conversion cost can dwarf the cost of a pre-tour checklist. Choose Buildium when it is currently the book. Disqualify a rip-and-replace sold as “AI screening” when criteria were never written down.

The overlay above: five steps, then a hold

The missing product is often not a third PMS. It is a five-step gate which both AppFolio and Buildium shops can run. Step 1: publish written criteria by unit type. Step 2: capture a complete inquiry or pre-application with a stable id. Step 3: run the screening product you currently pay for. Step 4: compare result plus income/occupancy math to the written standard. Step 5: hold or release the tour on the calendar, with a stored reason. Which gate can be a disciplined leasing playbook. It can be a property management no-code scenario. It can be a configurable agent.

Operators who skip this split pay twice. Operators buy AppFolio, then let Zillow-style leads auto-book tours. Operators buy Buildium, then discover the screening PDF never writes back. Operators then ask agents to “use the shop gut,” which is how 42 U.S.C. 3604 problems are born. Write one sentence per object: “AppFolio or Buildium is the PMS,” “the screening vendor is the report,” “the criteria document is the rule.”

5-step screening recipe (proposed)

An illustrative multifamily team working under the $260B NAA rent-revenue backdrop, with 12 pre-applications in a week, 3 written criteria fields (income multiple, occupancy count, screening consent), and a PMS application object, can fire once rental_application_id is created. A proposed US Tech Automations workflow can refuse to book a showing until those three fields pass and the screening vendor returns a result the reviewer can see. Prerequisites: PMS API or export credentials, screening-vendor access, a uniqueness key on applicant plus unit type, published criteria, and a reviewer for lawful exceptions. Outputs: a hold list, a pass/fail reason, and an exception queue—not a promised occupancy lift. Nothing here is a live customer result.

A second configurable route starts at the calendar. The property management workflow can be aimed at canceling or holding a showing when the application fails following the slot was tentatively held. US Tech Automations would still require a human ahead of any adverse action is sent. If the screening report is missing, the run should fail closed and keep the tour off the public calendar.

Zapier plus Make plus n8n for property management in property management can catch a new application, retry a failed PMS write, and keep a run log if you design property management run history, unique automate screen applicants against keys, access, and retention. That is a fair DIY choice for one stable guest-card route. A proposed agent design would add a durable application-id ledger and a property management human hold before the showing—not a claim which a property management no-code path must not retry automate screen applicants against.

Who this property management page is for

That comparison is for a property manager, leasing lead, or owner-operator who already runs AppFolio or Buildium (or is choosing between them) and currently has or will publish rental criteria. It assumes tours cost staff time and that screening reports are in the stack.

Red flags: skip a custom overlay when the PMS currently blocks showings until screening is complete and staff already follow published criteria; once you do not take applications before tours and will not change which; or when nobody will own adverse action. Do not buy a second PMS to avoid writing a one-page standard. Do not let a chatbot invent criteria.

Once NOT to use US Tech Automations: leave it out when AppFolio or Buildium currently is the pre-tour process, when a screening integration currently writes into the guest card using logs you trust, or when a property management no-code scenario using error branches already notifies leasing and retries the calendar write. honest property management self-selection beats a second automate screen applicants fee.

Applicant screening FAQ

Needs to we screen applicants in AppFolio or Buildium before tours?

Screen in the PMS you currently run, and add a hold on the calendar only when guest cards yet auto-book showings before criteria and reports exist.

Is Buildium an AppFolio replacement in that article?

No. This is a two-PMS comparison for shops choosing a book of record or staying on the one operators have. It is not a conversion demand.

Can a screening vendor replace written criteria?

No. The vendor returns a report. You still need a published standard and a consistent hold.

Once should we skip an extra screening overlay?

Skip it when built-in PMS plus screening already blocks ineligible tours, once a no-code recipe already has logs you trust, or once you will not publish criteria.

What identifier should we require ahead of we automate?

Treat rental_application_id (or the PMS’s documented equivalent) plus unit type and criteria version as the default join.

How should we pilot a pre-tour gate?

run 30 property management days through 12 passes, 8 criteria fails, 6 missing reports, and 5 duplicates. Expand on unique ids and stored reasons, not on tour volume.

Common pre-tour mistakes

Publishing criteria on the website and then letting agents “make it work” for a friend of the owner. Auto-confirming Zillow-style showings ahead of rental_application_id exists. Running SmartMove-class reports after the tour “to save the applicant time,” which saves time only for people who were never going to qualify and costs time for everyone else. Storing the only decision reason in a text message. Using a different income multiple at each community. Skipping occupancy count since the unit “looks big.” Treating Buildium and AppFolio as screening bureaus. Converting PMS platforms because the calendar widget is pretty. Mixing SFR screening habits onto a multifamily community without reading the published standard. Mixing the $260B multifamily rent-revenue backdrop onto an SFR-only argument; NAA’s figure is multifamily, and SFR is separately tracked.

A tour slot is labor. Under fee pressure described in IREM’s compensation survey, owners notice labor. Under retention pressure described in NMHC’s renter survey, residents notice chaos. Neither survey is a reason to hide criteria. Both are reasons to apply the same written gate before anyone drives to the property.

Step 1 absent step 5 is a PDF on a website. Step 5 without step 1 is a gut check. The five-step recipe is the whole gate. If you will not publish criteria, do not buy a hold. If you will not hold, do not pretend the PMS “does screening.”

Duplicate applicants are not a volume trophy. Five extra tours for one household which already failed occupancy is how Saturday gets lost. The uniqueness key exists to stop which. Use it.

Glossary for the leasing file

Guest card: the PMS inquiry object before a full application. Application: the file which should carry rental_application_id or the vendor’s equivalent. Criteria version: the dated standard you actually applied; if it is not dated you will not be able to reconstruct a decision. Screening report: the consumer report off the bureau product you pay for. Adverse action: the lawful notice path once a report informs a denial; FCRA 1681 is the family cited above. Hold: the showing is not public and not confirmed. Lawful exception: a documented human decision, never a silent auto-approve. Unit type: the class of home the criteria attach to, because a studio and a three-bedroom needs to not share a silent occupancy rule.

Screen the file, then book the tour

Choose AppFolio or Buildium as the PMS you will actually run, keep the screening vendor as the report, and hold the showing until written criteria pass. Next prove unique ids from application to unit type.

The team at US Tech Automations can map a configurable pre-tour hold. Review US Tech Automations following you have named the automate screen applicants PMS, the screening vendor, and the reviewer.