Tips for managing subcontractors in FieldPulse?

We're expanding our reach into adjacent territories and have begun partnering with certified subcontractors for overflow work and specialized services. I am curious how others are incorporating third-party technicians into their FieldPulse workflows.

Specifically, I would be interested to hear about:

  • How you structure subcontractor access — dedicated user licenses, shared dispatch accounts, or external coordination
  • Whether you require subcontractors to use the mobile app directly, or if your internal team handles documentation on their behalf
  • How you handle customer-facing elements (notifications, portal access) when work is performed by non-employees
  • Any contractual or compliance workflows you've built into checklists or documentation requirements

Another way to frame this: for those who have moved beyond simply "tracking" subcontractor jobs to truly integrating them into your operational framework, what proved to be the critical shift?

We want to ensure we're setting both our internal team and our partners up for success without creating unnecessary administrative burden or customer confusion.

Parents
  • Hi Nadia — great question, and one we hear frequently as customers scale their extended workforce strategies.

    A few resources that might help as you think through your approach:

    • We recently published Tips for Rolling Out FieldPulse to a Field Team of 50+ which includes a section on mixed employee/contractor environments
    • The user role permissions documentation covers how to restrict customer pricing and job visibility — worth reviewing before provisioning accounts

    We want to make sure you're set up for success with this expansion. I'm happy to connect you with a few other customers in similar situations if peer conversations would be valuable — just let me know and we can set something up.

Reply
  • Hi Nadia — great question, and one we hear frequently as customers scale their extended workforce strategies.

    A few resources that might help as you think through your approach:

    • We recently published Tips for Rolling Out FieldPulse to a Field Team of 50+ which includes a section on mixed employee/contractor environments
    • The user role permissions documentation covers how to restrict customer pricing and job visibility — worth reviewing before provisioning accounts

    We want to make sure you're set up for success with this expansion. I'm happy to connect you with a few other customers in similar situations if peer conversations would be valuable — just let me know and we can set something up.

Children
No Data