Forum Discussion

ProperGuy's avatar
ProperGuy
Contributor 3
20 days ago

Estimated Time or Duration of Jobs

How are others scheduling jobs without any duration or estimated time fields in Jobber?  When creating a new job, it simply prompts us to put in the exact day and time of the job we are creating.. as if we have our entire calendar and routes memorized and can just rattle it off.  So we have to mark the job as unscheduled.  But when that happens, Jobber assumes all unscheduled jobs are one hour.  There is no field for us to input HOW LONG the job is going to take.. thus all unscheduled jobs in history.. are one hour.  $50,000 paver job? 1 hour.  1,500sq ft lawn mow? 1 hour.   It seems the logical thing would be during the create a job flow, to have a field where we could put in the estimated time it’s going to take.  Then Jobber knows our calendar and can say… hey.. these are some times i found that seem to work.  Or if it’s unscheduled.. at least when we go to schedule it.. Jobber’s ‘find a time’ tool.. would be able to work off the actual time it’s suppose to take.  

So I’m asking.. how are ya’ll handling this now?  I assume most of us estimate based off how long a job will take as a the main factor… but that doesn’t really transfer to jobber well.  Are you writing estimated times in the description and then having your office manually adjust and mess with each visit individually each time a job is scheduled? Is there another way?  Are you just scheduling all jobs for 2am on a Sunday and then manually dragging them to your 10-12 routes that week?  

Really looking forward any insight into this as I don’t think Jobber is going to add time as a factor for jobs anytime soon. If we did it manually and had to falsely schedule all jobs for some random time before they were moved to a correct position on the schedule.. we’d then have to turn off all our clients upcoming visits views in the portal. 

5 Replies

  • We solved this by baking the time into the service itself instead of waiting on Jobber to add a duration field.

    Every line item in our price book carries a code that tells us the labor block up front. Format is duration / crew size / complexity / distance:

    • H1SN = half day, 1 guy, simple, near
    • F1SN = full day, 1 guy, simple, near
    • F2HF = full day, 2 guys, hard, far

    So when the office or a tech sees H1SN on a job, there's no guessing and no digging through the description — it's a half day, one man. The estimate and the schedule come off the same line item.

    To be clear, this doesn't automate anything. We still go into the calendar and manually find a slot. Jobber's "find a time" still won't help, because it doesn't know the duration. But the scheduler knows how many hours the tech needs before they start looking, so they're placing a known block instead of guessing and adjusting later. That alone killed most of the back-and-forth.

    And for what it's worth, I'm with you on the feature request. If Jobber let us attach a duration to a service, then a code like H1SN would carry four hours with it automatically and "find a time" could actually find a real slot. That's the missing piece. Everything we've built is a workaround for the fact that it isn't there.

    Two things I'd add:

    Put the codes in your actual services and line items, not the job description. Descriptions don't sort, filter, or report — services do.

    And don't show the customer the time. If they know you budgeted 4 hours and you wrap in 2, they start wondering if they should've paid less. Sell the work, not the clock.

    We run about 75 prebuilt electrical services this way through AccuPrice (accupricelists.com), which syncs with Jobber — but the concept isn't trade-specific. Pavers and mowing would build the same way, you'd just define your own duration buckets.

  • travisshepherd's avatar
    travisshepherd
    Verified Community Coach

    I keep track of estimated job times by putting the expected hours right in the job description or line item notes when creating the quote.

    ​When it comes time to schedule, we use a external scheduling app. I drag the job onto the calendar grid and manually stretch or adjust the visit block to match the actual duration.

    ​If you want to save time, you can also set start and end times directly on the schedule step when creating the job, or turn on line item durations in your settings if you have standard durations set up for your services.

    • ProperGuy's avatar
      ProperGuy
      Contributor 3

      That is what customer support suggested.  It’s just very hard and laborious to scale with several hundred jobs per week. For now, I think we’re going to see what kind of stuff we can do with their API to help us out. I just really wish unscheduled jobs allowed some sort of time management. It would fix a lot of issues and really make Jobbers own routing tool, much better. 

  • krista's avatar
    krista
    Jobber Support Team

    Hi ProperGuy​ and travisshepherd​ 

    Thanks for taking the time to lay this out in so much detail. The examples you shared really help illustrate the workflow you're trying to accomplish and, more importantly, why having duration available before a job is scheduled matters for your business.

    At this time, Jobber doesn't have a dedicated estimated duration field at the job level that works in the way you've described—where you could enter the expected duration of an unscheduled job and have that information carry into tools like Find a Time when you're ready to schedule it.

    Travis shared some helpful workarounds for managing this with the tools available today, but I also recognize that those still require additional manual steps and aren't the same as the workflow you're describing.

    We really appreciate you sharing the use case behind the request. Understanding not just the feature someone is asking for, but how its absence impacts estimating, routing, scheduling, and managing a high volume of unscheduled work is incredibly helpful context for our team. I'll make sure this feedback is captured and shared.

    • ProperGuy's avatar
      ProperGuy
      Contributor 3

      Thanks, Krista.  I know I’ve spoken with support about this before.. just trying to see if anyone has a hack or workaround.  I still feel like a company generally already knows how long a job is suppose to take, whether scheduled or unscheduled.  So allowing a company to put that information into the job and having that data drive scheduling now or in the future, would save time and improve the scheduling features Jobber already has. Travis having to manually drag, drop and expand jobs and add data points like timing into the description… all point to why duration is good data to have. Duration would also allow timers on the job to show techs how long they have on the job.  It would allow Jobber to automatically schedule jobs once created.  Lots of positives for having the data point off rip. Fingers crossed we hear something about this in the September Jobber event.