A board of directors is unusually well equipped to interrogate some parts of a business and strangely helpless before others. Put a capital allocation decision in front of a competent board and it will probe the assumptions, stress the model, and challenge the return. Put the strategy in front of it and directors will question the market read, the competitive position, and the timing. These are the areas boards are built to govern, and they govern them with real rigor. Now ask the same board a simpler question. Is the operation underneath all of this actually healthy, or is it slowly deteriorating in ways that will surface as a crisis two years from now? Here the rigor tends to evaporate. Not because directors do not care about operations, but because operations is the hardest thing for a board to see clearly, and the information that reaches the boardroom about it is the most likely to be filtered, flattering, and late. This is a governance gap hiding in plain sight. In property ...

When a property company implements a platform like NetSuite, customization feels like pure gain. The system can be shaped to fit exactly how you work: a script here to automate an approval, a custom field there to capture something specific, a tailored workflow that matches your process precisely. Each request is small, each one is reasonable, and each one makes the system fit a little better. Nobody in the room is thinking about what any of it costs, because the cost does not arrive at the moment of building. It arrives later, and it keeps arriving. Every customization you add is not a one-time purchase. It is a standing obligation. It becomes part of your system's codebase that has to be maintained, and it has to be re-tested every time the platform underneath it changes, which for NetSuite is twice a year, every year, for as long as you run it. The build is the down payment. The tax is what you pay at every release afterward, and most organizations never see the tax coming because ...

Ask a property operator how often their elevators must be inspected and most will answer "annually," with some confidence. For a single building in a single jurisdiction, they are often right. For a portfolio spread across several states, the answer is not annually, or quarterly, or every six months. It is all of those at once, depending on where each building sits, because there is no single federal or nationwide legal rule setting how often a private building's elevator must be inspected. The obligation is set state by state and sometimes city by city, and the pieces that vary are not trivia. The interval varies, the authority that enforces it varies, the person legally allowed to perform the inspection varies, the filing and penalty structure varies, and the rules change over time. This article covers why the federal government does not set this rule, what actually governs it, how far the state regimes diverge, and why the real exposure for a multi-state operator is not the ...

Quick Reference: Ohio Self-Help Eviction Rules at a Glance Issue Rule Authority Core prohibition No act, including utility termination, exclusion from the premises, or threat of an unlawful act, to recover possession outside the court process R.C. 5321.15(A) Seizing belongings for rent Prohibited unless a court of competent jurisdiction has ordered it R.C. 5321.15(B) Penalty All damages caused to the tenant, plus reasonable attorney fees R.C. 5321.15(C) Attorney fees Mandatory once a violation and damages are established Crenshaw v. Rowland, 2011-Ohio-5942 (6th Dist.) Statutory remedies vs tort claims Cumulative, not exclusive; conversion and trespass claims survive alongside Shroades v. Rental Homes, 68 Ohio St.2d 20 (1981) Applies to holdover tenants Yes, expressly covers a tenant whose right to possession has terminated R.C. 5321.15(A) and (B) Lease waiver Chapter 5321 rights cannot be waived by agreement, with one narrow exception R.C. 5321.13(A) and (F) Pre-suit notice Three or ...

Every organization runs on two kinds of work. The first kind is visible. It has a name, a number, a line on a report, an owner who can be praised or blamed. The second kind is invisible. It is the reconciliation someone does by hand every month so the figures finally agree, the workaround one person invented years ago that the whole process now silently depends on, the tenant issue resolved in a phone call that no system ever recorded, the judgment a long-tenured manager applies so instinctively that nobody has ever thought to write it down. The uncomfortable truth of most enterprises is that the second kind of work is doing far more to keep the business alive than the first kind, and it is precisely the kind leadership cannot see. This is not a minor reporting gap. It is a governance problem, because an organization is governed through the picture that reaches the top, and invisible work is defined by its absence from that picture. Leaders are, in effect, steering by a map that ...

Minnesota's eviction process is fast on paper. A straightforward case can move from filing to a hearing in as little as seven days, and most cases never reach a trial. But two changes that took effect in 2023 and 2024 reshaped the process in ways that catch landlords who are working from an older playbook, and one of them isn't the one most people point to. Ask a Minnesota landlord what changed recently and they'll usually name the new 14-day pre-filing notice. That's the visible change, and it matters: skip it and the court dismisses your case and expunges the record, so you lose the filing and the tenant walks away with a clean slate. But the larger operational shift is quieter and mostly unnoticed. Minnesota rewrote its eviction expungement law so that a large share of eviction records now come off the public file automatically, and pending cases are sealed from public view entirely. For any landlord who relies on eviction history to screen applicants, the public dataset they've ...

Ask anyone who runs a building what good maintenance looks like and the answer is some version of "stay ahead of it." Inspect on a schedule, service on a schedule, replace before it breaks. Preventive is responsible; reactive is negligent. The whole industry is organised around the belief that more preventive maintenance is always better. For most of the components in a building, that belief is backwards. The evidence, which comes from outside property entirely, from aviation and reliability engineering, is that the majority of equipment does not fail because it got old, and for anything that does not wear out with age, servicing it on a schedule does nothing useful and can actively make it less reliable. This article covers where that finding came from, why it means preventive maintenance is the wrong default for most assets, and how to tell the minority where it genuinely pays from the majority where it does not. One boundary first, stated plainly because it matters: safety-critical ...

A resident falls three months behind. The number in front of the property manager is the arrears: three months of rent, plus late fees, sitting in the delinquency report. The instinct, and often the policy, is to file. The resident broke the agreement, the money is owed, and eviction is how you enforce the lease and get the unit back. That decision is almost always made on the wrong number. The arrears figure is the smallest of the costs in play, and the decision to evict sets in motion a sequence of much larger ones: weeks or months more of lost rent while the case runs, legal and court fees, a vacant unit after you finally recover possession, a turn, a re-lease, and a judgment you will most likely never collect. Add those up and the true cost of an eviction is frequently several times the arrears that triggered it. Once the full figure is on the table, the arithmetic surprisingly often points somewhere else: a payment plan, or paying the resident to leave. This article works through ...

Every company maintains two versions of its numbers. There is the version you manage from, with the ugly variances, the receivable that is really a problem, the property that is quietly underperforming, the one-time item that was not quite one-time. And there is the version you present, cleaned up for the board, the lender, the investor, framed to tell a coherent story, with the awkward parts contextualized into something more comfortable. This is normal and mostly fine. External audiences need a summary, not the raw mess, and framing a summary is not deception. The danger is subtler and rarely discussed. Over time, the polished version has a way of migrating inward, until it is not just the version you show outsiders but the version leadership half-believes, and the messier truth you should actually be steering by gets quietly displaced by the story you have been telling about it. When the presented number becomes the managed number There is a well-established principle that explains ...

Two maintenance teams cover similar portfolios with similar work. One is scheduled to about 80 percent of its capacity and consistently turns work around quickly. The other is scheduled to 95 percent, looks more efficient on paper, and is drowning: residents wait days, the team feels permanently behind, and every week the backlog is a little worse. The natural explanation is that the second team is understaffed, badly run, or both. The natural fix is to tighten scheduling and push utilisation higher still. Both the explanation and the fix are wrong, and the reason they are wrong is a property of queues that has been understood mathematically since 1961. This article covers why a busier team is a slower team, why maintenance is the worst kind of work for this effect, and what the actual levers are. The Counterintuitive Part, and Where It Comes From The instinct in every operation is that a resource should be kept as fully utilised as possible. Idle time is waste. A technician booked to ...