Performed is not the same as proven.

LabDesk keeps the evidence with the instrument, so when someone asks to see the maintenance, you can show it.

Built for lab and QA managers whose maintenance record lives in a spreadsheet and an inbox.

We set up every trial and demo ourselves, so we ask a few questions first.

Most labs do the maintenance. What goes wrong is the day someone asks to see it.

  • The vendor's service report is in somebody's email.
  • The record of what was done is in a spreadsheet one person understands.

Your real alternative is not another vendor. It is the spreadsheet you already have. It stops working on a date you can see coming: a closure, a consolidation, a site move, an audit, or the person who owns the spreadsheet leaving.

The evidence lives with the instrument.

Each instrument has its own page. It shows the service visits, the calibration records, and the vendor reports and certificates filed to it. When someone asks, you open the instrument and show them. Reports are filed to the instrument as a whole, not to an individual service visit. The limits of this record are stated under "What LabDesk does not claim", further down this page.

An instrument's page in a sample lab. Its Schedule tab lists a completed service visit, and the tabs beside it hold the instrument's documents and calibration records.
One instrument's page, open on its service visits; its documents and calibration records sit in the tabs beside them. Sample data from a fictional lab, not a customer's.

Vendor service reports, filed to the instrument they belong to.

Once your register is in LabDesk, you upload a batch of your vendor's service reports. A report whose barcode or serial number matches exactly one of your instruments is filed to it. Anything that does not match, or that could belong to more than one instrument, waits for a person to check. The match reads the text of the PDF.

This is set up with each customer. Ask us and we will show it working on a few of your own reports, in a trial or demonstration account. Files you send are stored with our hosting providers, and no terms of service or data processing agreement is in effect yet; the security page lists both.

Ask for a demo with your own reports

A finished service-report import in a sample lab. Two vendor documents are filed to their instruments, and one waits in review for a person to check.
A finished import batch: two documents filed to their instruments and one waiting for a person to check. Sample data from a fictional lab, not a customer's.

Transfer requests go to approvers. Disposals leave a record.

Transfers

When you use LabDesk's transfer request, it goes to the approvers you name. Nobody can approve their own.

Disposal

A disposal is recorded with its disposition, when it was recorded and by whom, and the method if one is entered.

Only a transfer request goes to approvers: editing an instrument's location directly and recording a disposal need none, and moving instruments in bulk or on an inventory walk leaves no audit-log entry.

What LabDesk does not claim.

LabDesk holds no third-party security certification: no SOC 2 report, no ISO 27001 certificate and no independent penetration test. We do not claim 21 CFR Part 11 compliance and we do not offer Part 11 electronic signatures. Our audit log covers key events such as transfers, disposals, calibration records and ownership changes, not every edit. LabDesk itself is not ISO/IEC 17025 accredited. The security and trust page lists the limits: LabDesk staff can and do change or delete records by console outside the audit log, the audit log is tamper-evident rather than tamper-proof, and uploaded files are not backed up.

Read the security and trust page

Start with the records you already have.

Customers run LabDesk in production today.

We offer to build your register from your spreadsheet and your vendor reports, one at a time and up to three a year.

Already have an account? Sign in