Cal. Civ. Code § 441.510
Civil action, how maintained — procedure
Operative Text
1. If any building or dwelling is found to be in violation of building or housing codes which the county, municipality, local housing corporation or neighborhood association in the exercise of reasonable discretion believes constitutes a threat to the public health, safety or welfare, and alleges the nature of such threat in its petition, the county, municipality, local housing corporation or neighborhood association, in addition to any other remedies available to it, may apply to a court of competent jurisdiction for the appointment of a receiver to perform an abatement. 2. At least sixty days prior to the filing of an application for appointment of a receiver pursuant to sections 441.500 to 441.643, the county, municipality, local housing corporation or neighborhood association shall give written notice by regular mail to all interested parties of its intent to file the application and information relative to: (1) The identity of the property; (2) The violations of the building or housing codes giving rise to the application for the receiver; (3) The name, address and telephone number of the person or department where additional information can be obtained concerning violations and their remedy; and (4) The county, municipality, local housing corporation or neighborhood association which may seek the appointment of a receiver pursuant to sections 441.500 to 441.643 unless action is taken within sixty days by an interested party. 3. A county, municipality, local housing corporation or neighborhood association may not apply for the appointment of a receiver pursuant to sections 441.500 to 441.643 if an interested party has commenced and is then prosecuting in a timely fashion an action or other judicial or nonjudicial proceeding to foreclose a security interest on the property, or to obtain specific performance of a land sale contract, or to forfeit a purchaser's interest under a land sale contract. 4. Notice of the application for the appointment of a receiver shall be served on all interested parties. 5. If, following the application for appointment of a receiver, one or more of the interested parties elects to correct the conditions at the property giving rise to the application for the appointment of a receiver, the party or parties shall be required to post security in an amount and character as the court deems appropriate to ensure timely performance of all work necessary to make corrections, as well as such other conditions as the court deems appropriate to effect the timely completion of the corrections by the interested party or parties. 6. In the event that no interested party elects to act pursuant to subsection 5 of this section or fails to timely perform work undertaken pursuant to subsection 5 of this section, the court shall make a determination that the property is in an unsafe or insanitary condition and appoint a receiver to complete the abatement. 7. A receiver appointed by the court pursuant to sections 441.500 to 441.643 shall not be required to give security or bond of any sort prior to appointment.
Missouri Revised Statutes § 441.510 establishes a civil court process through which a county, municipality, local housing corporation, or neighborhood association can seek the appointment of a court-supervised receiver to address serious building or housing code violations that threaten public health, safety, or welfare. Before filing for a receiver, the petitioning entity must give all interested parties at least 60 days' written notice identifying the property, the violations, and a contact for more information. Interested parties — such as owners, lenders, or contract purchasers — have the opportunity during that window to voluntarily correct the violations, though they may be required to post security with the court to guarantee timely completion of the work. If no interested party acts or follows through, the court may appoint a receiver to carry out the abatement.
Plain English — not legal advice.
Under Mo. Rev. Stat. § 441.510, property owners who receive a 60-day notice of intent to seek a receiver appointment should treat it as a formal deadline: compliant operators typically document their remediation plans promptly, communicate with the notifying entity, and begin corrective work within the notice period. If an owner elects to correct the violations, the court may require posting of financial security to guarantee timely completion, so operators generally ensure they have the resources to satisfy that requirement. Owners who are already pursuing foreclosure, specific performance, or forfeiture proceedings on the property may have grounds to prevent the receivership application from moving forward under the statute's protections.
General guidance for property managers — not legal advice for your specific situation. Consult an attorney for advice on your case.
Mo. Rev. Stat. § 441.510 can be relevant to tenants living in buildings with serious code violations, because it gives local governments and certain housing organizations a legal pathway to force repairs through a court-appointed receiver when an owner fails to act. Tenants who are aware of significant health or safety violations may consider contacting their local municipality, housing department, or a tenant-rights organization to learn whether a receivership proceeding under sections 441.500 to 441.643 might be applicable to their building. Understanding this process can help tenants recognize their rights when a receiver is appointed and the building's management changes hands under court supervision.
General guidance for tenants — not legal advice for your specific situation. Consult a tenant-rights organization or attorney for advice on your case.
Generated October 14, 2026 — auto-generated, not yet human-reviewed. See /transparency for methodology.
Effective Timeline
References Out
Rules and statutes cited by this regulation
References In
Rules and statutes that cite this regulation
Related Rules
Source Information
Use this in your app
Access this data programmatically via our API