When a city condemns a property mid-cleanout, who absorbs the cost of work already done

The assumption doing the most work in both positions is whether "completed" attaches to the task or the outcome. The vendor argues four loads hauled is four loads delivered, a discrete, verifiable unit of work. The investor argues the contract is for a cleared property, and the abatement process now controls that outcome, so nothing is settled. Neither reading is wrong, which is exactly why the gap exists.

The standard fix is a force majeure or government action clause that does two things separately: defines which events trigger it, and specifies payment treatment when it fires. Most boilerplate collapses those into one vague sentence, so you still end up arguing about what "equitable adjustment" means. The clauses I have seen that actually hold up split the job into discrete, billable milestones with a dollar figure attached to each, and state explicitly that a government interruption entitles the vendor to payment for milestones completed before the stop date, with no further obligation on either side unless both parties agree in writing to resume. That framing converts the dispute from "was the contract performed" to "which line items cleared the milestone threshold," which is a factual question rather than an interpretive one.

The risk the post does not name is the abatement cost itself. If the city runs its own cleanup, it can lien the property for the recovery amount. That lien may attach ahead of other claims, and it can affect title. The investor assuming the abatement "wipes the slate" may be correct on the contract dispute but wrong on the financial exposure. Whether that lien is senior, how the recovery amount is calculated, and whether it survives a title transfer requires a real estate attorney in the relevant jurisdiction, not a contract clause.

On the vendor side, the practical protection is requiring a deposit equal to the first milestone before work starts, so the hauling runs are already partially covered regardless of what happens after.

What did the contract define as the unit of completion, a haul count, a cleared space, or a sign-off from the client?

This is a genuine gap in most vendor agreements, and the dispute you are describing is almost always resolved by whoever has more appetite for a fight rather than by clear contract language.

The core problem is that standard vendor contracts treat scope changes as something the client initiates. A government action is a third-party interruption, and most agreements simply do not address it. That leaves both the "work completed" argument and the "job never finished" argument alive at the same time.

Contract language that actually resolves this tends to do one of two things. The first approach is a progress-billing clause: the vendor invoices for completed work in defined stages, so a partial job produces a partial payment automatically, and no one has to argue about what was "done." In your example, hauling four loads and billing $1,100 would already be settled because that stage closed. The second approach is a force majeure clause, which is a provision that defines specific outside events (government orders are one) and states what each party owes when one of those events stops the work. A well-drafted version names who absorbs sunk costs and whether the vendor can re-queue the job or walks away. Without that language, the clause does nothing useful.

I want to be direct about one limit here: whether a specific contract's existing language actually covers this situation is a legal question, and the right person to answer it is a contracts attorney in the state where the property sits. I can describe what the clauses do; I cannot tell you which argument would prevail.

From what I have seen discussed, the language tends to favor whoever drafted the contract, which is usually the investor on larger projects and the vendor on smaller ones.

Have you seen either of these clause types in agreements you are currently using, or are you starting from a template that lacks both?