Chiller Refrigerant Purge Unit Runtime Log
Track centrifugal chiller purge unit runtime, starts, alarms, and operating conditions in one log so you can spot non-condensable buildup and refrigerant-side leakage early.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Commercial Real Estate · Hospitals And Healthcare · Universities And Campuses · Manufacturing Facilities
Overview
The Chiller Refrigerant Purge Unit Runtime Log is an inspection and audit template for centrifugal chillers that use a purge unit to remove non-condensables from the refrigerant circuit. It captures the inspection date and time, chiller identification, operating mode, purge runtime, purge starts, alarm or fault status, service indicator condition, and the system conditions that help explain why purge activity changed.
Use this template when you need a repeatable record of purge behavior over time, especially on chillers that show rising condenser pressure, unstable performance, or suspected refrigerant-side leakage. The trend fields are designed to help maintenance staff distinguish normal purge activity from a developing problem. It is also useful after refrigerant service, during seasonal startup, after major load swings, or when a BAS trend suggests the machine is working harder than expected.
Do not use this log as a substitute for a refrigerant leak inspection, a repair record, or a lockout-tagout procedure. It is not intended for absorption chillers, packaged rooftop units, or systems without a purge device. If the purge unit is offline for maintenance, the log should note that condition and route the issue to the appropriate corrective action process. The value of the template is in consistent trend capture: the same fields, recorded the same way, so the team can spot non-condensable accumulation early and act before efficiency loss or equipment damage escalates.
Standards & compliance context
- This template supports preventive maintenance documentation commonly used in facilities programs aligned with OSHA general industry expectations and ANSI/ASSP safety management practices.
- If the log leads to refrigerant handling, leak repair, or component isolation, follow the applicable EPA refrigerant management requirements and your site lockout-tagout procedure before work begins.
- For facilities with formal maintenance systems, the log can support ISO 9001-style records of inspection, non-conformance tracking, and corrective action follow-up.
- Where chiller rooms are part of a broader life-safety or mechanical compliance program, align escalation and access controls with applicable NFPA and local Authority Having Jurisdiction requirements.
- Always defer to the chiller manufacturer's maintenance instructions for acceptable purge behavior, alarm interpretation, and service intervals.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
What's inside this template
Inspection Details
This section establishes the who, what, when, and operating context so every reading can be tied to a specific chiller and reference period.
- Inspection date and time
-
Chiller identification
Record chiller tag number, asset ID, or equipment name.
- Inspector name
- Operating mode
-
Reference log period
Identify the shift, day, or date range covered by this log entry.
Purge Unit Runtime
This section captures the purge device's direct operating behavior, which is the clearest signal for changing non-condensable load or purge system trouble.
-
Purge unit runtime since last log
Enter total purge unit runtime since the previous inspection entry.
-
Purge unit starts since last log
Count each purge cycle or start event since the previous entry.
- Purge unit currently running
- Purge unit alarm or fault present
- Purge unit service indicator condition
System Conditions
This section records the chiller and room conditions that help explain whether purge activity is normal, load-driven, or a sign of a developing defect.
- Condenser pressure
- Evaporator pressure
- Leaving chilled water temperature
- Ambient machine room condition
-
Recent load change observed
Indicate whether a significant load swing occurred since the last entry.
Non-Condensable Trend Indicators
This section turns raw readings into a maintenance decision by flagging whether the pattern suggests accumulation, leakage, or another abnormal trend.
- Purge frequency trending upward
- Purge runtime trending upward
- Evidence of refrigerant-side leakage suspected
- Observed non-condensable accumulation indicators
Follow-Up and Documentation
This section closes the loop by assigning corrective action, setting the next review date, and preserving the inspection record for later comparison.
- Corrective action required
-
Corrective action details
Describe any leak check, service action, purge unit repair, or escalation needed.
-
Next inspection date
Schedule the next purge runtime log entry or follow-up inspection.
- Inspector signature
How to use this template
- 1. Enter the inspection date, chiller ID, operating mode, and reference log period before you review any readings so the entry can be compared to the correct prior interval.
- 2. Record purge unit runtime, purge starts, current running status, alarm or fault condition, and service indicator state directly from the purge controller or maintenance display.
- 3. Capture condenser pressure, evaporator pressure, leaving chilled water temperature, machine room ambient condition, and any recent load change observed during the same visit.
- 4. Mark the trend indicators for rising purge frequency, rising runtime, suspected refrigerant-side leakage, or other non-condensable accumulation signs based on the current log and prior entries.
- 5. Document the corrective action required, add specific follow-up details such as leak check, purge service, or escalation to HVAC service, and assign the next inspection date.
- 6. Sign the log after verifying the entry is complete and route any critical findings through your maintenance or work order process.
Best practices
- Record the purge unit runtime and starts from the same source each time so the trend is comparable across inspections.
- Note the operating mode and recent load change because purge activity often shifts when the chiller is staging, starting, or recovering from a demand swing.
- Treat repeated increases in purge runtime as a trend to investigate, not as a one-time anomaly to dismiss.
- Photograph or attach controller screens for alarms, faults, and service indicators when the reading is abnormal or likely to be questioned later.
- Keep the machine room ambient condition in the log because poor ventilation or unusually warm conditions can affect purge behavior and interpretation.
- Separate suspected refrigerant-side leakage from confirmed leakage in the notes so the log stays factual and defensible.
- Use the corrective action field to assign an owner and due date, not just a vague note to 'monitor.'
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What is this log used for?
This template records purge unit runtime, starts, alarms, and related chiller conditions so you can trend non-condensable accumulation over time. It helps maintenance teams spot refrigerant-side leakage, air ingress, or purge system issues before they become performance or reliability problems. It is a monitoring log, not a repair procedure.
How often should the purge unit runtime be logged?
Use it at a cadence that matches the chiller's operating pattern, commonly daily, weekly, or after major load changes and service events. Facilities with frequent starts, unstable loads, or known leakage concerns may log it more often. The key is consistency so trends in runtime and starts are meaningful.
Who should complete this template?
It is typically completed by a qualified HVAC technician, building engineer, or maintenance supervisor familiar with centrifugal chillers and purge systems. The person logging the data should be able to read pressures, recognize alarm conditions, and note abnormal operating trends. If the log drives corrective action, a supervisor or licensed contractor may need to review it.
Does this template satisfy any OSHA or code requirement?
This template supports preventive maintenance and documentation practices, but it is not a standalone compliance form. It can help demonstrate good maintenance control under general industry safety programs and support facility procedures aligned with ASHRAE, ANSI, and manufacturer guidance. If refrigerant handling or lockout-tagout is involved, use the applicable OSHA and EPA-required procedures separately.
What are the most common mistakes when using a purge unit log?
Common mistakes include logging runtime without the related pressures or load conditions, which makes the trend hard to interpret. Another pitfall is treating a single high reading as proof of leakage instead of looking for repeated increases over time. Teams also sometimes skip documenting alarms, service indicators, or corrective actions, which weakens follow-up.
Can this be customized for different chiller brands or BAS systems?
Yes. You can add manufacturer-specific alarm names, purge controller display fields, refrigerant type, setpoints, or BAS trend references. Many teams also add fields for oil return, condenser water temperature, or service ticket numbers so the log matches their maintenance workflow.
How does this compare with ad-hoc notes in a maintenance ticket?
Ad-hoc notes usually capture only the problem of the day, while this template creates a repeatable trend record. That makes it easier to see whether purge activity is increasing, whether a fault repeats, and whether system conditions changed before the issue appeared. It also gives the next technician a clearer baseline.
What should trigger follow-up after a log entry?
Follow-up is usually warranted when purge runtime or starts trend upward, alarms recur, or the log shows evidence of non-condensable accumulation or suspected refrigerant-side leakage. A sudden change in condenser pressure, evaporator pressure, or machine room conditions can also justify investigation. The template includes a corrective action section so the response is documented, not just observed.
Related templates
Go deeper on the topic
-
A daily huddle is a brief (10–15 minute) standing meeting held at the start of a shift or workday to align the team on priorities, surface issues, and...
-
A deskless worker is any employee whose job happens without a desk, a company laptop, or a fixed workstation. They're roughly 80% of the global workforce —...
-
A frontline employee app is a phone-first application that gives hourly, field, and deskless workers access to their schedule, pay, announcements, training,...
-
A frontline worker is any employee whose job happens away from a desk — on a production floor, in a patient room, behind a store counter, in a customer's...
-
Spring '26 brings AI Course Creation, Power BI-connected AI Agents, and smarter content governance to MangoApps. See what's new across the platform.
-
Integrated digital workplace task management tips to keep work moving, reduce stalls, and turn conversations into accountable action.
-
When scheduling tools lack leave and budget data, costly errors follow. See how integrated workforce management closes the context gap.
-
Data governance for AI: Build a trusted knowledge base with MangoApps to deliver accurate, permission-aware enterprise AI answers.
Ready to use this template?
Get started with MangoApps and use Chiller Refrigerant Purge Unit Runtime Log with your team — pricing built for small business.
