There is an open work order on the clubhouse roof.
There is an owner three months behind.
By Friday, both of those belong to somebody who has met neither.
Neither one is trivia. An unpaid balance can follow the house as a lien. An open repair is money the community has committed and not yet spent, on a building the buyer is about to own a slice of.
So the record has to answer both. On the day of the sale, not on the day somebody last ran a report.
A work order carries what kind of job it is, the unit it was raised against, the vendor it is assigned to, its priority, its estimated cost, its status and when it is due.
A delinquent account carries the balance, how far down the collection path it has travelled, aging and balance reports, and the payment schedule if somebody agreed to one.
A payment plan is a promise. A balance is a fact. A disclosure has to carry both and never mix them up.Both sit on the same screen a community manager already works in, next to the units and the owners they belong to.
And both travel. A balance can drop straight into a letter. An open repair can print itself as a live table on a disclosure at the second it is generated.
Here is the part that decides whether any of it is worth having.
None of this gets copied into our own database overnight. Balances, delinquencies and open repairs are the fast-moving half of a community's data. The half we deliberately never keep a copy of. It is fetched live, the moment somebody asks.
The old way was a report exported on the first of the month. Which is flawlessly accurate on the first of the month, and spends the next thirty days being a historical document with a very confident tone.
Nobody inherits last month. They inherit Friday.
Next: the five money screens staff used to walk down the corridor and ask accounting about.