Skip to content

Early stage · Pilot program open to integrators

Know what’s missing before handover day.

RobotDocket is commissioning-records software for robotics integrators. Configuration backups, acceptance tests, training records and sign-offs live in one register per project, so gaps show up weeks before the customer asks for the pack.

  • For integrators and commissioning teams
  • Records, not robot control
  • People sign off, software tracks

Fictional project shown for illustration.

One register per project

Every robot, tool and safety device has its own record with the tests and documents that belong to it.

Gaps flagged by rule

Filed records are compared with the checklist as the project runs, so a missing record has an owner early.

AI suggests, people decide

Document matches are suggestions to confirm. Results and sign-offs are always entered by a person.

Pack from the record

The handover pack is generated from the register and stays locked until required records are in.

The problem

The robot is running. The paperwork isn’t finished.

A robot installation is complete when the customer accepts it, and acceptance depends on records: configuration backups, signed test sheets, training attendance, safety documentation. Today those records are assembled by hand at the end.

Where commissioning records live today

  • Shared drive

    Controller backups in folders named by whoever saved them

  • Spreadsheet

    The SAT checklist, copied from the last job and edited

  • Clipboard

    Signed E-stop sheets, scanned on a phone days later

  • Email

    Shift B training attendance, sent by the customer

  • Laptop

    Photos of guarding, labels and test setups

  • Chat

    “Who approved the payload change?”

  • Gaps surface at the end

    Missing evidence is found while compiling the pack, after engineers have left site and the customer is waiting.

  • Every job is rebuilt

    Checklists differ by customer and get recreated per project, so nobody is sure what a given cell requires.

  • Sign-off is hard to trace

    Reviews happen in email and conversation, leaving no clear record of who checked what, and when.

  • Delay is expensive

    An incomplete handover can mean a return site visit, delayed acceptance and a held final payment on work that is already done.

Without a register

  • Requirements live in a spreadsheet nobody owns
  • Gaps found when the pack is compiled
  • Approvals reconstructed from email

With RobotDocket

  • The checklist defines “done” before work starts
  • Each upload is matched against it as it arrives
  • Every review and sign-off is recorded with a name and time
Product

Built around the records an acceptance needs.

Seven capabilities, one workflow: from the customer’s checklist to a pack the customer can accept.

Project and asset registers

Each robot, controller, end-of-arm tool and safety device on a project has its own record, with the documents and tests that belong to it.

Benefit: See the state of R2 without opening six folders.

Customer-specific checklists

Define the acceptance tests and documents a customer requires, including the evidence each item needs, before work starts.

Benefit: “Done” is agreed up front, not argued at the end.

Evidence filed at the source

Engineers record results and attach signed sheets, photos and backups directly against the checklist item.

Benefit: Evidence lands where it is needed, when it is created.

Document reading and classification

Scanned reports are read and suggested as a document type, asset and checklist item for a person to confirm.

Benefit: Less manual filing of the dozens of documents a cell produces.

Gap detection with owners

Filed records are compared with checklist requirements, and each gap is assigned to a named owner.

Benefit: A missing training record appears in week two, not on handover day.

Review and sign-off trail

Assign records to reviewers, capture decisions with a name and timestamp, and see which approvals are open.

Benefit: A clear trail of who reviewed what, and when.

Exportable handover packs

Generate an index, asset register, completed checklist, linked evidence and sign-off log once the project is complete.

Benefit: Export stays locked while required records are missing.

How it works

One workflow from kickoff to handover.

RobotDocket follows the way commissioning already runs. Each step is labelled by who or what does the work.

  1. 1

    Set up the project

    Register the site, cell and robot assets, then load the customer’s acceptance checklist.

    Coordinator

    DEMO-0142 · 6 assets · 18 items

  2. 2

    Capture evidence

    Engineers add results, signed sheets, photos, backups and training records as the work happens.

    Engineers

    SAT-07 · signed_sheet.pdf

  3. 3

    Read and match

    Text is extracted from scans and a document type, asset and checklist item are suggested. Rules then compare records with requirements.

    AI-assisted + rules

    Suggested: SAT-07 · confirm?

  4. 4

    Review and sign off

    Named reviewers check the linked records and sign off or send them back with a note.

    Qualified reviewers

    REV-03 · P. Nair · due 12 Oct

  5. 5

    Export the pack

    When no gaps or reviews remain, generate the handover pack from the register.

    Generated

    Index · checklist · evidence · log

Interactive demo

Work through a handover yourself.

This is a working prototype of the RobotDocket workspace running on sample data in your browser. Nothing you do here is uploaded or stored.

  1. 01 Open Documents, choose Add sample file, and add the Shift B attendance list. Watch it get read, then confirm the suggested match.
  2. 02 Open SAT-07 in the Checklist and add the signed sheet and setup photo. Try the unrelated file to see what happens when nothing matches.
  3. 03 Open Reviews and sign off REV-03. The Handover pack unlocks once nothing is outstanding.

Demo Manufacturing Co. / DEMO-0142 / Line 3 Palletizing Cell

Sample data

Line 3 Palletizing Cell

Target handover 14 Nov 2026

Completion by asset

  • R1 6-axis robot · infeed A3/3
  • R2 6-axis robot · infeed B3/4
  • EOAT-1 Vacuum layer gripper (R1)1/2
  • EOAT-2 Vacuum layer gripper (R2)2/2
  • SAF-1 Safety controller and light curtains3/3
  • CELL Cell-level records3/4

Checklist items complete, by week

Weekly history is sample data
091807 Sep14 Sep21 Sep28 Sep05 OctNow

Gap summary · AI-assisted draft

3 items stand between this project and handover. • CFG-03 EOAT-1 payload configuration (18.4 kg): Waiting for reviewer sign-off. (Priya Nair, due 12 Oct) • SAT-07 Safety-rated speed monitoring in collaborative zone: 0 of 2 evidence files filed. • TRN-02 Operator training: Shift B: No matching record found.

Draft generated from the records on this page. Status and sign-off are set by people and rules, not by the model.

Blocking the handover pack3

Recent activity

  • 05 Oct, 16:20
    Uploaded the maintenance manual issue receipt. Matched to HND-02.
  • 05 Oct, 15:05
    Approved REV-02 (R2 controller configuration).
  • 05 Oct, 11:30
    Flagged TRN-02: no document matches the Shift B attendance requirement.

All projects, people, files and figures in this demo are fictional. Extracted fields and suggestions are scripted for illustration.

Who it’s for

Made for the people who deliver robot installations.

Customers are robotics integrators and automation services firms, plus manufacturers with their own automation teams. Buyers are typically the head of delivery or commissioning.

Company

Robotics integrators

The problem
Each project ends with a scramble to assemble acceptance and handover documents, and quality depends on who ran the job.
How RobotDocket helps
A consistent record structure and checklist template across projects, with handover readiness visible on every active job.
Typical moment
Four cells commissioning in the same month, each at a different stage.
Role

Commissioning engineers

The problem
Evidence is captured on site under time pressure, on paper, phones and laptops, and filed days later.
How RobotDocket helps
Results and files go straight against the checklist item, and the register shows what is still needed before leaving site.
Typical moment
Closing out an E-stop test and confirming the signed sheet is filed before packing up.
Role

Project coordinators

The problem
Chasing documents and approvals across engineers, reviewers and the customer, mostly by email.
How RobotDocket helps
One list of gaps with owners, open reviews and due dates, and an export-ready pack when everything is in.
Typical moment
Asking the customer for Shift B attendance in week two instead of week six.
Company

In-house automation teams

The problem
Manufacturers commissioning robots on their own lines still owe operations and maintenance a complete record.
How RobotDocket helps
Training records, configuration backups and maintenance documents captured against each asset before go-live.
Typical moment
Handing a retrofitted cell to the maintenance team with its change history attached.

Typical projects

  • New robot cell handover
  • Multi-robot line rollout
  • Retrofit or redeployment
  • Machine tending and palletizing cells
  • Welding and assembly cells
Technology

Rules, AI suggestions and human decisions stay separate.

Commissioning records support safety-relevant acceptance decisions, so RobotDocket keeps each kind of output visibly distinct on screen and in the data.

Deterministic

Rules

Same inputs, same result. These decide whether a handover pack can be exported.

  • ›Checklist completeness
  • ›Required evidence present per item
  • ›Reviews still outstanding
  • ›Export readiness

AI-assisted

AI suggestions

Useful but fallible. Always labelled, and always linked to the source document.

  • ›Text from scanned reports
  • ›Suggested document type, asset and checklist item
  • ›Draft gap summaries for coordinators

Human decisions

People

RobotDocket records these decisions. It never makes them.

  • ›Test pass or fail
  • ›Acceptance and safety validation
  • ›Reviewer sign-off
  • ›Final handover approval

Access by project

Sign-in with access scoped to teams and individual projects.

Encrypted storage

Encryption in transit and at rest using AWS-managed keys.

Audit trail

Uploads, status changes, reviews and sign-offs recorded with user and time.

Source traceability

Every suggestion and gap flag links back to its document or rule.

RobotDocket manages records. It does not control robots. It does not connect to robot controllers or safety systems to change their behaviour. Qualified personnel remain responsible for acceptance decisions and safety validation. RobotDocket does not currently hold third-party security certifications.

Architecture

How We Use Amazon Web Services

A signed test sheet is only useful once it is stored, read, matched to a checklist item and checked against the rules. RobotDocket is designed so that each of those steps maps to an AWS service, with Step Functions carrying every upload through them and DynamoDB holding the state people review.

  1. 01

    Evidence capture

    • Amazon Cognito
    • Amazon API Gateway

    Engineers sign in, then request upload URLs for test sheets, photos, controller backups and training records.

  2. 02

    Secure storage

    • Amazon S3
    • Amazon DynamoDB

    Files are stored per project in S3; assets, checklist state and sign-offs are stored as records in DynamoDB.

  3. 03

    Processing

    • AWS Step Functions
    • Amazon Textract

    Each upload starts a workflow that reads text, tables and form fields from scanned documents, with retries and a visible state.

  4. 04

    AI intelligence

    • Amazon Bedrock
    • AWS Lambda

    Bedrock suggests document type, asset and checklist item. Lambda then applies the rule-based completeness checks.

  5. 05

    Application experience

    • Amazon SES
    • Amazon CloudWatch

    The workspace shows gaps, reviews and the handover pack. SES sends reviewer notifications; CloudWatch watches the workflows.

Services and their role

  • Amazon S3: Provides object storage for scanned test sheets, site photos, controller backups and exported handover packs.
  • Amazon Textract: Extracts text, tables and form fields from scanned acceptance sheets and training attendance lists.
  • Amazon Bedrock: Suggests a document type, asset and checklist item for each upload, and drafts plain-language gap summaries for review.
  • AWS Step Functions: Orchestrates the upload, extract, classify and check workflow, with retries and per-document state.
  • AWS Lambda: Runs the deterministic checklist and export-readiness rules whenever a record, file or review changes.
  • Amazon DynamoDB: Stores assets, checklist items, evidence links, gap flags, reviewer tasks and the sign-off log.
  • Amazon Cognito: Handles user sign-in and scopes access by team and project for integrators, engineers and customer reviewers.
  • Amazon API Gateway: Exposes the application API, including authenticated upload requests and the website enquiry endpoint.
  • Amazon SES: Sends reviewer assignments and gap notifications, and delivers website enquiries to the RobotDocket inbox.
  • Amazon CloudWatch: Collects logs, metrics and alarms so a failed document-processing run is noticed rather than silently lost.

This describes the architecture RobotDocket is built around. The website itself is static, and the demo above runs entirely in your browser. Using these services does not by itself make RobotDocket compliant with any standard.

Early access

Run your next handover in a pilot.

We are looking for robotics integrators and automation teams with an upcoming installation, who would use RobotDocket alongside their current process and tell us what is missing.

  • Workflow and record model defined

    Projects, assets, checklists, evidence, reviews and the handover pack.

  • Interactive prototype built

    The workspace on this page runs the real rule logic on sample data.

  • AWS architecture designed

    Upload, read, match, check and review pipeline described above.

  • Pilot program open

    We are working with robotics integrators on real project workflows. Tell us about yours.

Request a pilot

Tell us about your work. We read every request and reply by email.

This opens an email to hello@robotdocket.space. Nothing is sent until you send it.

Pricing

Priced for the way you deliver projects.

Three plans, priced per month. Pilot customers confirm plan, scope and terms with us in writing before they start.

Starter

A single team running a small number of projects.

$10/ month

  • Project and asset registers
  • Checklist templates
  • Evidence filing and gap flags
  • Handover pack export
Request access
Multi-project teams

Growth

Integrators running several projects and teams at once.

$30/ month

  • Everything in Starter
  • Portfolio view across active projects
  • Shared templates per customer
  • Reviewer assignments and notifications
Request access

Enterprise

Larger organisations with security, integration or support requirements.

$50/ month

  • Everything in Growth
  • Single sign-on and access policies
  • Integration with project systems
  • Security review and contract terms
Request access

Prices in US dollars. Inclusions per plan are confirmed in the pilot agreement.

Team

The Team Behind RobotDocket

  • Stephen Ogunleye

    Founder

    Founded RobotDocket in 2026 to give robotics integrators one place to keep the records a robot installation needs at handover.

  • Tunji Kamil

    Co-Founder

    Co-founder of RobotDocket, working with Stephen on the product and its pilot program.

Contact

Questions, partnerships, security reviews.

Use the form for anything that is not a pilot request, or write to us directly.

Looking to try RobotDocket on a project? Use the pilot request form instead.

This opens an email to hello@robotdocket.space. Nothing is sent until you send it.