Before an operator sets how much coagulant a water plant should feed, they need to know what dose the current raw water actually wants, and the oldest and most trusted way to find out is to try several doses side by side on the bench. That experiment is the jar test. It reproduces coagulation, flocculation, and settling in a row of small beakers so the operator can watch which dose and pH produce the best floc and the clearest settled water. This guide explains what a jar test is, how it is run, how its result becomes a SCADA dose setpoint, and how online instruments increasingly automate what the jar test has traditionally done by hand.
Jar Test in one line: A jar test is a bench-scale experiment in which several samples of the same raw water are dosed with different amounts of coagulant, and sometimes different pH values, then rapidly mixed, slowly flocculated, and allowed to settle, so the operator can see which condition gives the best floc and the lowest settled turbidity. The dose and pH that produce the clearest settled water are taken as the optimum and used to set the plant's coagulant feed and pH setpoints. It is the classic method for coagulant dose optimisation, now increasingly supplemented by online streaming current and turbidity monitors.
A jar test recreates the plant's coagulation train in miniature. A gang stirrer holds several identical jars, each filled with the same raw water, and a paddle in every jar can be run at a set speed. The operator doses each jar with a different amount of coagulant, commonly alum or a ferric salt, spanning a range around the dose they expect to need. Some tests also vary pH between jars, since coagulation works best within a certain pH window and the two variables interact. Running the jars side by side means every dose is tested against exactly the same water at the same time.
The stirring sequence mimics the full process. A brief burst of fast mixing stands in for the flash mix, dispersing the coagulant and destabilising the particles. Then the paddles slow to a gentle speed for a longer period, standing in for flocculation, during which the operator can literally watch floc form and grow in each jar. Finally the stirrers stop and the jars are left to stand, standing in for sedimentation, so the floc settles and leaves clearer water above. This compressed but faithful re-enactment is what makes the jar test predictive of how the real plant will behave at each dose.
The result is read from what the jars show. The operator looks for the jar with the largest, fastest-settling floc and, above all, the clearest supernatant, judged by eye and confirmed by measuring the settled turbidity of the water drawn from each jar. The dose and pH of the jar that gives the lowest settled turbidity, without over-dosing, is taken as the optimum. Because the jars were all treated identically apart from the variable under study, the comparison isolates the effect of dose and pH cleanly.
The jar test is not an academic exercise; its output is an operating decision. Once the optimum dose and pH are identified, the operator translates the bench dose into a plant feed rate and enters it as the coagulant setpoint, and adjusts the pH control target if the test showed a better result at a different pH. The plant then feeds coagulant flow-paced to that setpoint, so the concentration the jar test found stays constant as throughput changes. In this way a small experiment on the bench directly determines how the full-scale process is dosed.
Raw water is not static, so jar testing is repeated as conditions change. A storm event, a seasonal shift, a change in source, or a swing in raw turbidity or temperature can all move the optimum dose, and a jar test is the way operators confirm the new best dose before committing the plant to it. Running one keeps the dose matched to what the water currently needs rather than to what it needed last week, which avoids both under-dosing that lets turbidity through and over-dosing that wastes chemical and can foul downstream filters.
It is worth being clear about the jar test's limits. It is a snapshot of one grab sample at one moment, it takes time to run, and its floc judgement carries some operator subjectivity. Those limits are exactly why plants pair jar testing with continuous online instruments and why the setpoint it produces is treated as a starting point to be trimmed against live plant performance, not a number to be locked in and forgotten.
The jar test answers a question continuously in the plant that the bench can only answer intermittently: is the coagulant dose right for the water flowing right now. Two online instruments increasingly do that job. A streaming current monitor responds to the same particle-charge destabilisation the coagulant is meant to achieve, giving a continuous signal that tracks whether the dose is neutralising the charge, so it can be used to trim coagulant feed in real time. Online turbidity analysers on the settled and finished water report the actual clarity being produced, closing the loop on whether the current dose is working.
Feeding these signals into a SCADA platform such as Merobix lets the plant hold coagulation on target between jar tests and react far faster than a batch of beakers can. A streaming current monitor's reading can be trended against coagulant feed and settled turbidity so an operator, or an automatic control scheme, keeps the dose in the band the jar test identified, adjusting continuously as raw water shifts. In effect the online instruments carry out, moment to moment, the comparison the jar test makes occasionally, and SCADA is where their signals are combined and acted on.
The two approaches are complementary rather than competing. The jar test remains the reference that establishes what good looks like for a given water and calibrates operator judgement, especially when a new source or an unusual event calls for a fresh look. The online monitors then hold the plant near that optimum continuously and flag when it drifts. Together they let a plant set its dose from solid bench evidence and then keep it there automatically, which is both more responsive and less labour-intensive than jar testing alone.
After the mixing and settling sequence, you compare the jars and look for the one with the largest, fastest-settling floc and, most importantly, the clearest water above the settled solids. Measuring the settled turbidity of the water drawn from each jar confirms the visual judgement, and the dose and pH of the jar with the lowest settled turbidity, without over-dosing, is taken as the optimum. Because all jars were treated identically apart from the variable being studied, the comparison isolates the effect of dose and pH.
A jar test should be run whenever the raw water conditions change enough to move the optimum coagulant dose, such as after a storm, a seasonal shift, a change of source, or a noticeable swing in raw turbidity or temperature. Some plants also run routine periodic tests as a check even when conditions seem stable. Between tests, online streaming current and turbidity monitors help hold the dose on target and signal when a fresh jar test is warranted.
Online streaming current and turbidity monitors can carry out continuously what the jar test does occasionally, trimming and confirming the coagulant dose in real time, which the bench test cannot do. In practice they supplement rather than fully replace the jar test, which remains the reference that establishes the right dose and pH for a given water and calibrates operator judgement. Plants typically use the jar test to set the target and online monitors to hold the plant near it.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.