Multi-Branch · Project-Scoped · OSHA + FMCSA
Cranes, CDL trucks, forklifts, aerial lifts, excavators, and rigging — in one platform. Multi-branch support, project-scoped operators, REST API, and telematics-ready.
14-day free trial · No credit card · All 44 templates included
Stop paying for a DVIR app, an inspection-template app, a JSA tool, and a separate BOL platform. Fleet operators run all of it from a single dashboard — and the deficiency workflow ties it together end-to-end.
Daily, monthly, and annual templates for cranes, CDL units, forklifts, aerial lifts, excavators, generators, and rigging — all with citations referenced inline. No template hunting on day one.
FMCSA 396.11 pre-trip and post-trip DVIRs sit alongside OSHA 1926/1910 equipment inspections. Drivers and operators use the same UI; dispatch sees both flows on one dashboard.
Equipment and users scoped per branch. A user can belong to one branch or many; Company Admins see the whole org. Regional yards run independently without a second tenant.
Tag operators to projects via project IDs — they only see equipment for those projects. Equipment without a project tag stays globally visible (the rigging-yard default). Mechanics bypass scoping by design.
Operator flags a fail. Mechanic gets it on their dashboard. Repair logged → verified on next inspection → audit log complete. The closed-loop replaces tag-and-call coordination.
Equipment marked Non-Operable is flagged across the fleet dashboard and locked from new lift plans. Catches the failure mode where the dispatch board didn't get the deficiency note.
Schedule monthly, annual, 250-hour, 500-hour — by date or meter hours. The dashboard surfaces upcoming and overdue items per unit so PMs don't slip when the yard gets busy.
Every unit gets a 0–100 health score blending pass-rate, open deficiency load, and overdue scheduled work. Spot the units degrading before they fail in the field.
Public /api/v1 with hashed bearer tokens. Outbound webhooks fire on inspection-completed, deficiency-opened, and repair-completed. Pipe data into your BI, ERP, or existing FMS.
Installable PWA on iOS, Android, Windows, macOS. Caches the inspection routes and queues submissions locally. No-signal yards and remote sites are first-class.
Auto-generated on the 1st against the prior month — and on-demand any time. One document per branch with pass-rate, deficiency turnaround, and overdue scheduled work.
Every inspection submission, repair logged, deficiency opened, lift plan signed, and admin setting change is timestamped and user-attributed. The first thing auditors and insurers ask for.
CSV or hand-enter. Pick the equipment type per unit — OSHA/FMCSA/ASME templates load automatically. Assign branches and projects as needed.
Operators, mechanics, supervisors, admins. Scope by branch and project. The role determines which dashboard and which workflows they see.
Daily inspections, scheduled periodics, deficiency closeout. Monthly compliance PDF lands in your inbox on the 1st. Audit log carries the rest.
FAQ · BEFORE YOU ASK
Everything that has an OSHA, FMCSA, or ASME inspection requirement on heavy iron — mobile and tower cranes, CDL trucks and trailers, forklifts and telehandlers, aerial lifts, excavators and dozers, concrete pump trucks, generators, and rigging gear. One platform replaces the stack of paper books, per-equipment-vendor apps, and DVIR-only tools that most yards stitch together.
Equipment, users, and inspections are scoped per branch. A user can be assigned to one branch or many; Company Admins see everything. The same Company can run separate branches in different regions, each with their own equipment, operators, and dashboards, without spinning up a second tenant.
Operators and supervisors can be tagged to specific projects via project IDs — they only see equipment for those projects. Equipment without a project ID stays globally visible, which is the right default for rigging gear and shared yard equipment. Mechanics are exempt from project scoping by design (they go everywhere).
Yes. Public REST API at /api/v1 with SHA-256-hashed bearer tokens. Outbound webhooks fire on inspection-completed, deficiency-opened, repair-completed, and other key events. Useful for piping inspection data into a BI dashboard, an existing fleet management system, or an ERP.
There's a telematics adapter framework with a Samsara connector wired in for pulling meter hours and asset locations. Additional vendors are scoped on the roadmap; if you have a vendor we don't yet support, the connector contract is documented for custom builds.
Yes. PDF export per inspection, CSV / ZIP bulk export by date range and equipment, monthly compliance rollup PDFs auto-generated on the 1st of each month, and an audit log of every action. Most audits we've seen come down to 'show me the documentation' — this puts it in your inbox before they ask.
14-day free trial. No credit card. All 44 templates included.
Start Free Trial