Practices and firms

Property management: every request sorted and summarised

For operations leads and property managers at companies managing 200 to 2,000 units. Workflows capture and summarise requests; your team commits to repairs and dates.

Your week, in your words

iSystematic works with property management companies whose week goes on maintenance requests, after-hours calls, emergencies, work orders, tenant questions, rent arrears and monthly owner reports.

Leah (fictional), the operations lead at a company managing 800 units, starts each Monday with the weekend's messages and works out which ones could not wait. The workflows on this page are written for a week like hers.

Where most start

Most companies start with W02 Inbox Triage and Draft Replies for requests and the W03 Approved FAQ Assistant for tenant questions, configured with you in a setup session. Requests are sorted and summarised, and urgent ones are marked for a person.

A different start fits portfolios where arrears or tenant onboarding take the most time: the Receivables Assistant or Intake to Onboarding, built and run for you.

Works with your systems

Requests are captured and summarised without any integration; creating work orders in your platform is assessed first.

What it doesWhat it needs
Capturing and summarising requestsNo integration. It runs in your own assistant account.
Creating work orders in your property management platformA connector (level 3) or a custom integration (level 5), assessed first.

Software is named here only to say what has been tested with it. Nothing on this page implies an integration that has not been built.

How it is built

Every system we build for a property company keeps the promises below; each is the plain-words form of a framework explained on How we build.

What we promiseWhat stands behind it
It never promises a tenant anything you have not approvedThe Boundary Invariant
It checks every answer against your own sources before anyone sees itPEVG: the verifier
It cannot change its own instructions; you approve what it learnsPARA: adaptation bounded like action
Nothing goes live until a named person at your company signs it offFive-Gate Deployment Model™: G3 Approval
Confidential questions go only to the AI services you approved, in Canada where requiredGoverned Routing Policy; Cross-Border AI Architecture Patterns™
It has a monthly spending limit it cannot exceedBudget as Boundary
We check every service we put into your setupAI Vendor Risk Framework (AVRF)™
If something goes wrong, we can show exactly what happened, and fix the causeAI Incident Response Protocol (AIRP)™ and the event identity
You can see what it did and whyThe BOE Declaration

These promises describe the systems we build and run for you. A free card is a manual routine: you run it and check its output yourself.

What always stays with you

Your team decides these, every time.

  • Any commitment to a repair date
  • Any charge
  • Any notice to a tenant
  • Anything about a deposit

What we never do

We never build any of these into a property company's setup.

  • Legal notices drafted as final
  • Arrears reminders that do not follow the tenancy rules where the property is
  • Tenant screening on personal attributes

Leah is a fictional persona. Workflows prepare; people decide.

Tell us what arrives after hours

We reply with one recommended start.