🎯 Your Role in the Repair Workflow
As a manager, your role isn’t to turn wrenches — it’s to make sure the right people know about the right problems, and that repairs are handled without disrupting the field.
CrewHero gives you the tools to:
- Acknowledge field-submitted repair requests
- Prioritize urgency
- Add comments for clarity
- Flag unsafe equipment
- Keep your crews informed and protected
✅ Step-by-Step: Reviewing a Repair Ticket
1. Go to the Repair Requests tab
Find the ticket submitted by the crew via the Frontline App. New requests will show as Status: New.
2. Click into the ticket
Review the asset, issue description, and any uploaded photos. You’ll also see who submitted it and which division it belongs to.
3. Change the status to Received
This tells the frontline worker:
“We saw your request. We’re on it.”
It creates instant clarity and trust.
4. Assign a Priority Level
Use low/medium/high to guide the Fleet Team on urgency.
- High = Safety risk or equipment needed ASAP
- Medium = Problematic but not blocking work
- Low = Annoyance or minor performance issue
Pro Tip: Adding this saves back-and-forth questions from mechanics.
🛑 Optional: Flag the Asset
If the asset is unsafe or unreliable, hit “Add Repair Alert”.
- This flags the asset in Dispatch
- It helps your team avoid assigning it while it's under review
- Use it when the asset shouldn’t be used — even before repairs begin
💬 Leave a Comment (Always)
Add a comment that:
- Confirms the issue is being reviewed
- Asks any clarifying questions
- Thanks the crew member for reporting it
Example:
🧠 What Happens Next
Once your review is complete, the Fleet Tech or Fleet Manager takes over:
- They’ll update the ticket status to In Progress when the asset is being worked on
- Then mark it Ready when it’s fixed
- At that point, you’ll see it again to review and set to Accepted
You close the loop. That’s how repairs stay clean and crews stay confident.
🔄 Summary Workflow
Step | What to Do |
1. View Ticket | New repair submitted from the field |
2. Set to Received | Acknowledge the issue |
3. Set Priority | Low / Medium / High |
4. Add Alert (if needed) | Flag asset as unsafe |
5. Leave a Comment | Clarify or thank |
6. Monitor | Review once marked Ready by Fleet |
7. Accept | Confirm the asset is good to go |