Content Plan & 10 Titles

The strategy behind this pack

Northline sells two things that look like one thing: preventive maintenance contracts (recurring revenue, planned labor, predictable truck routing) and emergency repair (high margin, unplanned, and the way most new customers meet you). The buyer for both is usually the same person — a facility manager or owner-operator who is not an HVAC expert, is accountable for occupant comfort and budget, and is quietly worried about being caught unprepared.

That buyer does not search for "commercial HVAC contractor Columbus" until the day something breaks. Long before that day, they search for the questions that keep them up at night: how often should rooftop unit filters be changed, what should a PM contract cover, is it worth repairing a 19-year-old RTU, what does the new refrigerant rule mean for my building. Those are the searches this pack is built to own.

The content strategy is deliberately not "HVAC tips." It is a set of ten articles that each do one job: give the buyer a framework they can use immediately, and in doing so demonstrate that Northline thinks about their building the way a good in-house engineer would. Every article ends with a soft, specific call to action rather than a hard sell, because this audience is researching months before they buy.

How the ten fit together

The pack is sequenced as a funnel, not a list:

Articles 1, 5 and 9 are the commercial money pages — they map most directly to a purchase decision and deserve the strongest internal linking. Articles 3, 4 and 7 are the durable reference pieces that earn links and repeat traffic. Articles 6, 8 and 10 are the trust builders that make a facility manager think these people have actually worked in a building like mine.

The ten titles, as published

• What a Commercial HVAC Maintenance Contract Should Actually Include (and What Gets Quietly Left Out)
• Calendar-Based vs. Runtime-Based Maintenance: Why "Quarterly" Is the Wrong Answer for Half Your Equipment
• Filters, Belts, Coils and Bearings: The Real Service Intervals for Commercial HVAC
• The Refrigerant Rules Are Changing: What Building Owners Need to Know About Leaks, Records, and the R-410A Phasedown
• How to Write an HVAC Emergency Response SLA That Actually Means Something
• Maintaining HVAC in an Occupied Building: Scheduling Around Students, Staff and Production
• Seasonal Changeover: The Spring and Fall Punch Lists That Prevent Summer Emergencies
• How to Read an HVAC Service Report: What "Completed" Should Look Like
• Repair or Replace? A Decision Framework for Aging Rooftop Units
• Deferred Maintenance Is a Budget Decision, Not a Maintenance Decision

Publishing notes

• Cadence. Roughly one every 10–14 days covers a quarter. If you would rather front-load, publish 1, 5 and 9 first — they convert — then fill in the reference pieces.
• Internal linking. Every article should link to at least two others in this pack. Suggested links are noted in-line where they are natural.
• Local signal. Each article mentions Central Ohio conditions where genuinely relevant (freeze-thaw cycling, humid summer latent load, school calendars). Do not force the city name into every paragraph; it reads as spam to both readers and search engines.
• Numbers. Where an article would normally quote an industry statistic, it instead explains the mechanism, or leaves a bracket for you to insert a figure from your own service history — e.g. `[X — insert your figure]`. Filling those brackets with real Northline data is the single highest-value edit you can make to this pack, because nobody else can publish your numbers.
• CTA. Each article closes with a call to action containing `[phone]`, `[email]` and `[link]` placeholders. Replace with live contact details before publishing.

---

Article 1

What a Commercial HVAC Maintenance Contract Should Actually Include (and What Gets Quietly Left Out)

Most commercial HVAC maintenance contracts are two pages long and say almost nothing. They promise "quarterly preventive maintenance visits" and "priority service," list a monthly price, and leave the details to trust. That is fine right up until the day a compressor fails in July and you discover that "priority service" meant priority over the customers who have no contract at all, and that refrigerant, filters and after-hours labor were never included.

A maintenance agreement is a scope document. If it does not describe the work in enough detail that a technician you have never met could arrive at your building and perform it correctly, it is not a scope — it is a subscription.

Here is what belongs in one.

1. An equipment list that is actually current

The contract should open with an asset inventory: every unit covered, by tag, make, model, serial, location on the roof or in the mechanical room, tonnage, refrigerant type and charge, filter sizes and quantities, belt sizes, and approximate year of installation.

This sounds administrative. It is the most important page in the document. Without it:

• You cannot verify a technician actually visited every unit.
• Nobody can pre-stage the right filters, so "PM visits" become "PM visits, plus a return trip."
• Refrigerant recordkeeping obligations cannot be met, because you do not know your charge by unit.
• The day you plan capital replacement, you start from zero.

Ask whether the equipment list will be built during the first visit and whether you receive it as a file you own — not a screenshot inside a contractor's portal you lose access to when the contract ends.

2. Task-level scope, split by frequency

"Quarterly PM" is not a scope. A real scope reads more like this:

Note the word logged. Readings that are taken but not recorded are readings you cannot trend, and trending is the entire point of preventive maintenance.

3. A clear line between what is included and what is billable

Every contract has this line. Bad contracts hide it. A good one states plainly:

• Included: all PM labor, standard pleated filters, belts, lubricants, condensate treatment, minor electrical components under `[$X]`, and full documentation.
• Billable: compressors, motors, coils, boards, refrigerant beyond `[X lbs]` per unit per year, and any repair over `[$X]` — always with written approval before work begins.
• Never a surprise: trip charges, after-hours multipliers, and travel time, all disclosed as rates in the agreement rather than discovered on an invoice.

If a contractor will not put filter and belt inclusion in writing, they are planning to bill you for them.

4. Response commitments with definitions attached

"Four-hour response" means nothing until you define response. Is it a returned phone call, a technician dispatched, or a technician on site? Does the clock start when you call, when a human answers, or when a ticket is created? Does it run overnight, on weekends, on the Fourth of July? See our companion article on writing an emergency SLA for the full treatment — but at minimum, the contract should define the trigger, the clock, and the remedy if the commitment is missed.

5. Documentation and reporting you can use

You should receive, per visit and per unit: the tasks performed, the readings taken, the parts installed, deficiencies found with a severity rating, and a photograph of anything the technician wants you to act on. You should receive an annual summary that rolls those deficiencies into a prioritized list. That summary is what you take into budget season.

6. Escalation, staffing and continuity

Who is your account contact? What happens when they are on vacation? Are technicians assigned to your site consistently, or is it whoever is closest? Consistency matters more than most buyers realize — a technician on their fourth visit to your building knows which unit has the noisy bearing and which economizer has been fighting its actuator since spring. Ask whether the contractor tracks site assignment deliberately.

What gets quietly left out

Scan any proposal for these five omissions:

• Coil cleaning frequency — often listed as "as needed," which means never.
• Filter media grade — a MERV 8 swapped in where the design called for MERV 13 will pass a visual inspection and quietly change your filtration.
• Belt replacement vs. inspection — inspecting a belt costs nothing; replacing it on a schedule prevents a failure.
• Controls and BAS work — frequently excluded entirely, which means the most common comfort complaints fall outside your contract.
• Refrigerant compliance recordkeeping — the obligation stays with you as the owner even when the contractor does the work. Make sure someone is producing the records.

The one question worth asking

Before you sign anything, ask a prospective contractor: "Show me a sample service report from a real visit, with the customer's name redacted."

The answer tells you almost everything. A contractor whose reports contain measured readings, unit-by-unit detail and photographed deficiencies is running a maintenance program. A contractor whose reports say "PM performed, unit operational" is running a route.

---

Northline Mechanical maintains commercial HVAC systems for office buildings, schools and light industrial facilities across Central Ohio. If you would like a second set of eyes on a maintenance proposal — yours or a competitor's — send it over and we will mark it up honestly, including where our own scope would need to be tighter. Call `[phone]` or email `[email]`.

---

Article 2

Calendar-Based vs. Runtime-Based Maintenance: Why "Quarterly" Is the Wrong Answer for Half Your Equipment

Almost every commercial HVAC maintenance contract in the country is scheduled on a calendar. Quarterly for rooftop units, semi-annual for split systems, annual for the boiler. It is simple, it is easy to price, and it is wrong often enough to matter.

The reason is straightforward: equipment wears by operation, not by date. A rooftop unit serving a south-facing conference room that is used two hours a week and a rooftop unit serving a 24-hour data closet in the same building will receive exactly the same number of visits under a calendar-based contract, despite one accumulating perhaps thirty times the runtime of the other.

One is over-maintained. The other is under-maintained. You are paying for both mistakes.

What runtime actually drives

Not every maintenance task is runtime-driven, and this is where the nuance lives. Sort your tasks into three buckets:

Runtime-driven. Belt wear, bearing wear, motor brush and winding stress, compressor cycling fatigue, filter loading in a constant-volume system. These accumulate in proportion to hours of operation and to start/stop cycles. A unit that short-cycles fifteen times an hour is aging its contactor and compressor far faster than its runtime hours alone suggest — cycle count is its own wear axis.

Calendar-driven. Corrosion, gasket and seal degradation, UV damage to wire insulation and roof curb sealant, rodent and insect intrusion, drain pan biofilm growth, and refrigerant leakage through joints and Schrader cores. These happen whether the unit runs or not. A unit that sat idle all winter can still greet you in May with a plugged condensate trap and a leaking core.

Event-driven. Post-storm inspection, post-power-event control checks, filter change after nearby construction or roof work, coil rinse after a season of cottonwood.

A good program uses all three triggers. A calendar-only program uses one.

How to get runtime data without a building automation system

The common objection is that runtime scheduling requires a BAS most buildings do not have. It does not.

• Runtime hour meters. Inexpensive elapsed-time meters wired to the blower or compressor contactor give you exact hours per unit. On a mixed-use building, installing them on your ten most critical units costs less than one emergency call.
• Smart thermostats and connected controllers. Many already log runtime and will export it. If a unit is on a connected controller, the data probably already exists and nobody has asked for it.
• Utility interval data. Not unit-level, but building-level electrical interval data tells you the shape of your load — when the plant actually runs, and whether it is running when the building is empty.
• Proxy estimation. Occupancy schedule × design load × degree days gets you a defensible estimate. It is not precise, but "this unit runs roughly four times as much as that one" is enough to change your schedule.
• The technician's own observation. Belt dust on the deck, wear polish on a sheave, motor bearing noise — an experienced tech reading a unit at each visit is a runtime sensor with legs.

What a hybrid schedule looks like in practice

Here is a workable structure for a mixed portfolio, expressed as triggers rather than dates:

Notice that the calendar does not disappear. It sets the floor. Runtime sets the additional visits on the equipment that earns them.

The objection: "This makes scheduling harder"

It does, for the contractor. That is the honest answer. Calendar routing is easy to dispatch — you group by geography and knock out a neighborhood in a day. Runtime-triggered work is lumpy and harder to route efficiently.

That difficulty is precisely why most contractors do not offer it, and it is why the ones who do tend to be the ones running real dispatch systems rather than a whiteboard. If you are evaluating contractors, asking "how would you adjust the schedule for a unit that runs 4,000 hours a year versus one that runs 400?" is a fast way to find out how their operation actually works.

Where runtime scheduling pays for itself

Three places, mechanically:

Belts. A belt that fails takes airflow with it. A belt replaced on a runtime trigger is a five-minute planned task. A belt that snaps on a Tuesday afternoon in an occupied school is an emergency call, a comfort complaint, and possibly a frozen coil if the unit keeps calling for cooling with no airflow.

Bearings and motors. Bearing failure is progressive and audible long before it is catastrophic. Runtime-triggered inspection catches it in the audible phase. Calendar inspection catches it whenever the quarter happens to land.

Compressors. The expensive one. Compressors fail from liquid floodback, from running low on charge, and from cycling. All three are detectable through readings taken while the unit is running under load — which means the visit has to happen during a season when the unit runs, not in a mild October when the compressor never stages on. This is the single most common flaw in a rigid quarterly schedule: the visits land when the equipment is not working hard enough to reveal anything.

Start here

You do not need to reinvent your program. Do this instead:

• Rank your units by criticality — what happens to the business if this one fails today?
• For the top tier, get real runtime data. Meters or controller export, whichever is cheaper.
• Keep the calendar floor for everything.
• Add runtime-triggered visits only on the units where the data says they are earning it.
• Re-rank annually.

That is a one-afternoon exercise that will change how you spend your maintenance budget for years.

---

Northline Mechanical builds maintenance schedules around how your equipment actually runs, not just around the calendar. If you want to see what a runtime-weighted schedule would look like for your building, we will map your unit list and show you where the current schedule is over- and under-serving you. Reach us at `[phone]` or `[email]`.

---