Property management has many workflows, and they all pass through the same few people. Automating them works best one workflow at a time, with a person approving anything that reaches a resident, a vendor or an owner.
This guide walks through the common workflows, how to map one, and what to check before you trust it.
The workflows in a typical office
Most of the routine work falls into a short list:
- Maintenance intake. A request comes in, gets sorted and becomes a work order.
- Vendor coordination. A vendor is told about the job and confirms a time.
- Resident updates. The resident hears that the request was received, scheduled and finished.
- Move-in and move-out. A checklist of documents, keys, inspections and notices.
- Owner questions. An owner asks what happened at a property and someone pulls the history together.
- Renewal reminders. A lease is close to ending and the resident needs a note.
None of these needs deep judgment for the ordinary case. All of them need care for the unusual case.
Map one workflow before you automate it
Write the workflow down as it really happens, not as the handbook says it should. For each one, answer five questions:
- What starts it? An email, a form submission or a request from a colleague.
- What information is needed? Unit, name, problem, access details, photos.
- What are the steps? In order, including the small ones people do without thinking.
- Where does a person decide? Spending money, choosing a vendor, anything urgent.
- What does finished look like? A work order exists, the resident has a reply, the sheet is updated.
If you cannot answer these, the workflow is not ready to hand over. Fix the process first.
Decide where approvals go
Three kinds of step deserve an approval:
- A message that leaves the office. A wrong reply to a resident is hard to take back.
- A record that others rely on. A work order with the wrong unit sends a vendor to the wrong door.
- A cost. Anything that commits the owner's money.
Low-risk steps, such as adding a line to an internal log, are different. Approving those one by one adds delay without adding safety.
Plan for the unusual case
Automation often fails on the request that does not fit. The resident gives no unit number. Two emails about the same leak arrive an hour apart. The form says "urgent" for a squeaky door.
Decide in advance what should happen. The safe rule is simple: when information is missing or conflicts, stop and ask a person. A workflow that guesses will be wrong on exactly the cases that matter.
How Tensor handles these workflows
In Tensor, each workflow you hand over is a responsibility. You describe it in plain words, or you show it once in your own browser with nothing to install. Tensor repeats the steps you showed. You can also start from the Library, which holds ready-made responsibilities by industry and grows as new ones are proven.
Work arrives by email or as a request typed in the app. A forwarded resident email works. So does the notification email your website form sends.
Gmail, Google Calendar and Google Sheets connect directly, and so do Outlook, Outlook Calendar and Excel in OneDrive, through Microsoft 365. Your property system is handled differently. If it runs in a browser, you show the steps once and Tensor repeats them.
Tensor asks before it writes or sends. A reply it writes always waits for your approval. You can set limits it may work within, so routine steps inside those limits run without asking. When information is missing or conflicts, it stops instead of guessing. You approve, decline or correct.
A week of maintenance intake, as an example
Say you hand over maintenance intake on a Monday. Each request you forward becomes a task. For each task, Tensor reads the request, looks up the unit in your sheet, prepares the work order and writes a reply to the resident. You approve each one.
By Friday you have a stack of receipts. Each receipt shows what came in, each step, what you approved and the result. Reading them tells you two things: which steps you approved every time without changes, and where you had to correct something.
The first group is a candidate for limits. The second group tells you how to improve the responsibility. Each change is saved as a new version, and you can roll back if the new version is worse.
What to check before you rely on it
- Does every outgoing message wait for a person?
- Can you see afterwards exactly what was done and why?
- Does the workflow stop when details are missing?
- Can you undo a change to the steps?
- Does it work with the systems you already use?
If you want a closer look at the day-to-day admin side, read AI for property management. For how a record of each run should read, see what a receipt should show.
The quickest way to judge this is to watch one task run. The live demo lets you try a sample task with no sign-up.