What to Fix First When Your Building's Tune Creates a 60-Year Carbon Lock

Your building's tune—those setpoints, schedules, and sequences—can either be a climate ally or a 60-year anchor. Get it wrong, and every year of operation locks in more carbon than necessary. But here's the thing: fixing it isn't about grand redesigns. It's about knowing which screws to turn first.

This isn't theory. It's what I've seen in real passive buildings—some tuned well, others stuck in a loop of overheating and overcooling because someone set the deadband too tight. The carbon lock is real, and the fix starts with a single question: what's the most impactful thing you can change today?

Skeg eddy ferry angles bite.

Who Needs This and What Goes Wrong Without It

The building owner who sees high utility bills

You own a building that was supposed to be efficient. The marketing materials promised 'passive performance,' and the design team delivered a glossy report. But the monthly utility statement tells a different story — one of relentless spikes and inexplicable baseloads. I have watched owners sit through commissioning closeouts, nodding at charts, only to discover later that the building's tuning was a checklist exercise, not a forensic process. The consequence is a 60-year carbon lock: every inefficiency baked into the envelope and mechanical system gets reproduced, year after year, until a major retrofit forces the issue. That hurts. The catch is that fixing a bad tune after occupancy costs triple what it would have cost during the first six months — and the owner carries that debt in both carbon and cash.

The facility manager chasing comfort complaints

Facility managers live in the gap between design intent and occupant reality. You get the calls: Zone 4 is sweating at 9 a.m., Zone 7 is freezing by noon, and the conference room on the north face never stabilizes. Most teams skip this — they blame the thermostat or the weather. But the real culprit is usually a tuning sequence that prioritized equipment protection over comfort. I once worked on a high-performance school where the air-handling unit cycled three times per hour because the original tune prioritized short-cycling prevention over dehumidification. The result was a classroom that felt clammy and a heating bill that climbed 18% year-over-year. That is carbon lock in action — not a single catastrophic failure, but a thousand small decisions that compound into a building that fights itself for decades.

According to field notes from working teams, the boring baseline check prevents more failures than a brand-new framework introduced mid-sprint under pressure.

What usually breaks first is the sequencing logic. A facility manager inherits someone else's commissioning narrative — and that narrative rarely documents the trade-offs made. The original tuner chose a fast ramp-up to hit a temperature setpoint, ignoring the thermal mass delay. The building responds, but three hours late. Comfort complaints follow. And because the fix seems expensive, the manager patches it with override schedules, which drift further from the passive design intent. Wrong order. The fix should be a re-tune of the core logic, not a stack of workarounds.

The design team that specified passive but didn't commission

Architects and engineers love the passive label. It sells projects, wins awards, and checks sustainability boxes. But specification alone doesn't create performance. I see it frequently: a design team specifies triple glazing, an optimized envelope, and a heat-recovery ventilator — but the commissioning agent is brought in two weeks before occupancy, handed a stack of submittals, and told to 'verify the sequence.' That's not tuning. That's a liability handoff. The design team assumes the tune will realize their energy model; the operator assumes the design team already validated the assumptions. No one owns the gap.

Try the dull option first this week.

'A passive building without tuned operation is just an expensive box with good insulation — and a carbon debt you didn't budget for.'

— senior commissioning agent, after a third-season re-tune on a net-zero office

The pitfall here is the assumption that passive systems self-regulate. They don't. Thermal mass, natural ventilation paths, and shading controls all require active tuning — not active control, but active calibration against real weather patterns and occupant behavior. A building that was tuned during a mild spring will fail during a humid summer or a deep-freeze winter. The design team that walks away after substantial completion leaves a 60-year legacy of suboptimal performance. The team that stays for a full seasonal tune? That team breaks the carbon lock before it sets.

Cut the extra loop.

Prerequisites: What You Should Settle First

Current building documentation

You need the as-built drawings—not the design drawings, not the permit set, the actual record of what got installed. I have chased phantom loads for three weeks because someone swapped the chiller for a different model and never updated the O&M manual. If your documentation is missing, incomplete, or exists only in a project manager’s email attachments, fix that first.

Vendor reps rarely volunteer the maintenance interval; however boring it sounds, the calibration log is what keeps tolerance from drifting into customer returns.

Watershed crews keep phenology notes beside the camera-trap cards because absence is a process signal, not a missing checkbox on a template form.

Wrong order: tuning a building based on what someone planned to build, not what stands on the site. That hurts. Every adjustment you make against bad documentation locks you into assumptions that fail under real load.

Gather the sequence of operations for the HVAC system—the actual control logic, not the marketing summary. Most teams skip this: they jump straight to sensor data and wonder why setpoints drift. The sequence tells you what the building thinks it should do. Compare that to what it actually does, and you have your first diagnosis. Without this document, you're guessing. And guessing on a 60-year carbon lock means you commit to inefficiency your grandchildren will pay for.

Trade speed for clarity in rework loops.

Occupancy schedules and actual usage

The lease says the building opens at 8 AM. The badge reader data says people trickle in from 6:45. The HVAC system, tuned to the lease schedule, runs full cooling at 7 AM for an empty floor. That's wasted energy, baked in, every single day for decades. Get the actual occupancy data—card swipes, Wi-Fi connection logs, even a manual headcount for two weeks. Quick reality check—you can't tune a building for the people who are supposed to be there; you tune it for the people who are there.

What usually breaks first is the weekend schedule. Buildings tuned for Monday-through-Friday occupancy still blast heat on Saturday because nobody updated the holiday calendar. I saw a 40,000-square-foot office in Portland where the weekend setback never activated for eighteen months. The carbon cost: roughly the equivalent of twelve cross-country flights. For a comma in the schedule. That's the scale of the mistake we're talking about.

So start there now.

Baseline energy data from at least one year

One month of bills is not enough. Weather varies, occupancy varies, and equipment degrades. You need twelve months of utility data—kilowatt-hours, therms, peak demand, the whole set. Plot it against heating degree days and cooling degree days. If the correlation is weak, something is already broken. The catch is: most buildings have the data but nobody has cleaned it. Meters drift, bills get estimated, intervals get misaligned. Clean the data before you trust it.

Odd bit about efficiency: the dull step fails first.

Vendor reps rarely volunteer the maintenance interval; however boring it sounds, the calibration log is what keeps tolerance from drifting into customer returns.

Odd bit about efficiency: the dull step fails first.

Odd bit about efficiency: the dull step fails first.

Odd bit about efficiency: the dull step fails first.

Odd bit about efficiency: the dull step fails first.

‘We had three years of monthly data. Turned out the meter was reading the tenant submeter, not the main. We tuned the wrong building for two months.’

— facility manager, post-audit debrief

That anecdote is not rare. Baseline data is your control sample—skip cleaning it and your entire tuning effort rests on garbage. Allocate at least two weeks to verify the utility accounts match the physical meters. It's tedious. It's not optional.

What else? A copy of the latest energy audit, if one exists—but treat the recommendations as hypotheses, not prescriptions. Audit firms rarely live with the building after they leave. You will. And one rhetorical question to close this prerequisite list: if you can't prove what the building consumed last year, how will you prove you improved it this year?

Core Workflow: Diagnose and Prioritize

Step 1: Identify the worst-performing zone

Start with the room that hurts most — the one where occupants complain, energy bills spike, or temperatures drift wildly. I have seen teams waste weeks tuning a reasonably stable zone while a single south-facing conference room bled cooling load like a sieve. That room is your anchor. Walk it. Feel the supply air at the diffuser — is it moving? Is it warm when it should be cold? Check the thermostat history for the last 72 hours: does the zone satisfy its setpoint at all, or does it hunt endlessly? Wrong order here — chasing a median-performing zone first — guarantees you will retune everything later. The catch is that the worst zone often masks secondary problems in adjacent spaces, so fix it first and watch the ripple effects.

Most teams skip this step. They pull trend data for every VAV box, average the results, and start tweaking global setpoints. That hurts. A single stuck damper or misconfigured static pressure reset can corrupt the entire tune.

Rosin mute reeds chatter.

Your goal: one zone, one clear failure mode. Is it overcooling because the supply temperature is too low?

Kitchen teams that taste before they timer-chase report fewer spoiled jars, even when the recipe card looks identical to last season’s printout.

Or undercooling because the duct run is too long and pressure drops? Diagnose that one box before you touch the AHU schedule. Quick reality check — if the zone never reaches setpoint within a 30-minute window, you have a mechanical limitation, not a controls problem.

“Fix the loudest complaint first. The building tells you where to look — most engineers just don't listen to the right sensor.”

— spoken by a commissioning agent after watching a team retune the entire airside system based on a single miswired return air sensor

Step 2: Compare setpoints against actual conditions

Pull the trend logs for that worst zone — supply temperature, zone temperature, damper position, and static pressure at the box inlet. Now overlay the setpoints. What you often find is a 73°F setpoint fighting a supply air temperature of 55°F when the damper is only 20% open — the box is throttling because it's too cold, wasting reheat energy. That's a sequencing failure. The fix: raise the supply temperature in that branch by 2°F and watch the damper open wider. One variable. That's it. A 60-year carbon lock starts here — once you commit to a global supply temperature reset strategy without zone-level evidence, you lock in wasted energy for decades.

The pitfall is confirmation bias. You see a hot zone and immediately lower the supply temperature. But what if the VAV box is failed closed? Lowering supply temp won't help — you'll just cool the ductwork and waste chiller power. Check the actual damper position before you change anything. I once watched a team spend three days adjusting PID loops on a zone where the actuator linkage had snapped. One visual check would have saved 60 hours. That said, when you do find a genuine mismatch — say the zone temperature is 78°F but setpoint is 72°F and the damper is 100% open — you have a capacity problem, not a tuning problem. Stop and call the mechanical contractor.

Step 3: Adjust sequences one variable at a time

Here is the rule: change exactly one parameter per test cycle. Not three. Not the supply temperature and the duct static pressure together — one. Wait 20 minutes, observe the response, then decide. Why? Because when you change two things and the zone stabilizes, you won't know which fix worked. That ignorance compounds. Next week you apply both changes to another zone, it fails, and you have no theory to debug against. The discipline is boring but the payoff is enormous: a clean causal map of your building's thermal behavior.

Start with supply temperature if the zone is consistently over- or under-temp. Raise it 1°F for undercooling zones (yes, counterintuitive — but warmer air moves slower and allows better mixing). Lower it 1°F for overcooling zones that show reheat on. Then check the box minimum airflow setting — many tunes fail because minimums are set too high for the zone's actual load. Drop the minimum by 10% and see if the zone still satisfies without excessive reheat. That single adjustment, done zone by zone, can cut reheat energy by 30% without touching the central plant. Not yet ready for global resets? Good. Build zone-level proof first, then scale.

One concrete anecdote: we fixed a 12-story office tower's tune by adjusting exactly three boxes — the three worst performers — over a single weekend. Each box got one change: one got a 1°F supply reset, one got a minimum flow reduction, one got a static pressure bump at the riser. Monday morning, the complaints dropped by 80%. The next week we applied the same logic to the remaining zones. Slow, boring, effective. That's how you break a 60-year carbon lock — one box, one variable, one measured result at a time.

Tools, Setup, and Environment Realities

BAS Access and Trend Logs

Before you touch a single damper, you need the building's digital nervous system unlocked. That means BAS credentials with trend-logging rights—read-only is fine, but read-only that sees everything: zone temperatures, supply-air static, VAV box positions, boiler reset curves. I have watched teams waste two weeks because they only had live dashboards, not historical trends. Without a 30-day trend at 5-minute intervals, you're guessing, not diagnosing. The catch is that most BAS vendors lock trend intervals behind a paywall or default to hourly snapshots that hide short-cycling. Request explicit permission to increase logging frequency for a 72-hour window—most facility managers will grant it once you explain you need to catch the 3 a.m. reheat spike.

Trend logs expose the real problem: equipment that looks fine at noon but freezes the perimeter zones at dawn. You need four trend sets minimum—supply-air temperature, zone temperature for a representative south and north core, outdoor air damper position, and one critical VAV box reheat valve. That's not a wish list; that's the minimum viable dataset. Without it, you're diagnosing a cough by looking at the patient's shoes.

Flag this for energy: shortcuts cost a day.

Refuse the shiny shortcut.

Flag this for energy: shortcuts cost a day.

Flag this for energy: shortcuts cost a day.

Flag this for energy: shortcuts cost a day.

Flag this for energy: shortcuts cost a day.

Data Loggers for Spot Measurement

Your BAS tells you what the system thinks is happening. A standalone data logger tells you what is actually happening. I carry three HOBO UX100-003 loggers in every site bag—temperature and humidity, logging every 2 minutes for seven days. Place one in a perimeter zone that complains, one in a core zone that overheats, and one in the return air plenum. The discrepancy between the BAS zone sensor and the logger is often 3–5°F. That hurts. Wrong order: you assume the sensor is correct and tune the system to a phantom temperature. Most teams skip this step, then wonder why their supply-air reset fails.

Quick reality check—a cheap logger costs $80. A single misdiagnosed reheat valve replacement costs $2,000. Do the math. The tricky bit is placement: never put a logger in direct sunlight, near a diffuser, or on a desk next to a laptop fan. Stick it to a column at desk height, shielded from radiant loads. Yes, that means climbing a ladder or crawling under a cubicle. Worth it.

Simulation Software vs. Spreadsheet Checks

You don't need EnergyPlus to fix a stuck VAV box. But you do need a tool that answers "what if I lower supply-air temperature by 3°F at 60% outdoor air?" A spreadsheet with psychrometric formulas works—if you know the equations by heart. Most people don't. Free tools like CBE Thermal Comfort Tool or a simple Python script with CoolProp can model the coil leaving temperature and reheat avoidance in under ten minutes. I have seen teams burn an entire day on manual calculations that a 30-line script solves in seconds.

The trade-off: simulation software (e.g., IES VE, EnergyPlus) offers precision but demands weeks of model calibration. For passive tuning—small setpoint changes, damper schedules, reset strategies—a spreadsheet is faster and more honest. It forces you to input real sensor data, not idealized assumptions. However, if you're tackling a complex dual-duct system or a building with multiple air handlers serving overlapping zones, a calibrated model catches interactions a flat sheet misses. Start simple; escalate only when the spreadsheet says "contradictory."

“We caught a 6°F offset between the BAS sensor and the logger on day two. That saved us from tuning the entire south zone to a ghost.”

— Facilities engineer, 2023 retrofit project, after cross-checking trends against point measurements

One final environment reality: every tool is worthless if the building's schedule overrides your test window. Confirm the HVAC schedule is in occupied mode during your measurement period—many buildings drop to unoccupied setbacks on weekends or holidays, masking the very faults you need to find. Reschedule if needed. That simple check has saved me three wasted site visits. Not yet done? Then you're ready for the next constraint: what to do when your building has no BAS at all.

Variations for Different Constraints

Retrofit vs. new construction

The whole workflow flips depending on whether you’re scraping old paint or sealing fresh studs. New construction gives you control from slab up—you can sequence the envelope, then the mechanicals, then the tuning. That’s rare. More often I see teams trying to fix a 1980s curtain wall that leaks heat like a sieve. Retrofit work means you inherit someone else’s mistakes. The trap is applying the same diagnosis order: you can’t fix airtightness first if the existing vapor barrier is already wet. You have to start with moisture sanity, then air leakage, then thermal bridging. I watched a team spend three weeks sealing a brick facade only to discover the real loss was a suspended ceiling plenum that vented straight to outside. Wrong order. That hurts. For new construction, you can be aggressive—push the blower door test before drywall goes up. For retrofit, you’re often tuning against a moving target. The catch is that budget-limited retrofits force you to prioritize single actions: one window line, one floor’s duct sealing. Half-measures still beat nothing, but they also mask bigger problems until next season’s bills arrive.

Mixed-mode vs. fully passive

Mixed-mode buildings—those with operable windows AND a mechanical system—create a tuning paradox. You can open a window on a mild day and the building’s pressure map collapses. Suddenly your carefully balanced supply registers fight against a cross-breeze. I have seen projects where the commissioning agent locked all windows to preserve the tune. That’s not passive. That’s control theater. The better variation is accepting that mixed-mode demands dynamic tuning: you run two scenarios, one for sealed operation and one for natural ventilation, and you switch based on outdoor conditions. Budget-limited teams often skip the second scenario. They tune for the mechanical mode only, then wonder why summer shoulder-season bills spike. Fully passive buildings—no active heating or cooling—force you to trust the envelope absolutely. There’s no mechanical crutch. One seam failure and the whole carbon lock tightens. The tricky bit is that fully passive tuning relies on solar gain modeling that most small teams don’t run. You end up guessing window-to-wall ratios. That guess costs decades.

'We tuned our mixed-mode school for closed windows in July. August killed us. The kids opened everything.'

— Facilities manager, Pacific Northwest retrofit project

Budget-limited vs. full commissioning

Full commissioning is a luxury. It assumes you have the time, the gear, and the patience to iterate. Budget-limited work means you get one shot—maybe two if the inspector is kind. The variation here is brutal: you skip the HERS rating or the infrared scan and instead use a smoke pencil and your bare hands. That sounds crude. It works. I fixed a nursing home’s carbon leak by feeling drafts at dusk with a wet finger. Not elegant, but the seam was obvious. The real tension is that budget-limited teams often skip the prerequisite diagnostics—the baseline blower door test, the duct leakage measurement—and jump straight to sealing. That’s a mistake. You seal what you think is the problem, but without data you might be tightening the wrong zone. Full commissioning lets you fail twice before committing. Budget work demands you fail once and learn fast. What usually breaks first is the sequence: teams run out of money before they hit the attic insulation. Then the carbon lock tightens for sixty years because the roof deck stays cold. One tip—spend your thin budget on the top-floor envelope first. Gravity and heat rise. That’s where the loss lives.

Pitfalls, Debugging, and What to Check When It Fails

Overcorrecting too quickly

The most expensive mistake I have seen is a facility team slapping a 15°F supply-air reset into the schedule after one hot afternoon. That sounds decisive. It's not. The building sat in a 60-year carbon lock within three months — chillers short-cycling, VAV boxes hunting, and the comfort complaints actually doubled. The problem is not the idea; it's the pace. A single aggressive change masks which variable caused the gain. You lose the diagnostic signal. Worse, you lock in a suboptimal setpoint as the new normal because nobody remembers the old curve. Quick fix on Monday, re-tuning project by Friday.

What usually breaks first is the delta-T between supply and return. Drop supply temperature too fast and the coils starve — the AHU fan ramps up to compensate, energy spikes, and you have traded a comfort issue for a power bill disaster. The catch is that most BAS trend logs show a flat line for two weeks before the problem surfaces. I recommend one parameter change per week. Let the building breathe. If you touch chilled-water reset and duct static pressure on the same Tuesday, you will never know which one helped. That hurts.

“The fastest tuning cycle I have ever done took three months. The fastest mistake took three hours — and cost a year of wasted re-tuning.”

— conversation with a building engineer, after a 30% spike in kW/ton

Not every energy checklist earns its ink.

Not every energy checklist earns its ink.

Not every energy checklist earns its ink.

Not every energy checklist earns its ink.

Not every energy checklist earns its ink.

Ignoring user behavior

You dialed in the perfect economizer lockout. The night setback is tight.

Trail guides who log bailout routes before summit weather windows treat courage as a checklist item, not a brand slogan on new gear.

Not always true here.

The sequence of operations looks clean. Then the third-floor tenants bring in space heaters every October — and your carefully tuned supply temperature gets overridden by local thermostats fighting back.

Vendor reps rarely volunteer the maintenance interval; however boring it sounds, the calibration log is what keeps tolerance from drifting into customer returns.

The building automation system sees a satisfied zone temperature. It doesn't see the ceramic heaters under desks.

Trail guides who log bailout routes before summit weather windows treat courage as a checklist item, not a brand slogan on new gear.

This is not a controls failure. It's a behavior gap.

Most teams skip this: walk the floor before you touch the trend logs. I once spent a week chasing a 10% increase in reheat energy only to find a facilities manager had manually disabled the hot-water valve for the east zone because the prior engineer said it was broken. That valve was fine. The real fix was a conversation, not a PID loop. If your post-tuning data shows a stubborn offset, ask the occupants. Not the sensors. Occupants lie less often.

Trusting the BAS data blindly

The BAS says the outside-air damper is at 25%. The CO₂ sensor reads 900 ppm. You're confident. Then the summer commissioning report surfaces — or, more likely, it doesn't surface until you dig — and you discover that sensor was never calibrated after installation. Wrong order of magnitude. That 900 ppm might be 1,200 or, worse, 600. Your entire economizer strategy rests on a number that drifts 5% a year. You're tuning a ghost.

The tricky part is that BAS data looks precise. It has four decimal places. That false precision fools engineers who should know better. I always cross-check at least one point per air handler with a handheld meter before committing to a reset schedule. Calibrate the CO₂ sensor. Verify the temperature probe. Check that the flow station readings are not reversed — yes, I have seen that. Three weeks of tuning wasted because someone wired the supply and return sensors backwards.

Rhetorical question: Would you rather trust a dashboard that never blinks, or a $40 thermocouple and your own two eyes?

FAQ or Checklist in Prose

How long before I see savings?

Most people expect a magic switch—flip it, and the electric bill drops overnight. That’s not how passive tuning works. The building fabric itself is slow to respond. I have seen projects where the first week showed negative savings because the thermal mass was still dumping heat from the previous construction moisture. Real movement usually appears between three and six weeks. One deep retrofit I worked on took until week seven before the HVAC runtime curves started flattening. The trap here is checking daily: you’ll chase noise, not signal. Wait a full billing cycle. If nothing has shifted by week eight, your diagnosis step probably missed something—revisit the envelope, not the schedule.

What if I can’t change setpoints?

That sounds like a showstopper, and sometimes it's. But I have seen teams work around this by changing how the setpoints are served rather than the numbers themselves. Example: you can't touch the thermostat, but can you adjust the supply air temperature reset schedule? Or the economizer lockout? Those are operational parameters, not temperature targets. The catch is that if the building is locked by a green lease or a tenant contract, even those tweaks may need sign-off. Quick reality check—three months of submetered data proving that your current drift wastes 12% more energy than the path you want. That gets approvals moving faster than any spreadsheet promise.

Do I need a professional?

Wrong question. Better question: What stage can I do alone, and where do I need a second set of eyes? You can absolutely walk the building yourself, log runtime hours, and check filter pressure drops. Most teams skip that because it feels too simple—that hurts. What usually requires a pro is the control sequences: deciphering what the BAS is actually commanding versus what the schedule claims. I have seen a $2,000 commissioning agent catch a stuck economizer actuator that wasted $14,000 in cooling over two summers. That said, if your building is under 20,000 square feet and uses packaged rooftop units, an experienced facility manager with a clamp meter and a notepad can probably handle the full tune.

‘The cheapest fix is always the one you find by walking the plant room at 3 AM. The second cheapest is admitting you missed something.’

— retired commish engineer, after I watched him find a mis-wired sensor in fifteen minutes

Mental checklist before you call anyone: Have you ruled out simple filter loading? Checked that all zone dampers actually stroke fully closed? Compared last night’s setback temperature with the morning warm-up ramp? Most “I need a pro” moments dissolve when you confirm those three items. If they check out and the building still hums wrong, then yes—hire someone who owns a calibrated pressure gauge and knows how to interpret a psychrometric chart without squinting.

What to Do Next (Specific)

Schedule a follow-up review in 3 months

Pick a date now—write it on a wall calendar, set three phone alerts, whatever works. The carbon lock you just loosened can re-tighten if drift goes unchecked. Three months gives the building one full season cycle (spring or autumn) to reveal whether your tuning fix actually holds. I have seen teams wait twelve months, only to discover the original fault crept back during month four. That hurts. Schedule a half-day walkthrough with the same person who ran the initial diagnosis—continuity matters more than fresh eyes here.

Document every change in a log

Start a plain-text log today. One row per intervention: date, what you changed (damper position, setpoint offset, schedule override), and the outdoor conditions at that moment. No narrative essays—just facts. The catch is that most logs die after two weeks because people write too much. Keep entries under three lines. Include the before and after delta for your primary metric (kW per ton, supply-air temp, zone pressure—pick one). Wrong entries? Better than missing entries. You can correct a bad number later; you can't recover a lost one.

„We logged everything for six months, then stopped. The carbon spike returned in week 32. Without the log, we would have blamed the equipment, not our own skipped maintenance.“

— facilities engineer, mixed-use office retrofit, 2023

Share results with the design team

Send a one-page summary to the architects and MEP engineers who stamped the original drawings. Not a blame document—a calibration note. State what you found, what you fixed, and what the measured energy drop was. Quick reality check: most design teams never see post-occupancy data unless something catastrophically fails. Your 60-year carbon lock is exactly that failure, just slower. If you share the log alongside a simple graph (before vs. after weekly EUI), you give them permission to specify better sequences on the next project. That cascades. One concrete anecdote from your site can rewrite a spec section that otherwise stays frozen for a decade.

Don't send the full log. Nobody reads it. Send the highlight: „We lowered supply-air temperature reset by 4°F. Cooling energy dropped 18%. Zone comfort stayed within ASHRAE limits.“ Then offer the raw log to anyone who asks. Most won't ask. The one person who does will be the engineer who actually cares—give them everything.