Reading a Robots-as-a-Service Contract: Uptime, Exit, and the Clauses That Cost You

The Gap Between the Pitch and the Paper

Robots-as-a-Service is sold on flexibility: no capital outlay, no ownership risk, cancel if it does not work. Having read a number of these agreements as they are actually written, the paper is considerably less flexible than the pitch. That is not a scandal — a vendor financing hardware onto your floor needs term certainty, and the economics do not work otherwise. But a buyer who signs believing they have bought optionality is going to be surprised at month nine.

This guide walks the clauses that matter, with the caveat that terms vary and that a summary of what is common is not a substitute for your own counsel reading your own agreement. Where something is well documented we say so; where it is our view about what a buyer should push for, we say that too.

Uptime Is Usually Not in the Contract at All

This is the single most useful thing to know before you negotiate. Field-robot subscription agreements, as commonly drafted, do not commit to an availability percentage. They commit to effort. The recurring formulation is that the vendor will use commercially reasonable efforts to support the equipment and maintain accessibility, often paired with an express statement that the vendor makes no representation of availability and does not warrant that use will be uninterrupted or error free.

Meanwhile the marketing material may cite 97% or 99.5% uptime. Those figures generally live on a website, not in the agreement. Ask for the number to be written into the contract and you will quickly learn whether it was ever a commitment.

Where remedies do exist, they tend to be thin. Two documented structures give the flavour: one agreement triggers a credit only when equipment is offline for more than three consecutive business days, and then applies that credit at the commencement of the next renewal term — so it has value only if you renew. Another gives a credit when maintenance suspends service for more than 48 hours. Both are worth improving on, and both are improvable.

Three things to push for. First, define availability at the task level, not the platform level — completed scheduled runs as a percentage of scheduled runs is what you actually care about, and it is measurable from data the vendor already has. A robot whose management interface is up while the machine sits in a lift lobby is not available in any sense that matters to you. Second, make credits creditable against the current invoice, in cash terms, not against a renewal you may not want. Third, add a chronic failure right — if a unit misses its committed level in, say, three months of any rolling twelve, you can require a replacement unit or exit that unit without penalty.

Also read the exclusions, because they are where an uptime number goes to die. Standard carve-outs include scheduled maintenance, emergency maintenance, force majeure, third-party network and power failures, misuse, and — specific to robots and easy to miss — customer failure to grant physical access. That last one is reasonable in principle and a trap in practice: if your ward is busy and the technician cannot get to the unit, the clock may stop. Agree what constitutes reasonable access in advance.

Response Times, and the Words “Where Available”

Response time is more commonly committed than uptime, and it is normally tiered. A representative published structure runs from a basic tier at two business days for remote response with no on-site component, through one business day, to 24 hours with on-site included, to a premium tier at four hours remote with same-day or next-day on-site. Industrial service agreements elsewhere in robotics publish on-site response bands of roughly four to 48 hours by tier.

The phrase to interrogate is “where available.” On-site response in this industry is almost always geography-conditioned, and the contract rarely lists the geography. If you operate across several sites, confirm the on-site commitment per address and get it in an appendix. A four-hour on-site commitment that applies to your flagship building and not to the three regional sites is a materially different product from the one you thought you bought.

Ask also who holds spares and where. A four-hour response by a technician who then waits nine days for a part is a four-hour response in name only. We would put parts availability, not just response time, into the service schedule.

Renewal, Exit, and the Acceleration Clause

Renewal is usually evergreen. The common structure auto-renews for successive one-year periods unless either party gives notice — frequently 30 days. Miss the window and you are bound for another year. Put the non-renewal date in a calendar the day you sign, and note that price-increase notice windows often close before the renewal-notice deadline, so they need tracking separately.

Early exit is usually full acceleration. This is the clause that most contradicts the flexibility pitch. The typical drafting is that if the vendor terminates for your breach, or you terminate without cause, you remain liable for all payments that would have fallen due during the then-current term. Economically that is a stipulated-loss provision: the remaining term is the remaining term. If someone tells you a RaaS agreement is cancellable, ask them to show you the clause.

Purchase options are not standard. In the agreements we have reviewed there is no buyout right at all, and the ownership position is stated affirmatively — the equipment is loaned, the software licensed, and neither is sold. A purchase option is something to ask for at negotiation, not something you will be offered. If end-of-term ownership matters to you, raise it in the first commercial conversation, because it changes the structure.

Return condition is conventionally “good condition and working order, ordinary wear and tear excepted, substantially as at commencement.” Interestingly, the RaaS agreements we have read contain no restocking or refurbishment fee — those come from the traditional equipment-lease world, where return-condition charges and damage-fee schedules are normal. If a RaaS quote includes a refurbishment fee, it is worth asking what it is for.

Escalators and the Renewal Repricing

A useful finding: the RaaS agreements we have reviewed contain no automatic in-term escalator. The price risk is not mid-term, it is at renewal, where upgrades and continuations are priced at the vendor’s then-current rates. In other words the renewal is a repricing event by default.

If you do accept a CPI-linked escalator, the Bureau of Labor Statistics is unusually direct about what a clause must specify to be unambiguous: the population group, the item category, the geographic area, and the reference base. Its recommended full specification for the broadest measure is “the Consumer Price Index for All Urban Consumers (CPI-U); U.S. City Average; All items, not seasonally adjusted, 1982–1984=100 reference base.” BLS also advises using not-seasonally-adjusted data, because seasonally adjusted series are revised annually, and expressly addressing floors and ceilings.

The two words that carry the money are greater and lesser. “The greater of 3% or CPI” guarantees you a 3% floor. “The lesser of 3% or CPI” caps your exposure. Buyer-side language worth proposing: any increase shall not exceed the lesser of three percent per annum or the increase in CPI-U over the trailing twelve months.

One documented data point on payment timing: at least one vendor prices monthly billing at a 10% premium over prepayment for the term. That is a rare published figure for the implied cost of capital sitting inside a RaaS rate, and it is a fair reference when you are weighing prepayment against holding your cash.

How Your Finance Team Will Look at It

General information, not accounting advice. Whether a specific agreement is or contains a lease is a facts-and-circumstances judgment for your own accountants and auditors. What follows describes how the standard is structured so you can ask better questions at the drafting stage — which is the only stage where the structure can still change.

Under ASC 842 a contract is or contains a lease if it conveys the right to control the use of an identified asset for a period in exchange for consideration. Three points matter for robots specifically, and each surprises people:

• A swap-on-failure provision does not make the asset unidentified. A substitution right defeats the identified-asset test only if the supplier has the practical ability to substitute throughout the period and would benefit economically from doing so. A right to replace a defective unit does not qualify, and a substitution right requiring your approval does not qualify either. Where you cannot readily determine whether a right is substantive, the standard directs that you presume it is not.
• Vendor maintenance and remote operation do not, by themselves, prevent lease treatment. Rights to operate or maintain an asset are not rights to direct how and for what purpose it is used. If you decide when the robot runs, what it carries and where it goes, the direction test tends to point toward a lease.
• The 12-month line is the practical lever. The short-term lease exemption lets a lessee elect, by class of underlying asset, not to recognise leases of twelve months or less with no purchase option reasonably certain of exercise. This is the single cleanest way to keep a genuine pilot off the balance sheet — and it is another reason to structure a first deployment as a short term with an option to extend, rather than a three-year commitment.

Where the arrangement is a lease with a term over twelve months, both finance and operating classifications put a right-of-use asset and a lease liability on the balance sheet. The income statement differs — amortization plus interest for a finance lease, a single straight-line cost for an operating lease — but the balance sheet entry appears either way. A vendor’s statement that the equipment is “loaned, not sold” or that “this is not a lease” does not control the accounting.

The one thing to ask for at quote stage, and it costs the vendor nothing: break the monthly rate into hardware, software and service components. Maintenance and operating services are non-lease components, allocated on relative standalone prices. If the quote is a single blended number you have no standalone prices to allocate against, and the practical alternative — electing to combine lease and non-lease components — grosses up the right-of-use asset and liability because the service portion gets capitalized too. Asking for a three-line rate at quote stage is free. Asking after signature is not.

Data and Telemetry: the Two Buckets

Robot agreements consistently split data into two buckets, and the split is more consequential than it first appears. The customer typically owns the capture — audio, video, incident reporting data from the deployment. The vendor typically owns the telemetry — everything else the machine and platform generate. In at least one published agreement the vendor’s machine data is expressly not accessible or provided to the client at all.

For a hospital or campus that wants operational analytics — utilisation, route efficiency, dwell time, where the robot actually waits — that data is the vendor’s property under the standard form. If you want it, negotiate for it explicitly, ideally as a defined reporting deliverable rather than as raw access.

Retention windows are shorter than people expect. Documented examples include a two-week download window for captured content, after which the vendor may delete at its discretion, and a 120-day retention elsewhere — with deletion on termination and post-termination retention available only for a fee. Anyone relying on robot footage for incident investigation, litigation hold or accreditation documentation needs those windows extended in writing.

Watch also for a product-improvement licence — vendor rights to use your captured data to “debug, improve and enhance” the service. In healthcare and education that clause deserves a constraint: no model training on your data, or de-identified only, with an express carve-out.

Healthcare. A vendor that creates, receives, maintains or transmits protected health information on your behalf is a business associate and needs a BAA with the content required at 45 CFR 164.504(e). The conduit exception is narrow — entities that access PHI on a regular or frequent basis to perform a service are not conduits — so a robot storing video of patient areas or transporting specimens is unlikely to escape it. Note that the flow-down to the vendor’s cloud host and remote-operations subcontractors is the vendor’s obligation, not yours.

Education. A vendor with access to personally identifiable information from education records qualifies under the FERPA school official exception only if it performs an institutional service, meets the legitimate-educational-interest criteria in your annual notification, is under your direct control as to use and maintenance of records, and does not redisclose. The Student Data Privacy Consortium’s National Data Privacy Agreement is the closest thing to a market standard here and gives you concrete numbers to hold a vendor to — district ownership of student data, no sale, targeted advertising strictly prohibited, breach notification within 72 hours of confirmation, and return or destruction within 60 days of request or termination.

Title, Risk of Loss and Insurance

Vendor-owned equipment on your premises creates a set of exposures that facility teams routinely miss.

Title. Agreements assert absolute retained ownership, typically with an express carve-out stating the equipment remains the vendor’s property even if installed or attached to real property. That matters for facilities work — a charging dock bolted to a wall does not become the building owner’s. If you lease your building, a landlord waiver is worth considering.

Risk of loss. You will usually carry replacement-cost liability where loss or damage results from your negligence or a failure to keep the equipment reasonably secure. One published agreement caps that exposure at 24 months of subscription fees; another leaves it uncapped. That cap is the most useful benchmark we have found in this section, and it is a reasonable thing to ask for. Look too at how “reasonably secure” is defined — it is often circular, and it is the trigger for your exposure.

Third-party damage. A documented approach repairs the first occurrence of third-party damage at the vendor’s expense and charges subsequent occurrences to you. For a public hospital lobby or an open campus, one free incident is thin. Expand it.

Insurance. Notably, RaaS forms are often silent on insurance even while imposing replacement-cost liability. Conventional practice for lessor-owned equipment is all-risk physical damage cover at full replacement cost, commercial general liability on an occurrence basis with combined single limits commonly seen at $1M, $2M or $3M depending on scale, the owner named as loss payee and additional insured, and a waiver of subrogation. The gap most facility policies have is coverage for property of others in your care, custody or control — confirm the robot is either scheduled or falls under that endorsement, and reconcile the amount insured against whatever cap the contract sets.

Indemnity. The better forms are mutual and narrowly scoped — each party indemnifies for third-party claims of injury or property damage directly caused by that party, for its own gross negligence or wilful misconduct, and for its own legal non-compliance, plus a vendor IP indemnity. For robots operating around patients, students and the public, press for an explicit vendor indemnity covering bodily injury caused by the robot’s autonomous operation or a software defect. Neither of the forms we have read clearly provides this, and an autonomy failure does not sit cleanly inside “directly caused by that party or its personnel.”

A Redline Checklist

Fourteen things to take into the negotiation:

1. Availability defined as completed scheduled runs over scheduled runs, with a stated percentage
2. Credits applied to the current invoice, not a renewal term
3. Chronic-failure right to a replacement unit or a penalty-free exit for that unit
4. Access-failure exclusion defined, with agreed access windows
5. On-site response committed per site address, listed in an appendix
6. Spare parts availability, not just technician response time
7. Non-renewal notice window diarised, and the price-notice window diarised separately
8. Early-exit terms understood as acceleration, and priced accordingly
9. Purchase option raised explicitly if end-of-term ownership matters
10. Escalator capped with “lesser of,” CPI specified the way BLS recommends
11. Rate broken into hardware, software and service at quote stage
12. Operational telemetry provided to you as a defined reporting deliverable
13. Retention windows extended to match your incident and accreditation needs; BAA or FERPA terms attached
14. Replacement-cost exposure capped; insurance reconciled to the cap; vendor indemnity for autonomous-operation injury

Not every item will be conceded, and a vendor who concedes all fourteen without discussion may not have thought about any of them. What matters is that the conversation happens before signature, when the terms are still terms rather than facts.