Insurance Programs, Risk Transfer & Resident Insurance Structures

MFC recommends adding an operator-funded income-disruption program, deployed first to the 27 Midwest communities at approximately $84,290 a year. Confidence: 71%. This service line is empty. When a resident loses a job or has hours cut, the operator has three tools - a payment plan with no standard terms, a notice, and an eviction filing. All three happen after payment has already stopped. The operator wrote off $1,187,000 in bad debt last year, filed 412 evictions, and absorbed 203 skips, and it cannot say how much of that involved residents who would have recovered, because nothing in its process records why a resident stopped paying. This recommendation is made on structure rather than on evidence, and the document says so throughout: the category has no controlled proof anywhere, and at the low end of MFC's model the program roughly breaks even. It is recommended because it is the only option that covers every unit regardless of whether a resident elects it, because the cost is fixed and bounded on 60 days' notice, and because operating it produces the reason-code data the operator has never had. Three conditions apply, and one item on the action list - adding a reason-for-non-payment field to the delinquency workflow - costs nothing, needs no vendor, and should begin whether or not this recommendation is accepted.

What the operator has

Renters insurance is required and tracked. Every lease at all 76 communities requires the resident to carry renters insurance with the operator named as an interested party. Compliance is tracked through a module inside the core property management platform. Portfolio compliance sits at 91%, which is a good number for this asset mix.

Property-side coverage is in place. Master property policy, general liability, and umbrella coverage are placed through a commercial broker and renew annually each March. This is owner-level insurance and is outside the scope of this service line.

Deposit alternatives are in place at some communities. Seventeen of the 76 communities offer a deposit alternative in place of a cash security deposit. This is a different product solving a different problem - move-in affordability, not payment continuity - and it sits with deposit alternatives.

What the operator does not have

Nothing addresses resident income disruption.

When a resident loses a job, has hours cut, or takes unpaid medical leave, the operator has three tools:

1. A payment plan, negotiated by the on-site manager, with no standard terms
2. A notice
3. An eviction filing

There is no product, no program, and no funded mechanism between "resident stops paying" and "operator starts a legal process." The gap is not partial. It is total.

What the gap currently costs

These are the operator's own numbers for the trailing twelve months.

The part nobody is tracking

The operator does not record why a resident stopped paying. There is no field for it in the platform, no requirement that on-site staff capture it, and no report that would surface it.

This matters more than it appears. A resident who stops paying because they lost a job in month seven of a twelve-month lease is a different problem from a resident who could never afford the unit and a different problem again from one who is choosing not to pay. Those three cases have different solutions and the operator cannot currently tell them apart. Every number in the table above blends all three.

Contract posture

There is nothing to renew, nothing to exit, and no incumbent to displace. This service line is unoccupied. That is unusual and it is the reason the recommendation is an Add rather than a comparison against something already in place.

Nobody at this operator asked for this. That is the point of raising it.

The gap surfaced during stack review, not from a complaint. No regional manager flagged income disruption. No owner asked about it. It appeared because MFC walks every service line in the taxonomy against what the operator actually runs, and this one came back empty while the numbers underneath it did not.

The framing question is not "what is broken." It is "what is this operator absorbing as normal."

$1.19 million a year in bad debt is being treated as a cost of doing business. It might be. Bad debt at 0.71% of billed rent is not alarming for a portfolio weighted toward Class B value-add. An operator could look at that number, conclude it is in line with the market, and stop.

The reason to keep going is that the number is being managed at the wrong end. Everything the operator currently does about non-payment happens after payment has already stopped: the plan, the notice, the filing. Nothing happens before. And the events that most often cause payment to stop - job loss, reduced hours, medical leave - are temporary. A resident who loses a job in March is frequently employable by June. The lease has twelve months to run. The unit is occupied, the resident wants to stay, and the operator's only tools are ones that end the tenancy.

What this decision is actually about. Not whether $1.19 million is too much. Whether some meaningful portion of it is the operator paying full turn-and-vacancy cost to remove residents who would have recovered.

What makes this hard to decide

The operator cannot size the opportunity from its own data. Without a reason-for-non-payment field, there is no way to know how much of the 412 filings and 203 skips involve temporary income loss versus chronic affordability versus non-payment by choice. That is the central limiter on this recommendation and it is why confidence sits at 71% rather than higher.

There is a real risk of buying the wrong thing. This category contains products with very different mechanisms, very different cost structures, and very different failure modes. Buying the well-marketed one rather than the one that fits this operator's actual mix is the most likely way to waste money here.

And there is a straightforward argument for doing nothing. Bad debt is within market range. The operator has 38 point-solution contracts already and no vendor-management function. Adding a thirty-ninth for a problem nobody complained about is a defensible thing to decline. §5 and §7 have to beat that argument, not ignore it.

What this category is

Products that address the gap between a resident losing income and the operator losing the unit. They are not one kind of thing. They divide into three genuinely different mechanisms, and the differences matter more than any feature comparison.

Resident-elected protection. An optional add-on the resident chooses and pays for, usually attached to the renters insurance requirement at lease signing. If qualifying income loss occurs, a defined portion of the rent obligation is covered for a defined period. The operator's cost is near zero. The operator's control is also near zero - coverage exists only for residents who opted in, and election rates in this category are typically low without active promotion.

Operator-funded programs. The operator pays a per-unit fee across the portfolio and protection applies automatically, without resident election. Cost is predictable and budgetable. Coverage is guaranteed. The operator pays on every unit, including the large majority that will never generate a claim.

Hardship servicing. Not risk transfer at all. Software that detects payment distress early - from payment timing patterns, partial payments, communication signals - and runs a structured workout process instead of leaving it to whichever on-site manager picks up the phone. Materially cheaper. Nothing is guaranteed; it improves how the operator handles the situation rather than transferring the loss.

What the field is moving toward

Three currents are visible. Automatic enrollment is displacing resident election, because election rates were the category's central problem. Employer-side and payroll-linked income verification is being used to confirm income loss faster. And several providers are combining risk transfer with servicing rather than offering one or the other.

A caution about the proof

This category's evidence base is weak and prospective buyers should know that before reading any vendor's numbers.

Most published results come from the providers themselves. Most describe single portfolios. Most compare outcomes before and after adoption without controlling for what else changed in the same period - and the last several years contain enough rent-market movement to swamp a program effect entirely.

MFC found no independent study, and no provider was able to supply a controlled comparison between protected and unprotected units within the same portfolio in the same period. That comparison is the one that would actually settle the question, and it does not currently exist in the public record.

Every capability claim in §6 is marked confirmed or claimed on this basis. Where a number came from a provider and MFC could not verify it against an operating reference, it says so.

A structural note on the category

These products sit close to deposit alternatives, flexible rent and resident financial wellness, collections and delinquency, and lease guarantee. Several providers cross those boundaries. An operator evaluating here should confirm what it is actually buying rather than trusting a category label - a product marketed as income protection may in practice be a collections tool, and the two do very different things to the same resident.

Add an operator-funded portfolio program, deployed first to a defined subset rather than portfolio-wide.

Why operator-funded rather than resident-elected

Resident election is where this category fails. A resident-paid rider costs the operator almost nothing, which makes it an easy approval. It also protects only residents who chose it - and the residents most likely to experience income disruption are systematically the least likely to elect an optional monthly cost at lease signing. The operator would be paying nothing and receiving protection precisely where it is least needed. The cheap option is cheap because it does less.

Operator-funded coverage applies to the unit, not to the resident's decision. Every unit in scope is covered. The operator can forecast the cost, budget it, and know what it bought. For a portfolio where 47 communities are owned and 29 are managed for institutional owners, a predictable per-unit line is far easier to carry through an owner approval than a program whose value depends on resident behavior nobody controls.

It fits how this operator already handles risk. Master property policy, general liability, umbrella coverage - all operator-funded, all portfolio-wide, all budgeted. This is the same shape and will be evaluated by the same people using the same instincts.

Why not hardship servicing alone

Servicing is genuinely cheaper and it addresses a real weakness: the operator's current hardship response varies by whichever on-site manager handles it, with no standard terms. But servicing improves the process without transferring the loss. When a resident cannot pay, a better workout process still ends with the operator absorbing the shortfall. For an operator with $1.19 million already written off, better process alone does not move the number enough to justify the change-management cost.

Servicing is the right second purchase, once the reason-code data from Item 1 shows where the process is failing. It is not the right first one.

Why deploy to a subset first

The operator cannot yet size this. Without reason-for-non-payment data, nobody knows how much of the loss is temporary income disruption. Buying portfolio-wide would commit roughly $234,000 a year against an unquantified opportunity.

A defined subset produces the missing data while providing real coverage. MFC recommends the 27 Midwest communities - 7,020 units. They carry the portfolio's highest delinquency, its highest eviction rate, and its oldest asset base. If the mechanism works anywhere in this portfolio, it works there, and if it does not work there it will not work in Texas.

This is a phased Add, not a pilot. The distinction matters and is deliberate: the operator is buying real coverage for real units under a real agreement, with a defined expansion decision at twelve months. It is not a trial with an option to walk.

What the operator is actually buying

Not a reduction in bad debt as such. A tool that keeps a recoverable resident in place. The value shows up as evictions that do not happen, units that do not turn, and 41-day vacancies that do not occur - not as a line item labeled savings.

And a second thing, which may end up mattering more: the operator will finally know why residents stop paying. Any program in this category requires the reason to be captured to process anything at all. That data does not exist today and cannot be reconstructed retroactively. It is the input every future decision in this area depends on.

What this section can and cannot tell you

This is the honest headline: MFC cannot tell this operator what this program will return. Nobody can, including any provider that offers to.

The reason is in §2. The operator does not record why residents stop paying. Without that, the share of the $1.19 million in bad debt that involves recoverable temporary income loss is unknown. Every return figure below is modeled from an assumption about that share, and the assumption is not the operator's data. It is MFC's estimate.

What follows is therefore a modeled, second-order projection, not a savings forecast. It is presented as a range with its assumptions exposed, so the operator can disagree with the assumptions rather than with the conclusion.

The confirmed cost side

Note what that delta sign means. This recommendation increases spend. There is no cost offset in year one and none should be claimed. What follows is the argument that the increase is worth making - not a claim that it pays for itself on the budget line.

The modeled return

Confirmed inputs. Midwest subset trailing twelve months: 189 eviction filings, 71 evictions completed, 94 skips, $498,000 bad debt written off, 41 days average vacancy following eviction against 22 on a standard turn.

MFC's assumption, stated plainly. MFC models that 20-35% of completed evictions and skips in this subset involve temporary, recoverable income loss rather than chronic affordability or non-payment by choice. This range is drawn from MFC's cross-portfolio observation and from published category figures. It is not this operator's data and it has not been validated against this operator's residents. It is the single largest assumption in this document.

Modeled outcome, using $4,850 per completed eviction and the operator's confirmed turn and vacancy costs:

Read the low case first. At the low end this program roughly breaks even and may lose a small amount. That is a real possible outcome, not a formality. An operator that considers the low case unacceptable should decline this recommendation, and declining on that basis would be a reasonable decision.

What is not in the model

Deliberately excluded, because MFC cannot size them and will not inflate a case with unquantified benefits:

• Reduced legal and administrative time for on-site and regional staff
• Retention effects among residents who never file but know the program exists
• Reputation effects
• The value of finally having reason-code data - arguably the most durable benefit here, and not monetizable

Confidence - cost side

The operator stops being blind to its own delinquency. Today $1.19 million is written off with no record of cause. Any program in this category requires the reason to be captured to process anything. Within twelve months the operator would know what proportion of its loss is temporary income disruption, what is chronic affordability, and what is non-payment by choice. Those three have different solutions and the operator currently cannot distinguish them. This data cannot be reconstructed after the fact and does not exist today at any price other than starting to collect it.

Hardship response becomes consistent. Right now the outcome for a resident who loses a job depends on which on-site manager takes the call. There are no standard terms, no documented process, and no consistency across three regions. That is a fair-housing exposure as much as an operating one - inconsistent discretion applied to residents in similar circumstances is exactly the pattern that draws scrutiny. A defined program replaces discretion with a documented, uniformly applied process.

It is a credible answer to a question institutional owners are asking. Four institutional owners hold 29 communities. Resident stability and delinquency management appear in owner reporting and increasingly in owner diligence. An operator that can describe a funded, structured program is answering a question its competitors answer with a payment-plan policy. For an operator whose stated priority is growing the fee-managed portfolio, that is a differentiator in a pitch, not just a cost line.

It fits where this operator is weakest. The Midwest subset carries the highest delinquency, the oldest assets, and the highest technician vacancy rate - the same region flagged in Document 1. Concentrating the first deployment there aligns this recommendation with the portfolio's actual pressure point rather than spreading it evenly across regions that need it less.

Tied to stated goals. Leadership named consistent cross-region operating performance and fee-managed growth. This serves both - the first by standardizing a process that is currently improvised, the second by producing something to say to owners that is more than a policy.

Owner approval is the real obstacle, and it is not a formality. Twenty-nine communities are managed for four institutional owners. A new per-unit expense line requires each owner's approval, and any owner may decline. If two of the four decline, the Midwest subset fragments and the twelve-month data set becomes too thin to support an expansion decision. This risk sits ahead of every other consideration in this section and the implementation sequence in §10 is built around it.

The evidence base is genuinely weak. No provider in this category supplied a controlled comparison of protected against unprotected units. Published results are self-reported, uncontrolled, and drawn from periods with substantial rent-market movement. This recommendation rests on structural reasoning - the mechanism covers every unit, produces the missing data, and costs a predictable amount - not on demonstrated results. An operator that requires demonstrated results before spending should decline, and that position is defensible.

The low case is a real outcome. At 20% recoverable share the program roughly breaks even. The operator should enter this expecting the possibility of spending $84,290 and receiving data plus process consistency rather than a financial return. If that outcome would be treated as a failure, this should not be started.

Getting the wrong thing under the right label. Several providers in this category cross into collections. A product sold as income protection that operates as a collections tool does something very different to a resident in hardship, and would undercut the retention logic entirely. Contract review must confirm what the mechanism actually does, not what the category label implies. This is named as a diligence item in §12.

Resident data handling. The program requires income and employment information from residents in hardship. See §11 - this is a mandatory flag, not a risk to be weighed.

Adverse selection at expansion. Deploying to the highest-loss region first is correct for testing the mechanism and produces a biased sample for economics. Results from the Midwest will overstate the return available in Texas and the Mountain West. Any expansion model must discount accordingly rather than extrapolating the subset result portfolio-wide.

Cascade - two service lines move.

• Collections, Debt Recovery & Delinquency Management - a functioning income-disruption program should reduce collections volume and changes what the collections process is for. If a collections vendor is engaged during this period, scope this first.
• Flexible Rent & Resident Financial Wellness - overlaps in intent. Any future evaluation there must account for what this program already covers, or the operator will pay twice for adjacent coverage.

Maintenance management is unaffected. Identity and income verification is unaffected.

What MFC could not verify. No independent study of this category exists. Provider claims about election rates, intake handling, and outcomes were not confirmed against operating references at comparable scale. The two portfolio references above 15,000 units are self-reported by the provider and were not contacted directly by MFC.

Add an operator-funded income-disruption program, deployed to the 27 Midwest communities, on an annual term with a defined expansion decision at twelve months. Confidence: 71%.

The service line is empty and the loss underneath it is $1.19 million a year, managed entirely after the fact. The operator has no way to tell recoverable hardship from chronic non-payment, because nothing in its process ever required that to be recorded. This recommendation puts a funded mechanism in front of the loss and, as a condition of operating, produces the data the operator has never had.

It is recommended on structure rather than evidence, and the document says so throughout. The mechanism covers every unit regardless of resident election, the cost is predictable and approvable, and the exposure is bounded at $84,290 on a 60-day notice. The recommendation is not that this will return money. It is that the operator should stop absorbing a seven-figure loss it cannot see inside of, at a cost it can afford to be wrong about.

Conditions

This recommendation is firm on direction and conditional on three things:

1. At least three of the four institutional owners approve. Below that, the subset is too fragmented to produce a usable twelve-month data set. Fall back to the owned communities only - 14 of the 27 - and extend the evaluation period to eighteen months.
2. The contract confirms the mechanism is protection, not collections. If review shows collections behavior, this recommendation does not apply to that provider.
3. Reason-code capture is contractually required, not optional. If the provider will not commit to supplying reason-coded event data back to the operator, the primary strategic benefit disappears and the case reverts to the return model alone - which is not strong enough on its own.

How to act on this

Weeks 1-6 - Approvals first, procurement second. Take this to the four institutional owners before selecting a provider. Owner approval is the binding constraint and the slowest step; running it in parallel with procurement wastes weeks if an owner declines. Present it as a bounded twelve-month program with a defined decision point, not as a permanent new line. Have the CFO lead - this is a budget conversation, not an operations one.

Weeks 4-10 - Provider selection and contract review. Request written terms from at least three providers spanning the mechanisms in §6, so the operator confirms the structural argument itself rather than accepting MFC's. Legal review confirms the collections question in Condition 2 and the reason-code requirement in Condition 3. Confirm the connector to the core platform before signing, not after.

Weeks 8-14 - Baseline capture. Before anything goes live, reconstruct the true per-eviction cost from the operator's own records and set the twelve-month measurement baseline. This step is skippable and skipping it destroys the expansion decision - without a baseline captured the same way it will be measured, the twelve-month result cannot be compared to anything.

Weeks 12-18 - Deployment. Configure the connector, train on-site and regional staff on intake and on what the program does and does not do, communicate to residents at the 27 communities. Staff training is the failure point: a program residents never hear about from the people they talk to will not be used.

Months 4, 8, 12 - Review points. At month 4, confirm the mechanics work and events are being reason-coded. At month 8, first look at whether the recoverable-share assumption is holding. At month 12, the expansion decision, made against the operator's own twelve months of data.

Month 12 - The decision. Expand portfolio-wide, hold at the subset, or exit on 60-day notice. All three are live outcomes. Exit is not a failure - it is what the annual term and the notice period were structured to preserve.

Confidence gaps, tracked

Item 4 deserves separate attention. It is the only item on this list that requires no vendor, no contract, and no approval. Reason-for-non-payment capture can begin next week with a field and a staff instruction. It is the single highest-value action in this document, it costs nothing, and it should start regardless of whether this recommendation is accepted. If the operator does one thing from this document, do this one.

Operational next steps

Confidence - full rationale