Capture, Triage & Convert Work
Requests Into Work Orders
Squarerigger gives drivers, technicians, and supervisors a single way to flag an issue. A problem reported from
the cab becomes pending work in the shop without a phone call, a text thread, or a piece of paper.
Turn Driver Repair Requests Into Real
Maintenance Faster
A work request only helps when the problem gets captured clearly, routed
correctly, and turned into action before details get lost.
1. A Driver Hears Something Off Mid-Route
The driver texts the manager. Sometimes it gets read. By end of day, nothing's written down. The asset sits in the lot.
The driver submits a request from the cab, with the asset, location, and photos included. It lands in the shop queue.
2. The Manager Reviews New Requests
Requests live in three places: a text thread, an inbox, and a list on a whiteboard. None of them is complete.
Pending requests sit in one queue, sortable by priority, asset, and submitter. New requests notify the assigned reviewer.
3. The Manager Approves or Rejects
The decision is verbal or made in a phone call. The reasoning is not recorded. The same request can be approved twice by two people.
Approval, rejection, and reassignment write to the audit trail. Request reasoning and decisions are visible to submitters
4. The Approved Request Becomes a Job
The work order is built from scratch. Notes, photos, and the symptoms reported by the driver are re-keyed. Some context is lost.
The approved request is converted to a work order in a single step. Notes, photos, and asset attachment carry over without re-entry.
5. The Driver Asks Whether the Request Was Handled
The driver asks the dispatcher. The dispatcher asks the shop.
The driver gives up reporting issues after a few cycles like this.
The driver sees the status of their request from the phone they used to submit it. Visible follow-through keeps drivers reporting.
1. A Driver Hears Something Off Mid-Route
The driver texts the manager. Sometimes it gets read. By end of day, nothing's written down. The asset sits in the lot.
The driver submits a request from the cab, with the asset, location, and photos included. It lands in the shop queue.
2. The Manager Reviews New Requests
Requests live in three places: a text thread, an inbox, and a list on a whiteboard. None of them is complete.
Pending requests sit in one queue, sortable by priority, asset, and submitter. New requests notify the assigned reviewer.
3. The Manager Approves or Rejects
The decision is verbal or made in a phone call. The reasoning is not recorded. The same request can be approved twice by two people.
Approval, rejection, and reassignment write to the audit trail. Request reasoning and decisions are visible to submitters
4. The Approved Request Becomes a Job
The work order is built from scratch. Notes, photos, and the symptoms reported by the driver are re-keyed. Some context is lost.
The approved request is converted to a work order in a single step. Notes, photos, and asset attachment carry over without re-entry.
5. The Driver Asks Whether the Request Was Handled
The driver asks the dispatcher. The dispatcher asks the shop. The driver gives up reporting issues after a few cycles like this.
The driver sees the status of their request from the phone they used to submit it. Visible follow-through keeps drivers reporting.
How It Works
Step 1
The driver submits a
request from the cab
with a photo and priority
Step 2
The request appears in
the repair shop's
pending queue
Step 3
The maintenance
manager reviews and
approves it
Step 4
The request becomes a
work order with notes
and photos carried over
Step 5
The driver receives a
status update on their
phone
One Fleet Work Request
Record the Whole Way
Digital Submission from Any Role
The intake matches who is reporting.
- Submission from drivers, technicians, and supervisors.
- Phone, tablet, or desktop.
- Asset, location, priority, and photo attached at submission.
Approve, Assign, or Reject with Audit Trail
The decision lives with the request.
- Approval, rejection, and reassignment recorded.
- Reasoning attached so the decision is reviewable.
- Repeat submissions of the same issue caught from history.
Status Visibility for the Requester
The driver who reported the issue sees what happened next.
- Status visible from the same device used to submit.
- Notification when approved, scheduled, or resolved.
- Trust built when reports lead to visible action.
Triage Queue with Priority and Asset
The request is observable before it is approved.
- Sortable by priority, asset, submitter, and date.
- Notifications fire to the reviewer on submission.
- Linked to DVIRs and telematics diagnostic codes.
Work Order Without Re-Entry
The request and the work order share one record.
- Notes, photos, and asset carry over.
- Technician, parts, and labor assigned from the request.
- The work order is the next step, not a separate document.
Digital Submission from Any Role
The intake matches who is reporting.
- Submission from drivers, technicians, and supervisors.
- Phone, tablet, or desktop.
- Asset, location, priority, and photo attached at submission.
Triage Queue with Priority and Asset
The request is observable before it is approved.
- Sortable by priority, asset, submitter, and date.
- Notifications fire to the reviewer on submission.
- Linked to DVIRs and telematics diagnostic codes.
Approve, Assign, or Reject with Audit Trail
The decision lives with the request.
- Approval, rejection, and reassignment recorded.
- Reasoning attached so the decision is reviewable.
- Repeat submissions of the same issue caught from history.
Conversion to Work Order without Re-Entry
The request and the work order share one record.
- Notes, photos, and asset carry over.
- Technician, parts, and labor assigned from the request.
- The work order is the next step, not a separate document.
Status Visibility for the Requester
The driver who reported the issue sees what happened next.
- Status visible from the same device used to submit.
- Notification when approved, scheduled, or resolved.
- Trust built when reports lead to visible action.
Where Fleet Driver Repair Requests Go Next
A request connects the inspection that found the problem to the
work order that closes it out.
Telematics integrations
Diagnostic codes from 70+
providers raise requests in
the same queue.
Who Watches the Queue
Fleet Technician
The pending queue is the same queue holding the rest of the work. Approved requests arrive with context intact.
Driver and Dispatcher
Submission and status visibility on a single phone. Issues do not depend on someone remembering to walk to the office.
Fleet Maintenance Manager
Triage, approval, and audit trail in one place. Repeat submissions and recurring issues become observable.
Fleet Safety Pro
Driver-reported safety concerns are recorded with a time-stamp and follow-through visible to the safety team.
Watch a Driver-Reported Issue
Become a Work Order in One Step
Thirty minutes is enough to see a submission from a phone, a triage in the shop queue, an
approval with an audit trail, and a conversion to a work order with photos and notes intact.
FAQ
How does your fleet work request software handle triage before work orders open?
A work request is the report of an issue; a work order is the job that fixes it. Squarerigger lets supervisors approve, reject, or merge requests in one step.
Can drivers submit requests from their mobile devices?
Yes. The submission flow runs on phones and tablets. Asset, location, priority, photos, and notes can be attached from the same device.
How are requests routed to the right reviewer?
Routing is configured during onboarding. A request can route by asset, by location, or by the role of the submitter. Notifications fire to the assigned reviewer when the request lands in the queue.
Can a request be rejected without losing the record?
Yes. Rejected requests retain the audit trail, including the reasoning. The history is visible if the same issue is submitted again, which catches recurring patterns.
What happens if a driver reports the same issue twice?
Repeat submissions surface in the queue and the request history. The shop can merge requests onto a single work order rather than create two jobs for the same problem.
Can telematics create requests automatically?
Yes. Diagnostic trouble codes from the 70+ supported telematics providers raise requests in the same queue as driver and technician submissions.