Make-up air low-limit sensor and damper winter startup record

Direct answer

Before winter startup, a make-up air unit record should identify the unit tag, location, serving area, equipment type, heating source, outside-air path, discharge-air sensor tag, low-limit or freezestat point name, alarm point, outside-air damper tag, actuator model or signal type where visible, BAS graphic, trend range, startup boundary, exceptions, and release decision. The record should show the sensor and damper as installed, not only as lines on the controls submittal.

The minimum useful record has three kinds of evidence. First, it has photos: the discharge-air sensor or sensing tube, the sensor wiring or module, the damper blades, the actuator, the linkage or direct shaft connection, labels, access doors, and any reset or HMI screen used by the project. Second, it has controls evidence: point names, setpoint or alarm threshold from the approved sequence, alarm delay where the controller exposes it, alarm state, reset state, fan command, heating command, damper command, and damper feedback if feedback exists. Third, it has release notes: who reviewed the packet, what could not be verified, what was corrected, and what condition would hold the unit from winter operation.

Do not reduce this record to the sentence "MUA checked." Make-up air failures usually hide in the boundary between mechanical installation and controls checkout: a discharge sensor mounted in the wrong airstream, a low-limit alarm that exists on the controller but not in the BAS alarm list, an outside-air damper that opens but does not close fully, an actuator installed with the wrong spring-return direction, or a reset button that cannot be reached after the first cold trip. The winter-startup packet should make those conditions visible before the building depends on the unit.

Why this record matters in the first cold week

A make-up air unit is often judged by whether it starts, heats, and moves air. That is not enough for winter startup. The field risk is that the unit can satisfy a short start command on a mild day while still being unable to protect the building, coil, kitchen, loading area, vestibule, or process space when outside air drops and exhaust loads change. The low-limit sensor and outside-air damper are the parts of the system that prove the unit can recognize cold discharge air and control the air path that creates it.

The manufacturer sources reviewed for this article are consistent on the main documentation themes. Greenheck controller material describes supply-air low-limit alarm behavior, sensor alarms, alarm outputs, alarm review, and a supply discharge temperature sensor. CaptiveAire MUA manuals describe discharge temperature control, freezestat setpoints, freezestat timer behavior, freezestat alarms, HMI reset, and checking discharge sensor values. AAON material places freeze stats, low-limit control, preheat discharge supply-air temperature sensors, discharge temperature terminals, and alarm relay outputs in the unit documentation. Trane and Johnson Controls sensor instructions show that discharge-air sensors are physical assemblies with probe, tube, insulation, hole, bracket, wiring, and vibration details. Honeywell, Belimo, and Johnson Controls actuator documents show that damper actuator direction, shaft engagement, spring return, mounting brackets, service clearance, and proof of full travel are not paperwork details.

That evidence matters because winter problems are rarely isolated. A low-limit alarm can stop the supply fan, shut the unit down, lock out heating, or create an alarm that operations must notice. A failed outside-air damper can overcool the discharge path, flood the unit with cold air, leave a kitchen short of replacement air, or defeat a startup sequence. A sensor placed where it reads a hot streak or a stagnant corner can make the controller appear correct while the actual discharge air is not. A good record does not promise that winter will be trouble-free; it gives the owner and contractor enough proof to know what was checked and what was not.

The record is also a coordination tool. Mechanical crews know the unit, duct, damper, access panels, gas or hydronic heat, filters, and curb conditions. Controls technicians know the BAS points, alarm routing, setpoints, overrides, and trend names. TAB or commissioning staff know the functional intent and whether the unit was tested under representative airflow. Operations knows whether the alarm will be seen after hours. Winter startup fails when these groups each document their own small piece and nobody ties the evidence together. The packet should make one shared decision possible: release, release with a written limitation, or hold.

Define the unit, boundary, and startup condition

Start the record with a precise boundary. Identify whether the packet covers one rooftop make-up air unit, one direct-fired heater, one indirect-fired unit, one compact unit, one kitchen replacement-air system, one DOAS-style unit serving a zone, one mixed-air section, or one unit with both outdoor-air and return-air paths. Use the same tag names found on drawings, submittals, BAS graphics, nameplates, and field labels. If the BAS calls the unit MAU-2 while the drawing calls it MUA-2 and the roof curb label says RTU-2, record the cross-reference instead of letting the mismatch remain unexplained.

Then define the startup condition. "Before winter startup" can mean different things on different projects. It may mean before owner occupancy, before the first heating-season enable, before gas heat is released, before kitchen exhaust is turned over, before water coils are exposed to freezing weather, before the BAS schedule is made automatic, or before a seasonal test after summer shutdown. The record should say exactly which condition is being released and which conditions remain outside the release. If the unit has been run in manual mode but not released to automatic schedule, say that. If heat was checked but low ambient conditions were not available, say that too.

The unit boundary should include the outside-air intake, intake screen or hood, damper section, actuator, linkage, filter bank, heat section, discharge-air sensor or sensing tube, fan status, discharge duct, BAS controller, alarm routing, and any reset point that matters to the low-limit sequence. It should also identify adjacent systems that can change the unit behavior: exhaust fan interlocks, building pressure controls, kitchen hood control panels, occupancy schedules, fire alarm shutdown, smoke control interfaces, freeze-protection kits, and heating-water or gas enable permissions.

A boundary statement prevents false confidence. A photo of the HMI may prove a freezestat setpoint but prove nothing about damper closure. A BAS trend may prove discharge temperature but not prove the sensor is in the intended location. A photo of an actuator may prove installation but not prove the alarm is mapped to operations. The record should make clear which evidence supports which part of the release.

Separate discharge-air low limit from freeze protection

Use the project language, but do not blur terms. A discharge-air low-limit alarm, a freezestat, a freeze-protection timer, a building freeze-protection option, a low-discharge-temperature cutout, a coil freeze-protection device, and a supply-temperature low-limit alarm can all appear in manufacturer literature or controls sequences. They are related, but they do not always protect the same asset or trigger the same response.

Greenheck controller references include a supply-air low-limit function that can disable the unit and activate an alarm after a preset delay when supply air falls below the low limit. Greenheck catalog and IOM material also discusses coil freeze protection, low-discharge-temperature cutout, building freeze protection, and freeze protection alarm notification in different product contexts. CaptiveAire manuals describe freezestat setpoints, timers, freezestat trips, checking discharge sensor values, and resetting through the HMI. AAON material references freeze-stat startup, low-limit control, preheat discharge supply-air temperature sensors, discharge temperature sensor terminals, and alarm relay output.

Those examples support a conservative documentation rule: record the name of the actual point and the actual sequence used by the project. If the BAS point is "SA Low Limit," do not call it a coil freeze stat unless the approved sequence and hardware say that. If the HMI uses "Freezestat," do not assume it protects every coil or every downstream branch unless the unit documentation and sequence say so. If the controller exposes an alarm delay, record it as the controller displays it, then tie it to the approved sequence instead of treating a factory default as a design value.

This distinction matters during turnover. Operations may respond differently to a supply-air low-limit alarm intended to protect occupied areas from cold discharge air than to a manual-reset freeze-protection device intended to protect water coils. Some events are alarm-only; some shut down the unit; some require manual reset; some clear after the cause is fixed; some route to a dry contact or BMS; some remain local at an HMI. The record should show which one exists on this unit.

Confirm the discharge-air sensor identity and location

The discharge-air sensor is the fact source for the low-limit decision. Treat it like a field-installed measurement point, not a hidden accessory. The record should show the sensor tag, controller input, wiring label, probe or sensing tube, duct location, distance from the unit or fan wall when available, relation to the heat section, relation to the discharge duct, access route, and whether the sensor sees the mixed discharge stream that the sequence expects.

Trane discharge-air sensing kit instructions show the physical nature of the assembly: sensing tubes, mounting brackets, insulation, knockout locations, discharge or supply duct covers, sensor module assembly, and secured installation details. Johnson Controls discharge-air sensor instructions show a probe mounted through a duct hole, secured with screws, with a caution about excessive vibration. Those documents are useful because they push the photo record beyond "sensor present." A useful packet should prove that the sensor is physically installed in the airstream that controls the alarm.

For a make-up air unit, location is not a minor detail. A sensor too close to a burner, heat exchanger, electric heat element, bypass path, or cabinet corner may not read the same air that reaches the occupied space. A sensor downstream of a mixing problem may see stratified air. A sensor installed before the intended heat source may report a different condition than the sequence expects. A sensor hanging loose in the cabinet may be exposed to vibration, radiant heat, service damage, water, or stagnant air. The record should call out these risks without pretending that the field team is redesigning the unit.

Photograph the sensor in context. A close photo of the label helps identify the part, but it does not prove location. A wide photo of the unit helps orientation, but it does not prove the sensor was connected. The packet should include both: a wide photo that shows the unit section or duct, a mid-range photo that shows the sensor or tube in place, and a close photo that shows tag, mounting, wiring, insulation, and access. If the sensor cannot be photographed because it is factory-concealed, capture the nearest access label, the controller point, the HMI value, and the manufacturer page or startup form that identifies the factory location.

Build the sensor photo set

A strong sensor photo set answers five questions. What is the sensor? Where is it? What is it connected to? Can it be serviced? Does the BAS or HMI value match the physical point? If the packet does not answer those questions, a later low-limit alarm will turn into a search project instead of a controlled response.

Start with the unit nameplate and field tag. Then photograph the sensor tag, access panel, discharge duct or cabinet wall, probe or sensing tube, screws, bracket, insulation, grommet or penetration, wiring path, junction box, terminal strip if safely visible, and controller input label. Do not remove covers or enter energized compartments solely for a photo. If a cover must remain closed, record that limitation and capture the label or HMI evidence that can be safely observed.

Include condition photos. Look for loose sensor bodies, missing screws, unsealed penetrations, crushed insulation, wires rubbing on sheet metal, water exposure, vibration points, sensor tubes not supported, blocked access panels, field labels that do not match BAS points, and sensor values that appear frozen or unreasonable during startup. The record does not need to diagnose every cause; it needs to preserve enough evidence for the responsible trade to correct or accept the condition.

Tie photos to the point list. A common turnover failure is that photos show "a sensor" while the BAS trend shows "SAT," "DAT," "SA_TEMP," "Freezestat," or "LLT" with no proof they are the same point. The record should include a point-name crosswalk: field label, controller input, BAS point, HMI menu path, alarm name, and trend name. If the equipment has separate intake, return, discharge, and outside-air sensors, do not assume the most convenient value is the low-limit input. CaptiveAire manuals, Greenheck controller references, and AAON documentation all show that MUA controls can use multiple temperature inputs.

Record setpoint, delay, alarm, and reset status

Low-limit evidence should be recorded exactly as the project exposes it. Capture the approved sequence reference, controller or HMI menu, BAS setpoint, local device setting where visible, alarm threshold, alarm delay, differential or timer if shown, reset type, alarm priority, alarm recipient, and whether the alarm is local, remote, dry-contact, BMS, or both. If a value is hidden behind password-protected controls, record the approved value from the controls submittal and the name of the qualified person who verified it.

Manufacturer examples should not be copied as universal settings. Greenheck material reviewed for this package includes supply-air low-limit examples around 35 F with a 300 second delay in certain controller contexts. CaptiveAire parts and manuals reference freezestat ranges, factory settings, and timer ranges for specific controls. Those values are useful evidence that low-limit and freezestat functions are real controller features, but the field record should not convert them into a design rule. The approved sequence, equipment manual, controls submittal, commissioning plan, and authority having jurisdiction remain the controlling documents.

Alarm evidence needs a before-and-after story. If the commissioning plan allows a trip, simulation, or test-menu function, document the method only at a high level, the qualified party performing it, the time, the point name, the alarm text, the alarm priority, fan command, heat command, damper command, and reset outcome. CaptiveAire manuals include test-menu and HMI reset context, while Greenheck controller material includes alarm review, data logger, and reset behavior. The packet should show that the alarm exists where operations will see it, not merely that a technician saw a local screen on the roof.

Reset status is part of winter readiness. A manual reset or HMI reset that is hidden behind a locked roof hatch, blocked access panel, missing platform, disabled display, or unknown password is not a reliable turnover condition. If the low-limit alarm can only be reset locally, record who has access and how the owner will be told. If it clears only after the cause is corrected, record what condition must change. If the alarm cannot be reset during the visit because the cause is still active, document that as a hold, not as a completed test.

Prove outside-air damper position and fail action

The outside-air damper deserves its own evidence. On a make-up air unit, it controls the air path that creates the low-temperature risk. The record should show damper tag, blade condition, frame, seals if visible, actuator, shaft, linkage or direct-coupled connection, command signal, power source, spring-return or fail position, minimum-position setting if used, end switch or feedback if provided, and whether return-air or relief-air dampers must move with it.

Honeywell actuator wiring material specifically lists outside-air dampers on 100 percent outside-air or make-up air handlers as an application for direct-coupled actuators. Belimo training material reviewed here warns that certain minimum-position approaches should not be used for outside-air damper applications because the damper may never reach full closeoff, which can lead to coil freeze or other system problems. Johnson Controls spring-return actuator instructions show that spring-return direction, shaft size, anti-rotation bracket, manual override, and full-stroke verification are installation details that affect whether the damper actually does what the sequence expects.

Do not accept "damper opens" as the winter-startup proof. The risk may be failure to close, wrong fail position, binding blades, loose set screws, actuator slipping on the shaft, an anti-rotation bracket that allows the actuator body to twist, a minimum stop that prevents closeoff, or a feedback point that never proves blade position. A photo set should include open and closed positions where safe and allowed, actuator pointer or position mark, blade position mark, command screen, feedback screen if present, and any mechanical stops.

Fail action must be stated in project terms. Some dampers are intended to spring closed on loss of power; some may fail open for ventilation or smoke-control reasons; some are tied to exhaust operation; some are governed by kitchen hood controls or building pressure logic. The record should not declare what the damper should do unless the approved sequence says it. It should state what was observed, what the sequence requires, and whether those two facts match.

Document actuator mounting and service access

A damper actuator can look complete while being hard to maintain or mechanically unreliable. The record should show the actuator mounted square to the shaft, adequate shaft engagement, clamp or U-bolt condition, anti-rotation bracket condition, conduit or cable strain relief, weather protection where required, manual override access, position indicator, stroke stops, auxiliary switches if used, and enough clearance for removal without dismantling unrelated work.

Belimo LF training material discusses shaft length, extended shafts, obstruction problems, service space, and actuator mounting on damper shafts. Johnson Controls M9220 instructions discuss direct mounting on shaft sizes, spring-return direction, anti-rotation bracket position, avoiding binding, manual override, releasing the spring, and verifying a full stroke. These are not abstract product details. They become jobsite evidence when a winter alarm sends a technician to a roof in bad weather and the actuator cannot be reached, identified, or trusted.

Service access is often missed because startup photos are taken with temporary access conditions. A ladder may be present during construction but not after turnover. A ceiling tile may be open during fit-out but closed after inspection. A roof path may be accessible in September but blocked by snow, piping, exhaust discharge, or safety rules in January. Photograph the normal access path and any permanent platform, working clearance, panel swing, and label location that operations will rely on.

If the actuator is behind a factory panel, photograph the panel, label, wiring diagram pocket, HMI point, and field note that confirms the actuator could not be safely photographed without disassembly. A limitation is better than a false photo. The packet should distinguish between observed evidence and inferred evidence.

Connect damper proof to heat enable and fan status

The low-limit record should not isolate the damper from the rest of the sequence. Capture the relationship between outside-air damper command, heat enable, supply fan status, exhaust interlock, discharge temperature, and alarm state. If the project has damper end switches, airflow proving, gas heat enable, heating-water valve position, electric heat stages, or burner status, include the points that the approved sequence uses to prevent cold discharge air.

Direct-fired and compact make-up air manuals from CaptiveAire describe MUA boards targeting discharge temperature and monitoring discharge temperature inputs. Greenheck MUA controller references discuss pre-programmed operating sequences, supply and exhaust proving alarms, sensor alarms, supply temperature low-limit alarm, and alarm output. Those sources support a record that includes the sequence context, not just a single sensor. A discharge low-limit alarm with no fan status or damper status is hard to interpret later.

For field review, the most useful trend window usually includes outside air temperature, discharge air temperature, supply fan command and proof, outside-air damper command, damper feedback if present, heating command, heating output or valve command, freezestat or low-limit status, alarm state, and occupancy or enable status. Add return-air damper command if the unit uses a mixed-air box. Add exhaust fan status if the make-up air unit is interlocked with kitchen or process exhaust. Add building pressure or duct pressure only if the sequence uses it for this decision.

The record should also state whether the test happened under representative load. A unit can appear stable when the exhaust system is off, the outside-air damper is at minimum, or the building is unoccupied. If the startup condition did not include the exhaust fans or normal occupied schedule, record that limitation so operations does not treat the packet as proof of every winter scenario.

Build the BAS trend packet

A BAS trend packet should be short enough to read and complete enough to defend. Use a trend window that covers the startup command, damper movement, heat enable, discharge temperature response, alarm state, and return to stable operation. Include timestamps, units, point names, sample interval, controller name, trend export date, and the reason the window was selected. If the trend is a screenshot, make sure the axis labels and legend are legible. If it is a CSV export, preserve the file name and attach the plotted view used for review.

The trend should align with the photos. If the photo says the sensor is DAT-1 but the trend uses SAT-3, explain the point mapping. If the photo shows damper actuator A-1 but the BAS point is OA_DMP_CMD, identify that relation. If damper feedback is not installed, say that the record uses command and visual position only. If discharge temperature is from a factory controller and not the BAS, include the HMI photo or controller menu path in the same packet.

Capture alarm routing. A low-limit alarm that appears only on a local controller is not the same as an alarm that reaches the BAS, owner workstation, after-hours notification workflow, or remote alarm contact. Greenheck controller material discusses alarm review, data logger, remote alarm indication, and BMS communication where equipped. The record should show where the alarm appears and who accepted that routing for winter operation.

Trend review should stay within the commissioning plan. Do not force low-temperature conditions, bypass safeties, defeat burner controls, block dampers, or create unsafe airflow just to make a dramatic graph. If the weather is mild and a true cold trip cannot be observed, document a simulated point test or alarm review only if the qualified controls or commissioning team performs it under the project plan. Otherwise record the limitation and the retest trigger.

Field walk sequence before release

Use a consistent walk order. Start at the equipment tag and nameplate. Move to the outside-air intake and damper section. Verify damper photos before heat and fan evidence because the damper controls the air entering the unit. Move to the actuator, shaft, linkage, wiring, and access path. Then document filters, access panels, heat section labels, discharge-air sensor, discharge duct, controller or HMI, and BAS graphic. End with trend and alarm evidence.

This order reduces missed photos. If the field team starts at the HMI, the packet often becomes controls-heavy and misses the physical damper. If it starts at the damper, it often misses the BAS alarm routing. If it starts with a trend export from the office, it may never prove the sensor is actually in the duct. The record should force all three perspectives into one package.

During the walk, record exceptions immediately. Examples include damper blades not visible, actuator not labeled, sensor tag missing, HMI password unavailable, BAS point not trending, alarm not mapped, access panel blocked, unit not enabled to automatic, heating source not released, exhaust interlock not ready, or weather not cold enough for a full condition test. An exception is not a failure by itself, but an unclosed exception is not a release.

Assign owners for corrections. Mechanical may own damper linkage. Controls may own point naming and alarm routing. TAB may own airflow proof. Commissioning may own functional test acceptance. The owner may own after-hours alarm routing. Put the responsible party and retest evidence in the packet so the hold does not become a vague punch item.

Inspection table

Use a compact table so mechanical, controls, TAB, commissioning, and operations review the same evidence before winter startup.

Before-startup checklist

Run this checklist before the make-up air unit is released to winter operation, automatic schedule, owner use, or seasonal startup.

• Unit tag, roof or mechanical-room location, serving area, and startup boundary are identified.
• Equipment nameplate and field label match drawings, submittals, BAS graphics, or a recorded cross-reference.
• Outside-air intake, damper frame, damper blades, actuator, and access path are photographed.
• Damper open position and closed or fail position are visually documented where safe and allowed.
• Actuator model or label, shaft connection, anti-rotation bracket, manual override access, and service clearance are recorded.
• Damper command and feedback, if installed, are captured on the BAS/HMI trend or screen.
• Discharge-air sensor, sensing tube, probe, bracket, insulation, wiring path, and access panel are photographed.
• Sensor point names are crosswalked between field label, controller input, HMI, BAS graphic, trend, and alarm list.
• Approved low-limit or freezestat threshold, timer, alarm delay, differential, and reset type are recorded without substituting factory examples for project values.
• Alarm text, alarm priority, BAS routing, local HMI display, remote dry contact or notification path, and reset result are documented.
• Trend window includes outside air temperature, discharge air temperature, fan command/proof, damper command, heat command, low-limit or freezestat state, and alarm state.
• Heating source release, gas or hydronic permissions, electric heat status, and exhaust interlock status are noted as in scope or out of scope.
• Photos and trend timestamps are close enough in time to support the same startup condition.
• Operations access to roof, HMI, reset point, BAS alarm, and after-hours response path is confirmed or listed as an exception.
• Any unsafe, blocked, hidden, or password-protected item is documented as a limitation rather than assumed complete.
• Corrections have responsible parties, completion photos, retest notes, and reviewer names.
• The final decision says release, release with named limitation, or hold, and does not exceed the evidence in the packet.

Weak versus strong record

Weak record: MAU checked. Freezestat set at 35 F. Damper works. Ready for winter.

That record is weak because it does not identify the unit, prove which sensor was checked, show whether the value came from the approved sequence, show damper closeoff, show BAS alarm routing, show reset access, or state the startup boundary. It may be true, but it is not useful when the first cold alarm occurs.

Strong record: MAU-3 serving the Level 1 kitchen replacement-air system was reviewed for winter startup under WSR-17. Photos show the unit tag, outside-air intake, damper blades at commanded open and spring-return closed positions, actuator A-MAU3-OA with shaft clamp and anti-rotation bracket visible, discharge-air sensor DAT-MAU3 mounted in the discharge duct downstream of the heat section, and the sensor wiring label matching controller input U4. BAS screenshots show OA damper command, supply fan proof, heating command, discharge temperature, low-limit status, alarm point LL-MAU3, and alarm priority. The approved controls sequence lists the low-limit threshold and alarm delay; the record notes that the project sequence, not the manufacturer example, controls the value. The alarm was observed at the BAS workstation, reset access was photographed at the HMI, and the packet lists one limitation: final cold-weather trend to be repeated when outdoor air is below the seasonal retest trigger.

The strong record is not longer for its own sake. It is stronger because every claim points to evidence. It avoids design approval, avoids unsafe testing instructions, and still gives operations a practical map: where the sensor is, how the damper moves, what the alarm is called, where the reset happens, what was not tested, and what should be done if the condition repeats.

Common mistakes

The most common mistake is documenting the controller screen while ignoring the field sensor. A BAS value is only as reliable as the physical input behind it. If the sensor is loose, mislabeled, hidden, installed in the wrong duct, or not the point shown on the graphic, the screen capture creates false confidence.

Another mistake is treating a factory low-limit example as the project setting. Manufacturer documents often show example thresholds, defaults, ranges, or timer values for a specific product. The field record should cite the approved sequence, submittal, or commissioning procedure for the project value. If the project value cannot be verified, that is an exception, not a reason to write down a common number.

Damper mistakes are just as common. Teams photograph the actuator but not the blade position. They command the damper open but never prove closeoff. They record spring return without checking direction. They accept a visual actuator pointer even though the shaft is slipping. They omit the anti-rotation bracket. They miss a minimum stop that prevents full closure. They do not state whether feedback exists. All of those errors leave the cold-air path unresolved.

Controls mistakes include trend screenshots without legends, point names that do not match labels, no alarm recipient, no alarm priority, no reset result, no timestamp, and no record of automatic versus manual mode. A trend that proves stable discharge temperature during a manual test may not prove the same behavior under occupied schedule, exhaust interlock, or building pressure control.

Handoff mistakes include burying the record in a generic startup folder, failing to assign corrections, closing a hold without retest evidence, and using release language that sounds broader than the test. If the heat source was not fully released, if exhaust fans were off, if outdoor conditions were mild, or if the alarm was not routed to the owner, the packet should say so directly.

When to hold winter startup

Hold winter startup if the discharge-air low-limit sensor cannot be identified, photographed, mapped to the BAS/HMI point, or tied to the approved sequence. Also hold if the sensor is loose, damaged, not installed in the intended airstream, exposed to excessive vibration, inaccessible for service, or reporting a value that does not make sense relative to other temperature points.

Hold if the low-limit alarm threshold, delay, timer, reset type, or alarm routing cannot be verified by qualified staff. Hold if the BAS alarm text does not identify the unit, if the alarm is not routed where operations expects it, if reset access is blocked, if the HMI cannot be accessed, or if the alarm remains active because the cause has not been corrected.

Hold if the outside-air damper does not match the sequence. Examples include wrong fail position, no closeoff proof, binding blades, damaged linkage, loose actuator clamp, missing or mispositioned anti-rotation bracket, unverified spring-return direction, no service clearance, or feedback that does not match observed blade position. A damper that opens on command but cannot be proven to close may not be ready for cold weather.

Hold if related systems make the evidence misleading. If the exhaust interlock is not complete, the heating source is locked out, the gas train is not released, the hydronic heat source is unavailable, electric heat is disabled, fan proof is missing, fire alarm interlock is unresolved, or the unit is not ready for automatic schedule, the packet should not say the winter startup is complete.

Hold if the record relies on unsafe testing. Do not bypass safeties, block dampers, defeat burner controls, override protective devices, or expose personnel to moving parts or energized compartments to create evidence. The correct response is to document the limitation, assign the qualified party, and retest under the approved plan.

Owner handoff

The owner handoff should include the unit tag sheet, photo log, sensor point crosswalk, low-limit or freezestat sequence reference, HMI/BAS screenshots, alarm routing evidence, trend export, damper open/closed photos, actuator mounting photos, reset access photos, exception log, corrective photos, retest notes, and final release decision. Keep it with startup reports, controls checkout, TAB documentation, commissioning functional tests, O&M manuals, and seasonal readiness records.

Make the file names searchable. Use the unit tag, date, issue type, and evidence type: MAU-3_DAT_photo, MAU-3_OA-damper_closed, MAU-3_low-limit_alarm, MAU-3_winter-startup_trend. A useful packet can be found quickly during an alarm call. A folder full of image numbers cannot.

The handoff should tell operations how to respond without turning the article into a service manual. It should identify where the alarm appears, who receives it, what the alarm is called, where the reset is located, which access route is expected, what retest condition is required, and which contractor or service provider owns unresolved work. It should also warn that manufacturer instructions, project sequences, and qualified service procedures control any troubleshooting or reset work.

If the project cannot test under cold conditions before turnover, write a conditional handoff. State that physical installation, point mapping, alarm routing, and trend under available conditions were reviewed, but cold-weather verification remains due when the retest trigger occurs. That is better than overstating proof and leaving the owner to discover the gap during the first freeze event.

AEO and SEO field answer structure

For answer engines and search users, the page should answer the practical question in the first screen: what should be documented before winter startup of a make-up air unit low-limit sensor, freeze alarm, and outside-air damper? The answer is not a generic winter maintenance list. It is a record package built around physical sensor evidence, damper proof, controls evidence, alarm routing, reset access, exceptions, and release language.

Use exact trade terms naturally: make-up air unit, MUA, discharge-air sensor, supply-air low limit, low-temperature cutout, freezestat, freeze alarm, outside-air damper, spring-return actuator, damper feedback, HMI, BAS trend, alarm delay, reset access, winter startup, and operations handoff. Avoid stuffing these terms. The strongest page is one a field team can use while standing at the unit.

The content should remain source-backed but not source-dominated. Manufacturer sources support the existence and documentation relevance of low-limit alarms, freezestat timers, discharge sensors, damper actuators, spring return, alarm outputs, HMI reset, and mounting details. The article should convert those facts into a clear field record without pretending to replace the equipment manual or controls sequence.

Questions before release

Which make-up air unit is being released, and for what condition: automatic schedule, seasonal startup, owner turnover, kitchen exhaust operation, gas heat release, hydronic heat exposure, or cold-weather retest? Which systems are inside the release boundary, and which are not?

Where is the discharge-air sensor that drives the low-limit or freezestat decision? What is the field tag, controller input, HMI path, BAS point name, alarm name, and trend name? Does the sensor location match the approved sequence and manufacturer installation requirements?

What is the low-limit threshold, timer, delay, differential, reset type, and alarm routing? Did the project verify those values from the approved sequence or qualified controls review instead of copying a manufacturer example?

Does the outside-air damper move the way the sequence requires? Can the packet show open position, closed or fail position, actuator mounting, shaft connection, service access, command, feedback if present, and any limitation?

What would make the unit unsafe or unreliable to release? Who owns each correction? What evidence will close the hold? The release decision should answer those questions before the first cold-weather operating period.

Compliance and safety limits

This article does not select a make-up air unit, choose a low-limit setpoint, tune a burner, approve a gas train, set freeze-protection values, design a controls sequence, specify damper fail position, bypass a safety device, reset a protective control, authorize winter operation, or replace manufacturer instructions. It is a record structure for preserving field evidence before winter startup.

The controlling documents are the approved drawings, specifications, controls sequence, equipment submittal, manufacturer installation and operation manuals, commissioning plan, TAB scope, local code requirements, owner operations standards, and qualified service procedures. Use this checklist only to organize evidence and exceptions. Any testing, adjustment, reset, energized work, damper work, burner work, or control modification belongs to qualified personnel following the project documents and safety rules.

If the evidence conflicts with the approved sequence or manufacturer instructions, hold the release and escalate through the project process. A clean-looking packet should never override a real unsafe condition, unresolved alarm, inaccessible reset, unverified damper, or missing heat-release permission.

Sources checked

• Greenheck, Model VSU Make-Up Air Unit Installation, Operation and Maintenance ManualUsed for make-up air unit startup, direct-fired MUA context, building freeze protection, RT4 timer, and optional low-temperature trip context.
• Greenheck, Model MSX Modular Make-Up Air Unit Installation, Operation and Maintenance ManualUsed for MSX make-up air startup, alarms, building freeze protection, low-temperature lockout, freeze temperature adjustment, and outside-air/return-air damper behavior context.
• Greenheck, Microprocessor Controller for Make-Up Air Products Reference GuideUsed for supply-air low-limit alarm, sensor alarm, alarm output, data logger, remote display, supply discharge temperature sensor, and supply-temperature low-limit shutdown context.
• Greenheck, Modular Make-Up Air Unit Model MSX CatalogUsed for discharge temperature control, discharge temperature sensor feedback, coil freeze protection, freeze protection alarm contacts, and low-discharge-temperature cutout context.
• CaptiveAire, Direct-Fired Make-Up Air Installation, Operation, and Maintenance ManualUsed for MUA board discharge temperature control, discharge temperature thermistor inputs, freezestat setpoints, freezestat timer behavior, test menu, alarm output, and troubleshooting context.
• CaptiveAire, Compact Make-Up Air Installation, Operation, and Maintenance ManualUsed for compact MUA discharge temperature setpoints, freezestat timer, freezestat alarm, discharge sensor values, reset through HMI, and test-menu context.
• CaptiveAire, Thermostats/Sensors Parts Detail: Freezestat ControlUsed for freezestat control range, factory-set low-temperature sensor context, timer range, and separate sensor-length context.
• AAON, RQ Series Installation, Operation and Maintenance ManualUsed for freeze-stat startup, low-limit control option, preheat discharge supply-air temperature sensors, discharge temperature sensor terminals, and alarm relay output context.
• Trane Technologies, Discharge Air Sensing Kit InstallationUsed for discharge-air sensing tube, temperature sensing module, insulation, knockout, bracket, supply/discharge duct cover, and sensor assembly photo context.
• Johnson Controls, NS Series Network Discharge Air Sensors Installation InstructionsUsed for discharge-air sensor duct mounting, probe insertion, screw mounting, vibration caution, addressing, wiring, and replacement limits.
• Honeywell, Direct Coupled Actuator WiringUsed for direct-coupled actuator wiring and the specific application of outside-air dampers on 100 percent outside-air or make-up air handlers.
• Belimo LF Series Spring Return Direct Coupled Actuator, CaptiveAire training copyUsed for actuator service space, damper shaft requirements, outside-air damper closeoff warning, manual override context, and spring-return actuator documentation.
• Johnson Controls, M9220-GGx-3 Proportional Electric Spring Return Actuators Installation GuideUsed for spring-return actuator mounting, shaft size, anti-rotation bracket, manual override, full-stroke verification, spring return direction, and safety-device context.

Related guides