FCC Waiver DA 26-789: Updates for Covered Robots

What DA 26-789 does for robots already in service

On July 28, 2026, the FCC added foreign produced advanced robotic devices to its Covered List. Covered equipment cannot receive new FCC equipment authorizations, according to K&L Gates and Steptoe coverage of the action. Waiver DA 26-789 softens that restriction for robots that already hold an authorization.

The waiver is an Office of Engineering and Technology waiver covering devices authorized before July 28, 2026. It lets those devices keep receiving software and firmware updates through at least January 1, 2029. That window is the core answer for any facility team asking whether its covered robots can still be maintained.

Treat the window as a limit on what the relief allows, not a general approval. The law firm and trade pieces we reviewed are search level summaries, and the order itself controls. The sections below explain what the summaries say, where they stop, and what to confirm before you decide.

Which updates qualify under the waiver

The waiver covers Class I and Class II permissive changes. Summaries describe qualifying updates as those that mitigate consumer harm, such as patches for vulnerabilities and compatibility fixes that let a device work with different operating systems. Security patches are the category most facility teams will care about.

Qualifying is not the same as unlimited. Squire Patton Boggs notes that grantees must still comply with other applicable FCC rules, so an update that fits the waiver can still raise a separate compliance question. Feature changes that do not fit the harm mitigation description should be treated as unresolved until the order is read.

The vocabulary in the coverage is loose. Law firm pieces describe the relief as blanket updates, while consumer focused coverage calls it basic firmware updates. Neither phrase is defined in the excerpts we saw, so do not assume either one carries the legal weight of the order text.

Why the term new model stays undefined

The Gadgeteer's July 30, 2026 coverage says the waiver does not authorize new models. That matters for fleet planning. A replacement unit or a refreshed hardware revision may fall outside the update window even when the unit it replaces is covered.

We could not find a definition of new model in the excerpts we reviewed. A unit carrying the same product name may be treated differently from one with a changed hardware revision, and no summary we read says where that line falls. Treat any model change as an open question until the order or a written FCC answer settles it.

A separate route exists. According to one summary, a company can seek conditional approval, and only the Department of War can determine that a device or class is not a national security risk. The FCC would then update the list. We did not verify that process against the order, so describe it as a summary claim if you repeat it.

What to confirm with a vendor before a lease decision

Put these questions to the vendor in writing. The answers will tell you more about your exposure than the headline waiver does, and they belong in any robot lease financing discussion.

A three year robot lease signed in late 2026 runs past January 1, 2029. That makes the update window part of the lease term itself, not a regulatory footnote.

• Which FCC authorization and grant date cover each model in the fleet, and whether any unit was authorized on or after July 28, 2026.
• Whether the vendor commits to security patches and compatibility fixes after January 1, 2029, and what happens if it cannot.
• How the vendor classifies each update, and which changes it treats as a new model.
• What replacement or swap terms apply if a unit loses update eligibility during the lease.
• Which service engineers install updates, and how your site is notified before a change touches a running robot.

How a later FCC waiver changes the picture

A Wiley alert dated October 27, 2026 reports that OET granted a waiver allowing hardware modifications to a grandfathered robotics product to Intel, described as the first robotics waiver of its kind. Wiley describes the grant as company specific. It is not a change to the update waiver.

Read it as evidence that the FCC handles robotics relief case by case. It is not a template a facility can apply to its own fleet, and it should not be cited as general permission for hardware changes.

How to verify the rules before any decision

Start with the order itself, DA 26-789, and the FCC Covered List entry for the robot category. We ran two searches and did not open the order for this article, so our summaries are pointers, not proof. Have counsel read the definitions, the dates and the scope language.

Next, check the FCC ID printed on each unit and confirm its grant date against the July 28, 2026 cutoff. Keep the grant records with the fleet file, so any later update question starts from documents rather than memory.

Where Service Robot Co. fits in a covered fleet decision

Service Robot Co. is a vendor neutral robot integrator. We lease commercial robots through financing on a three year lease, with one fixed robot lease payment quoted after a site assessment. We deploy, integrate, train and service every unit under RoboCare, our robot maintenance service plan, backed by regional service engineers in every state we service.

Because the update question is a fleet level question, ask it before signing. Put the vendor questions above to every integrator in your evaluation, including us. A clear answer on authorization dates and update commitments is worth more than a quote that looks complete but leaves the window unexplained.