Golden Relay

The record that determines
your warranty outcome was
formed at installation.

Warranty claims are adjudicated months after execution closes. The startup sheet, commissioning data, and closeout package from that installation — in whatever condition they are in — determine what your organization can defend, and what it absorbs.

For the first time, AI-assisted record analysis makes it possible to know the composition of that exposure before the next review cycle begins — not after.

AI-assisted technical review, with human judgment reserved for higher-consequence cases.

Request Executive Brief
HVAC technician working on rooftop commercial condensing units Commercial rooftop installation — startup record formation
The financial picture — publicly disclosed
$675M
Annual warranty claims paid by major U.S. HVAC manufacturers — publicly disclosed in quarterly financial statements. The number moves year-over-year. Investors watch it. Peers watch it.
Source: Public 10-Q filings, U.S. HVAC manufacturers
0.9%
Long-term industry accrual rate as a share of product revenue. For a $10B OEM, that is $90M reserved annually — a number that has held stable across two decades.
Source: Long-term average, U.S. HVAC manufacturer public filings
Unknown
The portion of that expense that is recoverable — claims absorbed not because of product failure, but because records could not support a technical defense. This has never been measurable. Until now.
The gap Golden Relay closes
The moment nobody talks about

Every warranty claim begins at a desk, not at a rooftop unit. Someone opens a file. They need the startup commissioning sheet from an installation that closed eighteen months ago. What happens next determines the financial outcome — and it has nothing to do with whether the installation was correct.

HVAC technician recording startup data on tablet at outdoor condenser unit Startup data recorded at execution — the record that will determine review outcomes months later

A warranty claim arrives. Compressor failure, twenty-five ton rooftop unit, eighteen months post-installation. The warranty team contacts the installing contractor. The original field technician has left the company. The project manager remembers the job vaguely. The commissioning sheet — refrigerant charge, superheat, subcooling, electrical readings — was filed in a field service app that was migrated to a new platform eight months ago. Historical records did not fully transfer.

They find a photo of a handwritten sheet in an email thread. The serial number does not exactly match the unit number in the claim file. The refrigerant readings are partially legible.

The warranty team has three options: contest the claim with incomplete documentation, commission a field inspection eighteen months after the fact, or settle.

They settle. The claim is $4,200. Multiply this across a quarter. Multiply the settled fraction across a fiscal year. Now try to tell the CFO how much of that number was this kind of settlement, versus claims the organization genuinely could not have defended.

You cannot. Nobody can. That distinction has never been possible to make at scale. Until now.

Why this is not an operations problem

The gap is structural. No checklist closes it.

Field operations owns execution. Warranty and quality functions own review. The fitness of records for downstream use — their ability to support a judgment made by a stranger, months later, in an adversarial context — is owned by neither. It is no one's KPI. The problem persists not because organizations are careless, but because the function that would prevent it does not exist.

Record fragmentation

A commercial HVAC installation generates records across the general contractor's project management platform, the BAS/BMS, the OEM service portal, the distributor's ERP, the subcontractor's field service app, and email attachments. None of these systems communicate with each other. None were designed with a warranty reviewer in mind.

The time gap

The interval between execution and review is typically six to twenty-four months. Within that window, field teams turn over, subcontractors move to other projects, and systems are migrated. The institutional context that made an informal record interpretable no longer exists when the claim arrives.

The ownership gap

No function within a mature HVAC organization owns record usability for downstream review. Field operations delivers the installation. Warranty and quality teams receive the record months later. Whether the record will hold up under scrutiny belongs to no one's accountability structure.

The reporting gap

Warranty P&L contains two fundamentally different cost types: claims driven by genuine product issues, and claims absorbed because records could not support a defense. These have different remediation paths. In current reporting, they appear as a single line item. The composition has never been visible.

What governance failure actually costs

The following are composite scenarios drawn from patterns common in mature HVAC environments. The financial loss is visible in the expense line. The legal exposure compounds it. Root cause in each case: a governance layer without the information required to make defensible judgments.

HVAC technician working on electrical connections at condenser unit Field execution — the moment the record is formed
Case A — Warranty + Legal Exposure
The compressor that couldn't be defended — and the lawsuit that followed

A warranty claim arrives: compressor failure, eighteen months post-installation. The OEM's warranty team requests the original startup commissioning sheet. The installing contractor was acquired eight months prior; historical records did not fully migrate. A photo of a handwritten sheet surfaces in an email thread. Serial number does not cleanly match. Refrigerant readings are partially legible.

Without startup data, the OEM cannot establish original refrigerant charge. The contractor asserts the charge was correct. The OEM settles: full compressor replacement plus labor. $11,400.

Three months later, the building owner files against the installing contractor for business interruption during the repair window. The contractor's insurance carrier requests OEM commissioning records. The OEM's file contains a settlement agreement and a note that startup documentation was unavailable. The carrier uses the OEM's inability to establish original installation conditions as partial basis for arguing contributing OEM responsibility. The OEM is drawn into litigation it did not anticipate.

Total exposure: Equipment replacement, legal defense costs, management time. Root cause: no retrievable startup record. The claim was settled not on technical merit, but on documentation absence.
Case B — Channel Program Liability
Extended warranty sold without a verifiable installation baseline

A national OEM operates a preferred installer channel program. Certified installers can offer ten-year extended warranty coverage as a competitive selling point. The program requires startup commissioning documentation uploaded to the OEM portal within 90 days of installation.

An audit two years after launch: 34% of installations enrolled in the extended program have incomplete or missing startup documentation. The warranties were sold. The documentation is not there.

The OEM's legal team raises the question: if a claim is filed on these installations and commissioning documentation cannot be produced, what is the liability exposure for having issued extended warranty coverage without verifying the installation met program requirements? No clean answer exists. Outside counsel recommends a reserve increase. The channel program is suspended. Remediation — recontacting hundreds of contractors — takes seven months.

Total exposure: Reserve increase, seven-month channel program suspension, legal advisory costs, dealer relationship damage. Root cause: no systematic record verification at program enrollment.
Case C — Quality Exception + Class Action Exposure
A failure pattern that could not be investigated — or defended

An OEM identifies a pattern of early-cycle failures in a specific product line across a regional market. Internal quality review determines the pattern is inconsistent with manufacturing defect — likely installation conditions or incorrect startup procedures.

To establish root cause, they need startup commissioning data from the affected installations. The data spans eighteen months, four distributors, sixty installing contractors. Retrieval takes eleven weeks. Records return in nine different formats from eleven different systems. Forty percent of affected installations have no retrievable startup data.

The OEM cannot determine root cause with statistical confidence. They cannot exonerate their product. During the investigation, a class action firm files a demand letter requesting all startup and commissioning documentation. The OEM's counsel responds with partial records for some units, nothing for others. The absence of records — which would have established installation anomalies — means the OEM cannot efficiently defend. Settlement becomes the path of least resistance.

Total exposure: Warranty costs across the cohort, class action settlement, eleven weeks of quality investigation without conclusion. Root cause: no accessible, normalized startup record across the installation base. The product may have been exonerated by the data. The data was not there.
What Golden Relay does

AI-assisted technical review of the record landscape your warranty decisions depend on.

AI-assisted aggregation, normalization, and analysis — with human judgment reserved for higher-consequence determinations. Not manual: the volume makes that impossible. Not fully automated: the consequence level does not permit it.

01 — Aggregation
Record ingestion across systems
Startup sheets, commissioning data, closeout packages, field notes, and supporting documentation drawn from whatever systems the organization and its installer network use — without requiring those systems to change. BAS exports, contractor field service apps, distributor portals, PDF attachments, project management platforms.
02 — Normalization
Standard field contract schema
Records from disparate formats and systems are normalized against a standard equipment and installation schema. A commissioning sheet from one contractor's app becomes directly comparable to a startup report from another contractor's platform. Equipment identifiers are reconciled against warranty claim serial numbers.
03 — Continuity analysis
Record integrity assessment
Each record is assessed for completeness against original design specification, continuity from startup through closeout, equipment-level traceability, and temporal integrity — whether the record can be verified as unmodified from the time of execution.
04 — Claim comparison
Record-to-claim cross-reference
Where warranty or quality review data exists, records are cross-referenced against claim conditions systematically — establishing the technical basis, or its absence, for each claim category. Refrigerant charge at commissioning versus claimed failure mode. Electrical readings versus environmental conditions at time of failure.
05 — Classification
Governance landscape map
The record landscape is classified into defensible, ambiguous, and exposed — across the entire scoped installation cohort. Each category implies a different financial trajectory and a different management response. This map, at scale, is information that does not currently exist in any OEM's warranty management process.
The three-category framework

For the first time: a map of what you can defend, what is uncertain, and what you will absorb.

Every installation in the scoped base is classified. The distribution across a product line, a channel cohort, or a deployment year is the governance information that has never existed before.

Defensible

Records clearly support the organization's technical position. Startup and commissioning data is complete, traceable, and consistent with design specification. Claims in this category can be contested on technical merit. This is the recoverable portion of warranty expense.

Ambiguous

Records are partial, degraded, or inconsistently linked to equipment. The technical case is not clear from the record alone. Targeted remediation — retrieving supplementary records, field verification — may shift the category before the claim is adjudicated.

Exposed

Records are insufficient to support any technical judgment. Claims will result in cost absorption regardless of what occurred at installation. For the exposed cohort, the relevant question shifts from claim defense to root cause — what in the process consistently produces unusable records.

Engagement model

A bounded technical assessment. Scoped, concluded, built to produce one thing: decision-relevant information.

Scope Defined by a specific installation cohort — a product line, a channel program, a regional market, a deployment year. Work is bounded by actual record conditions present in the organization's systems. Not a generic governance framework. An assessment of what exists and what it supports.
Method AI-assisted aggregation and technical analysis across the scoped record base, with human judgment at consequence-bearing decision points. Typical initial engagement: six to eight weeks from scoping to delivered brief. Designed to be completed and concluded — not to create ongoing dependency.
Deliverable Executive Brief supported by: Record Continuity Report (record-level findings across the cohort), Ambiguity and Exception Flags Register (specific items requiring attention), Review-Readiness Analysis (landscape classification — defensible, ambiguous, exposed), and Decision-Support Notes for high-consequence active claims.
What this is not A software deployment. A field operations change program. A training initiative. A long-term consulting retainer. The engagement produces information that does not currently exist in the organization's management view: the composition of warranty and quality cost exposure mapped against actual record conditions.
Executive Brief

The brief is where the conversation starts.

A concise, non-generic document for VP Warranty, VP Quality, or equivalent — covering current record conditions in mature HVAC environments, the exposure profile relevant to your organization's structure and installation base, and the criteria for a scoped assessment engagement. Not a proposal. The starting point for an informed decision.