Tank Capacity and Runtime FAQ: The Arithmetic of a Claim

Runtime is a division, and a claim that hides the divisor will be tested by a customer in a dry room. These questions cover capacity, output, the ambient condition and how to publish a table that survives a review.

Why does the runtime claim fail in winter?

Because the unit runs at a higher output when the room is dry, and the advertised runtime was calculated at the lowest setting. Winter rooms are dry, so the customer runs the unit harder and the tank empties sooner. The claim is not false at the setting it describes, and it is misleading at the setting the customer uses. A table of settings with output and runtime removes the gap, because the customer can see which row applies to their room.

What is usable capacity?

The volume up to the maximum fill line, not to the brim. A tank filled above the line can spill when moved or overflow when the valve closes late, so the line exists for a reason. Publish the capacity at the line and mark it clearly on the tank, because a customer who measures the tank and finds less will feel misled even though the design is correct.

How is output measured?

In millilitres per hour at a stated ambient temperature and humidity, at each fan setting, with the unit in steady state. A measurement taken in the first hour includes the warm-up and the initial surge, and a measurement at a moderate humidity does not reflect a dry room. Report the condition with the number, because an output figure without it cannot be compared with another unit or with a customer’s experience.

Why does the room size matter?

Because the same output raises the humidity quickly in a small room and slowly in a large one, so the unit runs longer at high output in a large room. A runtime claim that does not state a room size describes a condition the customer may not have. Give the room size and the starting humidity the claim refers to, and let the customer match their own room.

What should the table contain?

Setting, output, runtime and a note on when to use it. Add a row for the automatic mode, because the control decides the output and the customer experiences the control. A table with four rows costs a few lines in the manual and a small block on the shop page, and it replaces the single number that creates the complaint.

Does the control strategy change the runtime?

Yes. A unit that ramps to maximum whenever the humidity is below target will use the tank faster than one that runs a lower setting for longer, even though both deliver similar water over a day. The control logic is part of the runtime claim, and it should be described in the manual in plain words. A control that is efficient is a better product, and a control that is explained is a better claim.

How many refills should a customer expect?

Say it. In a dry room at high output, a small tank may need a refill during the night, and a customer who knows will plan for it or buy a larger model. A brand that hides the refill frequency gets a review about a small tank; one that states it gets a customer who chose the product for the right room.

What about noise at high output?

High output usually means higher fan speed and more noise, so the runtime claim and the noise claim are linked. Publish the sound pressure at each setting alongside the output, and the customer can see the trade. A unit that is quiet at low output and loud at high output is normal; a table that shows both is honest.

What belongs in the specification?

The capacity at the fill line, the output per setting with the ambient condition, the runtime per setting with the room assumption, the control behaviour, the refill expectation and the noise per setting. Add a measurement report at the stated conditions. A specification that states a runtime and not its divisor has described a hope.

Consider publishing the runtime as a night rather than as hours. A customer thinks in nights, and a statement that the tank covers one night in a normal room and half a night in a dry one is more useful than a number of hours. The translation from hours to nights is simple and it is the unit the customer uses when deciding whether to buy.

Check the low-water behaviour. A unit that runs dry and continues to run can damage the transducer, and a cutoff that stops the mist but leaves the fan on will confuse a customer who hears the fan and sees no mist. Describe the behaviour in the manual, because a runtime claim implies a tank that empties, and the customer needs to know what happens next.

If the tank is small, sell the refill as part of the design rather than as a limitation. A wide opening, a handle and a clear line make a refill a minute, and a customer who can refill easily will tolerate a shorter runtime. The same tank with a narrow neck produces a complaint about size.

Measure the runtime with the lid and the demister fitted, because accessories change the airflow and the output. A measurement on a bare unit can be several percent optimistic, and the customer uses the unit with everything in place.

Give the customer a simple way to estimate their own runtime: divide the tank volume by the output of the setting they use, and compare with the hours they sleep. A short worked example in the manual does more than a table alone, because it shows the arithmetic with numbers the customer recognises.

Be careful with the phrase continuous operation. A unit that cycles on and off uses less water than one that runs continuously at the same setting, and the runtime depends on the cycle. State whether the figure assumes continuous operation or the unit’s own control behaviour.

Check the tank for a maximum line that is easy to see in dim light. A line that is only visible in daylight will be exceeded at night, which reduces the effective capacity and can cause a spill. A moulded mark or a coloured line is a small tooling change with a direct effect on the claim.

Finally, review the table when the fan or the transducer changes. A new component can shift the output by a few percent, which is enough to make a published runtime optimistic. The table is a specification and should be revised with the hardware.

Ask the support team how they answer the runtime question today. If the answer is a range of hours with a caveat, the manual is already behind the practice, and the table simply writes down what the team knows. The team’s script is a useful draft for the published claim.

Compare the runtime at each setting with the noise at the same setting, and publish the pair. A customer choosing between a quiet night and a full tank is making the trade the product actually offers, and a table that shows both is more useful than two separate claims.