Wishlist: what feature would make the biggest difference for your team?

Hey everyone! Wave

We're always looking for ways to make FieldPulse work better for the teams using it every day. While we have a roadmap we're excited about, we want to make sure we're building what you actually need.

So here's the question: if you could wave a magic wand and have one new feature (or big improvement to an existing one), what would it be?

We're especially interested in hearing:

  • What pain point this would solve
  • How often it comes up in your daily workflow
  • What you're doing as a workaround today

No idea is too small or too ambitious—we want to hear it all! This thread will be shared directly with our product team, so your voice will absolutely be heard.

Looking forward to learning what's on your wishlist! Pencil

Parents
  • Pro tip: conditional logic in checklists. We do commercial HVAC and the questions I need to answer on a rooftop unit vs a split system vs a chiller are completely different. Right now I have three different checklist templates and I have to know which one to pick before I even see the equipment.

    What I want: one master checklist that asks "What type of system?" and then shows me only the relevant sections based on that answer. Would clean up our template library and reduce mistakes from picking the wrong form.

    I'm aware some form tools do this but having it native in FieldPulse would be huge. The current checklist template setup is solid but this is the gap that's cost us time on site.

Reply
  • Pro tip: conditional logic in checklists. We do commercial HVAC and the questions I need to answer on a rooftop unit vs a split system vs a chiller are completely different. Right now I have three different checklist templates and I have to know which one to pick before I even see the equipment.

    What I want: one master checklist that asks "What type of system?" and then shows me only the relevant sections based on that answer. Would clean up our template library and reduce mistakes from picking the wrong form.

    I'm aware some form tools do this but having it native in FieldPulse would be huge. The current checklist template setup is solid but this is the gap that's cost us time on site.

Children
  • yesssss this basically I do electrical and commercial vs residential is so different also sometimes I'm doing panel upgrades and sometimes troubleshooting and the checklist that's useful for one is like completely irrelevant for the other so what I did was I made this giant checklist with everything and I just skip the parts that don't apply but that's basically not a real solution tbh and I worry about missing something because I'm scrolling past so much stuff you know

  • +1 on conditional logic. Our workaround:

    • Job type drives template assignment (via automation rules)
    • Still requires dispatcher to categorize correctly upfront
    • Fails when job type doesn't predict actual work needed

    Would prefer technician-facing logic that adapts in the field.