A community mikvah is one of the strangest engineering problems in building services. It is at once a public bathing facility subject to state health codes, a piece of ritual infrastructure whose water must satisfy a body of law that predates plumbing by two millennia, and a building that operates twenty-five hours a week with no one permitted to touch a switch. Each fails differently: a health-code failure closes the building, a halachic failure makes it useless, a controls failure makes it miserable.

What follows is the engineering view. Every halachic parameter below is decided by the rav overseeing the project, and no two projects come back identical. The engineer's job is to build to whatever ruling arrives, and to ask the questions early enough that the answer can still be accommodated.

The Water Architecture That Drives Everything Else

The immersion pool a person enters is not, by itself, the halachically operative body of water. Validity comes from a reservoir, the otzar, holding rainwater collected and delivered without ever being carried in a vessel or lifted by human hands. The pool itself holds ordinary treated municipal water and becomes valid through contact with the otzar. Three engineering consequences follow, and they constrain the entire mechanical design.

  • The rainwater collection path cannot contain a vessel. Continuous fall from roof to reservoir with no receptacle anywhere in the run, no traps, no in-line filter housings, no fittings that hold standing water, and slopes maintained throughout. A plumber working from habit will install a cleanout that ruins the run.
  • The connecting opening has a minimum size and must stay open. Its dimensions, position, and whether it may ever be plugged are ruling-dependent. If a plug is permitted, its actuation becomes a controls problem on Shabbat.
  • The otzar water generally cannot pass through the circulation system. Pumps, filters, and heaters draw from and return to the immersion pool only, and piping has to be laid out so no path exists, even accidentally, that would draw reservoir water through a pump.

That last point is where most engineering mistakes happen. Suction and return locations, valve positions, and drain-down sequences all have to be reviewed against the ruling, not just against good pool practice, and documented as testable requirements, the discipline described in writing halachic requirements into a product spec.

Filtration and Sanitation Under a US Health Code

In most American jurisdictions a community mikvah is regulated as a public pool or spa, which brings obligations that have nothing to do with halacha and everything to do with the local health department.

  • Turnover rate. Spa-classified vessels commonly must turn over their volume every thirty minutes to an hour, which for a several-thousand-gallon pool means a substantial pump and filter package.
  • Disinfectant residual. A measurable free chlorine or bromine level, continuously monitored in many jurisdictions, with automated feed and recorded readings.
  • Drain safety. Anti-entrapment outlet covers and split main drains under the federal pool and spa safety requirements. Inspectors check it.
  • Accessibility. As a place of public accommodation the facility falls under ADA obligations: a compliant lift or graded entry with handrails, plus accessible preparation rooms.

The practical tension is chemical load. Users immerse bare skin, and heavy chlorination is unpleasant. Well-designed installations pair a modest halogen residual with secondary treatment, typically medium-pressure ultraviolet or an ozone loop with adequate contact time, keeping the residual at the low end of the allowed band. Controllers dosing on oxidation-reduction potential and pH hold the chemistry steady.

Heating: Comfort, Recovery, and Shabbat

Immersion water is typically held around 96 to 102 degrees Fahrenheit, and users notice a two-degree deviation. The load comes less from raising the water than from holding it against evaporative losses, so an insulated shell, a thermal cover during off hours, and good ventilation do more for the energy bill than a larger heater.

Heat exchangers separating the boiler loop from the pool water are standard, for corrosion reasons and because they simplify the review of what touches the immersion water. Sensor placement matters more than sensor accuracy: a probe in a dead leg reads a temperature no user experiences, and the tradeoffs are those covered in choosing a temperature sensor.

On Shabbat and Yom Tov no one may initiate heating, and in most rulings no one may adjust a setpoint. The accepted design maintains temperature through pre-set scheduling, with the control loop running continuously from before the onset of the day. The patterns are those used in Sabbath mode thermostats and HVAC controls: no display changes triggered by presence, no user-facing setpoint, and a schedule loaded in advance.

The Shabbat Controls Problem

The facility runs on its busiest nights under conditions where switches, sensors, and screens are off limits. Everything must be arranged in advance, or arranged so human action does not directly cause an electrical result. The standard toolkit:

  1. Scheduled operation. Lighting, circulation, heating, and ventilation run from a controller programmed before the day begins, an approach detailed in Shabbat timers and time controllers.
  2. Lighting that does not respond to people. Occupancy sensors, motion-triggered corridor lights, and automatic bathroom fans must be defeated or scheduled, and preparation rooms need light levels that work without adjustment, as discussed in lighting and light control for Shabbat observance.
  3. Grama interfaces where interaction is unavoidable. Indirect-action mechanisms decouple the human act from the electrical result, the subject of grama mechanisms in Shabbat engineering.
  4. Doors, locks, and privacy indicators. Electronic access control, occupied-room indicators, and intercoms all become live issues, and institutions serving observant guests face the same list, covered in Shabbat technology for hotels and institutions.

Monitoring and Records

A modern installation logs water temperature, chemistry, filter pressure, and pump runtime continuously, alerting a maintenance contact when a reading drifts out of band. That log satisfies health department record-keeping and gives the supervising rav evidence the system behaved as specified.

Getting the Review Right

The most common project failure is engaging the halachic authority after the mechanical drawings are complete. By then the pipe routing is fixed and changes cost real money. Bring the supervising rav in at schematic stage and treat the answers as design inputs on equal footing with the health code. The same logic applies to any product seeking approval, as described in halachic certification for products.

Engineering Support for a Mikvah Project

Projects House works with US communities and institutions on the technical side of these builds: control system design, heating and filtration engineering, sensing and monitoring, and the documentation that keeps inspectors and supervising authorities aligned. Describe the project through our contact form.