Request a unit for a work package
Identify project, site, date, asset class, task, operator requirement, and expected duration.
Connect project demand, unit allocation, operator readiness, pre-start checks, worked and idle time, fuel, transfers, downtime, and release decisions without losing the record behind the status.
Jodoo manages the project-facing workflow and human decisions. It does not replace equipment telemetry, GPS, OEM diagnostics, or regulated operator systems.
Start with Jodoo’s Free plan for up to five users. No credit card required.
Road vehicles, owned equipment and hired machines share a project, but they do not share the same operating limits.
Remaining work, hire end date, transport booking, return condition and daily hire charge.
For example, three unused days at $240/day add $720 before transport. Extend or release the hire deliberately; this is an example, not a market rate.
Current engine hours, next service reading and expected hours for the next work package.
A unit at 480 hours with service due at 500 has only 20 hours remaining. Schedule service or allocate another unit if the job needs more.
Mileage for the truck, engine hours for the excavator, operator qualification and site restrictions.
Keep units and inspection questions distinct. Do not combine kilometres and engine hours into one utilization number.
Defect severity, release decision, action owner and the receiving site’s need.
Resolve the hold before releasing the machine. A transfer booking is not a safety clearance.
See which unit is affected, what the project will lose and who needs to act before reallocating equipment.
Hold the unit, preserve inspection evidence, notify fleet and site supervision, and decide repair or replacement.
Show both projects the revised date, reason, impact, transfer requirement, and accountable owner.
Compare planned demand, actual worked hours, idle reason, next project need, and cost before reallocating.
Route expired or missing qualification to the supervisor before the unit is issued.
Connect the unit, project, time lost, cause, workaround, maintenance handoff, and expected return.
Permissions and views should follow the decision each role owns.
Unit readiness, allocation, documents, inspections, transfers, service position, and constraints.
Release, hold, reallocate, or send to maintenance.
Units assigned, planned release, worked and idle hours, downtime, and incoming transfers.
Confirm demand, impact, workaround, or revised release.
Today’s units, operators, pre-start exceptions, stop-use items, and due actions.
Allow work, stop use, or escalate.
Assigned unit, mobile pre-start, meter, fuel, condition, and immediate issue report.
Accept custody and report current evidence.
Failed checks and downtime records sent from the project workflow.
Plan repair and verify return to service.
Manual operating records and automated machine data serve different purposes.
Demand, allocation, approval, site handoff, operator record, inspection evidence, transfer, downtime response, and release.
Live equipment location, geofencing, automated engine hours, fault codes, remote diagnostics, or theft recovery.
Different project fields, asset classes, site checks, decision routes, permissions, and client reporting.
OEM-specific machine data, certified operator compliance, or equipment finance and rental billing.
Bring essential specialist signals into the project workflow through available integrations.
Keep the original telemetry or OEM platform as the authoritative machine source.
Road vehicles and heavy equipment need different checks, usage measures, and service schedules. Choose a workflow that keeps those differences clear.
Manage units, asset classes, projects, sites, operators, demand, allocation, inspections, service position, fuel, utilization updates, idle and downtime reasons, transfers, documents, costs, and release decisions.
Yes, with different required fields, checklists, operating units, and views. Do not force a passenger vehicle, excavator, and trailer through one identical form.
No. The example uses manually reported meter, worked-hour, and idle-hour records. Automated utilization requires an appropriate telematics or OEM integration.
Yes. The form supports condition choices, defect severity, evidence, release decision, action owner, and due date.
A failed check or downtime record creates a clear handoff with unit, site, severity, evidence, and impact. A focused maintenance workflow should manage work orders, parts, labor, and return-to-service verification.
Yes. A trained administrator can adapt forms, choices, views, permissions, rules, and dashboards for different project or asset requirements while preserving shared fleet records.
Try a failed pre-start check in the sample app. Review the hold and required action before planning the unit’s next assignment.