Skip to content

Submit a repair request

Report a broken component, abnormal condition, or needed repair from the field.

Required role

Technician, Mapper, Admin, PegotecUser (any mobile-enabled role with mobile.repair.request).

Overview

A repair request is how you flag a problem that needs work — something's broken, worn, leaking, or otherwise outside of its normal state — without blocking your current task. The request goes to your Supervisor's queue, where it's triaged, assigned, and ultimately resolved.

A repair request is not the same as a shutdown:

Use Action
Equipment is broken but the line can still run Repair request
Line stopped / production halted / safety engaged Shutdown report — see Reporting a shutdown

It's fine to raise both for the same incident if both apply.

Prerequisites

  • You're at the asset, or you just came from it.
  • Ideally, you have a photo of the problem.

Steps

1. Open the repair request form

Several ways in:

  1. Inside the task, tap the three-dot menu.
  2. Tap Raise repair request.
  3. The form opens with the asset pre-filled.
  1. Open the asset in the hierarchy browser.
  2. Tap Raise repair request.
  1. Menu → Repair request.
  2. You'll need to pick the asset manually — tap Select asset and navigate the tree, or scan the NFC tag / barcode.

2. Fill in the form

Field Required Notes
Asset Yes Pre-filled if you came from a task. Tap Change to pick a different one.
Failure type Yes From the master list of repair-request types configured by your Admin.
Description Yes Free text. Describe what you see: "Oil leak from bearing housing, approx 1 drop per minute." Be specific — "it's broken" doesn't help the Supervisor triage.
Priority Yes Low / Medium / High / Critical. See below.
Photos Recommended At least one photo of the problem. See Photos and attachments.
Notes Optional Anything the Supervisor should know that doesn't fit the description.

3. Pick the right priority

Use priority intentionally — it shapes how fast the request gets acted on.

Priority When to use
Low Cosmetic, non-urgent. Worn paint, loose label, anything that doesn't affect function.
Medium Affects function but not safety or production. Slight leak, unusual noise, minor wear. Default for most requests.
High Risks production or safety in the near term. Significant leak, vibration, heat, smell.
Critical Immediate safety or production risk. Equipment actively failing, smoke, sparks, major leak, unsafe condition. Often accompanied by a shutdown report.

Don't use Critical for convenience

If everyone marks their requests Critical, the Supervisor can't tell what actually is. Reserve it for real emergencies.

4. Add photos

At least one photo is strongly recommended. It shortens the Supervisor's triage by a lot — they can see what you're describing instead of interpreting your text.

  • Point the camera at the actual problem.
  • Include some context — a wider shot showing the asset in its surroundings helps.
  • Annotate with an arrow if the problem area isn't obvious.

See Photos and attachments.

5. Submit

Tap Submit.

  • Online: the request uploads immediately. A toast confirms.
  • Offline: the request queues in the outbox. Pending uploads on the Dashboard increments. It uploads automatically when connectivity returns.

What happens after submission

  1. The request enters the Supervisor's queue with status Submitted.
  2. A Supervisor or Admin acknowledges it (status → Acknowledged).
  3. They either assign it for immediate repair or schedule it.
  4. A technician resolves it, which generates a Repair task linked back to your original request.
  5. The status moves to Resolved → Closed.

You receive push notifications at each status change (if you have the notification category enabled — see Notifications (mobile)).

Track your open requests

Menu → Repair requests → Mine. You see every request you've raised, with its current status. Tap any row to open details — including the Supervisor's acknowledgement time and any response notes.

When a Supervisor asks you for more detail

If your request was submitted too thin, the Supervisor may ask follow-up questions via the notes field or in person. Update the request:

  1. Open it in Repair requests → Mine.
  2. Tap Add note.
  3. Type your response. Optionally attach another photo.
  4. Submit.

Things to watch for

Always include a photo

Photos roughly double the Supervisor's ability to triage correctly. Even a blurry photo helps.

Don't duplicate requests

If you raise a request, then find the same problem on the same asset an hour later, don't raise a second one. Add a note to the original instead.

Offline requests look pending

If you're offline when you submit, the request appears in Mine with status Pending upload. Once it syncs, the status updates. Don't try to re-submit.

Common patterns

Mid-task finding

You're executing a lubrication task and notice the seal is cracking. Don't halt the task:

  1. Finish the task (the lubrication still needs doing).
  2. Before submitting the task, note the finding in the task's notes field ("cracked seal, see repair request").
  3. Submit the task.
  4. Raise a repair request for the seal, with photo.

End-of-walk finding

You spot something on your way between tasks:

  1. Raise the repair request immediately while the detail is fresh.
  2. Continue your scheduled work.

Critical finding

You see something actively dangerous:

  1. First, address the immediate safety (radio the line, engage emergency stop if required).
  2. Raise the repair request with priority Critical.
  3. Follow up with a shutdown report if production stopped — see Reporting a shutdown.

Troubleshooting

Problem Fix
Form won't submit Check required fields (asset, failure type, description, priority)
Photo upload fails after submit Request still submits; photo retries — Photo upload is failing
Don't see the right failure type Ask your Admin to add it to Master data
Status never moves Supervisor may be backlogged; follow up via radio or in person