When the Tables Have Turned.

If You Want No Schedule Buffers, Take the Financial Contingency to Zero

Here’s the deal. As Takt production systems continue scaling across this industry, more large owners are now actively trying to remove buffers from genuine schedules. I tell contractors directly, you cannot let that happen. Tell them no.

Why Buffers Are Not Optional, Even When an Owner Pushes Back

Buffers are genuine system stabilization time, nothing more exotic than that. Removing them does not make a schedule more efficient. It simply removes the one thing protecting the entire system from normal, expected variation.

I understand why an owner would want them gone. A schedule with no buffer anywhere in it looks tighter and more impressive on paper, the same way a budget with no contingency looks leaner at first glance. Neither version actually survives contact with a real, ongoing project, and both eventually cost far more than whatever was saved by removing the protection in the first place, usually at the worst possible moment to discover it.

Here is the comparison that genuinely clarifies why this matters so much. If an owner refuses to allow schedule buffers, the equivalent ask would be taking the financial contingency on that same project down to zero. These are genuinely the same concept, just expressed in two different domains, and treating one as reasonable while rejecting the other outright is exactly where the real inconsistency lives.

Nobody would actually accept that financial version of the deal. Contractors would immediately recognize zero contingency and zero allowances as an unreasonable, unworkable ask, and they would simply decline to sign that contract. Yet somehow, the equivalent demand applied to a schedule, removing every buffer entirely, gets treated as a reasonable request rather than something just as unworkable.

Watch for these genuine parallels between schedule buffers and financial contingency that reveal why removing either one creates the same real risk.

• Both exist specifically to absorb normal, expected variation rather than representing waste or inefficiency hiding somewhere inside the plan.
• Both get targeted by people looking to tighten a deal, without genuinely understanding what function they actually serve underneath.
• Removing either one does not actually make the underlying work more efficient, it simply removes protection against problems that were always going to occur eventually.

We isolate these concepts constantly, treating the schedule and the budget as if they operate under entirely different rules, when in reality the same underlying logic applies to both. A contractor asked to work with zero financial contingency would simply walk away from the deal entirely. The same response is genuinely appropriate when an owner asks for zero schedule buffer.

Several contractors I work with have already started doing exactly this, telling owners directly that removing schedule buffers is simply not something they will agree to. That willingness to say no, clearly and without apology, is exactly what protects the rest of the project from a demand that was never actually reasonable in the first place, and it deserves genuine credit as good, confident practice rather than stubbornness.

What Would Happen if the Office Got the Same Treatment the Field Does

Here is a related thought experiment worth sitting with. Office based teams routinely tell field crews things like just work the weekend, push the crew harder, or figure out a way to compress the schedule further, usually without much thought about what that actually requires on the receiving end. Picture the exact same demands applied directly to an office instead.

Imagine walking into a design or project management office and announcing a few new requirements.

• Mandatory overtime for every single office employee, starting immediately, with no real discussion about why.
• Multiple people now expected to share a single desk and workstation, simply to save space and look more efficient on paper.
• One office engineer suddenly assigned to manage seven full projects simultaneously, with someone standing over their shoulder yelling about deadlines the entire time.

Nobody would genuinely accept any of that in an office setting. People would push back immediately, point out how unreasonable it genuinely is, and refuse to work under those conditions. Yet versions of this exact treatment sometimes get applied to field crews without anywhere near the same pushback, simply because the double standard has never been reframed clearly enough for people to actually notice it.

I genuinely believe most people issuing these demands toward the field are not acting out of malice. They simply have not stopped to picture themselves on the receiving end of the exact same request, phrased in terms that would hit much closer to home.

Why Reframing the Concept Changes Everything

All it takes to expose this double standard is genuinely putting it in the right frame of mind. Once you translate a demand from the field into its exact equivalent in the office, or from the schedule into its exact equivalent in the budget, the unreasonableness becomes immediately obvious to almost anyone. The concepts were never actually different. We had simply never stopped to notice they were the same thing wearing different clothes.

This reframing technique works precisely because it removes the familiarity that lets an unreasonable demand hide in plain sight. A request that sounds routine when aimed at a field crew sounds genuinely alarming the moment it gets aimed instead at the person making the request, which is exactly why this exercise is worth doing deliberately rather than only noticing the double standard by accident.

Building This Awareness Into Your Own Negotiations

None of this requires a complicated argument to make the point clearly. It requires a direct, simple reframe, translating whatever is being asked of the field into its exact equivalent somewhere in the office, and watching how quickly the unreasonableness of that request becomes obvious to everyone involved. Practice this reframe enough times, and it becomes a genuine habit you can reach for immediately, rather than something you only think of well after an unreasonable request has already been accepted.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your teams hold the line on genuine schedule buffers and other protective system elements, using exactly this kind of reframing to help owners and stakeholders actually understand what they are asking for, before that request ever gets accepted into a real contract.

So here is the challenge. The next time someone asks you to remove a genuine buffer, whether that is time, budget, or capacity, translate that exact request into its equivalent somewhere else in the organization, the office, the budget, a different department entirely. If that equivalent sounds genuinely absurd once reframed, the original request was never actually reasonable to begin with, no matter how normal it initially sounded.

Jason Schroeder said it plainly: “If you don’t want to give me buffers in the schedule, then let’s take the financial contingency to zero.” Use that same reframe whenever a genuine protection gets targeted for removal, and watch the demand lose its footing almost instantly.

On we go.

FAQ

Why does the article compare removing schedule buffers to eliminating financial contingency specifically?

Because both serve the exact same underlying function, protecting a plan against normal, expected variation that will inevitably occur during a real project. Framing a schedule buffer request as equivalent to eliminating financial contingency makes the unreasonableness of the original demand immediately obvious, since almost nobody would accept a contract with zero financial protection built in.

Why do people treat schedule buffers and financial contingency so differently, even though they serve a similar purpose?

Because these concepts typically get discussed in completely separate conversations, with different people involved, using different vocabulary, which makes the underlying similarity easy to miss entirely. Isolating concepts by department or domain, rather than recognizing their shared function, is exactly what allows an unreasonable demand in one area to pass unnoticed while the equivalent demand elsewhere would be rejected immediately.

What is the actual lesson the article wants readers to apply beyond this specific buffer example?

That reframing a demand into an equivalent scenario in a different context is a genuinely powerful tool for exposing unreasonable requests that might otherwise go unquestioned. Whenever a protective element, whether time, money, or staffing capacity, comes under pressure to be removed entirely, translating that request into its exact equivalent somewhere else often reveals whether the original ask was ever genuinely reasonable in the first place, long before any contract gets signed around it.