# How to Systematize Your Property Management Processes

- Author: Peter Lohmann (property management operator; owner of RL Property Management, Columbus, Ohio)
- Published: 2026-10-30
- Video: https://www.youtube.com/watch?v=0SvTu3sTPxM
- Course page: https://peterlohmann.com/courses/property-management-processes-systems/
- Topics: property management operations, process documentation, checklists, workflow software, process ownership, delegation, process automation, owner time freedom
- Sponsor disclosure: the video is sponsored by LeadSimple, the process automation software my company uses.

## Summary

Most property management owners own a job instead of a business: every decision, exception, and problem lands on them. I run a property management company with more than 700 doors and take the entire month of June off every year, and I have done that for 4 years straight. I did it by taking an engineering approach: I built a machine to run the business instead of running it myself. The method is to document the core processes as checklists, move them into workflow software that runs a separate copy for each property, tenant, or owner, give every process exactly one owner, remove myself from the steps, and set up triggers so processes start automatically. This course explains each step.

## Key terms

- **Core four:** the four core processes every property management company runs every month: new property/owner onboarding, move-in (new tenant), lease renewal, and move-out.
- **Checklist:** a plain, step-by-step list of the steps in a process, written in short form without detailed instructions at first.
- **Process template:** the master version of a checklist in workflow software. Changing the template changes every future instance of that process.
- **Process instance (copy):** one run of a process for one specific property, tenant, lease, or owner. Eight leases signed means eight instances of the move-in process.
- **Process owner:** the one person accountable for a process getting done right and on time, even when other people do individual steps.
- **Trigger:** an event that starts a process automatically, such as another process, a change in the property management software, a date, or a form fill.
- **The done test:** a process is done when somebody with no training can sit down at a computer and run the whole process without me.

## Prerequisites

- At least one person (the owner or a team member) who currently performs each process and can describe its steps.
- A place to keep checklists digitally, starting with something as simple as a Google Doc, and later workflow software, either the tool built into the property management software or a dedicated tool.

## Step-by-step

1. Start with the core four processes: new property/owner onboarding, move-in, lease renewal, and move-out. Most property management companies have five or six absolute core processes in total. Do not try to tackle all of them at once.
2. Pick one of the core four.
3. Write the checklist.
   1. Sit down with the person who actually performs the process. That can be the owner or a team member.
   2. Use a piece of paper. Fancy software is not needed, and it is better not to use it at the start.
   3. Ask what the first step is (for example, "When someone signs a lease, what's the first thing you need to do in the move-in process?"), write it down, then ask for the next step. Example step: accept the security deposit and record it in the system. Continue to the end of the process.
   4. Write steps in checklist format, not in detail.
   5. Review the checklist with the same person and reorder or reword steps until you both agree.
4. Make the checklist digital and simple.
   1. Put it in a Google Doc with checklists or basic workflow software.
   2. Do not use fancy workflow software, do not automate, and do not write detailed step-by-step instructions yet.
   3. Get the team using it.
5. Run a new copy of the checklist for every instance.
   1. Every time a new lease is signed or a tenant moves out, start a new copy of the checklist for that specific tenant, lease, property, or owner, and label it.
   2. After a few weeks there should be one copy per instance. If eight leases were signed in the last month, there should be eight copies of the move-in checklist, some fully completed, some partially completed, and some not started.
6. Move the checklist into real workflow software. The software must be able to:
   1. Hold templates for different types of processes.
   2. Create a new instance of a process for every new tenant, owner, or other subject of the process.
   3. Let multiple people view a checklist and check off different parts of it.
   4. Show an overview of the status of every instance. Example: in the move-in overview, 123 Main Street is halfway done, 456 Main Street is not started, and 789 Main Street is fully completed.
   5. For a full real-time example, I build a lease renewal process in LeadSimple from scratch in this video: https://www.youtube.com/watch?v=rphTnIq3SXQ
7. Use the five benefits of workflow software.
   1. See the status of every process instance: done, not started, or partially completed.
   2. Keep a written record of completion for every step, showing who checked off which step in which process on what date and time. This ends finger-pointing in disputes.
   3. Update a process once in its template (fix a typo, reorder steps, add a step), and every future instance uses the latest version.
   4. Add instructions to each step so everyone does it the same way, and reassign individual steps to other people. Example: in the move-out process, reassign "upload the move-out inspection to Dropbox" to a team member named Jeff; every future move-out automatically assigns that step to Jeff, while the owner can keep important steps assigned to themselves.
   5. Execute processes consistently and correctly, which frees up the owner's attention and time.
8. Roll out slowly. Start with the core four, get comfortable with the software, onboard the team, then expand.
9. Build each checklist for the common case.
   1. Do not try to cover every scenario, edge case, or exception, and do not add conditional logic for them.
   2. Exceptions are where a team member raises a hand and asks someone, instead of blindly following the checklist.
10. Apply the done test. If someone with no training can run the whole process without you, the process is done. If someone has to ask a question or cannot find a document or link, add more instructions to that step.
11. Put instructions inside the workflow software, on the step where the work happens, not in a separate document such as a separate Notion page.
12. Assign exactly one owner to each process.
    1. The owner can start out being the business owner, but as the business grows, delegate process ownership to other people.
    2. Different people can perform different steps.
    3. The process owner is accountable for the whole process getting done right and on time, and follows up with anyone whose steps are not done.
13. Get the team using the system.
    1. Ask everyone involved whether they are using the new process software, how they like it, what problems they have, and where the errors are.
    2. Give team members permission to edit the checklists in the software: fix typos, fix broken links, add missing descriptions, add steps, or reorder steps, then let the business owner know so they can review the change.
14. Build out the remaining core processes beyond the core four, such as collections or evictions, de-management, and a new employee checklist.
15. Remove yourself from the checklists.
    1. In the software, replace your name and profile photo on each step with a team member.
    2. Do it step by step, not all at once.
    3. Tell the team what is happening, especially whoever replaces you on each task, and train them if needed.
    4. Reassign even steps owners believe only they can do, such as security deposits or signing property management agreements (PMAs).
16. Automate process triggers.
    1. Use more advanced workflow software to start processes automatically instead of relying on someone's memory.
    2. Triggers can be other processes, changes in the property management software, dates, or form fills.
    3. Example: when a tenant submits a move-out notice through a form on the company website (such as a JotForm), the move-out process starts automatically for that tenant and assigns the first step, which is likely contacting the tenant to confirm all move-out details and the move-out date.
    4. The goal is for every process in the system to trigger automatically.

## Decision rules

- If you are just starting, systematize one of the core four processes before anything else.
- If a process is still on paper and being refined, keep it simple: no fancy software, no automation, no detailed instructions yet.
- If you signed N leases in a period, you should have N copies of the move-in checklist.
- If a situation is an exception or edge case, leave it out of the checklist and let a team member ask about it.
- If someone with no training can run the whole process without you, the process is done.
- If someone has to ask how to do a step or cannot find a document or link, add more instructions to that step.
- If a process has more than one owner, change it to exactly one owner.
- If a team member finds a typo, broken link, missing description, or a step that needs adding or reordering, they make the change and tell the business owner.
- If a process can be started by another process, a software change, a date, or a form fill, set it up to start automatically.
- If there is a big problem after you remove yourself from a process, you can step back in.

## Common mistakes

- **Owning a job instead of a business.** Everything runs through the owner, who spends the day firefighting. Fix: document and systematize the core processes so the team runs them.
- **Leaving core processes undocumented or inconsistent.** Undocumented, poorly defined, or inconsistently executed processes cause errors, waste team time, and keep the owner chained to the business. Fix: write a checklist for each core process with the person who performs it.
- **Starting with fancy software or detailed instructions.** Fix: start on paper, then a simple digital checklist; add workflow software and instructions later.
- **Trying to do everything at once.** Fix: start with the core four, get comfortable with the software, onboard the team, then expand.
- **Building for every exception.** Conditional logic for every edge case makes the checklist clunky, error-prone, and outdated because nobody wants to maintain it. Fix: build for the common case.
- **Keeping instructions in a separate place.** Fix: put instructions on the step in the workflow software where the work happens.
- **Two people responsible for one process.** The fastest way to starve a dog is to make two people responsible for feeding it. Fix: one owner per process.
- **Believing only the owner can do certain steps.** Owners hold on to steps like security deposits or signing PMAs. Fix: reassign them to competent, trained team members with the owner's support.
- **Relying on memory to start processes.** Fix: set up automatic triggers.
- **Focusing on door count instead of time freedom.** Fix: prioritize the ability to step away; growth is easier when the owner is not chained to the business.

## Questions and answers

**What are the core processes every property management company should systematize first?**
I start with the core four: new property/owner onboarding, move-in, lease renewal, and move-out. Every property management company runs these every month. Pick one and systematize it before moving to the next.

**How do I document a property management process?**
I sit down with the person who actually does the process, use a piece of paper, and ask for each step in order until the process is complete. I keep it in checklist format, review it with the same person, and then move it into a simple digital checklist.

**Should I use workflow software right away?**
No. I start on paper, then a Google Doc or basic workflow software, without automation or detailed instructions. Once the team is running a copy of the checklist for every lease or tenant, I move it into real workflow software.

**What should property management workflow software be able to do?**
It needs process templates, a new instance of a process for every tenant or owner, multiple people checking off steps, and an overview that shows the status of each instance. It also gives a time-stamped record of who completed each step.

**How detailed should a property management checklist be?**
Build it for the common case. Don't encode every exception or edge case with conditional logic, because the checklist becomes clunky and outdated. Add instructions to steps until someone with no training can run the whole process without me.

**Where should process instructions live?**
On the step in the workflow software where the work happens. I don't keep a separate Notion page explaining the move-in process; the instructions are built into the move-in process itself.

**How many people should own a process?**
Exactly one. Different people can do different steps, but one owner is accountable for the whole process getting done right and on time and follows up with everyone else.

**How do I get my team to adopt new processes?**
I ask everyone involved whether they're using the software, what problems they see, and where the errors are. Then I give them permission to edit the checklists and tell me what they changed. Teams latch on when they feel ownership.

**How do I remove myself from day-to-day property management tasks?**
Once processes are documented, I replace my name on each step with a team member, one step at a time, and train them as needed. That includes steps owners think only they can do, like security deposits and signing PMAs.

**How can property management processes start automatically?**
Advanced workflow software can start processes from other processes, changes in the property management software, dates, or form fills. For example, a tenant's move-out notice form can start the move-out process and assign the first step: contacting the tenant to confirm details and the move-out date.

**What workflow software do you use?**
My company uses LeadSimple, which sponsored this video. It integrates with AppFolio, Buildium, Rentvine, Propertyware, and other property management software. The steps in this course work in whatever workflow software you choose.

## Video timestamps

- 00:00 Intro: how I take June off every year
- 00:29 Why everything still runs through you
- 02:28 Start with the core four
- 03:46 Write the checklist with the person who does it
- 06:55 Move the checklist into workflow software
- 10:46 Build for the common case
- 12:57 Give every process one owner
- 14:34 Get your team using it
- 15:54 Take your name off the checklists
- 16:55 Let triggers start your processes
- 18:00 Time freedom over door count