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
  • We want to make sure you're set up for success with multi-visit workflows — this is a theme we're hearing from a lot of teams right now.

    A few of you mentioned the parent/child gap, and I can share that we're exploring native project containers that would let you group related work orders without the custom field workaround. Nothing committed to the roadmap yet, but it's on our radar.

    In the meantime, I'd love to hear more about how you're currently handling billing across phases — is it typically milestone-based, time-and-materials per visit, or something else? The more context we have, the better we can shape what's next.

    Feel free to reply here or drop ideas in our feature wishlist thread if you prefer. We're listening!

Reply
  • We want to make sure you're set up for success with multi-visit workflows — this is a theme we're hearing from a lot of teams right now.

    A few of you mentioned the parent/child gap, and I can share that we're exploring native project containers that would let you group related work orders without the custom field workaround. Nothing committed to the roadmap yet, but it's on our radar.

    In the meantime, I'd love to hear more about how you're currently handling billing across phases — is it typically milestone-based, time-and-materials per visit, or something else? The more context we have, the better we can shape what's next.

    Feel free to reply here or drop ideas in our feature wishlist thread if you prefer. We're listening!

Children