--- title: "Robotics field incident: what product and insurance records should a startup preserve?" description: "A structured first-day record helps a hardware team protect people, preserve facts, and route notifications without guessing at fault or coverage." canonical: "https://spot.insure/research/guides/stanford-cover/robotics-field-incident-documentation" 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-field-incident-documentation) ## Agent Guide **What this page is:** A structured first-day record helps a hardware team protect people, preserve facts, and route notifications without guessing at fault or coverage. **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 # Robotics field incident: what product and insurance records should a startup preserve? A structured first-day record helps a hardware team protect people, preserve facts, and route notifications without guessing at fault or coverage. By Meera Krishnan. Originally published by Stanford Coverage. ## Start with the operating change A customer reports that a deployed robot stopped unexpectedly, damaged property, or may have injured someone. Immediate safety and emergency response come first. Then the company needs a controlled factual record of the event, device state, people involved, and contractual notice paths. 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 Preserve the customer report, timestamps, device and software identifiers, relevant logs, telemetry, photographs, scene conditions, maintenance and service history, training record, witnesses, shipping and custody facts, and all communications. Restrict changes to the device or logs according to the safety and evidence-preservation plan. 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 Review notice and consent terms across the policies and customer agreement with qualified advisers. A product complaint, cyber event, workplace injury, or property loss can involve different facts and different reporting duties; do not assume that one notice automatically satisfies every requirement. 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. ## Separate immediate response from later conclusions Prioritize emergency care, stopping or isolating equipment safely, and preventing a second injury or loss. Record who made each safety decision and when. Do not delay required emergency or workplace reporting to finish an insurance file. Once the scene is safe, designate one evidence custodian and one communications lead so well-meaning team members do not overwrite logs, make inconsistent statements, or repair the unit before its condition is documented. Write a short factual chronology: first report, observed condition, last known normal operation, people present, actions taken, customer contact, and any change to the device after the event. Distinguish direct observations from a customer allegation, internal hypothesis, or preliminary engineering analysis. That distinction matters when a later investigation revises the sequence. ## Preserve the product and site record Capture serial number, model, configuration, firmware and software hashes or version identifiers, installed attachments, maintenance and update history, operator training, service tickets, customer instructions, and prior similar complaints. Export relevant telemetry and access logs with timestamps and time-zone information, preserving original files and a record of who copied them. Photograph the device, surrounding property, barriers, warning labels, damaged items, and any position that cannot be reconstructed later. Document custody: who owns the unit, who possessed it, whether a contractor serviced it, and where it is stored now. If testing or disassembly is necessary for safety, involve qualified personnel and retain a chain-of-custody and testing plan. Avoid assuming that a customer’s photo or a single log line establishes cause; physical, software, human, and site factors may interact. ## Route notices by duty, not by guesswork Open the executed customer agreement, incident protocol, insurance policies, and internal escalation chart. Note each notice recipient, deadline or trigger, required content, and who will approve the message. Some policies have consent or cooperation requirements for defense costs, remediation, or settlement. Send a factual, timely notice through the appropriate channel and keep copies. Do not promise a customer that an insurer will pay or admit fault before the investigation and advisers support that conclusion. A consumer-product safety question is not the same as an insurance claim. CPSC reporting guidance applies to covered consumer products and specified information, and may require prompt reporting; it should not be casually extended to every industrial robot. Have product-safety counsel assess product category, known facts, and any CPSC or other regulatory duties. Workplace, privacy, and contractual notices likewise depend on the specific facts and law. ## Create a defensible follow-up record Track engineering analysis, customer communications, remedial actions, affected units or versions, vendor involvement, repair costs, invoices, business interruption claims, and insurer requests in a dated log. Restrict speculation in broad chat threads while preserving ordinary records under counsel’s direction. If an update is rolled back or a unit is recalled from a site, record scope, reason, approver, and customer confirmation. After the urgent phase, compare the actual sequence with the pilot handoff: did the deployed version, site, operator training, remote-access setting, or service role differ from the original submission? Feed verified changes into safety and insurance renewal records. This is a documentation workflow, not legal advice or a prediction of which policy or party will respond. ## Sources - [CPSC — Duty to report: rights and responsibilities of businesses for consumer products](https://www.cpsc.gov/Business--Manufacturing/Recall-Guidance/Duty-to-Report-to-CPSC-Rights-and-Responsibilities-of-Businesses) - [OSHA — Industrial robots and robot system safety](https://www.osha.gov/otm/section-4-safety-hazards/chapter-4) - [California Department of Insurance — Commercial Insurance Guide](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-field-incident-documentation.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)