Area Report: reports at the truck
PlannedReport problems where they occur
Report is planned: a report page that opens via the QR code on the device, without signing in. Drivers and warehouse teams are meant to report a problem in a few steps: scan, choose the incident, take a photo, send. The report is meant to reach the people responsible and the right vehicle.
Features
What Report is meant to do and what exists today
Report itself is planned. Today, members of your team can record errors: in the customer portal, on the vehicle, depending on the plan.
Usable today
AvailableError documentation with photos and status
Record an error code that occurred on a vehicle, with photos, notes and operating hours, from open through in progress to resolved. Every vehicle builds up its own error history.
Vehicles with status and operating hours
Every vehicle with manufacturer, device type and status: active, maintenance, out of service or archived. You enter the operating hours; their history stays visible.
Team with roles
Invite colleagues to the customer portal as administrator or member. The number of users depends on the plan.
Planned
PlannedIntentions without a fixed date. What we build, we try out with pilot companies.
Report page via QR code, without signing in
Scan the code on the device, choose the type of incident, describe it briefly, attach photos and the displayed error code if needed, send.
Location only at the time of the report
Capture the place of the incident only when the report is sent, as a deliberate action of the person reporting and with its accuracy, or else as text. No continuous location tracking, no hidden tracking.
Reports to the right people
Rules per company decide who receives a report: for example fleet management, the workshop, the people responsible for a site or a service partner.
Confirmation and status link
After sending, a confirmation of receipt and a link where the person reporting sees how far their report has got, without an account.
Blocking with documented release
By default, an observation reported as safety-relevant marks the device as blocked as a precaution. It is released again only after a documented check by an authorised person.
Repair and release kept apart
A completed repair does not release a blocked device by itself. Release for operation is a separate, documented step.
Defects
Review reports and assign them to a defect. Several reports about the same problem lead to one shared defect; every original report is kept.
Who it is for
For the people at the truck and those who act
Drivers and warehouse teams
You notice a problem first. Reporting it is meant to be as easy as taking a photo, without an account and without looking for the person responsible.
Fleet management
You learn about damage and faults before they turn into downtime, with a photo, location and error code instead of a note stuck to the truck.
Safety officers
Accidents, collisions and safety defects are meant to reach you directly, if your company sets it up that way.
How it fits together
How Report connects with the other areas
ProDiagnosis
AvailableA reported error code is meant to lead straight to the matching explanation in Pro. Pro is available today.
More about ProFleetOwn fleet
Partly availablePlanned: reports end up with the device in Fleet; after review they are assigned to a defect or a service case.
More about FleetServiceCustomer fleets
PlannedPlanned: a report becomes a service case, in-house or with a service partner the operator has shared the device with.
More about Service
Principles
Safety and privacy in the flow
We have set these principles for Report. Like the area itself, they are planned.
- Blocked until a documented release
- When an observation is reported as safety-relevant, the people responsible are notified at once, and by default the device is marked as blocked as a precaution. It is released only after a documented check by an authorised person. The block is a note in ForkScan Pro, not an intervention in the truck.
- A repair is not a release
- A completed repair does not release a blocked device by itself. Completing the repair and releasing the device for operation remain separate, traceable steps.
- No hidden tracking
- The location is captured only when a report is made, as a deliberate action and with its accuracy. No continuous tracking of people or vehicles.
- The report stays as it was
- The original report with its photos and time is kept, even when it is later assigned to a defect or service case. Several reports about the same problem are grouped without getting lost.
Questions
Frequently asked questions
Do drivers need an account?
No, that is how Report is planned: the report page opens via the QR code on the device, without signing in. Whether a name or driver ID must be given is meant to be up to each company.
Will drivers' locations be tracked?
No. The plan is to capture the location only when a report is sent, as a deliberate action of the person reporting. Anyone who does not share their location describes the place in words.
What happens with a safety-relevant report?
Planned: the people responsible are notified at once, and by default the device is marked as blocked as a precaution until an authorised person releases it after a documented check. Until Report is available, please keep reporting safety-relevant defects directly and at once, as you do now.
When will Report be available?
We do not give a date. Report is the second stage of our roadmap. If you would like to help shape how reports should arrive in your company, register your interest or apply as a pilot company.
How do we record problems until then?
With the error documentation in the customer portal, depending on the plan: members of your team record an error code that occurred on a vehicle, with photos, notes and status.
Help shape Report
We are looking for companies with their own fleet to work out with us what drivers and fleet management really need from reports. As a pilot company you use Pro and Fleet today in the Professional plan and tell us what is missing.
Become a pilot companyRegister interest
Would you like to know how things develop, or do you have a specific need? Write to us about what you need. Your message reaches the people who develop ForkScan Pro.
Register interestUsable today: error code search, fleet and inspection dates in the trial. Start trial