Skip to main content

Diagnostics and the Service Checklist

Run the receiving checklist before opening a service order — templates, photos, and firmware checks.

Service technician

Every drone that enters your service bay should pass through a structured inspection before you open or advance a Service Order. The portal checklist captures condition at intake (Receiving) and at handoff (Release), giving you and the OEM auditable evidence if a Warranty Claim is filed later.

Where the checklist lives

You work with checklists in two places:

LocationWhen to use it
Service Order Details → Checklist tabPrimary workspace during active repair
Support → Checklist TemplatesReview available templates (managers create them)

On the service order, toggle between Receiving and Release with the phase control at the top of the Checklist tab. Progress shows as {completed}/{total} verified.

See Service Order Detail for the full page layout.

Step 1 — Apply a checklist template

If the Checklist tab shows No checklist applied:

  1. Open Apply Template

    Click Apply Template on the empty state. The drawer title is Apply Template — select a template to generate checklist items.

  2. Pick the correct phase

    Receiving templates cover intake inspection. Release templates cover post-repair verification. Apply the right phase for where you are in the job.

  3. Confirm generation

    Click Apply. You should see The checklist items were generated successfully. Items are grouped by category (Frame, Propulsion, Battery, Electronics, Software, Spraying system, and others).

Step 2 — Inspect each checklist item

Work through items top to bottom. For each row:

  1. Open Update inspection

    Click Edit checklist item (or the row action) to open Update inspection.

  2. Set status

    Choose OK, Issue Found, N/A, or leave Pending until verified. Flag real defects as Issue Found — this feeds your Diagnosis verdict later.

  3. Add notes

    In Notes, describe what you observed. Be specific: location, error codes, corrosion, impact damage. Notes appear in the audit trail and support warranty evidence.

  4. Attach photos when required

    Items marked Photo required need at least one image. Use Add photos in the dropzone (Add inspection photos — PNG, JPEG, WebP, or HEIC, max 10 MB). Some templates require photos on Software or Propulsion categories even when the drone looks fine — follow the template.

  5. Save changes

    Click Save changes. The item shows Verified by {name} with a timestamp when complete.

Step 3 — Verify firmware and software

Firmware and software checklist items

On the Overview tab of Drone Detail, compare Firmware Version to the OEM baseline for that Model. In the checklist:

  • Mark Software category items OK only after confirming the controller and aircraft firmware match policy.
  • Attach a photo of the version screen when the template requires it.
  • If sync fails, pause and see Drone Not Syncing before replacing hardware.

Step 4 — Record diagnosis and advance the order

When Receiving checklist progress reaches completion:

  1. Open Actions on the service order.
  2. Under Diagnosis, enter the Diagnosis verdict and click Save diagnosis.
  3. Move Next status from Open to Diagnosing, then Update Status.

The ticket timeline logs Receiving checklist completed with OK and issue counts — useful if the customer disputes findings later.

Common pitfalls

ProblemFix
Photo upload failedRetry with smaller files; only PNG/JPEG/WebP/HEIC under 10 MB
No active templates availableAsk admin to publish a template for your phase
Skipped software checksFirmware mismatches cause repeat visits — always verify

Next steps

Was this page helpful?

Edit this page on GitHub

Last updated Oct 20, 2018