Ask Kris Anything: Why Do My Labor Minimums Keep Getting Denied?

Minimums get denied because they are misunderstood. For the most part, it’s a flaw in the system’s logic. Let’s break it down.

You’re standing in a small bathroom watching a plumber detach a toilet so the flooring underneath can be replaced. The task takes minutes, but the visit eats half a day. So when the bill comes, there’s a labor minimum attached.

A couple of days later, the same plumber comes back to reinstall the toilet. Another visit. Another minimum. The plumber charged you a minimum twice, once for each visit. 

That minimum isn’t about the toilet. It’s about buying a block of that plumber’s day. 

Travel, setup, teardown, cleanup, and the administrative drag don’t disappear just because the task is “small.” They charge them because otherwise they lose money on short, inefficient visits. Then, everything else (materials, supplies, etc.) gets added on top.

Now, this example isn’t about billing the plumber’s minimum. It’s about understanding why minimums exist and why restorers run into trouble when their estimating system doesn’t account for the same inefficiencies. Xactimate doesn’t “think in visits,” but the real world revolves around them. 

That’s why restorers get pushback. When a reviewer removes the minimum, it’s not usually because the work wasn’t necessary. It’s because your estimate didn’t make the real-world cost of the visit visible, and the system doesn’t have built-in auditing tools to recognize this on its own.

In reality, instead of removing the minimums, reviewers should be accepting more of them.

As the estimator, you still have to capture the minimum time in the estimate. You can either use the labor minimum feature or turn it off and build the minimum manually. If you build it manually, enter the minimum hours as labor time and then add any related materials and equipment as separate line items. That approach works, but it can get confusing, cumbersome, and hard for the untrained eye. 

The Truth Behind Minimums: It’s About the Visit, Not the Task

A labor minimum isn’t tied entirely to the size of a task.  It reflects the real cost of getting a trade to the site, prepping, performing the work, cleaning up, and moving on. It’s the cost of on-site inefficiency: small tasks that consume big chunks of the day.

The pricing model spreads a trade’s work, planning, travel, and cleanup across an eight-hour day. That structure breaks the moment the job is too small to absorb those assumptions. That’s why the minimum exists: it corrects the math that the system gets wrong on small tasks.

But the minimum alone almost never tells the whole story. The estimator must account for everything the system can’t see. 

For example, let’s say a minimum is for 2.5 hours. Xactimate accounts for 60 minutes drive time in an 8-hour day, so 2.5 hours only allows for 18.75 minutes of travel time. If this isn’t enough, additional time must be entered manually. The same thing happens with planning: only a 30-second allotment for that. So, more time needs to be added, and so on. You get the point. 

Minimums apply only to the internal components built into that trade. If the real job requires disposal time, staging, admin, or coordination beyond that, you have to add it manually. Estimating platforms will never assume it for you; they’re built on a single set of assumptions. You can’t blame Xactimate for that; it’s how unit pricing works. The estimator’s job is to recognize when those assumptions don’t match the job and adjust accordingly.

Why Minimums Get Denied: The Blind Spot Inside Your Estimate

Reviewers aren’t rejecting the work. They’re reacting to the lack of explanation.

A tiny measurement on paper looks like it should fall inside a smooth, efficient workflow. Without context, the minimum looks unnecessary. And when the reviewer sees one small line item with a big minimum, they do what their process tells them to do: cut it.

Minimums get denied because the story is incomplete. So ask the question that forces clarity: If you don’t want it shown as a minimum, how do you want the cost shown? Rate and materials, or a separate mobilization charge?

The System Can’t Think Like a Trade, So You Have To

If you want to understand labor minimums, stop thinking like an estimator and start thinking like a subcontractor.

A plumber doesn’t adjust their minimum to match the length of the pipe they replaced. An electrician doesn’t lower their rate because the breaker swap was quick. Trades charge per visit. They charge for the disruption to the schedule and the break in the day’s momentum.  

The pricing model doesn’t know any of this unless you tell it. It only knows the quantity. You have to rebuild the real-world visit inside the estimate. That means separating visits, adding travel time, and accounting for the support tasks that the minimum doesn’t cover.

Honestly, that’s what an estimator’s job is: understand the scope, understand the cost to execute, then explain it clearly to the person paying the bill. 

Break the Job Down into Rate and Materials to Find The Truth

Let’s look at sequencing, or orders of operations. Think of this as how the job will actually get done.

Going back to the plumbing example, we remove the toilet. That might be 30 minutes of hands-on work, but it triggers a 2.5-hour minimum. Let’s say that costs $250. You can charge it as a minimum, or you can build it as a rate and materials charge of 2.5 hours at $100 per hour. Either way, it’s the same cost; the difference is how the system presents it.

The system fails when you have another small plumbing task later. The plumber will charge you another 2.5 hours to reset the toilet two days later. Another $250 minimum. But the system is dumb, not dumb dumb, but know the job is being executed across separate visits. It doesn’t recognize that the reset occurs after the floor is replaced, which requires another scheduleinterruption. So, the plumber charges $500 for two visits, while Xactimate may only allow one minimum of $250 if it’s written like one continuous workflow. 

That’s the break: minimums get applied to the job, not the schedule. The system prices “detach and reset the toilet” as if it happened in the same visit. It didn’t, and if it had, it would’ve been one $250 minimum.

The Truth: Small Jobs Are Where Margins Quietly Drain

Big jobs usually take care of themselves. There’s enough scope and production to absorb setup, travel, and inefficiencies, so the numbers stay balanced. 

The issue can still show up, though, when multiple trades are involved. In estimating theory, it can look like one minimum “covers” several small tasks. But in the real world, it doesn’t. An appliance tech and a plumber on the jobsite don’t share the same minimum. They’re two separate companies with two separate mobilizations and workflows, so one minimum ends up shorting both.

The real trouble shows up on the small jobs. The ones everyone thinks will be quick. The ones that look harmless until you add up what actually happened, and HOW it actually needs to be done. 

Most of the time, the measurable task is rarely the problem. It’s everything wrapped around it: the walk from the truck, staging, containment, cleanup, coordination, answering questions, and paperwork. All of that takes longer than the task you’re charging for. And if you have to go back, it’s a completely different visit on a different day, which requires a new minimum.

The problem is that the pricing model automatically shrinks those steps. Real life doesn’t. And that gap is where the business loses money, costs rise, and it all has to be accounted for.

That’s why jobs under $5,000 can quietly eat margin if minimums aren’t applied correctly. These little tasks are the most inefficient and the least forgiving. The minimum is often the only way to capture costs that the system will never detect on its own, especially when sequencing creates additional visits. Manually calculating the travel, plus the site work, is key. 

Small jobs may look simple. They’re not. They’re the ones that quietly drain profit when the minimum isn’t applied the right way.

How To Make Minimums Stick: Your Role in Telling the Real Story

A minimum only works when you show why it applies. If the task exceeds what the minimum covers, you add time. If the job requires multiple visits, you apply multiple minimums. If disposal, administration, or staging happened outside the minimum, you document it. If any travel time falls outside the minimum, it must be added manually. The system won’t capture it, and the business will absorb the cost if you don’t.

You are responsible for reconstructing the real job inside the pricing model. This means understanding adds costs to the job, then showing it clearly to your client. And if you choose to work in a program, you must clearly explain it to that partner. There’s a real disconnect between how work actually happens in the real world and how the estimating system accounts for it. 

There is more to this, but that’s the best explanation I can give you in a limited space. The takeaway is simple: communicate the complexity of the job, because the simplicity of Xactimate doesn’t cover this situation well. 

Have a Question for Me?

If you’d like your question featured in this column, submit it through the form on the landing page. Include your name, company, and location to be credited, or if you prefer, you can remain anonymous.

Want Estimators Who Understand Minimums Correctly?

Xactimate is a model. Your jobs aren’t. Estimating Secrets teaches your team how to bridge that gap: how to capture the visits, sequencing, support time, and the minimums the system won’t automatically see, and how to write it so reviewers can’t ignore it. If you want estimators who stop underbilling and start getting paid for how the job truly runs, visit ProfitableRestorer.com to learn about Estimating Secrets.