Start with a clear path forward.

Yes. TMS Software uses a multi-tenant workspace model. Authorized users can create or join multiple company workspaces, switch between them from their account, and keep each company's customers, drivers, shipments, documents, settings, and team access separated.

Immediately after verification, the only required company setting is your time zone. The setup screen also accepts these optional details:

• Fleet size
• Your role in the company
• Business phone number
• USDOT number
• MC number

You can skip the optional fields and update them later.

The workspace checklist recommends adding the legal business name, primary business address, company time zone, and applicable USDOT or MC/MX identifiers. These details become the foundation for your operational records.

Yes. Company setup can be skipped, and the company profile and preferences can be reviewed or updated later from workspace settings.

The dashboard guides you through four operational milestones: add a customer, add a driver and truck, create a shipment, and assign the shipment to a driver.

Yes. Customer and driver records support CSV imports with column mapping, validation review, and duplicate handling before you confirm the import.

Yes. The workspace owner can add teammates and manage their access roles. Set up the company under the first owner account, then add the dispatchers, operations staff, and other team members who need access.

Dispatchers can work with multi-stop shipments, assign drivers, update shipment and stop statuses, review route and map context, follow shipment activity, and keep operational documents attached to the load.

Yes. Drivers activate their own secure access and see only their assigned work. They can acknowledge loads, review stops, update stop progress, share location, and upload shipment documents such as proof of delivery.

Yes. Drivers can share location updates from the driver workspace, and authorized office users can review available driver-location context on operational maps. Deeper telematics and HOS integrations remain on the roadmap.

Yes. Reusable shipment forms, shipment custom fields, waypoint custom fields, and configurable shipment and stop statuses let each workspace shape its operating record.

Yes. Delivered loads can move through billing-readiness checks into numbered invoices. Your team can generate a PDF, send the invoice by email, review delivery attempts, and download an invoice package with supporting documents.

Yes. The accounts-receivable workspace supports partial and full payments, payment reversal, open balances, due dates, and aging visibility. Financial reports summarize invoiced revenue, payments, outstanding balances, operating costs, and margin.

Yes. Earnings and deductions can be recorded against loads, collected into a driver settlement period, reviewed, approved, marked paid, and downloaded as a settlement statement.

Yes. Provider-neutral accounting exports include invoice and payment snapshots, downloadable CSV files, retry status, external accounting identifiers, and record-level reconciliation. Direct connections to additional accounting providers remain part of the broader roadmap.

Safety, compliance, and maintenance readiness. The planned work includes driver qualification expirations, equipment documents, inspections, defects, dispatch warnings and holds, preventive maintenance, service history, and deeper HOS context.

No. The roadmap communicates product direction and current priority without inventing delivery dates. Scope and sequencing may change as workflows are validated with carrier teams.