Legionella Water-Management Records for Manufactured Home Communities

Published September 23, 2026

Research question

How can a manufactured-home community organize Legionella water-management evidence for offices, clubhouses, pools, spas, cooling equipment, vacant units, and other shared systems without claiming risks or duties that have not been assessed?

Bottom line

CDC's toolkit begins with determining whether a building or device needs a water management program, then describes a team-based process: describe systems, identify hazardous conditions and control locations, establish control measures and limits, monitor them, take corrective action, verify implementation and effectiveness, and document and communicate. That sequence matters. A generic temperature log is not a program, and a laboratory result is not a standalone explanation of exposure or safety. Community operators need a reviewed scope, current water-system diagrams, assigned expertise, dependable field records, and an immediate path for deviations, illness reports, closures, and public-health coordination.

Method and evidence boundary

This study reviewed CDC's current water-management-program toolkit page and guide, its toolkit for common sources of exposure, and environmental-assessment resources on September 22, 2026. Verified facts are attributed to CDC. The proposed document controls are MobileHomeBiz analysis. They do not determine whether a specific site needs a program, establish control limits, interpret a test, diagnose disease, identify an exposure source, or replace health department, water utility, engineering, laboratory, legal, or medical direction.

Manufactured-home communities differ substantially. Individual homes may have separate resident-controlled plumbing while offices, laundry rooms, bathhouses, pools, spas, fountains, irrigation, fire systems, cooling towers, storage tanks, or vacant units have different ownership and configurations. State and local requirements may be more specific. Begin with facts and qualified review.

Scope assessment

Create a record for each building and water-using device. Include ownership, population served, occupancy pattern, susceptible-population considerations handled without unnecessary personal data, building height and age, storage, heaters, recirculation, low-flow areas, aerosol-generating devices, cooling towers, decorative fountains, spas, recent shutdowns, renovations, and supply interruptions. Complete the CDC assessment worksheet with the responsible team and retain the version, answers, evidence, reviewer, decision, and review date.

Do not apply one scope decision to every asset. A clubhouse spa and a small office sink do not present identical systems. A “no program needed” conclusion should still show who assessed which facts and when it must be reconsidered.

Water-management team and authority

CDC recommends a multidisciplinary team with knowledge of the building water systems and authority to implement controls. Record team roles, qualifications, authority, contacts, backups, approval limits, and decision paths. Include facility operations, maintenance, management, water-treatment or engineering expertise, infection-prevention or public-health expertise when relevant, and vendors according to actual scope.

The remote administrator is a document coordinator, not the technical team. Make escalation available outside the ticket queue for control-limit deviations, suspected cases, loss of water pressure, disinfection failures, closures, and public-health requests.

System description and diagrams

Maintain versioned diagrams showing incoming water, treatment, storage, heaters, recirculation, distribution branches, distal outlets, mixing devices, dead legs, shared amenities, aerosol-generating devices, sampling points if approved, and responsibility boundaries. Link equipment IDs, valves, sensors, meters, and drawings. Record field verification and discrepancies rather than assuming an old plan is accurate.

Changes to plumbing, occupancy, hot-water settings, treatment, or devices should trigger diagram and program review. Preserve superseded versions because they explain earlier monitoring locations and decisions. Avoid publishing sensitive infrastructure maps.

Hazardous conditions and control locations

The qualified team identifies conditions that can support Legionella growth or spread and chooses control locations. The administrative register can record the condition, system segment, rationale, control measure, limit, monitoring method, frequency, responsible role, instrument, response, and source. It must not invent universal temperatures, disinfectant levels, or flushing intervals from a general article.

Control limits should be specific enough to produce an action. Record whether a reading is within the approved range, but retain the raw value, unit, time, location, method, instrument ID, operator, and unusual conditions. A colored dashboard without raw evidence cannot support later analysis.

Monitoring quality

Monitoring records require stable location IDs and calibrated or otherwise verified instruments under the approved method. Preserve calibration, maintenance, lot or reagent data when relevant, access failures, missed readings, sensor outages, and manual substitutions. Never backfill a missed measurement with a later value.

Trend review should consider system operation and occupancy. A series of values can reveal drift, but automated rules should not diagnose Legionella risk. The team decides whether a pattern requires corrective action, investigation, sampling, or program change.

Corrective actions

For every deviation, record detection time, exact location, value or observation, immediate protective measure, notification, technical decision, assigned action, completion evidence, follow-up measurement, review, and closure authority. Separate routine maintenance from a corrective action when the approved program does. Preserve failed attempts and repeated deviations.

Administrative staff should not tell onsite personnel to raise temperatures, add disinfectant, flush, close an amenity, or collect samples unless the instruction comes through the approved technical process. Those actions can create scalding, chemical, occupational, or exposure risks and may affect other systems.

Verification and validation

CDC distinguishes checking whether the program is being implemented as designed from checking whether it effectively controls hazardous conditions. Keep program verification, record review, task completion, diagram accuracy, team review, separate from validation evidence selected by the experts. A laboratory test may be part of validation or investigation, but testing strategy and interpretation require expertise.

Record laboratory identity, method, sampling plan, location, collector, custody, transport, result, limitations, and interpretation by the qualified owner. Do not publish or summarize a result as proof that a building caused or could not cause illness.

Shutdowns, vacancies, and service interruptions

Extended low occupancy, vacant units under operator control, seasonal amenity closure, construction, main breaks, pressure loss, heater outages, and boil-water or utility notices should trigger the program's reviewed response. Maintain an event record with affected systems, start and end times, utility communications, actions, reopening criteria, verification, and resident communications approved for that event.

Avoid generic reassurance. Communications should state known facts, actions, instructions from authorities, contact routes, and updates. Protect health information and coordinate suspected illness reports immediately with healthcare and public-health channels as directed.

Vendor and sampling controls

Vendor files should identify actual services, qualifications, methods, instruments, laboratories, response times, deliverables, and decision boundaries. Match invoices to asset and event IDs. A water-treatment vendor's visit does not prove that every control location met its limit, and a laboratory certificate does not prove that the sampling plan was appropriate.

Restrict system diagrams, security details, health reports, and identifiable resident data. The general task queue should carry only the minimum necessary operational status.

Audit tests

Sample scope decisions against current buildings and devices. Trace diagram components to field assets. Test readings for exact location, raw value, unit, method, instrument, and timely response. Look for changed plumbing without version updates, deviations closed by work-order status alone, identical copied readings, missed checks replaced with estimates, laboratory results without custody, and reopened amenities without approved criteria.

Useful measures include monitoring completion, unresolved-deviation age, recurrence by control location, instrument downtime, and time from system change to diagram review. None establishes health risk or compliance by itself.

Remote coordination boundary

A virtual assistant can control versions, schedules, document intake, calibration reminders, exception queues, and meeting packets. The assistant cannot design the program, set limits, interpret clinical or laboratory information, direct treatment, communicate a health conclusion, or decide reopening. Emergency and public-health escalation must bypass routine queues.

Implementation sequence

1. Name the accountable owner and multidisciplinary water-management team.
2. Inventory and assess every building and water-using device separately.
3. Verify and approve diagrams, responsibility boundaries, and source set.
4. Establish control locations, measures, limits, methods, and responses through experts.
5. Configure raw-data, deviation, correction, verification, and validation records.
6. Test a missed reading, pressure loss, vacancy, sensor failure, and suspected illness report.
7. Audit source evidence and field implementation without erasing prior versions.

What the evidence can show

The file can show program scope, system understanding, monitored conditions, deviations, actions, communications, and expert decisions. It cannot prove that Legionella was absent everywhere, that a person was or was not exposed at the property, that illness originated from a particular source, or that every applicable duty was met. Clear limits protect residents and decision makers from unsupported conclusions.

Sources reviewed

1. Toolkit: Developing a Legionella Water Management Program. Centers for Disease Control and Prevention. https://www.cdc.gov/control-legionella/php/toolkit/wmp-toolkit.html. Checked 2026-09-22.
2. Developing a Water Management Program to Reduce Legionella Growth & Spread in Buildings. Centers for Disease Control and Prevention. https://www.cdc.gov/control-legionella/media/pdfs/toolkit.pdf. Checked 2026-09-22.
3. Toolkit for Controlling Legionella in Common Sources of Exposure. Centers for Disease Control and Prevention. https://www.cdc.gov/control-legionella/php/toolkit/control-toolkit.html. Checked 2026-09-22.
4. Environmental Assessment and Sampling Resources. Centers for Disease Control and Prevention. https://www.cdc.gov/investigate-legionella/php/resources/environmental.html. Checked 2026-09-22.

Conclusion

Legionella water-management documentation is useful only when it reflects an expert-designed program for the actual systems. A strong community record keeps scope, diagrams, limits, measurements, deviations, actions, and validation connected while refusing to turn administrative completeness into a health claim.