“Dry complete” should be an evidence-backed state.

This is an operating-system discussion, not a substitute for technical standards or professional judgment. The goal is to show how documentation can make the basis for a drying decision visible and reviewable.

Repeatable monitoring points create continuity

If a reading cannot be connected to the same defined location over time, the trend becomes harder to interpret operationally. A monitoring point should have a stable identity that survives multiple visits and multiple readings.

Keep point identity stable over the drying cycle

The job record should make it clear which room, assembly or location the point belongs to and preserve the relevant material, meter or mode context used by the workflow. Changing labels midstream can make later comparison unreliable.

Capture method and context with the reading

A number by itself is not the whole record. The system should retain the context needed by the operation to understand the reading: point identity, date/time, method or device context where appropriate, environmental context used by the workflow, and the technician or source of the record.

Define the goal or control method

The operating workflow needs a visible basis for deciding whether monitoring is complete. That may be a defined dry standard, control method or other reviewed target appropriate to the job. Ordo should not invent that technical basis; the system should preserve the basis the qualified operation actually uses.

Daily readings should form a traceable series

The value of daily documentation is that it shows change over time. Each new record should append to the point history rather than overwrite the previous reading. That allows the operator to review direction, gaps and context.

Equipment and HVAC state belong in the operational record

When equipment placement, removal or building conditions matter to the workflow, they should remain visible alongside the monitoring history. The objective is not to make an automatic technical conclusion. It is to preserve what was happening around the readings.

Compare the trend with the defined target

The system can assist by organizing readings, highlighting missing records and showing the relationship to the defined goal. The final technical interpretation remains human-controlled where judgment is required.

Final readings should support the transition

If the workflow marks a point or job as complete, the supporting record should be available with it. A completion state that cannot point back to its evidence is difficult to audit later.

Exceptions need a reviewed path

Real jobs do not always follow the normal sequence. If a point cannot satisfy the normal rule, the workflow should require an explicit exception with reason, reviewer and disposition rather than silently changing the status.

Do not backfill missing readings as though they happened

Missing documentation should remain missing unless there is a legitimate later record explaining what is known. Reconstructing a reading after the fact can blur the difference between evidence captured in the field and information created later.

Where automation can help

Automation can identify missing point-day records, assemble the monitoring history, surface exceptions and prepare documentation. It should not manufacture field evidence or replace qualified judgment.