A solid ServiceTitan go-live checklist is the difference between a smooth launch and a week of missed calls, broken invoices, and frustrated techs. The night before you flip the switch, you should confirm that your Pricebook, Business Units, Job Types, dispatch board, and integrations are loaded and tested — then spend go-live day watching the phones and the board, not configuring settings. This guide breaks the launch into three windows: the day before, go-live day, and the first week.
What do you check the day before go-live?
The day before is for verification, not new setup. If something is still being built the night before launch, that is a red flag worth a hard conversation with your implementation team. Walk through this list:
- Pricebook loaded and spot-checked — confirm pricing, materials, and that key services have correct categories and images (Pricebook Pro if you use it).
- Business Units, Job Types, and Tags finalized so reporting and payroll map correctly from day one.
- Customer and equipment data imported and de-duplicated — pull up ten real accounts and verify history, addresses, and memberships look right.
- Memberships and Service Agreements migrated with correct renewal dates and recurring billing.
- Dispatch board configured — technician shifts, zones, capacity, and Arrival Windows set.
- Tracking numbers and Phones Pro routing tested with a live test call.
- QuickBooks integration mapped and a test invoice pushed end-to-end.
- Forms attached to the right Job Types, and the mobile app installed and logged in on every tech's device.
What should you do on go-live day?
Go-live day is about people and exceptions, not training. Your team learned the system in the weeks prior; today you watch real jobs flow through and catch what breaks.
- Have a war-room channel (text or group chat) where anyone stuck can get an answer in minutes.
- Designate a CSR lead, a dispatch lead, and a field lead — one go-to person per function.
- Book and dispatch the first few jobs slowly and deliberately. Watch each one move from call to schedule to dispatch to invoice.
- Confirm the first real invoice generates correctly, takes payment, and syncs to accounting.
- Keep a running issue log. Write down every snag with the job number so nothing gets lost.
- Resist the urge to change settings live. Note configuration gaps and batch them for later instead of editing the system while jobs run through it.
A common mistake is going live on your busiest day. If you can, launch midweek during a normal volume window so your team has breathing room.
What matters most in the first week?
Week one is where adoption sticks or slips. The system works; the question is whether your people use it the way it was built.
- Run a short daily standup to clear the issue log and answer field questions.
- Check that techs are completing jobs, capturing notes, and presenting Estimates in the mobile app — not reverting to paper.
- Watch your core Reporting and Dashboards: completed jobs, invoiced revenue, and unapplied payments. Numbers that look wrong usually mean a mapping issue, not a data issue.
- Reconcile the QuickBooks sync daily for the first week, then taper to weekly once it is clean.
- Confirm payroll inputs (timesheets, pay rates, job costing) are flowing before your first pay period closes.
- Schedule a configuration cleanup session at the end of week one to address everything you batched.
The honest takeaway
A go-live is not a finish line — it is the start of optimization. Expect rough edges, log them, and fix them in batches rather than mid-shift. The contractors who launch cleanly are the ones who verified everything the day before, watched real jobs on go-live day, and protected adoption hard in week one.
If you want a second set of eyes on your launch plan, TradeWeave is a ServiceTitan Certified Provider and can help you pressure-test the checklist before you flip the switch.