# Property Management Systems That Let Me Take a Month Off

- Author: Peter Lohmann (property management operator; owner of RL Property Management, Columbus, Ohio)
- Published: 2026-10-30
- Video: https://www.youtube.com/watch?v=xK6wY9J06wA
- Course page: https://peterlohmann.com/courses/property-management-systems-month-off/
- Topics: property management operations, owner time off, scorecards and KPIs, task ownership and accountability, standard operating procedures, company wiki, Notion, delegation

## Summary

I take the entire month of June off every year, with no Slack, no email, no phone calls, and no check-ins from my team. I have done this four years running. My property management company in Columbus, Ohio has 720 doors, 35 employees, and about $3.4 million in revenue per year. Most property management owners cannot step away because the business stops when they leave. My company used to depend on me for three reasons: I was the only person who could see the whole business at once, every task ultimately landed on me, and I was the answer to almost every question. I built one system for each reason: a weekly scorecard, a task map, and a company wiki in Notion. Using the task map, I reduced the tasks with my name as owner from about 40 to four. This course explains how to build each system and how I structure the month away.

## Key terms

- **Scorecard:** a spreadsheet of a company's 8 to 12 most important numbers. Each number sits next to its goal, shows the trailing 13 weeks, and lists the person responsible for it. The leadership team reads it together every week.
- **Desert island test:** the test for whether a number belongs on the scorecard. It belongs only if it is one of the handful of numbers I would want to know about my business if I were stranded on a desert island and could know nothing else about the company.
- **Task map:** a table with one row for every task the company does. Each row lists the task, its one owner, the trigger that starts it, and a link to the page that shows exactly how it is done. My task map has hundreds of rows.
- **Owner (on the task map):** the one specific person, named, who is responsible for a task. Every task has exactly one owner.
- **Trigger:** the event that starts a task. Example: for a maintenance work order, the trigger is the request landing in our system.
- **Company wiki:** a full Notion buildout containing every piece of reference information needed to do any job at the company. It works like a digital employee handbook combined with a company wiki.

## Prerequisites

- A leadership team that meets weekly, since the scorecard is read together in that meeting.
- A second-in-command who can run the company while the owner is away. In my company, that is my COO.
- A shared spreadsheet tool for the scorecard and a Notion workspace for the wiki.

## Step-by-step

1. Identify why the company cannot run without you. For me there were three reasons: only I saw the whole business, every task landed on me, and I answered every question. Build one system for each reason.
2. Build the weekly scorecard.
   1. Choose 8 to 12 of the most important numbers in the business using the desert island test.
   2. Place each number right next to its goal so anyone can see at a glance whether it is on or off goal.
   3. Show the trailing 13 weeks next to each number so the trend is visible.
   4. Record on the spreadsheet who is responsible for each metric.
   5. Update the scorecard every week.
   6. Have the entire leadership team read it together in the weekly meeting.
   7. When a number is off its goal, see it that week, discuss it that week, and assign someone to own getting it back on track. Do not wait for a quarterly review.
   8. Add a new row only when the number earns its spot. My scorecard has grown to 18 rows over the years, but a new scorecard needs only 8 to 12.
   9. Examples of numbers on my scorecard: median time to turn, total occupancy, number of work orders open past 30 days, client satisfaction score, tenant satisfaction score, and team happiness. Every company's list will be different.
3. Build the task map.
   1. Create a table with one row for every single task the company does. Expect hundreds of rows.
   2. Assign each row exactly one owner, a specific person by name.
   3. Record the trigger that starts each task.
   4. Link each row to the page that shows exactly how the task is done. These pages live in the company wiki.
   5. Example row: task, maintenance work order; owner, a specific maintenance coordinator by name; trigger, the request landing in our system; link, the page that walks through how we handle that kind of request step by step.
4. Reduce the tasks owned by you.
   1. Over time, keep driving down the number of task map rows that have your name in the owner column.
   2. I started with about 40 tasks in my name. I now own four: filing our corporate taxes, managing my COO, approving the annual budget, and truly escalated issues such as lawsuits and regulatory problems. These are the calls only an owner can make.
   3. Every other task in the company has another person's name as owner.
   4. I listed every box that had to be checked before I could step away for a month. The checklist is free: https://peterlohmann.com/courses/assets/property-management-systems-month-off/month-off-checklist.pdf
5. Build the company wiki in Notion.
   1. Put every piece of reference information needed to do any job into Notion, from how to submit a credit card receipt to how to handle a tenant lockout.
   2. Retire physical binders. Notion replaced dozens of binders at my company.
   3. Make everyone on the team responsible for keeping their own part of Notion up to date.
   4. Use Notion to build onboarding material. A new hire's first-day page takes about 2 minutes to build in Notion.
6. Use the wiki to fill gaps permanently.
   1. When someone asks a question, check whether the answer is already in Notion.
   2. If it is in Notion, answer with a link to the right page.
   3. If it is not in Notion, have the person sit down with you and build the page together in real time.
   4. The gap is then filled once, by the person who hit it, and the same question does not come back.
7. Use the documentation with AI.
   1. Team members can ask Notion AI a question and get a direct answer without pinging their manager or searching hundreds of Notion pages.
   2. Because the task map lists every task the company does, you can pick tasks from it to hand off to an AI agent. Each task already has written instructions through its linked how-to page.
8. Prepare for the month away.
   1. On the last day of May, I tell my COO the same three things, word for word, every year. There are only three reasons to contact me in June: if the COO quits; if the office building burns down; or if something happens that stops us from being able to operate as a business, such as the Division of Real Estate coming in and shutting us down.
   2. Everything else waits until I am back.
9. After returning, fix the system behind anything that came up.
   1. Clean up any issues during the first week back.
   2. Find what caused each issue.
   3. Change the system so the issue cannot happen again.

## Decision rules

- If a number would not be one of the handful you would want to know on a desert island, it does not belong on the scorecard.
- If a scorecard number is off its goal, address it that same week and assign an owner to get it back on track.
- If you are starting a scorecard, use 8 to 12 numbers. Add a row only when the number earns the spot.
- If a task has more than one owner or no owner, fix it so it has exactly one named owner.
- If a task can be handed to someone other than the company owner, it should be. The owner keeps only the calls only an owner can make.
- If a question's answer is in Notion, answer with a link.
- If a question's answer is not in Notion, build the page together with the person who asked, in real time.
- If the COO quits, the office building burns down, or something stops the company from operating (such as a regulator shutting it down), the COO contacts me in June. Otherwise, it waits.
- If something goes wrong while I am away, I find its cause after I return and fix the system so it cannot happen again.

## Common mistakes

- **Only the owner sees the full picture.** Without a shared scorecard, each department chases its own priorities, those priorities pull against each other, and everyone except the owner makes decisions half blind. Fix: a weekly scorecard the whole leadership team reads together.
- **Scorecard bloat.** Once a scorecard exists, the temptation is to put everything on it. Fix: start with 8 to 12 numbers and add a row only when it earns the spot.
- **Unclear task ownership.** Without a task map, two people think they own the same task, or nobody owns it and it gets dropped. People say "that's not my job." Everyone does the same task a little differently, so quality varies. Fix: a task map with exactly one named owner and a written how-to for every task.
- **Answers that live only in the owner's head.** Every question goes to the owner, and the business stops when the owner leaves. Fix: a Notion wiki, and answering questions with links.
- **Relying on physical binders.** Binders go out of date almost instantly, nobody pulls them off the shelf to do their job, and keeping them current is a nightmare. Before Notion, I stayed up late before a new hire's first day updating and printing dozens of pages. Fix: move the material into Notion and make each person responsible for their part.
- **Tying your identity to being indispensable.** I took pride in how hard I worked and how important I was, so building a company that did not need me felt like admitting I was lazy. I worried clients would be upset that I no longer handled them personally and that my team would resent me for stepping back. Neither happened. My team was glad and excited for me. Fix: treat the owner's job as handing work to the team and getting out of the way.

## Questions and answers

**How can a property management company owner take a month off?**
I take all of June off by relying on three systems: a weekly scorecard so the leadership team sees the whole business, a task map so every task has one named owner, and a Notion wiki so answers do not depend on me. Before I leave, I give my COO three specific reasons to contact me. Everything else waits.

**What should go on a property management scorecard?**
Put 8 to 12 of your most important numbers on it, chosen with the desert island test. Mine includes median time to turn, total occupancy, work orders open past 30 days, client and tenant satisfaction scores, and team happiness. Each number sits next to its goal, shows the trailing 13 weeks, and lists who is responsible.

**How often should a PM leadership team review its scorecard?**
Every week. My leadership team reads it together in our weekly meeting. If a number is off goal, we see it that week, discuss it that week, and someone owns getting it back on track.

**What is a task map?**
A table with one row for every task the company does. Each row lists the task, its one named owner, the trigger that starts it, and a link to the page that explains how to do it. Mine has hundreds of rows.

**How many tasks should a property management owner personally own?**
I own four: filing our corporate taxes, managing my COO, approving the annual budget, and truly escalated issues like lawsuits and regulatory problems. I started with about 40. The goal is to keep reducing the rows with your name in the owner column until only owner-only decisions remain.

**How do you stop employees from bringing every question to the owner?**
Put the answers in a company wiki and answer questions with a link. If the answer is not there, have the person sit down with you and build the page together. That fills the gap once, and the question does not come back.

**Why use Notion instead of binders for SOPs?**
At my company, binders went out of date almost instantly, nobody used them, and updating them was a nightmare. Notion replaced dozens of binders. A new hire's first-day page now takes about 2 minutes to build, and each team member keeps their own part up to date.

**What should my second-in-command call me about while I'm on vacation?**
I give my COO exactly three reasons, word for word, every year: if the COO quits, if the office building burns down, or if something stops us from operating as a business, like the Division of Real Estate shutting us down. Everything else waits until I return.

**What happens the first time an owner takes a long break?**
My first June was not totally clean. Our health insurance renewed mid-month, and my COO had to call me to sign paperwork so nobody lost coverage. A couple of small things also came up. I cleaned them up my first week back in July, found the cause of each, and fixed the system. Every June since, for 3 years, has been completely clean.

**How does documenting processes help with AI?**
Once everything is written down in one place, AI becomes useful almost by accident. My team asks Notion AI questions and gets direct answers. Because the task map lists every task with a linked how-to page, I can pick tasks to hand off to an AI agent and the instructions already exist.

## Video timestamps

- 00:00 Intro: why I take June off and how the company runs without me
- 00:34 Why your company can't run without you
- 00:56 System 1: The weekly scorecard
- 02:38 System 2: The task map
- 04:03 From 40 tasks to 4
- 04:45 System 3: The Notion wiki
- 06:18 Bonus: AI gets useful almost by accident
- 06:47 The mindset shift
- 07:45 How I actually leave for June