Bring every robot project to an organized handover.
RobotDocket is commissioning-records software for robotics integrators. It keeps configuration records, acceptance tests, training documents and handover evidence in one project register — and flags what's missing before you hand over.
Line 3 Palletizing Cell
Handover blocked- SAT-07 R2 safety-rated speed monitoring testResult entered · signed test sheet and photo not uploaded Evidence pending
- TRN-02 Operator training record — Shift BRequired by checklist · no matching document found Missing
- REV-03 Review EOAT payload configuration (R1)Assigned to commissioning lead · due in 2 days Review open
- CFG-01 R1 controller backup & parameter exportUploaded and classified · reviewed Complete
Interface preview with fictional project data. Not a real customer installation.
The robot is running. The paperwork isn't finished.
A robot installation isn't complete until 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 of the project.
Where commissioning records live today
Gaps surface at the end
Missing evidence is usually discovered while compiling the handover pack — after engineers have left site and the customer is waiting.
Every project is rebuilt from scratch
Checklists vary by customer and are re-created per project, so it's hard to know which tests and documents a given cell actually requires.
Sign-off is hard to trace
Reviews and approvals happen in email and conversations, leaving no clear record of who reviewed what, and when.
Delays cost real money
An incomplete handover can mean return site visits, delayed acceptance and held final payments — on work that is technically already done.
From scanned test sheet to handover-ready record.
A walk-through of one fictional installation: a two-robot palletizing cell with a pending acceptance test, a missing training record and an open reviewer task.
Engineer uploads a scanned, signed SAT sheet and two photos from site.
Text is extracted and the document is classified as an acceptance test for robot R2.
SAT-04 is now evidenced. SAT-07 is still pending; TRN-02 is flagged missing.
Coordinator requests the training record; a reviewer is assigned to REV-03.
| Tag | Asset | Records | Status |
|---|---|---|---|
| R1 | 6-axis robot — palletizing, infeed AController: CTRL-R1 · S/N on file | 12/12 | Complete |
| R2 | 6-axis robot — palletizing, infeed BController: CTRL-R2 · S/N on file | 10/12 | Evidence pending |
| EOAT-1 | Vacuum layer gripper (R1)Payload configuration under review | 4/5 | Review open |
| EOAT-2 | Vacuum layer gripper (R2) | 5/5 | Complete |
| SAF-1 | Safety controller & light curtainsValidation records linked | 6/6 | Complete |
| CELL | Cell-level recordsOperator & maintenance training | 3/4 | Record missing |
| ID | Test | Result | Evidence |
|---|---|---|---|
| SAT-03 | Pallet pattern A — 3 consecutive full pallets | Pass | 2 files |
| SAT-04 | Emergency stop response, all E-stop stationsMatched from scanned sheet uploaded today | Pass | 3 files |
| SAT-07 | Safety-rated speed monitoring in collaborative zoneRequired: signed sheet + photo of test setup | Pass (entered) | 0 of 2 |
| TRN-01 | Operator training — Shift A | Held | 1 file |
| TRN-02 | Operator training — Shift B | — | Missing |
| HND-01 | As-built electrical drawings | Issued | 1 file |
TRN-02 · Operator training record — Shift B
Missing recordChecklist requires attendance records for each operating shift. Shift A record found; no document classified as a Shift B training record.
SAT-07 · Speed monitoring test evidence
Evidence pendingResult recorded as "Pass" by commissioning engineer. Required evidence (signed sheet, photo of test setup) has not been uploaded.
REV-03 · EOAT payload configuration (R1)
Reviewer task openPayload parameters exported from R1 controller. Awaiting review by commissioning lead before sign-off.
All project names, assets and records shown are fictional and used for illustration only.
One workflow from project kickoff to handover pack.
RobotDocket follows the way commissioning already runs. Each step is labelled by who or what does the work.
Create project
Register the site, cell and robot assets being installed.
CoordinatorConfigure checklist
Set the tests and documents this customer requires for acceptance.
IntegratorUpload evidence
Add test results, scanned sheets, photos, backups and training records.
EngineersOrganize records
Extract text from scans and classify each document against assets and checklist items.
AI-assistedFlag gaps
Compare records with checklist requirements and list what's missing or pending.
Rule-basedReview & sign off
Assign reviewers, record decisions and track approvals.
Qualified reviewersExport pack
Generate a structured commissioning pack for customer handover.
Generated
Built around the records an acceptance actually needs.
Project & robot asset registers
Every robot, controller, end-of-arm tool and safety device on a project gets its own record, with the documents and tests that belong to it.
Why it matters: you can see the state of R2 without opening six folders.Customer-configured test checklists
Define acceptance tests and required documents per customer or project, including what evidence each item needs.
Why it matters: the definition of "done" is agreed before the work starts.Test-result & evidence uploads
Engineers record results and attach signed sheets, photos and controller backups directly against the relevant checklist item.
Why it matters: evidence is filed where it's needed, at the time it's created.Document extraction & classification
Scanned reports and PDFs are read and suggested as a document type, asset and checklist item — for a person to confirm.
Why it matters: less manual filing of the dozens of documents a cell produces.Missing-record flags
Continuous comparison of uploaded records against checklist requirements, with each gap assigned an owner.
Why it matters: missing training records show up in week two, not on handover day.Reviewer assignments & sign-off
Assign records to named reviewers, capture decisions with timestamps, and see which approvals are still open.
Why it matters: a clear trail of who reviewed what, and when.Exportable commissioning packs
Generate a structured handover pack — index, asset register, completed checklist, linked evidence and sign-off log — once the project is complete.
Made for the people who deliver robot installations.
Robotics integrators
- Their problem
- Each project ends with a manual scramble to assemble acceptance and handover documents, and quality varies by project team.
- How RobotDocket helps
- A consistent commissioning template and record structure across projects, with visibility of handover readiness on every active job.
Commissioning engineers
- Their problem
- Evidence is captured on site under time pressure — on paper, phones and laptops — then has to be filed later.
- How RobotDocket helps
- Upload results and evidence straight against the checklist item and asset, and see exactly what's still needed before leaving site.
Project coordinators
- Their problem
- Chasing missing documents and approvals across engineers, reviewers and the customer, often by email.
- How RobotDocket helps
- A single list of gaps with owners, open reviews and due dates — and an export-ready pack when everything is in.
Where RobotDocket fits.
New robot cell handover
An integrator installs a new palletizing or machine-tending cell and must deliver a complete acceptance package.
- Checklist configured from the customer's acceptance requirements
- Evidence captured during FAT and SAT
- Pack exported at handover
Multi-robot line rollout
Several robots installed across a line, with different engineers responsible for different cells.
- Per-asset records for every robot and tool
- Gap view across the whole project
- Reviewer assignments by cell
Retrofit or redeployment
An existing robot is moved, reprogrammed or upgraded, and the changed configuration needs to be documented and re-accepted.
- Updated configuration backups linked to the asset
- Re-test evidence against a focused checklist
- Sign-off trail for the change
Manufacturer's internal automation team
An in-house engineering team commissions robots on its own production lines and hands over to operations and maintenance.
- Training records per shift
- Maintenance documentation captured before go-live
- A consistent record for every installed asset
Clear lines between rules, AI suggestions and human decisions.
Commissioning records support safety-relevant acceptance decisions, so RobotDocket keeps each type of output visibly separate.
Rule-based checks
Same inputs, same result. These are what block or allow a handover pack.
- Checklist completeness
- Required evidence present per item
- Reviews outstanding
- Export readiness
Suggestions to confirm
Useful but fallible. Always labelled, always linked to the source document.
- Text extraction from scanned reports
- Suggested document type, asset and checklist item
- Draft gap summaries for coordinators
Decisions people make
RobotDocket records these decisions — it never makes them.
- Test pass / fail results
- Acceptance and safety validation
- Reviewer sign-off
- Final handover approval
Designed around AWS.
RobotDocket is being built on AWS to store project documents and test evidence, extract text from scanned reports, classify records, run checklist completeness checks and keep an auditable history of approvals. The architecture is sized for early pilot projects and designed to scale as projects and document volumes grow.
| Service | What it does in RobotDocket | Why it's needed |
|---|---|---|
| Amazon S3 | Stores uploaded documents, site photos, test evidence and exported packs. | Commissioning projects produce many large files that must be retained and retrieved reliably. |
| Amazon Textract | Extracts text and form fields from scanned test sheets and reports. | Much site evidence is signed on paper and scanned; it must be readable to be classified. |
| Amazon Bedrock | Classifies documents and drafts gap summaries for review. | Document types and naming vary widely between engineers, customers and robot vendors. |
| AWS Lambda | Runs checklist and completeness checks when records change. | Checks are event-driven and short-lived — triggered by uploads and status changes. |
| AWS Step Functions | Orchestrates the upload → extract → classify → check workflow. | Multi-step processing needs retries, error handling and a visible state per document. |
| Amazon DynamoDB | Holds assets, test status, gap flags, reviewer tasks and approvals. | Fast, structured reads and writes of per-project records and their state changes. |
| Amazon Cognito | Authenticates users and scopes access to teams and projects. | Integrators, engineers and customer reviewers need different access to the same project. |
| Amazon CloudWatch | Monitors processing workflows, errors and performance. | Failed document processing has to be visible quickly so evidence isn't silently lost. |
Why the workload grows with every project.
Infrastructure needs track the number of active projects and the documents they produce — not just the number of users.
Documents & evidence
Each robot cell generates test sheets, photos, backups and training records. Storage grows with every project and must be retained after handover.
Extraction & classification
Every scanned upload runs through text extraction and AI classification, so processing scales with document volume.
Completeness checks
Checks re-run whenever records or checklists change. More active projects means more background processing.
Teams & access
Additional integrator teams, customer reviewers and later project-system integrations increase authentication and API load.
Project records handled with care.
Commissioning records can include customer site details and safety documentation. These are the principles the platform is being designed around.
Authentication & access
User sign-in through Amazon Cognito, with access scoped to teams and individual projects.
Encryption
Documents and records encrypted in transit and at rest using AWS-managed encryption.
Data isolation
Each customer workspace's documents and records are logically separated.
Audit trail
Uploads, status changes, reviews and sign-offs are recorded with user and timestamp.
Source traceability
Every classification and gap flag links back to the source document or checklist rule.
Monitoring
Processing workflows monitored in Amazon CloudWatch so failures are detected and retried.
Subscriptions that follow your project load.
RobotDocket is in its pilot phase. Pricing is discussed directly with pilot participants; general pricing will be published at launch.
Pilot program
- Single commissioning template and document workflow
- Set up with your own checklist
- Direct line to the founding team
- Your feedback shapes the roadmap
Per active project
- Suited to integrators with variable project load
- Pay while a project is active
- Records retained after handover
Integrator team
- Suited to teams running several projects at once
- Shared templates across projects
- Team-level reviewer and access management
Software for the last mile of robot projects.
RobotDocket is building project and commissioning software for the industrial robotics sector. Robot installations are increasingly common, but the work of proving an installation is complete — through tests, configuration records and training — is still done with folders, spreadsheets and email.
We think handover documentation should build up as the project runs, with gaps visible early, so integrators can close projects on time and customers receive a complete, traceable record of what was installed.
- NowSingle commissioning template and document workflow, developed with pilot integrators.
- NextMultiple templates, reusable checklists across customers, richer handover pack formats.
- LaterIntegrations with project management and document systems that integrators already use.
- Building
- Commissioning-records software for robot installation projects
- Industry
- Industrial robotics, automation services, manufacturing
- Customers
- Robotics integrators and in-house automation teams
- Stage
- In development · pilot program open
- Model
- Subscription by active project or integrator team
- Contact
- hello@robotdocket.com
Kelvin Chukwu
Tobi Hunter
Bring a real project to the pilot.
We're looking for robotics integrators and automation teams with an upcoming or active installation who want a better handover process.
Prefer email? hello@robotdocket.com
- A short call about your current commissioning and handover process.
- We set up your acceptance checklist as a RobotDocket template.
- Run it on a live or recent project and tell us what's missing.