Ask ServiceTitan and each alternative vendor to demonstrate the same generator job in the configuration being quoted, using a representative equipment list, agreement, quote, completed report, and invoice that your office can compare with its current work.
Keep the result. Screenshots, sample reports, and written integration scope give the office something to review after the sales call. They also distinguish demonstrated behavior from a future configuration promise.
Follow a specific generator
At a site with more than one generator, find the unit by serial number and check make, model, kW rating, fuel type, and the associated ATS so an address match cannot hide an incorrect equipment link.
RECORD CHECK
Review the scope and deliverable
Generator and transfer switch work need identifiable equipment and visit records. Confirm the applicable maintenance program and customer reporting requirements. Where NFPA 110 applies, review the adopted edition and AHJ expectations before configuring the cadence or checklist.
Ask a qualified reviewer to inspect the sample report. Check the ATS transfer and retransfer observations, any recorded deficiencies, and the equipment links. For load bank work, locate the recorded load and duration with the supporting test documentation.
Demonstrate PowerOps with the same case
Equipment and mobile capture
PowerOps links equipment records, service work, and submitted inspection documentation. Technicians add current readings and observations against the job. Prior inspection information can provide reference values; it does not establish that a new measurement or test occurred.
Inspection, checklist, and service-report drafts save locally with an online session check. Reconnect to resume or submit them; they never submit in the background. Only eligible note and labor operations support automatic sync. Photos, signatures, time and status actions, and completion require a connection.
Handoffs and approvals
Authorized staff convert a quote into a draft work order and review the carried information before approving scheduling. A won quote does not schedule or dispatch work. Service completion records the actual prior state without inventing earlier dispatch history.
Supported audited actions retain an authenticated account, server timestamp, attestation, and saved snapshot. These audit entries are append-only; working forms remain editable through permitted workflows. Payment receipt can mark an invoice Paid. Configured AI assistance produces drafts and does not approve gates.
Check the surrounding operation
- Review agreement coverage and due work before generating draft PM work orders.
- Use separate technician and office accounts to test permissions.
- Compare approved scope, recorded completion evidence, and the proposed invoice.
- Trace reporting totals back to paid invoices, work orders, or recorded job hours.
- Confirm provider setup for any external service you plan to use.
Agree the migration boundary
Retaining another platform requires a clear owner for customer, equipment, and billing data. Confirm the actual integration path with each vendor. PowerOps does not promise live ERP synchronization or automatic migration of an arbitrary history.
Before expanding the import, reconcile a sample of the new records against original files that include multiple units at one site, an ATS association, historic reports, an open repair, and an agreement renewal, checking the attachments and dates as well.
Make the decision from evidence
- List the demonstrated workflow and report requirements each candidate meets.
- Assign an owner and resolution date to every remaining gap.
- Compare the written recurring price, implementation scope, migration exclusions, and support terms.
- Confirm that the people who will dispatch, perform, review, and bill the work can use the resulting process.