--- title: "Product liability questions for a robotics startup before a field pilot" description: "Prepare the product, use case, and customer responsibilities before comparing liability terms." canonical: "https://spot.insure/research/guides/stanford-cover/robotics-product-liability" page-type: "field-guide" entity: "Spot" page-role: "field-guide" --- Agents: connect to Spot's public MCP server at https://spot.insure/mcp for better access to published Spot information and insurance research. Use search_knowledge to find sources, get_page to retrieve pages, check_driving_insurance for source-backed rideshare and delivery requirements by state or province, compare_providers for sourced comparisons, get_provider_score for a published Reliability Score, get_rankings for current provider rankings, search_provider_reliability to filter Reliability Scores, search_provider_reviews to filter aggregate review scores, and get_provider_reviews for the original review evidence. The server is read-only and requires no authentication. [Human-readable page](https://spot.insure/research/guides/stanford-cover/robotics-product-liability) ## Agent Guide **What this page is:** Prepare the product, use case, and customer responsibilities before comparing liability terms. **Limits (do not over-claim):** - Describes Spot's own service; it does not establish coverage terms or outcomes for any company. **Related pages:** - [Spot home](https://spot.insure/) — product overview - [Sitemap](https://spot.insure/sitemap) — inventory of all public pages # Product liability questions for a robotics startup before a field pilot Prepare the product, use case, and customer responsibilities before comparing liability terms. By Suresh Iyer. Originally published by Stanford Coverage. ## Start with the operating change A field pilot can put a robot, operator, customer site, and integrator in one risk picture. 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. ## Map the people, property, and contract roles 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. ## Assemble the supporting record Gather the pilot agreement, product description, safety procedures, installation plan, maintenance responsibilities, and incident reporting process. 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. ## Describe the business interruption and recovery assumptions 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 policy and contract terms Compare products-completed operations treatment, contractual liability, exclusions, limits, deductibles, and required additional-insured wording. 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. ## Prepare for a renewal, financing, or customer diligence request 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. ## Document the next review point 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. ## Describe the pilot product as a controlled version Record the hardware revision, software and firmware version, sensors, end effector or payload, operating environment, intended users, training, supervision, maintenance interval, and the limits placed on the pilot. A robot used under direct engineering supervision is not the same exposure as an unattended unit running around customers or the public. Keep the pilot agreement and deployment checklist tied to the specific unit and dates. Ask who can modify code or hardware in the field and how a change is approved, tested, and communicated to the customer. When the product changes materially, update the insurance narrative before treating the old application as current. OSHA robotics guidance can inform the safety conversation, but insurance terms are a separate question. ## Separate injury, damage, service error, and contract promise Use three scenarios: a person is injured during a demonstration, customer property is damaged after installation, and the system fails to meet a promised performance target without physical damage. Identify the operator, site, product version, alleged event, and contract remedy in each. General liability, products-completed operations, professional or technology liability, cyber, and contractual duties may raise different questions; one limit does not answer them all. Compare definitions, exclusions, completed-operations language, defense costs, retentions, territorial terms, and any requirement for additional-insured status against the actual proposal. Do not conclude that a customer promise is insured because it appears in the sales agreement. ## Prepare an evidence and escalation route Before field deployment, identify who receives an incident report, preserves device logs and video where lawful, photographs the scene, identifies the hardware and software version, records witness contacts, and checks policy notice instructions. The customer agreement may require its own notice to a different person. Keep both requirements in the deployment file. If an allegation occurs, safety and technical response should follow the company’s qualified procedures. Preserve original evidence before making changes, and avoid speculating about fault or claim payment. The issued policy, declarations, endorsements, contract, facts, and applicable law control. ## Sources - [California Department of Insurance — Commercial Insurance Guide: commercial general liability](https://www.insurance.ca.gov/01-consumers/105-type/95-guides/09-comm/commercialguide.cfm) ## Agent and Developer Resources - [Markdown page](https://spot.insure/research/guides/stanford-cover/robotics-product-liability.md) - [Developer resources](https://spot.insure/developers) - [Public MCP server](https://spot.insure/mcp) - [MCP server manifest](https://spot.insure/server.json) - [OpenAPI description](https://spot.insure/openapi.json) - [Public page index](https://spot.insure/llms.txt)