Recording Checks: jump to another article
Condition notes and corrective actions
A reading tells you a number is out of range. A condition note and a corrective action record what you actually saw and what you did about it — the difference between a bare data point and a usable maintenance record.
Condition noted
Toggle Condition noted on to describe what you observed — odor, tramp oil, residue, anything worth flagging about the fluid’s state. It’s a free-text field, shown directly on that check’s row in the machine’s history afterward.
Corrective action
If your organization has set up a Corrective Actions Library, you can pick what you did — for example, “Added concentrate” or “Added biocide” — from a row of options. Choosing one can pre-fill a cost estimate from the library; you can edit that estimate for this specific event, or leave it blank to use the library’s default.
When KeepSpec asks you to add one
Saving a reading that’s out of spec, with no condition note and no corrective action selected, prompts you: “Do you want to add a corrective action or condition note?” You can add one right there, or choose Save as-is and note it separately later. KeepSpec only asks once per save — if you’ve already noted something, it doesn’t ask again.