> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tread.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Go-Live Checklist
> The QA pass to run before flipping your fleet to Tread — data, integrations, mobile, billing setup, training.
## What you'll do
Run a final QA pass across nine categories before your first live dispatch. This is the last gate — once you flip live, drivers, customers, and vendors are on Tread.
## Before you start
* All [master data](/onboarding/master-data/overview) imports complete.
* [Integrations](/onboarding/integrations) connected.
* [Agent configurations](/onboarding/agent-configurations) reviewed.
* A test project ready for the dry-run dispatch.
## The checklist
Work through each category. Don't flip live until every box is checked.
All master data sets imported. Sample records reviewed by an admin.
* [Users](/onboarding/master-data/users) — all admins, dispatchers, and back-office staff invited. Internal drivers created here with the **Driver** role.
* [Drivers](/onboarding/master-data/drivers) — every O\&O and contract driver loaded with a unique phone.
* [Customers](/onboarding/master-data/customers) — including all Connected Customer invites accepted.
* [Vendors](/onboarding/master-data/vendors) — all subhaulers connected.
* [Equipment Types](/onboarding/master-data/equipment-types) — capacity and unit of measure set on each.
* [Equipment](/onboarding/master-data/equipment) — every truck loaded and named consistently.
* [Materials](/onboarding/master-data/materials) — pulled from accounting.
* [Sites](/onboarding/master-data/sites) — lat/long set, geofences validated.
* [Departments, Labels & Service Classes](/onboarding/master-data/departments-labels-classes) — only the ones you'll actually use.
Entities sit at the right level. Shared resources flow correctly.
* [Company hierarchy](/onboarding/company-hierarchy) reviewed — flat unless you have real regional splits.
* Equipment shared from owning entity into operating entities (if multi-entity).
* Drivers shared across the hierarchy where they run loads.
* See [Multi-Entity Billing](/specialized/multi-entity-billing) if money flows between entities.
Every system that needs to flow into or out of Tread is live.
* [Telematics](/integrations/telematics) — connected; assets matched to equipment; live GPS visible on the dispatch board.
* [Paver Tracker](/integrations/paver-tracker) — connected if you pave.
* Accounting integration ([QuickBooks](/integrations/quickbooks), [Sage](/integrations/sage), [Vista](/integrations/vista), [Foundation](/integrations/foundation), or [Spectrum](/integrations/spectrum)) authenticated and test invoice synced.
Decide what's on and what's off.
* **Ticket Chaser** — on or off? See [Agent Configurations](/onboarding/agent-configurations).
* **AI Reviews** — on or off? Add custom instructions for what the agent should approve or flag. There is no user-set confidence threshold.
* Review the [Common Mistakes](/resources/common-mistakes) page for agent-related pitfalls.
Field users have the apps on their devices and can sign in.
* [Driver App](/mobile/driver-app) installed on at least two driver phones — confirmed sign-in.
* [Foreman App](/workflows/foreman) installed for any field foreman who'll create or approve work.
* One test ticket captured end-to-end on a real device.
Every active customer can be invoiced correctly on day one.
* [Rates](/workflows/manage-rates) assigned — freight and material rates cover every active customer and project.
* Billing address and billing email set on each [customer record](/onboarding/master-data/customers) — the address prints on PDF invoices.
* One sample invoice generated and reviewed with the customer's AP contact.
One full project end-to-end on a real driver, real truck, real ticket — with billing skipped.
* [Project, order, and dispatch created](/workflows/create-a-project).
* Driver received the dispatch on their phone.
* Ticket captured and approved.
* Settlement generated but not sent.
Every role that will use Tread has had a walkthrough.
* Admin user — full platform tour.
* Dispatcher — dispatch board, [intra-day changes](/specialized/intra-day-changes), agent overrides.
* Foreman — [Foreman in the Field](/workflows/foreman) walkthrough.
* Driver — Driver App install, ticket capture, e-signature.
Everyone affected knows what's changing and when.
* Vendor notification sent — every connected hauler knows go-live date.
* Customer notification sent — AP contacts know to expect Tread invoices.
* Internal comms — ops, billing, and exec team aware.
* Escalation contact named — one person owns Tread questions during the first two weeks.
## Verify
Every category above shows as complete. Your test invoice cleared your accounting system. At least one driver has run a real ticket end-to-end and the settlement was reviewed. Then flip live.
## Common mistakes
**Going live without the dry-run.** A regional hauler skipped the test dispatch. Day one, the dispatch board worked but settlements failed because rates weren't tied to the right customer. Run the dry-run — it catches this kind of gap in an hour.
**Going live without an escalation owner.** Day one will surface questions. Without a named owner, those questions go unanswered and get worse. Pick one person before flipping live.
**Skipping vendor and customer notification.** Connected vendors and customers need to know when to expect connection invites and Tread-formatted invoices. Without notice, they'll bounce both. Send the notification at least one week before go-live.
## Related
* [Master Data Overview](/onboarding/master-data/overview) — every data set this gates on
* [Common Mistakes](/resources/common-mistakes) — pitfalls to spot before go-live
* [Track Drivers & Collect Tickets](/workflows/track-drivers-collect-tickets) — what runs on day one