Construction Float & Slack Time Guide for Contractors | Projul

If you have been running construction projects for any length of time, you already know that schedules rarely go exactly as planned. Weather kills a week. A material shipment shows up late. A subcontractor no-shows on a Monday morning. The question is never whether something will go sideways. The question is whether your schedule can absorb the hit.

That is where float comes in. Float (sometimes called slack time) is the built-in flexibility in your schedule that determines how much a task can slip before it starts causing real problems. Understanding float is not just an academic exercise for CPM nerds. It is a practical skill that separates contractors who finish on time from those who are constantly scrambling, burning cash on overtime, and making excuses to owners.

This guide breaks down what float actually is, the difference between the two types you need to know, how to use it strategically, and the mistakes that trip up even experienced contractors.

What Is Float in Construction Scheduling?

Float is the amount of time an activity can be delayed from its earliest start date without affecting either the next activity or the project completion date. Think of it as breathing room. Some tasks in your schedule have days or even weeks of flexibility. Others have zero. The ones with zero float are your critical path activities, and those are the tasks that keep you up at night.

Here is a simple example. Say you are building a commercial office and your schedule shows that the HVAC rough-in can start on March 5 but does not actually need to start until March 12 for everything downstream to stay on track. That seven-day gap is float. If the HVAC crew is a few days late, no harm done. But if they blow past March 12, now you are pushing back insulation, drywall, and everything after it.

Float exists because not every task in a project is on the longest path through the schedule. Some chains of work are shorter, and the difference between the shortest and longest path through any section of the schedule creates that pocket of flexibility.

If you are still building schedules on paper or in spreadsheets, float is nearly impossible to calculate accurately. That is one reason contractors are moving to dedicated construction scheduling software that calculates float automatically with every schedule update.

Free Float vs. Total Float: Know the Difference

Read real contractor reviews and see why Projul carries a 9.8/10 on G2.

This is where most contractors either check out or start mixing up terms. But the distinction matters, because free float and total float tell you different things about your risk exposure.

Total float is the maximum time a task can be delayed without pushing back the project completion date. This is the big-picture number. If a task has 10 days of total float, you can delay it by up to 10 days and still finish the project on time. Go past 10, and your end date moves.

Free float is the maximum time a task can be delayed without delaying the immediate next task in the sequence. This is the local number. A task might have 10 days of total float but only 2 days of free float. That means you can slip 2 days without affecting the next crew, but if you slip 5 days, the successor task gets pushed back even though the overall project end date is still safe.

Why does this matter in the field? Because free float tells you how much room you have before you start creating a chain reaction. If you are juggling crew assignments across multiple jobs and need to pull a crew off for two days, checking free float tells you whether that move will ripple into your next trade’s start date. Total float tells you whether you are risking the overall deadline.

Here is a quick way to remember it:

• Free float = room before you bother the next guy
• Total float = room before you bother the owner

Calculating both types requires a forward pass and backward pass through the schedule network. The forward pass determines the earliest start and finish for each task. The backward pass determines the latest start and finish. The difference gives you float values. If you want to understand the scheduling methods behind this, check out our guide on construction scheduling methods.

Most modern scheduling tools handle this math automatically. The important thing is that you know how to read the output and act on it.

How to Use Float Strategically on Your Projects

Float is not just a number on a Gantt chart. It is a resource, and like any resource, you can spend it wisely or waste it. Here are practical ways to put float to work on your projects.

Prioritize crew and equipment allocation. When you have limited crews or a single piece of specialty equipment, float tells you which tasks have flexibility in their timing. Schedule your constrained resources on critical path tasks first, then use float windows to slot in non-critical work. This prevents the all-too-common problem of tying up a crane on a task that has three weeks of float while a zero-float activity sits waiting.

Manage subcontractor conflicts. If two subs need the same work area at the same time, check which task has more float. The one with more breathing room gets bumped. This keeps the critical path moving without turning the jobsite into a parking lot of idle crews waiting for access.

Build in weather buffers without padding the whole schedule. Instead of adding blanket padding to every task (which owners and GCs hate to see), use float strategically. Place weather-sensitive activities like exterior concrete, roofing, or site grading on paths with existing float when possible. If that is not an option, at least know which weather-sensitive tasks are on the critical path so you can plan contingencies.

Negotiate change order timelines. When an owner requests additional scope, knowing your float situation gives you real data for the conversation. If you have float on the affected path, you might absorb minor changes without a time extension. If float is already consumed, you have the documentation to support a schedule extension request. This is closely related to how delay claims work in practice.

Sequence procurement around float. Long-lead items that feed into critical path tasks need early ordering. But materials feeding into high-float tasks? You can push those purchase orders back, improving your cash flow without putting the schedule at risk. Pair this thinking with solid budget tracking and you are managing both time and money with the same data.

The key mindset shift is this: float is not wasted time. It is a strategic buffer that you should be aware of, protect where needed, and spend deliberately when it makes sense.

Protecting the Critical Path: Where Float Equals Zero

The critical path is the longest continuous chain of dependent tasks from project start to finish. Every task on the critical path has zero total float. That means any delay on any critical path task pushes back the entire project. No buffer. No forgiveness.

Protecting the critical path is the single most important job of the project scheduler. Here is how to do it.

Identify it clearly and keep it visible. Your schedule software should highlight critical path tasks in a different color or flag them. Make sure your superintendent and project manager can see the critical path at a glance, not buried in a 500-line Primavera printout. Good scheduling best practices start with visibility.

Monitor near-critical tasks. Tasks with very low float (say, 1 to 3 days) are almost as dangerous as critical path tasks. One small delay and they become critical. Track these near-critical activities separately and treat them with nearly the same urgency.

Hold weekly schedule reviews. Do not just look at the schedule when something goes wrong. Review it weekly with your team. Walk through the critical path, check float consumption on key tasks, and flag anything that is trending toward zero. This is where milestone tracking becomes a practical management tool rather than a reporting exercise.

Control the predecessors. A critical path task can only start on time if its predecessors finish on time. Look upstream. If a predecessor with float is trending late, it might eat through its float and deliver a late start to a critical task. You need to catch this early, not on the day the critical task was supposed to begin.

Document everything. When float gets consumed, write down why. Contemporaneous records of float consumption are gold in dispute resolution. If the project ends up in a delay claim, your records showing when and why float disappeared will be the backbone of your position. Our guide on delay analysis methods covers this in detail.

The critical path is not static. It can shift as the project progresses and delays hit different parts of the schedule. A task that had 15 days of float in month one might be on the critical path by month three. This is why regular schedule updates are non-negotiable.

Common Scheduling Mistakes Contractors Make with Float

Even experienced contractors make mistakes with float. Some of these come from misunderstanding the concept. Others come from bad habits or shortcuts that seemed harmless at the time.

Mistake 1: Ignoring float entirely. Some contractors never look at float values. They build a schedule, hand it off, and manage by gut feel. That works until it doesn’t. When three tasks slip in the same week and suddenly the project end date moves by two weeks, the reaction is always surprise. It should not be. The float values were telling the story the whole time.

Mistake 2: Treating all float as free to spend. Just because a task shows 10 days of float does not mean you should casually burn through it. That float might be shared across multiple tasks on the same path. When one task consumes the float, every downstream task on that path loses it too. This is especially dangerous with total float on long chains of activities.

Mistake 3: Padding every task duration. Some schedulers add extra days to every task “just in case.” This creates artificially inflated schedules that nobody trusts. Owners push back. The field ignores the schedule because the dates seem unrealistic. And worse, the hidden padding obscures where the real float exists. Be honest with your durations and let the network logic create natural float.

Mistake 4: Not updating the schedule. Float values are only accurate if the schedule reflects reality. If you built the schedule in preconstruction and never updated it, the float numbers are fiction. Actual start dates, actual finish dates, remaining durations, and logic changes all affect float. Update weekly at a minimum.

Mistake 5: Confusing float ownership. On many commercial projects, the question of who “owns” the float becomes contentious. Does the GC own it? The owner? The sub whose task carries it? Contract language varies, but the default legal position in most jurisdictions is that float belongs to the project. Whoever needs it first gets it. This creates a race-to-consume dynamic that smart contractors manage by documenting float usage carefully and addressing float ownership in contracts before disputes arise.

Mistake 6: Using float to justify slow starts. A task has 15 days of float, so the sub starts it 10 days late on purpose. Then weather takes out 3 more days. Now that task is on the critical path with 2 days of delay already baked in. Float is a safety net, not an invitation to procrastinate. Encourage early starts when possible, and you will thank yourself when the inevitable disruption hits.

Mistake 7: Failing to communicate float status to the field. Your superintendent does not need to know every CPM calculation, but they do need to know which tasks can slip and which cannot. A simple color-coded schedule or a weekly email highlighting critical and near-critical activities goes a long way. If you are looking for tools that make this easier for field teams, take a look at construction apps built for the field.

Putting It All Together: Float as a Management Tool

Float is not some abstract scheduling concept that only planners care about. It is a daily management tool. When you understand float, you make better decisions about where to put your people, when to push back on change requests, how to sequence work around constraints, and when to sound the alarm on a slipping timeline.

Here is what putting float to work looks like in practice:

Monday morning planning meeting. Pull up the schedule. Look at this week’s critical path tasks. Which crews are assigned? Are materials on site? Any predecessors still open? Then check near-critical tasks. Any float consumption trending in the wrong direction? This takes 15 minutes and saves hours of firefighting later in the week.

Change order negotiation. Owner wants to add a feature. You check the affected schedule path. There is 8 days of float. The added scope takes 5 days. You can absorb it without a time extension but document the float consumption in writing. If another change hits the same path, you have the paper trail showing the float is already gone.

Subcontractor coordination. Two subs need the same area. Electrician’s task has 12 days of float. Plumber’s task has 2 days. Plumber goes first. Simple, data-driven decision instead of whoever complains the loudest.

End-of-month owner reporting. Instead of vague statements like “we are on track,” show the critical path status and float trends. This builds confidence with owners and gives you credibility when you need to request a time extension for legitimate reasons.

The contractors who consistently deliver on time are not lucky. They are not working with better subs or getting better weather. They understand their schedule at a deeper level than just a list of bars on a chart. They know where the flexibility is, where it is not, and they make decisions accordingly.

If your current scheduling setup makes it hard to see float, track the critical path, or update the schedule without a full-time planner, it might be time to look at tools designed specifically for how contractors actually work. Construction scheduling software has come a long way, and the best options today give you float calculations, critical path highlighting, and field-friendly interfaces without requiring a PhD in planning.

Book a quick demo to see how Projul handles this for real contractors.

Float is your schedule’s immune system. Take care of it, monitor it, and spend it wisely. Your projects will run smoother, your subs will stay coordinated, and you will sleep better at night knowing exactly where you stand.