Sump & ejector pump test log

Log

Somebody lifted the float, watched the pump run, and wrote down what happened.

The test is simple; remembering it happened is not

Lift the float, watch it run, watch it stop, check the water actually went where it should. Two minutes of work, and the only hard part is having a dated record six months later when a basement floods and somebody asks when it was last tested.

The stop matters as much as the start

A pump that starts and does not stop burns out, and a check valve that does not hold sends the same water round again. Both are on the list, because both are the failure people find out about at the worst moment.

How often is your decision

CompliMaint states no test frequency. Many operators test far more often before a wet season than any minimum would suggest, for the obvious reason.

Kept alongside: Water storage tank log · Storm preparedness log · Maintenance request log

A dated record of sump and ejector pump tests, kept per pump on your device. CompliMaint states no test frequency, publishes no run time or flow figure, and makes no determination that any pump is adequate for the water it has to move. Everything runs on your device.

Questions people ask

How often should a sump pump be tested?
CompliMaint states no frequency. It is your decision — many people test far more often before a wet season, because a pump that fails is a flooded basement.
Does it check the pump is big enough?
No. It publishes no flow or capacity figure and makes no adequacy determination. Sizing is a question for whoever installed it.
Can I record a backup pump or battery?
Yes — both the backup arrangement on the equipment record and a checklist item for operating it, marked N/A where none is fitted.
What if the alarm did not sound?
Record it as a finding; the engine will ask you to raise an action from it. What to do about it is your call.
Does it leave the device?
No. Pumps, tests and notes stay in this browser.