Everything Smartop does

Grouped by who uses it. If a capability is not listed here it is not built yet — this page describes the product that exists, not a roadmap.

For the operator

Assignments on the phone: Open work, the machine it is on, and the scheduled window — with the state the backend says it is in, never a state the phone guessed.
Pre-work checklist: Yes/no, numeric and free-text items with minimums, maximums and units. Every item is mandatory; a partial submission is refused by the server, not just hidden by the app.
Photo evidence: Items can offer the camera, and items that require evidence are not complete without it. Photographs upload after the submission and attach to the answer they belong to.
Meter readings: Hours or kilometres, fixed by the machine's category. The unit cannot be chosen on the phone, so an hours machine never collects a kilometre figure.
Works offline: Submissions, readings and damage reports queue locally and sync on reconnect. An entry that cannot sync is parked visibly instead of disappearing.

Approval queue: Pending work-start requests with machine, operator, reading and waiting time. Approve in one tap or reject with a reason the operator can read.
Escalation chain: An unanswered request notifies the company's admin tier after one hour and Smartop operations after six. Escalation signals that nobody answered; it never transfers the authority to approve.
Checklist template editor: Build templates per machine category, version them, and publish. Published templates are what operators see; drafts are not.
Works and assignments: Create a job with its scope, location and window, then assign a machine and an operator to it.
Damage triage: Operator-raised faults arrive in their own queue with photographs, independent of any checklist.

Machine catalogue: Add a machine by searching a shared model registry, or create the model if it is not there. Your machine is identified by your own serial number, inside your own company.
Categories define behaviour: A category sets the reading unit and the default checklist for every machine in it. Change the category, and the rules follow.
QR identification: Scan the code on the machine with the phone camera instead of searching a list in the sun.
Maintenance thresholds: Rules per category turn cumulative readings into scheduled tasks, and the schedule moves whenever a new reading lands.
Machine documents: Manuals, warranty papers and inspection certificates stored against the machine they belong to.

Roles and invitations: Admin, manager and operator. An admin invites managers; a manager invites operators. Every permission decision is made server-side.
Operator certification: Record which operator is certified for which class of machine, and block assignments that would break it.
Audit log: Append-only, SHA-256 chained, checked daily for tampering. Authentication events, approval decisions, role changes, registry submissions and escalations all land in it.
Reports and CSV export: Hours per machine and operator, approval lead time, damage history — on screen, and as CSV when somebody outside the system needs it.
Machine transfer: Hand a machine to another company with an audit trail, and decide whether its history goes with it.