How do you handle jobs that need multiple visits?

We've got a growing number of jobs that span 2–4 visits over a week or two — think system installations with staging, rough-in, then final commissioning. Right now we're creating separate work orders for each phase, but I'm wondering if there's a cleaner way.

The pain points I'm seeing:

  • Customers getting multiple appointment confirmations for "the same job"
  • Techs showing up without context from previous visits (photos, notes buried in older WOs)
  • Dispatched as separate jobs, so we're not seeing the true capacity load
  • Billing gets fragmented — sometimes we invoice per visit, sometimes at completion

I've experimented with using a single work order and just scheduling multiple appointments, but that gets messy when phases get delayed or rescheduled. What's actually working for your teams?

Would love to hear how you're structuring these — whether it's parent/child work orders, custom statuses, or just better handoff protocols. We're on FieldPulse 3.2 if that matters.

Parents
  • okay so basically what we do is just i mean its not perfect but we have a shared google sheet that tracks the project phases and who's assigned and then when i get to the job i look at the sheet and also the previous work order notes but honestly the notes are hit or miss because some guys write novels and some guys write "done" so what i really need is the photos and basically if the photos are there im good to go

    we tried the single WO thing but customers kept calling confused about why their job was still open when we "finished" already so we went back to separate ones

  • ...Google sheet. In 2025.

    Anyway. We use the checklist templates for handoff. Required field at end of each visit: "What does the next tech need to know?" Forces the conversation.

    Still get the occasional "done" but at least there's a prompt.

Reply Children
No Data