Whether a settling basin actually removes the floc it is meant to remove comes down to a surprisingly simple number: how much flow it handles for each unit of its water surface. That number is the overflow rate, also called the surface loading rate, and it decides which particles have time to settle out and which get carried over. This guide explains what overflow rate is, why it, rather than tank volume alone, governs settling, how it relates to a particle's settling velocity, and how the flow-to-basin ratio is watched in SCADA to keep settled-water turbidity in specification.
Overflow Rate in one line: The overflow rate, or surface loading rate, of a sedimentation basin is the flow divided by the basin's surface area, usually expressed as a volume per unit area per unit time such as gallons per minute per square foot. It represents the rate at which water rises to the outlet, and any particle whose downward settling velocity is greater than the overflow rate is captured, while slower-settling particles are carried over. Because of this, the overflow rate, not simply the tank volume or detention time, is the key parameter that determines whether floc settles out and the settled water stays clear.
Overflow rate is defined as the plant flow through a basin divided by the basin's plan surface area, and it has the units of a velocity - a flow per area is dimensionally the same as a speed. That is not a coincidence. The overflow rate can be pictured as the upward velocity at which water is effectively moving toward the outlet as it fills the basin from below over its whole surface. Comparing that upward velocity to how fast a particle falls is what tells you whether the particle reaches the bottom before it reaches the outlet.
This is why overflow rate, rather than volume, is the governing design and operating parameter. It is intuitive to think a bigger tank settles better, but what matters for a given particle is the surface area presented for settling relative to the flow, not the depth of water above. Classic settling theory captures this: for an ideal basin the removal of discrete particles depends on the surface loading rate and the particle's settling velocity, and is independent of depth. So two basins with very different volumes but the same overflow rate will, in the ideal case, capture the same particles.
The practical consequence is that pushing more flow through a basin raises its overflow rate and worsens settling, while the surface area is fixed. Every basin therefore has a loading beyond which the faster water begins to carry over floc that would otherwise have settled, and settled-water turbidity climbs. Sizing a clarifier is largely a matter of choosing enough surface area that the design flow gives an overflow rate low enough to capture the floc the process produces, and operating it is largely a matter of not exceeding that loading.
The link between overflow rate and settling is a direct comparison of two velocities. Each particle in the flocculated water has a settling velocity, the speed at which it falls through the water under gravity, which depends on its size and density; large, dense floc settles fast, while fine pinpoint floc settles slowly. If a particle's settling velocity exceeds the basin's overflow rate, it settles to the floor before the water carries it to the outlet, and it is removed. If its settling velocity is less than the overflow rate, the water reaches the outlet first and the particle escapes.
This comparison explains why upstream coagulation and flocculation matter so much to a settling basin. Those steps exist to grow floc that is large and dense, and therefore fast-settling, precisely so that its settling velocity comfortably exceeds the overflow rate. When flocculation is poor and only small, slow floc is produced, that floc's settling velocity may fall below the overflow rate and it will carry over no matter how the basin is run, which is why settling problems often trace back to coagulation rather than to the basin itself.
It also explains the role of detention time as a companion figure. Detention time, the average time water spends in the basin, is the volume divided by the flow, and while overflow rate governs whether a given particle can be captured, adequate detention gives the floc the quiet residence it needs to actually reach the floor and to keep the flow calm and non-turbulent. In practice engineers watch both, but it is the overflow rate that sets the fundamental limit on which particles can settle at all.
Because overflow rate is simply flow over a fixed area, the way to watch it in real time is to watch the flow going to each basin, and this is a natural SCADA measurement. With the plant flow and the number of basins in service known, the control system can express the current loading as flow per basin, and since the surface area is fixed the operator effectively has the overflow rate in front of them. Trending that against settled-water turbidity shows directly how the basin is coping with its present loading.
A platform such as Merobix can bring flow, basins in service, and settled-water turbidity together so the flow-to-basin relationship is visible and can be alarmed. This matters most during high-demand periods and when basins are taken offline for cleaning, since either can push the loading on the remaining basins up. If turbidity begins to rise as the loading climbs, the operator can respond by returning a basin to service, shedding flow, or adjusting coagulation, catching the carryover before it reaches and blinds the filters downstream.
For plants that run with limited staff or across remote sites, surfacing this through cloud SCADA turns overflow rate from a design number in a manual into a live operating indicator. An unexpected flow surge, or a basin left out of service too long, shows up as a rising loading and a turbidity trend heading the wrong way, and a notification can prompt action before finished-water quality is affected. Keeping the flow-to-basin ratio and settled turbidity trended together is one of the clearest ways to hold sedimentation performance in specification day to day.
Overflow rate is the flow divided by the basin surface area and behaves like a velocity, and it governs whether a given particle can settle, since any particle settling faster than the overflow rate is captured. Detention time is the basin volume divided by the flow and is the average time water spends in the basin, giving floc the quiet residence it needs to reach the floor. Overflow rate sets the fundamental limit on which particles settle, while detention time ensures they have time and calm conditions to do so.
For settling, what matters is the surface area presented relative to the flow, because whether a particle is captured depends on comparing the water's upward velocity toward the outlet with the particle's downward settling velocity, and that upward velocity is the flow divided by the surface area. Classic settling theory shows that ideal discrete-particle removal depends on surface loading rate and settling velocity and is independent of depth. So two basins of different volume but equal overflow rate capture the same particles in the ideal case.
If the overflow rate rises too high, the effective upward velocity toward the outlet exceeds the settling velocity of some of the floc, so that floc is carried over instead of settling, and settled-water turbidity climbs. This can happen when flow surges or when basins are taken out of service, concentrating the flow on the remaining ones. Operators respond by returning a basin to service, reducing flow, or improving coagulation to produce faster-settling floc.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.