Context switching costs landlords time and accuracy when a routine question requires reopening several tools, texts, and files before anyone can take the next step.
In this article
01
The hidden work is reconstruction
02
Map the searches that recur
03
Example: the duplicate plumber call
04
Centralize status, not judgment
The hidden work is reconstruction
A simple tenant reply can become a long search through the lease, earlier messages, bank activity, and vendor updates. The visible task is the message; the hidden task is rebuilding its context.
Map the searches that recur
For payment questions, repairs, renewals, and owner updates, write where the event arrives, who acts, where status lives, and which record resolves it. Multiple informal answers signal a weak handoff.
Example: the duplicate plumber call
A tenant texts two owners about a drain. One calls a plumber while the other searches an old repair message, and the vendor charges a trip fee for work already scheduled. A shared work record would show status and next update.
Centralize status, not judgment
A queue can show routine next actions while keeping the lease, ledger, or work evidence available for consequential human decisions.
Key takeaways
Measure the searching before the visible task.
Give common requests one intake route and shared status.
Centralize coordination while retaining evidence for judgment.