Match the unit to its record
Use the site asset ID and location to connect the visit with the correct equipment. If a remote component is part of the agreed coverage, make that relationship clear.
RESOURCE · RECORDS & VISIT PLANNING
Critical Cooling Maintenance Checklist for Facility Teams
Use this checklist to judge whether a cooling visit produced a useful result. It connects the equipment covered, work completed, findings and follow-up, so facilities teams can track critical-cooling maintenance without mistaking a ticked box for a resolved issue.
Describe the issue in your own words. Start with the information you have.
Critical cooling
NYC & Northern NJ
- Covered assetsIdentify the equipment in the plan
- Completed tasksRecord applicable care and findings
- Open itemsAssign repair and follow-up decisions
AT A GLANCE
A useful maintenance record answers four questions
Which asset was serviced, what work was completed, what did the technician find, and what happens next? Those four answers make a visit traceable. The technical task list still comes from the actual CRAC, CRAH or other cooling system; this owner checklist helps you evaluate the record and follow-up.
01 · PRACTICAL GUIDANCE
Before the visit: make the asset list usable
A small amount of preparation prevents gaps in coverage.
Flag the current problem
An active fault or recurring alarm belongs in the visit discussion. Label it as a problem needing attention rather than allowing it to disappear inside a routine maintenance request.
02 · PRACTICAL GUIDANCE
After the visit: separate actions from observations
The report should say what happened, not only what was intended.
Completed work
Look for tasks actually performed on the identified equipment. A planned task that could not be completed should remain visible with its reason and required next action.
Findings that need a decision
A condition report, repair recommendation and immediate site concern are different outcomes. The record should make the distinction clear enough for the right person to act.
03 · PRACTICAL GUIDANCE
Before closing the record: assign the next step
Unowned findings can recur from visit to visit.
Name the follow-up owner
A repair, missing document or third-party issue needs a responsible contact. Record whether it was approved, deferred or sent for further investigation.
Check repeated findings
Compare the current report with earlier visits. A recurring condition deserves a clear explanation of what has changed and which action remains outstanding.
Read a maintenance report as a chain of evidence
Start with one asset and follow the record from task to finding to next action. A completed maintenance task says what was done. An observation says what was seen. A diagnosis explains the cause of a problem. These are different kinds of information, and a useful report keeps them distinguishable.
Consider a hypothetical report that says drainage was inspected and evidence of a previous leak was found. That does not necessarily establish an active leak or a diagnosed failed component. The useful follow-up identifies whether the source was investigated, whether a repair is recommended and what remains unresolved. The owner can then act on the finding without converting an observation into an assumed failure.
A finding is stronger when the operating condition is recorded
Two maintenance visits can encounter different room loads, equipment states or building services. A difference between their observations is easier to interpret when that context is available. Otherwise a later reviewer may assume that an apparent improvement or deterioration occurred under identical conditions.
The owner does not need a large technical dataset for every task. The useful record explains the condition relevant to the finding and any limitation that affects its meaning. This helps a future service team compare like with like and decide whether a change deserves further investigation.
Treat skipped and incomplete tasks as information
A blank checkbox is ambiguous. It may mean the task did not apply, could not be completed, was deferred or was missed. Each state has a different consequence. A non-applicable task can close with an explanation; a deferred task needs a next step and a reason it remains open.
Use the checklist to ask for that distinction, not to judge the technician by the number of checked boxes. Some work depends on an approved operating condition or access to connected equipment. If the condition was unavailable, the report should say which check remains unperformed. That prevents a limited visit from being read later as proof that the entire system was examined.
Compare records without losing the equipment context
When a finding reappears, compare the asset, symptom and prior action. The same alarm wording on two different units may not have the same cause. A previously repaired issue can also differ from a new problem that looks similar to the person receiving the report. Keeping those distinctions visible makes the history useful for service decisions.
A hypothetical unit may have a recurring airflow complaint after routine care. The next question is whether the maintenance restored the relevant equipment condition and whether the complaint involves the room’s air path or another function. Repeating the same completed task without investigating the continuing symptom may not answer the owner’s question.
At review time, separate findings affecting current operation from those needing diagnosis and those suitable for planned work. Assign responsibility for the next step and retain the evidence that closes it. This checklist evaluates what happened during and after the visit. Use the separate agreement worksheet when the question is whether the task, repair or response was included in the contract.
COMMON QUESTIONS
Critical Cooling Maintenance Checklist questions
Is this a technician’s maintenance procedure?
No. It is an owner’s review checklist for service records. Equipment-specific procedures and intervals belong to the qualified service team and applicable manuals.
Should every unit have the same checklist?
No. CRAC, CRAH and other systems have different components and support systems. The record should reflect the installed equipment.
What should a report say when a task was not completed?
It should identify the task, why it could not be completed and the next action or decision needed. An unchecked item should not silently become completed work.
Does a maintenance report prove the room is redundant?
No. Redundancy is a separate system-level question involving load, available equipment and shared dependencies.
Should a report include a reason when an item is marked not applicable?
Yes, a short reason helps the owner distinguish an irrelevant task from an incomplete one. For example, a task may apply to a different cooling configuration. The record should remain tied to the actual asset so a later reviewer does not assume that a blank or non-applicable item was checked and found satisfactory.
How can we tell whether a recurring finding was resolved?
Look for a linked action and an account of the observed result, rather than the finding simply disappearing from the next report. A useful history identifies the repair or investigation performed, its date and any remaining limitation. If the same symptom returns, that record helps distinguish a repeat from a different problem.
RELATED GUIDES & SERVICES
Find the service for the work you need
FURTHER READING
Technical references
AIRPLEX MECHANICAL
Discuss Cooling Maintenance
Need a maintenance plan or help with a recurring finding? Contact Airplex with the room and equipment you want covered.