Questions, answered

Click Get started, then use Proto to configure Tire Management for your business. Pilot an operating organization with known vehicle assignments, dated tire observations and an independent Maintenance Reviewer. Rehearse a rotation, a rejected request and an uncertain completion before expanding.

The inspection retains the tire serial, inspection date, tread depth in thirty-seconds of an inch and position, together with its organization and parent load. Tire Inspector checks those details before submitting the observation for review.

Keep the earlier observation and add the later dated observation for the same serial. Use the maintenance evidence to explain the change. Confirm the relevant vehicle through the parent load’s assignment instead of attributing every observation to the latest assigned vehicle.

Maintenance Reviewer independently decides the submitted case with a recorded reason. Tire Inspector supplies the measurement and supporting evidence. A returned request needs clarification before work proceeds, while a rejected request does not authorize maintenance.

Complete an approved inspection after the actual maintenance evidence and the matching operation receipt support that outcome. A failed or uncertain result stays open for investigation until the team establishes what happened and retains the required receipt.

Fleet Coordinator reviews vehicle readiness and defect repair evidence with Dispatcher. Dispatcher checks the driver and vehicle interval, eligibility and other commitments before release. The load retains its original promised delivery time alongside actual movement evidence.

Supporting files belong to the parent load and retain their uploader, date, evidence type and Internal or Shared visibility. Agree the audience during setup and test access with a restricted account before sharing maintenance evidence across teams or partners.

Operations Analyst reads the original receipt, checks its action and revision, and compares the linked effects with physical evidence. Unresolved outcomes remain visible for review. The investigation should establish whether the action occurred before another execution is considered.

Yes, as a connection to set up with the provider and responsible operating owner. Agree identity mappings, evidence references and retry behavior, then test duplicated events and uncertain outcomes. Review the integration plan before enabling recurring exchanges.

The base account and ordinary manual work in the official interface follow the platform’s free usage policy. Machine work, model usage and retention beyond the included allowance are metered; implementation is priced separately. Use the pricing page for the rate card and credit rules.