Requests

Anyone on site can report a problem, without an account

A QR label on each machine, or a general link and poster. The report goes to whoever is responsible for the asset, and the person who sent it can follow it to the end.

The problem

“I told the shift leader on Tuesday. Has anyone looked at it?”

Requests by shout, paper slip and chat message get lost between shifts, and the people who raised them never hear back.

In Ophelm

From the scan to the fix

Review, accept, plan

Each report goes to the asset’s responsible person or team, or else to the workspace’s default. Accept it and create the work order in one step, link it to one that exists, or reject it with a reason.

Questions

What does the report form ask?

What is wrong, picked from your list or in the reporter’s own words, and optionally a description, up to five photos, fields you open to the portal, and name, email or phone, each set to not asked, optional or required.

Can reporters add photos?

Yes, up to five per report. You decide whether photos are optional or required.

Can people report without a QR label?

Yes. The portal has a general page with its own link, QR code and printable poster, where visitors type a label’s code or pick the asset from a list.

Who gets a new report?

The person or team responsible for the asset, otherwise the workspace’s default. They accept it and create a work order, link it to one, or reject it with a reason.

Can reporters see what happened to their report?

Yes. Each report has its own page that says whether it is waiting for review, planned, in progress or done, and it can be withdrawn while it waits.

How long do you keep reporters’ contact details?

As long as you set: 3, 6, 12 or 24 months after the issue is closed, or until someone removes them by hand. They are kept apart from the issue and shown to members by role.

See it with your own site

Sign up free, add a site and a few machines, and try it with your team.