Inspect every load, vehicle and depot — without the paper.

Every forklift pre-started, every service on the calendar.

The plant register is the company’s list of machines: the forklifts, reach trucks, scissor lifts, trucks and trailers, owned or hired in. Each one carries its service interval, its insurance, its operators and the tickets they operate under. The operator runs the morning pre-start from their phone against the checklist for that kind of machine, and a No goes straight to the managers with the machine, the site and the line that failed.

When a check fails, the manager sets the machine Out of service on the register and raises the defect or work order for the repair, so everyone can see which machines are off the floor, why, and who decided.

• Forklifts, trucks, trailers, EWPs
  One company register: make, model, serial, road and plant registration, and the hire company for gear that is hired in. A machine moves between sites without its history splitting in two.
• The daily pre-start, from a phone
  Your own checklist per category, so the forklift and the scissor lift get different questions. Yes, No or N/A on every line, an hours or km reading, and the operator’s signature. Nothing skips a line.
• A No tells the managers
  A failed check notifies every admin and manager with the machine, the site and the line that failed. The register shows Check failed, Not checked today or Checked today against each machine.
• Service due, insurance expiring
  Set the service interval and the next date works itself out. Managers get a reminder 14 days before a service and 30 days before a policy expires, and again if either slips past.
• Operators and their tickets
  Name who drives each machine and the licence they drive it under. When the ticket lapses, the machine shows it.
• Service history and certificates
  Every logged service, the service sheets and the insurance certificate kept against the machine, not in a folder on someone’s desktop.

The racking walk that raises its own faults.

Run reusable racking, dock and yard inspection checklists from a phone, filed against a named dock, aisle or bay. Every No raises a tracked defect with its photo, and the check flips back to Yes when that defect closes, so the walk and the fault list never drift apart. It works offline in the yard and the cold store. The same walk-through, run on an office building rather than a depot, is the facilities condition walk.

• Racking, dock and yard walks
  Build the walk once as a reusable checklist and run it per aisle, dock or site. Yes or no as you go, with a photo where it is a no.
• A No raises the defect for you
  Every failed check becomes a tracked defect linked back to the question, and the question flips back to Yes when that defect closes.
• Hold points for the checks that matter
  Mark the racking load sign or the dock leveller check as a hold point and the walk waits on it.
• Filed against the aisle or the dock
  The location tree resolves to Dock 3 or Aisle 14, bay 2. A QR label on the dock door opens that location’s list for a signed-in user.
• Works offline at the depot
  No signal in the yard or the cold store? Defects, photos and checklist answers save on the phone and sync when it reconnects.
• Reports for the site lead
  Fifteen reports across PDF, Excel and CSV, filtered to the site, location, date range or status, and scheduled to whoever needs them.

Settle the claim with proof, not paperwork.

Log damage at receipt and dispatch with annotated photos that keep their capture time and who took them. Every report is attributable and its history is append-only, so condition at each handover is clear, and a carrier who disagrees says so on the record rather than in an inbox. Outside carriers and contractors get an emailed link to the work issued to them, with no app and no seat.

• Damage logged at the handover
  Dock staff log damage at receipt or dispatch with photos and a description, while the driver is still standing there.
• Capture time, not upload time
  A photo taken in the cold store at 5:40 and synced at 9:00 still says 5:40, alongside who took it. Annotations never touch the original.
• Assign and auto-chase
  Issue it to maintenance, the carrier or the site lead with a due date, and let workflow rules chase what goes overdue.
• Filed where it happened
  Damage logged against the same dock door every week shows up as a pattern on one location, not as six emails with six spellings.
• A trail nobody edits
  Every status change is appended with a name, a role and a time. The record holds up for insurers, carriers and auditors.
• No login for carriers and contractors
  An outside company gets an emailed link to the work issued to them. They add the photo of the fix and mark it done; you close it.