GoPlumberBusiness resources

Scheduling & dispatch

Plumbing Job Time Estimates for Scheduling: Use Your Own History

At a glance

Use comparable completed jobs to estimate a service block, then add the separate time your schedule needs for travel, preparation, and closeout. Keep uncertain or unassessed work visible instead of treating every job type as a fixed duration.

In this guide
  1. Define the time you are estimating
  2. Group genuinely comparable jobs
  3. Compare the center and the spread
  4. Separate the customer's window from the internal block
  5. Build a review trigger for overruns
  6. Improve the estimate over time

Define the time you are estimating

A job's billed hours, on-site time, technician clocked time, and full schedule block may be different. Choose the definition before calculating an average.

For scheduling, the relevant block may include travel, preparation, service, and documentation. Do not add a travel allowance to a historical figure that already includes travel without checking the definition.

This is a planning method, not a technical standard for how long plumbing work should take. Job requirements and safe staffing remain professional decisions.

Group genuinely comparable jobs

Compare similar scope, access conditions, staffing arrangements, and service type. Do not mix an initial assessment with a complete installation simply because both were labeled under the same equipment category.

Record unusual events separately, such as missing access, unapproved additions, or an unexpected return trip. Do not delete them merely because they make the average less attractive. Understand whether they are rare exceptions or recurring parts of the workflow.

job_id,service_group,scope_basis,staff_count,on_site_minutes,travel_prep_minutes,closeout_minutes,exception_reason,record_complete
JOB-EXAMPLE,defined_service,approved_scope,1,90,25,10,,true

The sample is fictional. Use complete records with consistent definitions before calculating a planning value.

Compare the center and the spread

Suppose five fictional comparable service durations are 60, 75, 80, 90, and 145 minutes. The median is 80 minutes; the average is 90 minutes. The long visit should prompt a review of its circumstances, not automatic deletion.

If it involved a recurring access issue, that issue may need a readiness check. If it included separately added work, the duration may belong in a different scope group. If the data is simply wrong, correct it with a traceable note.

A small sample gives limited confidence. Use a planning range and revisit it as better records become available rather than presenting a precise duration as guaranteed.

Separate the customer's window from the internal block

A customer-facing arrival window communicates when the visit starts. The internal block reserves the team's capacity. They should be related but not confused.

For example, a 90-minute expected service plus 30 minutes of separate travel and closeout uses a 120-minute planning block. That does not mean the customer was promised exactly 90 minutes of work or a completion time regardless of conditions.

Build a review trigger for overruns

When the job materially exceeds its planning assumption, have the technician or office update the schedule and affected customers through the established process. Do not wait until the next appointment is already missed.

Record whether the cause was scope change, missing readiness, inaccurate estimate, or another factor. The reason is more useful than merely labeling the technician “slow.”

Improve the estimate over time

Review comparable jobs periodically and adjust the planning assumptions when the evidence supports it. Keep the previous definition and effective date so changes remain understandable.

The objective is not the shortest possible block. It is a schedule that reflects the work you actually perform and leaves the office enough information to communicate changes honestly.

Sources and editorial notes

Product and documentation references checked September 29, 2026. GoPlumber publishes this guide about its own product category. Examples and templates are original illustrative material, not customer case studies or market benchmarks. Confirm current vendor terms before acting.