Launching a robotics customer pilot: an insurance and safety-record checklist

A signed pilot can move a prototype into a workplace where customer employees, visitors, contractors, and the startup team may all interact with it. The first task is to describe the machine and site activity as they actually will occur, not as the product roadmap describes a future release. Put the date, entity, locations, product version, and customer role into the commercial insurance file before presenting the account to the market.

For robotics and hardware startups, the important detail is usually not the company label but the work being done today: prototype testing, a customer pilot, contract manufacturing, equipment transit, installation, remote support, or a production launch. Separate current work from plans that have not begun.

A startup insurance review should identify who owns the physical product, who has custody, who operates it, who controls the customer site, and who may make a decision after an incident. The answer can change between a lab, a warehouse, a third-party manufacturer, and an enterprise pilot.

Read the customer, supplier, integrator, and lease agreements alongside that map. Insurance requirements, indemnity clauses, limitation-of-liability language, certificates, and additional-insured requests should be captured as exact document questions, not summarized as a general contract obligation.

Retain the statement of work, safety assessment, product and software version, site diagram, installation plan, training record, maintenance split, remote-access roles, shipping and custody documents, insurance exhibit, and named escalation contacts. Keep contracts, schedules, values, and internal ownership of each fact together so follow-up questions can be answered consistently.

A dated record also separates current facts from planned activities, which matters when a prototype, pilot, or production program changes quickly. Use versioned product descriptions, equipment lists, current policy documents, and a short change log rather than reconstructing the account at renewal.

Business insurance decisions are stronger when property values and continuity planning are reviewed together. Identify critical equipment, replacement lead times, alternate suppliers, available spare capacity, customer commitments, and the operational cost of a delayed test or shipment.

This exercise does not determine whether a future interruption is covered. It gives the market a clear account of the operational dependencies that may matter when commercial property, inland marine, cyber liability, or time-element terms are compared.

Compare the pilot activity with the issued liability, product, property, inland marine, cyber, and any professional-services terms that were actually purchased. Record unresolved contract requests rather than interpreting a certificate as proof that every requirement has been met. Read the declarations, form, schedule, conditions, and endorsements rather than relying on a certificate or proposal headline.

Compare limits and deductibles or retentions with named insureds, scheduled locations, sublimits, definitions, exclusions, reporting requirements, notice conditions, and any subjectivities. A lower premium can reflect different values, different operations, or different terms rather than a like-for-like proposal.

Keep the final application, quote comparison, bind information, declarations, endorsements, certificates, and written market answers in one controlled record. Financing, procurement, customer, and board stakeholders often need different pieces of the same commercial insurance evidence.

Before a renewal or material business change, ask which facts have changed, which contract requirements are new, which values are stale, and which open question needs a direct policy answer. That process keeps the startup insurance program aligned with the business without promising a particular claim result.

Retain the final submission, terms compared, open questions, and decision record. Revisit the file when the company raises capital, changes a product, adds a customer commitment, moves equipment, or starts a new production run.

Stanford Coverage organizes the account, approaches the market, and explains the differences in the options presented. Issued policy wording, declarations, endorsements, and the facts of a future event control.

Write down the legal entity, customer, site address, pilot dates, number and model of units, hardware and firmware versions, intended tasks, operating envelope, human supervision, charging or power arrangement, and whether the robot is autonomous, teleoperated, or manually controlled. Identify who installs, trains, maintains, updates, retrieves, and can stop the equipment. This description should match the contract, internal safety record, insurance application, and customer-facing deployment plan; differences are a cue to pause and resolve the facts.

A pilot is not merely a sales demo. If the team moves from a controlled lab to a loading dock, hospital, or warehouse, the people and property exposed may change. Record barriers, signage, training, emergency-stop access, and site rules with the customer before operation. OSHA’s industrial-robot guidance is a useful hazard-identification reference, but the applicable obligations depend on the workplace and roles.

Copy each insurance requirement from the customer exhibit into a table with requested line, limit, insured entity, additional-insured wording, waiver, primary-and-noncontributory language, evidence deadline, and the person responsible for an answer. Beside it, identify the actual policy or endorsement, whether it has been issued, and any discrepancy. A certificate can summarize information; it does not itself add coverage or change an exclusion.

Keep indemnity, warranty, uptime, data-security, and limitation-of-liability clauses in the same review packet, but do not assume an insurance policy funds every contractual promise. Ask counsel and the insurance professional to review the interaction when the pilot contract transfers duties that are broader than the insured operations or when the startup agrees to control a customer site it does not actually control.

Map the device’s connectivity, administrator access, update channel, telemetry, cloud dependency, customer network boundary, and authority to pause or roll back an update. Ask the customer who approves access and what logs are retained. NIST’s operational-technology security guide is a useful framework for connected operational systems, not a substitute for a device-specific assessment.

Compare the cyber submission with the pilot facts. If the application says there is no remote access but engineers can support devices over a VPN, correct the factual record before relying on a proposal. Also identify whether an incident could involve bodily injury, physical damage, software service failure, privacy data, or several together; the relevant policy definitions and exclusions may differ.

Before shipment, have named owners sign off on the pilot scope, safety controls, equipment value and transit method, customer insurance exhibit, issued policy documents, certificate and requested endorsements, support plan, and emergency contact list. Mark each item complete, conditional, or unresolved. Keep the record tied to the product version and site, because a later software update or added work area can make the original handoff stale.

If a material request cannot be met, obtain a written contract amendment or make an explicit business decision with appropriate advisers; do not simply send a certificate that looks similar. Reopen the checklist when the pilot grows into a commercial deployment, a second site, new operating hours, or a changed product capability. Issued wording and the event facts control any insurance response.