Skip to content

Repair Request Types

The master catalogue of failure categories that technicians choose from when filing a repair request. Not to be confused with the repair requests themselves.

Required role

Mapper or Admin.

Not the same as repair requests

This page manages the dropdown options. To view or act on actual submitted repair requests, open the mobile repair-requests workflow or the Repair Request Report under Reports.

Overview

When a technician files a repair request from the mobile app, they pick a failure type from a dropdown. This page manages that dropdown.

A well-curated list of failure types:

  • Keeps submissions consistent — "seal leak" always maps to the same category.
  • Drives meaningful aggregation in the Repair Request Report.
  • Surfaces systemic issues (e.g. "45 requests were seal leaks this quarter" → maintenance review trigger).

Open the page

Configuration → Safety Standards → Repair Requests.

The table shows:

Column Meaning
Label The display name on the mobile dropdown.
Category Mechanical / Electrical / Hydraulic / Pneumatic / Structural / Instrumentation / Other.
Active On / off toggle.
Usage count How many repair requests in the last 30 days used this type.

Create a type

  1. New repair request type.

  2. Fill in:

    Field Notes
    Label Concise — fits on a mobile dropdown. "Seal leak", "Motor over-temp", "Vibration".
    Category Pick from the six. Drives aggregation in reports.
    Description (optional) Help text shown on mobile when the technician hovers / long-presses the option.

  3. Save.

Edit

Click a row → Edit. Changes propagate immediately to new submissions. Historical submissions keep the old label for report integrity.

Deactivate or delete

  • Deactivate — removes from mobile dropdown, keeps in reports. Reversible.
  • Delete — permanently removes. Blocked if any repair request references the type.

Prefer deactivate.

Good catalogue design

Do:

  • 10–30 types total, not 3 and not 100.
  • One clear category per type.
  • Short labels that fit mobile screens.
  • Coverage for your actual failure modes — use the last quarter of repair requests as a sanity check.

Don't:

  • Generic catch-alls ("Other" that's picked 80% of the time — split it).
  • Ambiguous overlap ("Seal leak" and "Oil leak" without a clear distinction).
  • Vendor-specific language your technicians don't use.

Seeding

On a new installation, start with a conservative list (~15–20 common types) and expand based on what technicians actually file. Watch the "description" field of incoming requests — patterns you see in free text are candidates for new types.

Bulk import

CSV import supported:

label,category,active
Seal leak,Hydraulic,1
Bearing failure,Mechanical,1
...

Things to watch for

Don't over-split at first

A catalogue of 100 highly-specific types fragments your reports. 15–30 broader types produce clearer aggregations. Split later if a category consistently hides multiple distinct patterns.

Keep 'Other' as an escape hatch

Always include 'Other' so technicians aren't blocked. But monitor how often it's picked — if >10%, your catalogue is missing common types.