Help centre/Record evidence

Evidence

How to keep calibration certificates with instrument history

Certificates are evidence of a completed calibration, but they are only useful if the team can connect them to the correct instrument and event. GagePilot stores certificate metadata with the calibration record and keeps it available from the instrument history.

GagePilot quality operations team · Last reviewed July 31, 2026
GagePilot calibration queue form for recording a calibration, result, next due date, and certificate12
Calibration record form captured from the live GagePilot desktop app. The numbered callouts are explained below.
  1. 1Choose the instrument and enter the performed date and next due date.
  2. 2Attach the certificate and record the result and provider for a complete history.

What to attach

  • PDF calibration certificates
  • PNG or JPG certificate images
  • The provider’s certificate number
  • Notes that explain findings or corrective action when needed

A reliable certificate workflow

  1. Confirm the instrumentSelect the exact asset ID before uploading evidence.
  2. Record the calibration eventEnter the performed date, result, provider, and next due date.
  3. Attach the certificateUpload the file in the same record so it does not become orphaned in a shared folder.
  4. Check the historyReview the instrument record and confirm the event and certificate are visible together.

Why filenames still matter

Even when the file is connected to an instrument, use a consistent filename such as `asset-id_provider_date.pdf`. It makes exports, downloads, and offline review easier for the people who maintain the quality records.

Certificates are part of your system, not the whole system

A certificate does not by itself prove that every controlled instrument was managed correctly. Your procedures, interval decisions, status controls, and response to failed results still matter.

See it in GagePilot

Keep the register, reminders, certificates, and history together.

Start a 14-day trial