Record inspection results without putting the part down
Open the inspection log, select the worksheet, and start Listening Mode. Then speak measured values, pass/fail results, and defect codes into Excel Online or Google Sheets without returning to the keyboard after every check.
Runtime capture is hands-free after setup.
Live speech
“For inspection QC-1048, set measured value to 24.96 and result to pass.”
| Inspection ID | Part / Lot | Feature | Measured | Result |
|---|---|---|---|---|
| QC-1047 | BRK-220 · L-418 | Overall width | 80.02 mm | Pass |
| QC-1048 | BRK-220 · L-418 | Mounting hole diameter | 24.96 mm | Pass |
| QC-1049 | HSG-310 · L-419 | Surface finish | — | Pending |
Applied
Measured Value → 24.96
Applied
Result → Pass
Do the check, speak the result, move to the next part
Lucy is designed to streamline how inspection results are recorded—not replace the inspector's judgment, inspection method, instrumentation, or review process.
- 1
Inspect
Use the approved gauge, drawing, checklist, or work instruction.
- 2
Read
Observe the measured value or categorical defect result.
- 3
Speak
Name the unique Inspection ID and the fields to update.
- 4
Continue
Review the outcome without selecting spreadsheet cells.
A unique Inspection ID matters more than the spreadsheet row number
Part BRK-220 and lot L-418 can appear in several checks. QC-1048 identifies this one row: the mounting-hole diameter inspected during the in-process stage.
The numeric observation and pass/fail result are separate actions, so Lucy can report exactly what was written rather than treating the sentence as one opaque entry.
Inspection ID
QC-1048
Authoritative row key
Feature
Mounting hole diameter
What was checked
Measured Value
24.96
Observed result
Result
Pass
Categorical outcome
Visible outcome
2 updates applied to QC-1048
If the destination is unclear, Lucy does not apply the change
Repeated part and lot values are normal in an inspection log. If an instruction does not identify a unique inspection record and named destination fields, Lucy skips the ambiguous update and reports why.
Incomplete instruction
“For lot L-418, set it to 24.96 and pass.”
Repeated target
The lot can appear on several inspection rows.
Unnamed field
“It” does not identify Measured Value.
Missing unit
The numeric observation lacks its measurement context.
Mixed intent
“Pass” likely means Result, but the first action remains unsafe.
Safer: “For inspection QC-1048, set measured value to 24.96 and result to pass.”
A focused input layer for an existing inspection spreadsheet
A strong fit when
- • An SME uses Excel Online or Google Sheets for a repeat inspection log.
- • A laptop or desktop sits near receiving, in-process, or final inspection.
- • The same measurements, results, or defect codes are recorded repeatedly.
- • Gloves, parts, instruments, or dirty hands keep the inspector occupied.
- • Switching between inspection and data entry interrupts the work.
Traceability for every update
When recording and persistent audit history are enabled, teams can review what was said, how Lucy interpreted it, and which spreadsheet actions were applied, skipped, or failed.
- Replay the instruction: Review the audio associated with a spoken update.
- Follow every action: See the inspection record, fields, and values Lucy resolved.
- Choose what to retain: Enable recording and audit history only when appropriate.
Manufacturing inspection logging with Lucy
Common questions about voice-first inspection capture, setup, and spreadsheet requirements.
Can Lucy receive measurements directly from instrumentation?
Not through the workflow described here. The inspector reads the result from the instrumentation and speaks it.
Can one instruction update several inspection fields?
Yes. A spoken instruction can identify one inspection and name several fields. Lucy validates and executes each extracted action independently, then reports which updates were applied, skipped, or failed.
Do inspectors need to select a spreadsheet cell before every update?
No. After opening the workbook, selecting the worksheet, and starting Listening Mode, the inspector can record updates without selecting individual cells. The spoken Inspection ID and field names tell Lucy where each value belongs.
What happens if an instruction is unclear or identifies multiple records?
Lucy does not apply an update it cannot resolve safely. It reports the action as skipped and explains why, allowing the inspector to provide a clearer instruction.
Can teams retain recordings and an audit history?
Yes. Audio recording and persistent audit history are opt-in. When enabled, teams can review what was said, how Lucy interpreted it, and which actions were applied, skipped, or failed.
Does Lucy work with Excel Online and Google Sheets?
Yes. Lucy supports inspection logs stored in Excel Online through OneDrive and in Google Sheets, with the same user-facing capture workflow wherever the provider APIs permit it.
Keep the inspection log moving without putting the part down
Start Listening Mode before the inspection run, then use the Inspection ID and field names already in your spreadsheet to capture each result.
Request Beta Access