Commercial and vendor scope
Entity and tax documents, equipment and services, schedule, fees, payment, cancellation, travel, insurance requirements, and contracting terms.
Enterprise readiness
Put the operating plan in writing before the robot goes to work.
RoboticsLive helps procurement, security, operations, and venue teams define the equipment, people, software, data, acceptance tests, support, and responsibilities for a robot program.
ScopeWritten for the specific project
Public operationTrained operator and stop procedure
Data and softwareDependencies and handling documented
Service levelsDefined in the signed agreement when required
Vendor review
One packet should answer the questions each team owns.
Requirements vary by customer and project. The applicable documents and commitments are confirmed before contracting.
Systems and data flow
Robot model and software, local and cloud processing, integrations, access, recording, retention, deletion, subprocessors, and incident contacts.
People, place, and controls
Operator roles, load-in, surface, power, boundaries, crowd plan, batteries, weather, stop authority, escalation, and pack-out.
Service levels
Define the support promise for the system being bought.
A live event, recurring on-site program, software installation, and customer-owned robot do not need the same support model. RoboticsLive does not publish a blanket SLA that hides those differences.
- Covered robot, software, integration, location, and operating hours
- Severity levels, contact method, response targets, and escalation path
- Maintenance windows, updates, client dependencies, and third-party exclusions
- Fallback, replacement, service credits or other remedy when applicable
- Term, renewal, handoff, data return, deletion, and exit responsibilities
Approval path
Move from review to an accepted operating plan.
Every step produces a decision or a document; nothing here replaces the signed agreement.
Intake
Name the use case, location, schedule, users, robot, software, data, integrations, and internal reviewers.
Review
Resolve safety, insurance, privacy, security, access, venue, operator, and procurement requirements.
Contract
Set the statement of work, responsibilities, acceptance tests, pricing, support, change control, and exit terms.
Deploy
Complete site checks, commissioning, operator handoff, acceptance, incident contacts, and closeout records.
Before the purchase order
Confirm the exact system and the conditions around it.
Use the final documents, not a manufacturer demo or website description, as the source of truth for capability and responsibility.
- Robot model, edition, firmware, accessories, batteries, and seller
- Supported job, operating environment, boundaries, and prohibited uses
- RoboticsLiveOS features, integrations, network needs, and fallback behavior
- Recording, logs, access, retention, deletion, and client-provided data
- Acceptance tests, training, documentation, support, and change process
- Price, taxes, shipping, travel, payment, cancellation, warranty, and remedy
Documents to request
Send your checklist and deadline at the start.
RoboticsLive will confirm which documents apply and what can be provided for the proposed project.
Commercial packet
Proposal or statement of work, equipment list, responsibilities, payment terms, cancellation terms, and requested vendor or tax forms.
Operating packet
Venue requirements, site plan, safety and operator plan, load-in schedule, emergency contacts, acceptance checklist, and closeout process.
Technical packet
Architecture and data-flow summary, integration list, access model, recording and retention position, support plan, and security questionnaire when required.
Start here
Start an enterprise or vendor review
Send the use case, location, schedule, robot or software scope, reviewers, procurement checklist, insurance requirements, and target approval date.
Prefer email?contact@roboticslive.com
Response timeComplete inquiries normally receive a reply the same day.
Questions
Enterprise review questions
Do you have a standard SLA?
No universal SLA applies to every project. If service levels are required, the signed agreement defines the covered system, support window, severity levels, response targets, exclusions, escalation, and remedy.
Can RoboticsLive complete our security questionnaire?
Send it before contracting. RoboticsLive will answer for the proposed hardware, software, data flow, integrations, operators, and service providers, and identify any control that does not apply or requires a project-specific decision.
Can you sign a data processing agreement?
If the project requires RoboticsLive to process personal data, the parties should define roles, data categories, purpose, retention, deletion, subprocessors, security responsibilities, and exit terms before data is introduced.
What insurance documents are available?
Send the venue or procurement requirements, certificate wording, additional-insured request, limits, and deadline. RoboticsLive will confirm what documentation is available for that project before either party commits.
Are the robots certified for autonomous public operation?
Do not assume that they are. RoboticsLive public deployments use a trained operator, an agreed operating boundary, and a stop procedure. Capability and responsibility are documented for the specific job.
What happens when a third-party service fails?
The statement of work identifies external dependencies, expected fallback behavior, support ownership, and any service-level exclusion. Core RoboticsLiveOS functions and optional cloud features should be distinguished in writing.