In this article
A prospect can move forward in the software while the team still disagrees about who should act next. A leasing map connects each change of stage to an accountable person and a visible acceptance condition.
Draw the route around decisions
AppFolio’s public leasing overview describes tools across the prospect-to-resident journey. That is product context, not proof that your account includes every listed capability. Begin with the stages your team actually uses: inquiry, showing, application, authorized decision, lease preparation and move-in coordination. Avoid borrowing a marketing diagram as your operating procedure.
For each stage, write the entry condition and the evidence that permits the next step. “Application received” is an event. “Application ready for review” is a judgment that someone must make. Keeping those separate prevents an incomplete file from moving merely because a notification arrived.
Give each crossing a receiver
A useful handoff has a sender, a receiver and a next action. The receiver is not everyone copied on a message. It is the role expected to acknowledge the transfer and identify any missing prerequisite. A backup role matters when the normal receiver is unavailable, but should not create two competing decision owners.
- Sender: records what has actually been completed.
- Receiver: accepts the next action or returns a specific gap.
- Decision owner: has authority under the company’s approved process.
- Observer: needs an update but is not being asked to decide.
Keep the decision boundary intact
A process map must not invent screening standards or determine who qualifies for housing. Use the organization’s approved, consistently applied criteria and authorized review process. Do not put applicant identities, screening results or eligibility judgments in a generic planning tool. This publication does not offer legal screening guidance.
Likewise, a prepared lease, an offered lease and a fully executed lease are not interchangeable. Record which condition is confirmed and who verifies the authoritative document. A planned move-in date is not evidence that every required step has been completed.
Fictional crossing: application to lease preparation
A leasing coordinator sees a completed application checklist and sends the file to a manager. The manager returns one missing review item. The correct route stays at review with an assigned follow-up; it does not advance to lease preparation just because the coordinator sent the message.
Test one exception before rollout
Walk through a late document, an unavailable reviewer and a changed move-in date. Ask which role receives the exception and how the prospect hears about the next step. If the answer is “someone will notice,” the map still has a gap. Use generic labels during the exercise, not a real applicant file.
Close the map with a confirmation: the receiving role knows the next action, the source record is available to authorized staff, and the prospective resident is not receiving conflicting instructions. Continue with readiness checkpoints or test a generic route in the handoff planner.
Source notes and boundaries
Public sources checked October 21, 2026. The process methods and fictional examples are original editorial guidance, not AppFolio instructions or a test of a private account. Features, labels and permissions can vary.
- AppFolio marketing and leasing — Public overview of leasing stages and tools; not a promise that every feature is enabled for every account.