Approve the test script before the day
Original diagram. Not a site record.
A script is a set of steps with an expected result, a stop, and a revision, approved before the window. A script written during the window to match what the plant did is a diary. Diaries do not support a certificate.
The expected result comes from the specification then in force, or from a limit the owner wrote and can point to. It does not come from the first calm hour. If the expected result cell is blank, do not start. Blank is not "use engineering judgment on the night." Judgment on the night is how a pass line moves.
Say who witnesses and who may accept a document instead. Those are different verbs. A letter that a setting was adjusted is not a witnessed changeover. If you did not witness every line, say what was sampled. "We saw enough" is not a sampling rule.
Stops belong in the script, not in someone's memory. The stop is the first safe state, not a root cause. You will not know the cause in the first minute. Writing one there is how the report inherits a guess.
From Finish a Liquid Cooling Verification, Tristan, Data Center Field Guides. No store link until the Kindle edition is listed.
Related: One system at a time.
Master the Complete Protocol: Design and Build a Liquid Load Bank for NVL72 Racks
A Field Guide to Interface Boundaries, P&ID Hydraulics, Thermal Envelopes, and Acceptance Sheets
Stop relying on contractor spreadsheets and vendor promises. This field guide provides the complete, auditable verification binder—including acceptance thresholds, physical equations, inspection checklists, and signed refusal templates.