Review Of Book: Takt Planning

Posted on September 22, 2026September 22, 2026 by va.jason.almas@gmail.com

Read 16 min

Why Takt Planning Needs Its Own Dedicated Resource

Here’s the deal. Takt is scaling across the globe as the preferred Lean system for scheduling construction projects, and it can still be exported automatically into a CPM schedule when a contract requires one. That combination, genuine flow based planning that still satisfies contractual reporting requirements, is exactly why Takt deserves a complete, dedicated resource rather than a handful of scattered concepts picked up here and there.

Software Integration Matters as Much as the Method Itself

Before getting into the core resource itself, it is worth naming a companion piece that matters just as much. A separate guide called Getting Started with Takt Planning walks through how to actually run this system using InTakt software, including the automatic export into a full CPM schedule, complete with logic, critical path, a summary, and float trends. If a contract genuinely requires that CPM formatted output, that export happens automatically once the Takt planning itself has been done correctly. You get the real production benefits of Takt while still satisfying whatever reporting format a contract demands.

What the Core Book Actually Delivers

The main resource, simply called Takt Planning, is built specifically for people who want to genuinely master Lean construction scheduling rather than pick up a surface level understanding of the terminology. Every page is highly visual by design, not because the content could not be explained in dense prose, but because most people genuinely do not have the time to work through a long, text heavy resource. Each section also links out through QR codes to specific instructional videos, walking through each concept step by step in more depth than the page itself can hold. Worked through completely, it teaches the entire Takt production system, not a partial version of it.

There is a real ecosystem of free resources that support this too. A free course. An updated software based simulation. Blog posts and videos. An Excel template for teams not yet ready to move to dedicated software. InTakt remains the preferred method for actually running this in practice, but none of these resources are locked behind a single required tool.

That matters for teams at very different starting points. A company just beginning to explore Takt can start with the free course and the Excel template, testing the concepts on a small scale before committing to dedicated software. A company ready to scale Takt across multiple projects can move directly into InTakt, where the automatic CPM export removes one of the biggest practical objections that slows adoption down.

Why This Specific Book Is Worth Owning

There are several concrete reasons this resource earns a place on a project delivery team’s shelf rather than staying a nice idea nobody actually implements.

It breaks an entire project down into genuine Lean construction planning, not a simplified summary of it. Worked through fully, it genuinely builds expertise rather than surface familiarity. It covers buffers directly, along with at least twelve distinct ways to recover from a delay without resorting to the kind of crashing that damages both schedule and people. And it includes the legal side of this work too, covering how to properly submit a delay and how to interface with an owner, which is territory a lot of purely technical Lean resources skip entirely.

Watch for these gaps in a typical Lean scheduling resource that this one is specifically built to close:

Buffers mentioned conceptually with no concrete recovery strategies attached to them
No guidance on how Takt based delays should actually be documented or communicated to an owner
Concepts taught in isolation with no clear path to implementing them as one coordinated system

A Governing Body for the Standards Themselves

To keep the underlying standards consistent and genuinely documented, we also built the Takt Production Institute, with its own website hosting the full set of governing requirements for the Takt production system. That resource exists specifically so the standards behind this method are not simply whatever any individual practitioner happens to remember or interpret loosely. They are written down, maintained, and available for anyone who wants to verify them directly.

That documentation matters more as Takt planning genuinely scales across the industry. A method spreading quickly without a stable, written reference point tends to fragment, with different companies and consultants each running a slightly different version and calling it the same thing. Having a maintained, public source of truth is what keeps the term Takt planning meaning something consistent, rather than becoming a loose label attached to whatever a given team happens to be doing.

Why Takt and Last Planner Belong Together

By the end of the book, everything ties directly into the Last Planner System. Takt planning is genuinely strong on its own, and it merges best with Last Planner rather than standing entirely apart from it. That combination produces real checklists your team can actually use, plus a full meeting system, every single meeting laid out clearly enough to scale directly into the field rather than staying theoretical. After the conclusion and final checklist, the book points back toward InTakt and the broader set of available resources, so the learning does not simply end once the last page is turned.

Format Options for However You Actually Learn

The full color format that makes this book so visually clear does come at a somewhat higher price than a plain text resource would. For anyone who genuinely wants the content but does not have time to sit down and work through a visual book, every bit of that same content also exists in a separate resource called The Takt Production System, available in both text and audio, so it can be listened to on a commute instead of read at a desk.

Why This Level of Depth Actually Matters

None of this exists to pad out a product catalog. Genuine mastery of Takt planning requires understanding zones, buffers, recovery strategies, legal documentation, and how the whole system connects into a real meeting cadence with trade partners and Last Planner sessions. Pick up fragments of that from scattered sources and the result tends to be a Takt implementation that looks right on the surface and falls apart the first time it hits a real delay, because nobody actually knew one of the twelve recovery strategies that should have applied.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your teams work through this exact system directly, applying the visual framework, the buffer and recovery strategies, and the meeting system to a real project rather than leaving your team to interpret the resource entirely on their own.

So here is the challenge. If your organization is running Takt planning with only a partial understanding of buffers and recovery strategies, pick one of the twelve recovery methods you are not currently using and study it directly before your next delay forces you to improvise a response instead. Knowing the full toolkit before you need it is worth far more than discovering it mid crisis.

Jason Schroeder said it plainly: “Takt is scaling the globe as the preferred lean system for scheduling construction projects.” Build the depth of understanding that matches where the industry is actually heading.

On we go.

FAQ

Why does it matter that Takt planning can still export automatically into a CPM schedule?

Because many contracts still require a CPM formatted schedule for reporting purposes, regardless of what method actually drives day to day production planning. Software that automatically exports a properly built Takt plan into CPM format, complete with logic, critical path, and float trends, lets a project satisfy that contractual requirement without abandoning the genuine flow based planning happening underneath it.

Why does a Lean scheduling resource need to cover legal topics like submitting a delay?

Because Takt planning does not exist in isolation from the contractual realities of a real project, and knowing how to properly document a delay or communicate with an owner is just as important as knowing the technical scheduling concepts themselves. A resource that skips this leaves teams technically capable but unprepared for the actual business side of managing a real delay when one occurs.

What is the purpose of having a separate organization like the Takt Production Institute maintain governing standards?

Because Lean methods can drift over time as different practitioners interpret and apply them loosely, an organization that documents and maintains the actual standards keeps the underlying system consistent and verifiable. That resource lets anyone check the governing requirements directly, rather than relying entirely on secondhand interpretations of how the system is supposed to work.

If you want to learn more we have:

-Takt Virtual Training: (Click here)
-Check out our Youtube channel for more info: (Click here)
-Listen to the Elevate Construction podcast: (Click here)
-Check out our training programs and certifications: (Click here)
-The Takt Book: (Click here)

Discover Jason’s Expertise:

Meet Jason Schroeder, the driving force behind Elevate Construction IST. As the company’s owner and principal consultant, he’s dedicated to taking construction to new heights. With a wealth of industry experience, he’s crafted the Field Engineer Boot Camp and Superintendent Boot Camp – intensive training programs engineered to cultivate top-tier leaders capable of steering their teams towards success. Jason’s vision? To expand his training initiatives across the nation, empowering construction firms to soar to unprecedented levels of excellence.

Review Of Book: Elevating Pre-Construction Planning

Posted on September 22, 2026September 22, 2026 by va.jason.almas@gmail.com

Read 16 min

Why Pre-Construction Planning Determines Project Success Before a Single Trade Shows Up

Here’s the deal. Planning a project right is one of the single most important things you can do to determine whether it actually succeeds. Not one factor among many. One of the biggest. Most of what goes wrong on a construction project traces back to gaps that existed long before anyone broke ground, which is exactly why we built an entire system specifically for the pre-construction phase.

Why This Deserves Its Own Complete System

We pulled together research from a wide range of sources to identify what genuinely strong construction pre-planning actually requires. That research aligns directly with integrated project delivery, target value design, and every established Lean approach to pre-construction that exists today. The book How Big Things Get Done makes a strong research case for why early planning matters so much. What we built is the practical field guide for actually doing it, the step by step system that turns that research into something a real project team can execute.

This is deliberately the second book in a two part series. The first, focused on building genuine project teams, exists because we build people before we build things. This second one is the system part, the actual mechanics of planning a project correctly before construction begins.

A Visual System Built Around Reflection and Scoring

The core of this system is highly visual, walking through pre-construction step by step. At the end of every critical section, there is a genuine reflection page, functioning both as a checklist and as a way to actually score your own project against that specific component. Implement what that section covers, move to the next one, and repeat the same reflection and scoring process there too.

That structure matters because it turns pre-construction planning from a vague, good intentions exercise into something genuinely measurable. You are not simply told to plan well. You are given a specific standard for each component, a way to check your own project against it honestly, and a clear next step once you have scored yourself. Followed all the way through, that process helps a project genuinely implement a real Lean foundation, not just talk about wanting one.

Most teams treat pre-construction as a single, undifferentiated phase, a stretch of time before the real work begins rather than a distinct discipline with its own standards. Breaking it into scored components changes that instinct entirely, because it forces a specific answer to a specific question at each stage, rather than a general sense that things feel mostly ready.

Watch for these signs your own pre-construction process is missing this kind of structure:

No specific checkpoint or scoring mechanism to confirm a planning step was actually completed well
Pre-construction treated as a single phase rather than broken into distinct components with their own standards
No clear path from identifying a gap to actually closing it before construction starts

The Trade Partner Preparation Process

The middle of the system focuses specifically on what some in the industry call the six step process, the same general approach used at companies like Hensel Phelps under that name. We call it the trade partner preparation process, and it covers buying out the contract, holding a genuine pre-mobilization meeting, running a real pre-construction meeting, establishing first in place work, following up consistently, and completing a final inspection.

Every piece of that process is included in detail, meeting agendas and all, alongside the visuals and real examples that make each step concrete rather than abstract. This section exists specifically because trade partner preparation is where a huge amount of downstream schedule and quality risk actually originates, and most projects handle it far too casually.

Consider what actually happens when this process gets skipped or rushed. A trade partner shows up without a genuine pre-mobilization meeting behind them, unclear on expectations, unclear on the sequence, unclear on what a clean handoff even looks like on this specific project. Every problem that follows from that gap gets blamed on the trade later, when the actual root cause was a missing step months earlier that nobody treated as essential.

Partnering With Designers Before Construction Even Starts

The third major component of the system covers the design side of pre-construction, specifically how a project delivery team should partner directly with designers during this phase to actually build the plan together, rather than receiving a finished design with no input into it. That process moves through schematic design, design development, construction documents, and finally mobilization, with a clear method for genuine collaboration at each stage.

Here is a simple way to think about how the whole system fits together, using an analogy worth remembering. What is the cake, meaning what are you actually building? Who eats the cake, meaning who is this entire project ultimately for? The answer is always the trade partners, since everything in this system exists to support the people who will actually execute the work. And how do you make the cake, meaning how do you actually build the plan step by step? That last question is where the system’s three major components, the visual step by step framework, the trade partner preparation process, and the design partnership process, come together into one complete answer.

Content Built for However You Actually Learn

Every section links out through QR codes to supporting videos and reference guides, so the visual content never stands alone without deeper support behind it. We also recognized that not everyone wants to sit down with a thick, highly visual book, so the entire body of content also exists as a complete textbook, titled The First Planner System, available on Audible for anyone who would rather listen during a commute than sit down and read.

Why This Deserves a Serious Look, Not a Skim

None of this is designed as filler content dressed up to look useful. It is built specifically so that when someone hands you a project and says you need to plan this, you have an actual, complete answer ready, rather than assembling one from scratch under real time pressure.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your teams apply this same pre-construction system directly to a real project, working through the reflection and scoring process together rather than leaving your team to interpret it alone. Getting pre-construction right is consistently one of the highest leverage investments available on any project, precisely because so much of what goes wrong later traces directly back to gaps here.

So here is the challenge. Before your next project moves into pre-construction, pick just one component, the trade partner preparation process is a strong place to start, and run it through a genuine reflection and scoring exercise rather than assuming it is already handled. That single exercise will likely reveal more real risk than most teams expect to find.

Jason Schroeder said it plainly: “Planning a project right is one of the single most important things you can do to determine project success.” Treat pre-construction with that level of seriousness, and the rest of the project has a real chance to follow.

On we go.

FAQ

Why is the trade partner preparation process specifically singled out as a major component of pre-construction planning?

Because a significant amount of downstream schedule risk and quality risk originates in how trade partners are brought onto a project, from contract buyout through the first work actually placed in the field. Steps like a genuine pre-mobilization meeting and a real pre-construction meeting set the tone for how a trade partner will perform for the rest of the project, which is why this process gets detailed attention rather than being treated as a formality.

What is the value of scoring a project against a checklist rather than just following the checklist itself?

Scoring turns a passive checklist into an active diagnostic tool, forcing an honest assessment of how well each specific component was actually implemented rather than simply confirming a step was technically completed. That distinction matters because a step can be checked off without genuinely being done well, and a scoring mechanism is what surfaces that gap before it becomes a problem during construction.

Why does genuine designer partnership during pre-construction matter more than simply receiving a finished design?

Because a design finalized without input from the people who will actually build it tends to carry constructability problems that surface expensively once construction begins. Partnering with designers through schematic design, design development, and construction documents lets the project delivery team catch and resolve those issues while changes are still relatively cheap to make, rather than discovering them in the field.

If you want to learn more we have:

Discover Jason’s Expertise:

The Field Engineering Methods Manual – Chapters 4, 5, 6, 7, 8, 9, & 10 – Summary

Posted on September 17, 2026September 17, 2026 by va.jason.almas@gmail.com

Read 16 min

Three-Quarters of an Inch That Changes Everything

A simple exercise makes a point most people never think to question. Take a standard cloth tape measure from a field engineer’s bag, measure out a hundred feet, then compare that same distance against a properly calibrated steel chain or a total station. The difference: three-quarters of an inch.

That might sound small. In construction, over the length of a building, across dozens of measurements that all need to line up correctly, three-quarters of an inch is a very big deal. And it reveals something worth taking seriously: the tools treated as automatically accurate are not always as reliable as they seem.

The Real Pain: Assuming Your Tools Are Always Right

The real pain is the natural assumption that basic equipment, tape measures, tribrachs, levels, straight out of the box, is inherently accurate simply because it is new or standard issue. In reality, roughly half of new tribrachs arrive out of calibration, and about a quarter of levels carry the same problem. Even without any wear or damage, the equipment itself often needs to be checked before it can be trusted.

The Failure Pattern: Skipping the Boring Stuff, Temperature, Tension, and Calibration

The failure pattern is treating the unglamorous fundamentals, correcting a steel chain for temperature, sag, and tension, or routinely calibrating tribrachs and levels, as unnecessary overhead rather than genuine discipline. A steel chain’s actual length shifts with temperature, and pulling it with the wrong tension or letting it sag changes the measurement just as much. Skipping these corrections does not make them less real, it just means the resulting error goes uncorrected and eventually shows up somewhere expensive.

A few specific habits protect real precision in the field, and they are worth naming directly:

Correct chain measurements for temperature using a prepared reference card, rather than assuming the chain’s marked length is always accurate regardless of conditions.
Use a tension scale to pull a consistent, correct amount of tension every time a chain measurement is taken.
Never “burn a foot,” meaning never distort the true zero point of a tape by hooking or butting it incorrectly against a surface.

This Isn’t About Being Obsessive, It’s About Understanding Real Limitations

None of this is about paranoid perfectionism. It is about genuinely understanding what a tool or instrument can and cannot do, and working within, and correcting for, its real limitations, rather than assuming perfect accuracy by default. A total station typically carries roughly fifteen thousandths of a foot of built-in measurement error, and knowing that real number, rather than assuming the tool is flawless, is exactly what allows a field engineer to work with genuine precision instead of false confidence.

Three Numbers That Should Match

Here is a genuinely useful technique worth understanding directly. In three-wire leveling, a field engineer reads three separate crosshairs, top, middle, and bottom, on a leveling rod. Averaging the top and bottom readings should produce a number that closely matches the middle reading. If it does not, that mismatch is an immediate signal that something in the shot needs to be rechecked.

This same discipline extends into a full level loop: taking a series of connected leveling shots that eventually close back to the exact benchmark where the loop began. The difference between where that loop should close and where it actually does close is called the linear error of closure, and it tells you directly whether the entire chain of measurements was accurate enough to trust, or whether something needs to be corrected before moving forward.

Why It Matters: The Twenty-Four Hour Window

This matters because of exactly how expensive a delayed check can become. Grid leveling, used to verify a concrete deck’s flatness before floors get finished on top of it, needs to happen within twenty-four hours of the concrete placement. Waiting longer than that window turns a simple, cheap correction into a serious, costly problem once other work has already been built on top of an unverified surface.

This is not a hypothetical risk. A missed floor-flatness check, deferred past the point where it could still be easily corrected, once cost a real project $320,000. The lesson is the same one that shows up throughout precise fieldwork: the timing of a verification check often matters just as much as the check itself.

Teach the Framework: Build Testing Into Your Calendar, Not Just Your Memory

The practical fix for equipment reliability is building an actual, physical testing routine rather than relying on memory or assumption. That means setting up a dedicated testing area on the project and maintaining a real testing calendar, so tribrachs, levels, lasers, and chains all get checked on a defined schedule, not only when something starts to feel obviously wrong.

Vertical benchmark transfers deserve the same rigor. Leveling up the side of a building, then physically chaining that measurement both up and back down, checking it with a different method or a different person along the way, catches errors that a single, unverified approach would miss entirely.

A few practical steps build real precision habits into daily field work:

Set up a dedicated equipment testing area and maintain an actual calendar for calibrating chains, tribrachs, levels, and lasers on a defined schedule.
Perform grid leveling and floor flatness checks within twenty-four hours of a concrete placement, not whenever there happens to be time later.
Verify a vertical benchmark transfer using a second method or a second person, rather than trusting a single measurement chain alone.

Turning This Into Daily Practice

Laminate a temperature correction card and keep it in your field bag so chain measurements can be adjusted immediately, on the spot, rather than estimated or skipped. Use a tension scale consistently rather than trusting a feel for the right amount of pull. And build routine equipment testing into an actual recurring calendar, the same way safety inspections or quality checks get scheduled, rather than leaving it to memory or convenience.

Connecting It Back to Building People, Not Just Projects

None of this happens without field engineers and superintendents willing to treat these small, unglamorous habits as genuinely important, rather than treating them as optional extras that can wait. Building real precision discipline into daily fieldwork is exactly what prevents the kind of costly, avoidable mistakes that come from trusting a tool or a moment in time without ever actually verifying it.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams build the kind of precision habits that protect a project from small errors becoming expensive ones.

The Challenge

So here is the challenge worth carrying onto your next layout task: check your equipment, correct for real conditions like temperature and tension, and never assume a tool is accurate just because it looks the part. As Jason put it plainly, “We should never burn a foot, ever, ever, ever.” On we go.

FAQ

Why would a standard tape measure differ from a calibrated chain by three-quarters of an inch?

Basic tape measures are not manufactured or maintained to the same precision standard as a certified, calibrated steel chain or total station, so real differences can show up even over a distance as short as one hundred feet. In construction, where multiple measurements need to align precisely, that difference can create real problems if it goes unchecked.

Why do new tribrachs and levels sometimes need calibration right out of the box?

Manufacturing tolerances mean that a meaningful percentage of new equipment, roughly half of tribrachs and about a quarter of levels, may not be perfectly calibrated even when brand new. Testing equipment before relying on it catches this issue before it affects real measurements in the field.

What is three-wire leveling, and why does it matter?

It involves reading three separate crosshairs, top, middle, and bottom, on a leveling rod, then confirming that the average of the top and bottom readings matches the middle reading. This built-in check helps catch errors immediately, rather than discovering a mistake only after the fact.

Why does grid leveling need to happen within twenty-four hours of a concrete placement?

Waiting longer allows other work to be built on top of a potentially unverified surface, turning what could have been a simple, inexpensive correction into a much more costly problem. A real project once lost $320,000 due to exactly this kind of delayed check.

What does a “linear error of closure” tell you in a level loop?

It measures the difference between where a series of connected leveling shots should return to the original benchmark and where they actually do, revealing whether the entire chain of measurements was accurate enough to trust. A large error of closure signals that something in the loop needs to be rechecked before the measurements can be relied upon.

If you want to learn more we have:

Discover Jason’s Expertise:

The Field Engineering Methods Manual – Chapter 3 – Fieldwork Practices

Posted on September 17, 2026September 17, 2026 by va.jason.almas@gmail.com

Read 13 min

From Six Feet Off to Consistently Right

A large contractor once had a real, persistent problem: buildings being laid out as much as six feet off, elevations coming in eight inches wrong. These were not new or inexperienced crews. The fix that actually turned things around was not a new tool or a training manual alone, it was a mindset shift: assume every piece of survey work is wrong until it has actually been checked.

Within a couple of months of adopting that single mindset shift, an entire district went from serious, costly layout errors to consistently good, reliable work. Nothing about the equipment changed. What changed was the assumption every field engineer carried into their own work.

The Real Pain: Confidence Without Verification Is Dangerous

The real pain is that confidence in your own measurement or layout, especially once you have real experience, is exactly what allows genuine mistakes to slip through undetected. The moment someone assumes they got it right the first time, the natural motivation to actually double-check disappears.

The Failure Pattern: Only Checking When You Doubt Yourself

The failure pattern is treating verification as something you do only when something feels off, rather than as a standing, unconditional habit applied every single time, regardless of how confident you feel. Mistakes are only ever caught by actually checking the work. If the starting assumption is “I got this right,” there is no real motivation to check, and that is precisely how expensive errors go undetected until they cause real problems downstream.

A few signs tend to show up when a team has confidence without real verification discipline, and they are worth checking honestly:

Measurements or layout get checked only when something seems questionable, rather than as an unconditional standard applied every time.
Experienced team members skip double-checking specifically because of their experience, assuming it makes errors less likely.
Mistakes get discovered only after other work has already been built on top of the original error.

This Isn’t About Distrust, It’s About Protecting the Whole Project

None of this is about doubting anyone’s competence or treating experienced people as unreliable. The best field engineers and surveyors in the world still double-check everything they do, precisely because they understand that mistakes are a normal, expected part of measurement work, not a sign of personal failure. Building that assumption into a whole team’s culture protects the entire project, not just one person’s reputation.

You Are the Front Line

This same discipline applies directly to safety. Field engineers and project engineers sit at the very first level of responsibility for safety on a project, which means real preparedness has to account for actual conditions, not just what feels familiar. Living and working primarily in Arizona for years meant the real danger of frostbite and cold-weather injury did not feel especially relevant, right up until working a project in the middle of winter in a genuinely cold climate made it clear how serious that risk actually is. Preparedness means taking every real hazard seriously, not just the ones that feel personally familiar.

Why It Matters: The Company That Changed Its Culture

The contractor story above matters because it shows this is not just an individual habit, it is a culture that has to be built deliberately across an entire team. One field engineer choosing to double-check their own work is good. An entire district collectively assuming every piece of survey work is wrong until verified is what actually changes real, measurable outcomes at scale.

Teach the Framework: Build Verification Into the Culture, Not Just the Individual

The practical shift worth making is treating “assume it’s wrong until checked” as a standing team norm, not something that depends on any one person doubting themselves in the moment. That means measuring distances twice, checking into more than one benchmark, and verifying calculations independently, every single time, regardless of who did the original work or how experienced they are.

A few practical habits build this culture directly:

Make double-checking measurements and layout an unconditional standard, applied the same way regardless of experience or confidence level.
Treat a discovered mistake as confirmation the system is working, not as a personal failure, which keeps people willing to actually look for errors rather than hide them.
Prepare for real, specific hazards relevant to the actual job site and season, rather than relying on what feels familiar from past experience.

Turning This Into Daily Practice

Build verification into the actual workflow itself, not as an optional extra step reserved for when something feels uncertain. A team that checks everything as standard practice catches small mistakes before they become expensive ones, and does so without anyone needing to feel personally doubted in the process.

Connecting It Back to Building People, Not Just Projects

None of this happens without leaders willing to build a genuine culture of verification, rather than relying on individual confidence or experience alone. That cultural shift, more than any single tool or technique, is what actually turns chronic layout errors into consistently reliable work.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams build the kind of verification culture that catches mistakes before they become costly.

The Challenge

So here is the challenge worth carrying onto your next project: assume the next measurement you take is wrong until you’ve actually checked it, and build that same standard into how your whole team operates.

On we go.

FAQ

Why does assuming your work is wrong actually improve accuracy?

Assuming a measurement or layout might be incorrect creates real motivation to actually verify it, rather than skipping that step out of confidence. Mistakes are only ever caught through genuine checking, so removing the assumption of being automatically correct is what keeps that verification habit active.

Isn’t constantly double-checking work a sign of not trusting your team?

No. Even highly experienced surveyors and field engineers build verification into their process as a standard practice, not because they lack confidence, but because they understand mistakes are a normal part of measurement work. Building this into team culture protects the whole project, not just individual reputations.

How did one contractor go from major layout errors to consistently accurate work?

The real shift came from changing the team’s underlying mindset, from assuming their work was correct to assuming it needed to be checked every time, rather than from new equipment or additional training alone. Within a couple of months of adopting that mindset broadly, the entire district saw significant improvement in accuracy.

Why does safety preparedness need to account for unfamiliar conditions?

Risks that feel irrelevant based on personal experience, like cold-weather injury for someone used to a warm climate, can still be genuinely serious when working in different conditions. Real preparedness means taking all relevant hazards seriously for the actual environment and season, not just the ones that feel familiar.

If you want to learn more we have:

Discover Jason’s Expertise:

The Field Engineering Methods Manual – Chapter 2 – Communication

Posted on September 17, 2026September 17, 2026 by va.jason.almas@gmail.com

Read 15 min

One Radio Away From Working Like One Organism

An underground concrete crew once operated so smoothly it looked like a single organism rather than a group of separate people. Every worker, every foreman, and the equipment operator all carried radios. The foreman never had to physically track someone down to relay information, he simply reached anyone on the crew instantly, whenever needed.

That crew was remarkably effective, and it is a pattern worth adopting far more widely, especially among trade partners and mid-sized companies where radios are often surprisingly absent. Smartphones have made it easy to assume this kind of direct, instant communication tool is unnecessary. In practice, a radio on every worker still tends to outperform waiting on a phone call or a text.

The Real Pain: Communication Breaks Projects, Not Just Feelings

The real pain shows up directly in industry research. Data compiled from sources including Dodge Data and Analytics, McKinsey, Deloitte, FMI, and the Project Management Institute suggests that roughly three out of four construction projects are delivered late, and a similar share finish significantly over budget. Roughly eight out of ten owners point to poor collaboration and communication with contractors as the root cause, and more than half of project rework, defects, and punch list items trace back to communication breakdowns rather than technical error alone. Communication is not a soft skill sitting alongside the real work of construction. It is one of the most direct, measurable causes of project failure across the industry.

The Failure Pattern: Treating Communication as an Afterthought

The failure pattern shows up in small, everyday moments that compound into real damage. One employee’s writing was so unclear and disorganized that clients and customers regularly came away confused and frustrated, never entirely sure what was actually being communicated. That pattern, left uncorrected, became one of the central reasons that employment ultimately did not work out. Nobody set out to fail at communication. It simply was never treated as seriously as it needed to be.

A few signs tend to show up when communication is quietly costing a project real money and trust, and they are worth checking honestly:

Written messages regularly leave the reader unsure of exactly what is being asked or reported.
People rely entirely on phones or texts to reach crews, even when a much faster, direct radio connection is available and unused.
Meetings are attended with phones or laptops open, attention split rather than genuinely focused on what is being discussed.

This Isn’t About Perfect Grammar, It’s About Being Understood

None of this is about achieving flawless writing or speaking style. It is about making sure a message actually lands the way it was intended, whether that message travels by radio, email, or a conversation in a meeting. A technically accurate plan that nobody actually understands correctly is just as much of a failure as a plan that was wrong to begin with.

Multiply Your Questions by Ten

Here is a direct, practical habit worth adopting. When working with a new field engineer, a common question is simply: how many questions are you asking each day? The typical answer tends to be one, two, or maybe ten. The real advice that follows is blunt: multiply that number by ten, and you still would not be asking too many.

The only genuinely bad question for a field engineer is the one that never got asked at all. Building the habit of asking constantly, rather than assuming or guessing, closes far more communication gaps than any amount of careful writing ever could on its own.

Why It Matters: Small Marks, Big Consequences

A real, costly example makes this vivid. On one project, several door frames had to be corrected after being installed at the wrong elevation, all traced back to a single sloppy field mark that was misread or misunderstood by the crew installing them. A mark that takes a few extra seconds to make clearly, labeled properly and unambiguous, prevents exactly this kind of expensive, avoidable rework.

Teach the Framework: Simple Habits That Actually Work

A handful of straightforward habits consistently close the gap between good intentions and real, effective communication. Equip crews with radios rather than relying entirely on phones, especially for trade partners and smaller companies where this tool is too often skipped. Take real, consistent notes and never rely on memory alone, since a team member who constantly needs reminding becomes a genuine liability, while one who never forgets an assignment builds trust quickly. Put phones and laptops away during meetings, and treat divided attention during a discussion as a real problem worth correcting, not a minor habit to shrug off.

A few practical habits make a real, immediate difference in day-to-day communication:

Equip crews with radios, not just phones, for instant, direct communication in the field.
Take detailed notes on every assignment and commitment, so nothing depends on memory alone.
Ask more questions than feels necessary, since an unasked question almost always costs more time later than asking it up front.

Turning This Into Daily Practice

Before assuming a message has been understood, double-check it directly, the same way a measurement gets double-checked before trusting it. A quick confirmation, repeating back what was heard or asked, catches misunderstandings before they turn into costly mistakes on the ground.

Connecting It Back to Building People, Not Just Projects

None of this happens without leaders willing to treat communication as seriously as any technical skill on a project. Building genuine habits around clear, direct, well-confirmed communication is exactly the kind of discipline that prevents the kind of costly rework and frustration that research consistently traces back to this single root cause.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams build the communication habits that keep small misunderstandings from becoming expensive mistakes.

The Challenge

So here is the challenge worth carrying onto your next project: look honestly at how your team communicates, in the field, in writing, and in meetings, and ask whether it would hold up against the standard of being genuinely, consistently understood.

On we go.

FAQ

Why does research point to communication as a leading cause of construction project failures?

Industry data suggests a large majority of owners cite poor collaboration and communication with contractors as a root cause of delays and cost overruns, and more than half of rework and quality issues trace back to communication breakdowns. This makes communication one of the most direct, measurable factors in project performance, not just a soft skill.

Why would equipping a crew with radios still matter in an age of smartphones?

A crew where everyone carries a radio can be reached instantly by a foreman or fellow worker, without needing to track someone down physically or wait for a call or text to be answered. This kind of immediate, direct communication tends to keep highly coordinated crews moving efficiently as a single, connected unit.

What is the real cost of unclear written communication on a project?

Confusing or poorly organized messages can leave clients, trade partners, or coworkers unsure of what is actually being communicated, which erodes trust and can lead to real professional consequences. Taking time to make written communication clear and understandable is not a minor courtesy, it is a genuine professional skill.

Why does asking more questions actually save time rather than waste it?

An unasked question that leads to a wrong assumption typically costs far more time and rework to correct later than simply asking it upfront would have. Building a habit of asking constantly, rather than guessing or assuming, closes communication gaps before they become expensive mistakes.

How can something as small as a field mark cause a costly mistake?

A sloppy or unclear mark used to communicate line, grade, or elevation to a crew can be misread, leading to work being installed incorrectly, as happened with door frames set at the wrong elevation due to one unclear mark. Taking the extra few seconds to make a mark clear and unambiguous prevents this kind of avoidable, costly rework.

If you want to learn more we have:

Discover Jason’s Expertise:

The Field Engineering Methods Manual – Chapter 1 – Responsibilities

Posted on September 17, 2026September 17, 2026 by va.jason.almas@gmail.com

Read 11 min

A Check That Didn’t Happen in Time

Early in one superintendent’s career, a simple task got missed: having the project engineers check floor flatness in a timely manner right after a deck placement. It seemed like a small thing to let slide for a moment amid everything else happening on the project.

That single missed check ended up costing $320,000. Not because anyone was careless or incompetent, but because a small, specific verification step, the kind that rarely feels urgent in the moment, turned out to carry enormous financial weight once it was skipped.

The Real Pain: Small Verification Steps Feel Optional Until They Aren’t

The real pain is how easy it is to treat routine field checks, as-built surveys, flatness verification, layout double-checks, as things that can wait, especially when a project is busy and attention is pulled in a dozen directions at once. In the moment, skipping a check feels harmless. The actual cost of that decision often does not show up until much later, and by then it is far more expensive to fix than it would have been to catch immediately.

The Failure Pattern: Letting the Small Stuff Slide When Things Get Busy

The failure pattern is deprioritizing routine verification work precisely when things get hectic, which is exactly the moment it matters most. Finished work should be checked right after it is completed, not whenever there happens to be a quiet moment to get to it. A flatness issue caught immediately after a deck placement is a manageable correction. The same issue discovered weeks later, after other work has built on top of it, becomes a very different and far more costly problem.

This Isn’t About Perfection, It’s About Timing

None of this means every measurement needs to be flawless. It means the timing of routine verification checks matters enormously. Catching an issue immediately after work is completed keeps a small problem small. Letting that same check slip, even briefly, gives a small problem real time to compound into something expensive and difficult to fix.

Why It Matters: The Role That Builds This Instinct

This is exactly why real time spent in a genuine field engineering role matters so much for a builder’s development. Learning to do as-built surveys, layout double-checks, and quality verification consistently and immediately, not eventually, is a habit built through real, sustained field experience, not something picked up casually or in a rush. Spending a real, extended period of time actually doing this work, rather than moving through the role quickly on the way to something else, tends to have a compounding effect on someone’s entire career.

Anyone looking to build this kind of technical grounding seriously should pick up Construction Surveying and Layout by Wesley G. Crawford, a genuinely excellent, detailed resource covering surveying, layout, and field engineering fundamentals in real depth. It is a book worth having on hand and working through directly, not just skimming.

Teach the Framework: Build the Habit, Not Just the Knowledge

A few practical habits protect against the kind of costly, delayed-check mistake described above:

Check finished work immediately after it is completed, flatness, elevations, embed locations, rather than deferring it to a quieter moment that may never come.
Treat routine verification steps as non-negotiable parts of the work itself, not optional extras to skip when things get busy.
Equip field engineers with real tools for the job, a genuine field book, Excel for tracking and calculations, a drawing program like AutoCAD, and a quick sketching tool, so verification work is never held up by a lack of the right resources.

Turning This Into Daily Practice

Build a simple standard: any finished work that requires verification gets checked the same day, not “when there’s time.” Treat that standard as seriously as any other safety or quality requirement on the project, because the cost of skipping it rarely shows up immediately, and by the time it does, it is usually far more expensive to fix.

Connecting It Back to Building People, Not Just Projects

None of this happens without giving field engineers real time, real tools, and real ownership of verification work, rather than treating it as something to squeeze in when convenient. Building that discipline early in someone’s career is exactly what prevents costly mistakes like this one later on.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams build the kind of verification habits that catch small problems before they become expensive ones.

The Challenge

So here is the challenge worth carrying onto your next project: look at what verification checks are currently being deferred until “there’s time,” and ask honestly what it would cost if that delay let a small problem compound into a big one.

On we go.

FAQ

Why did a delayed floor-flatness check end up costing $320,000?

Once other work is built on top of an unverified surface, correcting a flatness issue becomes far more disruptive and expensive than catching it immediately after the original work was completed. The delay, not the mistake itself, is what allowed the cost to grow so significantly.

Why do routine verification checks tend to get skipped on busy projects?

They rarely feel urgent in the moment compared to other pressing tasks, which makes them an easy thing to defer when a project gets hectic. The real cost of that decision often does not appear until much later, by which point it is far more expensive to address.

What tools does a field engineer genuinely need to do this work well?

A real field book, spreadsheet software like Excel for tracking and calculations, a drawing program such as AutoCAD, and a quick sketching tool are all considered practical essentials. Having the right tools readily available removes one common excuse for delaying verification work.

If you want to learn more we have:

Discover Jason’s Expertise:

Benefits of One-process-flow

Posted on September 17, 2026September 17, 2026 by va.jason.almas@gmail.com

Read 16 min

Eight Desks, Cut Wrong

While setting up office furniture for a new research laboratory, eight identical desk components were cut all at once, in a single batch, exactly the way it feels natural to do it. Only after all eight were fully cut did it become clear that something in the setup was wrong. Every single piece had to be recut, all eight, because the mistake had already been repeated eight times before anyone caught it. That is the real, hidden risk of batching. It feels efficient right up until the moment a mistake shows up, at which point it has already been multiplied across everything produced before anyone noticed.

The Real Pain: Batching Feels Efficient, Until It Isn’t

The real pain is that batching looks and feels organized. Cutting everything at once, assembling everything at once, finishing everything at once, all of it feels like a sensible, efficient way to work. What it actually hides is risk: if something is wrong, it does not get caught until an entire batch has already absorbed the same mistake.

The Failure Pattern: Not Trusting That Slower-Looking Can Be Faster

The failure pattern is simple disbelief. Most people genuinely struggle to accept that doing one thing at a time could actually be faster than doing things in efficient-looking batches. A simple demonstration makes the point unmistakably clear: the same person, working at the same personal speed, packs identical products into boxes two different ways. Using a batching method, laying out all the materials, wrapping everything, stuffing every box, and sealing them all in separate batched steps. Using one piece flow, completing one full box entirely, start to finish, before moving to the next.

The one-piece version finishes noticeably faster, even though every individual step looks slower in isolation. That result surprises almost everyone who sees it for the first time, and it holds up consistently once you actually test it.

A few of the clearest, most immediate benefits of one piece flow are worth naming directly:

Defects get caught and corrected immediately, rather than being repeated across an entire batch before anyone notices.
The first finished unit reaches whoever needs it far sooner, since nothing waits behind a full batch of unfinished work.
Materials and equipment stay organized by the specific zone or task at hand, rather than cluttering the whole workspace.

This Isn’t Just a Nice Theory, It’s Seven Concrete Benefits

It is completely understandable to feel skeptical here, batching genuinely does look more efficient at first glance. The real benefits of one piece flow are not abstract theory, they show up concretely in quality, speed, safety, morale, and cash flow, which is exactly why it is worth trusting the method even when old habits pull toward batching instead.

Every Worker Becomes an Inspector

The first and arguably most important benefit is built-in quality. Working one piece or one process at a time means every worker and foreman effectively becomes an inspector, catching a problem the moment it appears rather than discovering it only after a full batch has already been produced. That eight-desk mistake would have been caught and corrected after the very first desk, not all eight, if the work had been done one piece at a time from the start.

Why It Matters: The Full Chain of Benefits

Beyond quality, one piece flow creates real flexibility and shorter lead times. Producing that first finished desk could have taken one or two hours instead of the two full days it actually took to batch-produce all eight, meaning the customer or the next step in the process gets what they need far sooner, and the whole system stays more responsive to changing needs.

Productivity rises as well, since work organized by zone or production area avoids the wasted motion and transportation that comes with materials scattered everywhere for a big batch. Floor and workspace get freed up because materials are staged specifically for the task at hand rather than piled up in bulk. Safety improves because smaller, more controlled work zones mean less movement of large groupings of materials, equipment, and people, with more consistent crew counts and a genuinely more manageable environment. Morale improves because people can see immediate, tangible progress and completion, which builds a real sense of accomplishment rather than the feeling of grinding through an endless, unfinished batch. And costs come down directly, since capital is not tied up in a large batch of unfinished inventory and labor hours before anything is actually complete, which keeps cash flow healthier throughout the entire process.

Teach the Framework: See It to Believe It

Because this concept runs against such a deeply ingrained instinct toward batching, it is worth actually watching or running a live demonstration rather than just reading about it. Seeing the same person complete the same task meaningfully faster through one piece flow, despite every individual step looking slower, tends to convince people far more effectively than any explanation alone.

A few practical questions help identify where one piece flow could replace batching in real, immediate ways:

What task is currently being batched, cutting, assembling, finishing, all at once, that could instead be completed one full unit at a time?
How much faster would the very first finished unit reach the next step or the customer under a one-piece approach?
Where is a mistake currently at risk of being repeated across an entire batch before anyone catches it?

Turning This Into Daily Practice

Pick one recurring batched process, something regularly done in bulk, and deliberately try converting it to one piece flow as a genuine experiment. Track exactly how long it takes to produce the first fully finished unit under each method, and compare that number directly. The difference tends to be more convincing than any explanation.

Connecting It Back to Building People, Not Just Projects

None of this happens without teams willing to challenge a deeply ingrained instinct toward batching, even when it feels like the more efficient, organized way to work. Building genuine fluency in one piece flow is exactly the kind of shift that improves quality, speed, safety, morale, and cost all at once.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams build real one piece flow practices into daily work, rather than defaulting to batching out of habit.

The Challenge

So here is the challenge worth carrying into your next task list: pick one batched process this week and try running it one piece at a time instead, then watch what actually happens to your speed, quality, and morale. As Jason put it plainly, “We need to get our entire way of living restructured to where this is our standard mode of operation.” On we go.

FAQ

Why does one piece flow improve quality compared to batching?

Working one piece or process at a time means every worker effectively becomes an inspector, catching a mistake immediately rather than discovering it only after an entire batch has already repeated the same error. This can be the difference between correcting one mistake and having to redo an entire batch of work.

How does one piece flow create shorter lead times?

Because a single unit is completed fully before moving to the next, the very first finished piece reaches whoever needs it, a customer, the next production step, much sooner than waiting for an entire batch to be completed all at once. This also creates more flexibility to respond to changing needs along the way.

Why does one piece flow tend to improve safety on a jobsite?

Working in smaller, more controlled zones with consistent crew counts reduces the amount of large-scale movement of people, materials, and equipment across a wide area. That more contained, organized environment tends to reduce the safety risks that come with constantly shifting large groupings of people and materials.

How does one piece flow affect cash flow and overall cost?

Because capital and labor are not tied up in a large batch of unfinished inventory before anything is actually complete, cash keeps moving more freely throughout the process. This reduces the cost of holding unfinished work and the risk of that work needing costly correction later.

Why is it hard to believe one piece flow is actually faster than batching?

Each individual step often looks slower under one piece flow, since attention shifts to a single unit rather than processing many at once. Despite that appearance, actually timing the completion of the first finished unit under both methods consistently shows one piece flow finishing meaningfully faster overall.

If you want to learn more we have:

Discover Jason’s Expertise:

Bullying – We Just Don’t Do That around Here!!!!

Posted on September 17, 2026September 17, 2026 by va.jason.almas@gmail.com

Read 16 min

A Painful Memory From the Back of a School Bus

In middle school, a larger, older student, trying to impress the other kids on the bus, began hitting the back of one classmate’s head, daring him to fight back. Nobody spoke up. Not another student, not the bus driver. That classmate, scared and outnumbered, simply endured it.

Decades later, that memory still carries real weight. A simple, well-meaning flick to the back of the head from a colleague during a professional training session years later triggered an immediate, visceral reaction, evidence that some experiences from childhood never fully leave us. That kind of pain does not disappear with age. It shapes how a person sees the world, and for one construction leader, it shaped a genuine, lasting commitment to never let that kind of cruelty go unanswered again.

The Real Pain: Bullying Doesn’t Stay in the Past, It Shows Up at Work Too

The real pain is that the cruelty so many people remember from school hallways and bus rides does not disappear once people grow up and enter the workforce. It shows up on jobsites too, sometimes treated as simply part of the culture: cutting remarks, exclusion, mockery aimed at someone’s body, background, or appearance, all too often dismissed as harmless or just how things have always been done. That normalization is exactly the problem. Cruelty does not become acceptable simply because it happens among adults instead of children, or on a jobsite instead of a school bus.

The Failure Pattern: Staying Silent When You See It

The failure pattern is silence. On that school bus, an entire group of witnesses, including an adult responsible for those kids’ safety, said nothing while someone was being hurt in front of them. That same silence repeats constantly in workplaces, including construction sites, where people witness disrespect, harassment, or bullying and choose not to say anything. Silence in the face of mistreatment is not neutral. It is a quiet form of permission, and it is exactly the pattern that needs to be broken.

A few specific behaviors have no place on a construction site, and they are worth naming directly and without hedging:

Sexually inappropriate jokes, comments that objectify or demean women, and any form of racial or discriminatory remarks.
Mockery aimed at someone’s body, weight, background, or appearance, in any direction.
Deliberate exclusion, yelling, bullying, or making anyone on site feel isolated or unwelcome.

This Isn’t About Punishing Toughness, It’s About Protecting Dignity

It is worth acknowledging honestly that people who bully others have very often been hurt themselves at some point. That understanding does not excuse the behavior, cruelty is still cruelty, and it still deserves a firm, direct response. But recognizing that painful history helps frame the response correctly: firm and unwavering about the behavior itself, while still holding onto basic respect for the humanity of everyone involved, including the person doing the harm.

The Sticks That Mark the Path Home

A university president once led students on a mountain hike through deep snow, marking the safe path with sticks planted along the way to guide them home past hidden crevices hidden beneath the snowpack. Reflecting on it afterward, he made a simple but powerful point: those sticks were not valued for their height, their strength, or how attractive they looked. They were valued entirely for the position they held, guiding people safely home.

People deserve that same standard of respect. Worth is not measured by appearance, background, body type, or any surface trait. It is measured by shared humanity, full stop, the same way those sticks were valued not for how they looked, but simply for being trustworthy guides home.

Why It Matters: Somebody Has to Be the One Who Says Something

This matters because respect only becomes real culture when someone is willing to actually say something in the moment it counts. At a gathering once, a young man watched someone verbally tearing into his girlfriend, pushing her around and demeaning her in front of others. He walked over, stood tall, and said simply: we don’t do that around here. The situation stopped immediately.

A similar moment shows up in a short video that has stuck with many people who have seen it: two kids bullying a classmate, pushing him around and messing with his backpack, until another student stepped in, put his hands up, and said stop, then helped pick up the backpack. That single, small act of intervention is exactly the model worth carrying forward, whether the setting is a school hallway, a party, or a jobsite trailer.

Teach the Framework: “We Don’t Do That Around Here”

A simple, memorable standard is worth adopting directly: we don’t do that around here. It works because it is short, clear, and usable by absolutely anyone on a jobsite, a foreman, a laborer, a project manager, an office administrator, regardless of title or tenure, the moment they witness disrespect, harassment, or bullying.

This standard has to apply universally, without exceptions carved out for seniority, personality, or “that’s just how he is.” A workplace that tolerates disrespect from some people while holding others accountable for it has not actually adopted the standard at all.

A few concrete lines should never be crossed on any construction site, and stating them plainly matters:

No sexually inappropriate comments, jokes, or behavior directed at anyone, ever.
No discriminatory remarks about race, background, ability, or any other protected characteristic.
No mockery of someone’s body, weight, or appearance, in any direction, for any reason.

Turning This Into Daily Practice

Normalize saying something the moment disrespect or bullying is witnessed, rather than staying silent and hoping someone else addresses it. Make it unmistakably clear that this standard applies to everyone on site, regardless of position, seniority, or how long someone has been part of the team.

Extend genuine welcome, not mere tolerance, to everyone who steps onto a project, including women, veterans, people with disabilities, and anyone from a minority or underrepresented background. The goal is not simply avoiding complaints, it is building a site where people are actually glad to be part of the team.

Connecting It Back to Building People, Not Just Projects

None of this happens without leaders willing to set the standard clearly, live it themselves, and hold everyone on a team to it without exception. Building a genuine culture of respect, where “we don’t do that around here” is a real, enforced standard rather than just a poster on the wall, is exactly the kind of leadership that changes how an entire jobsite feels to work on.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams build a genuine culture of respect and dignity, one that protects everyone who steps onto the site.

The Challenge

So here is the challenge worth carrying onto your next project: the next time you witness disrespect, harassment, or bullying, be the person who says something, rather than the bystander who stays silent. As Jason put it plainly, “We don’t do that around here.” On we go.

FAQ

Why does understanding that “bullies have often been bullied themselves” matter, without excusing the behavior?

It helps frame a firm response to bullying with genuine compassion rather than pure anger, recognizing the person’s likely history while still holding them fully accountable for their actions. The behavior itself still needs to stop immediately and without exception, regardless of its origin.

What does the story about marking a path with sticks teach about respect?

The sticks were valued entirely for the position they held, safely guiding people home, not for their height, strength, or appearance. People deserve to be valued the same way, based on their shared humanity rather than any surface trait like appearance, background, or body type.

Why is staying silent when witnessing bullying or disrespect considered part of the problem?

Silence in the face of mistreatment functions as a quiet form of permission, allowing the behavior to continue unchecked. Real culture change requires people to actually speak up in the moment, the way both the brother-in-law and the student in the bullying video did.

What specific behaviors have no place on a construction jobsite?

Sexually inappropriate comments or jokes, discriminatory remarks about race or background, and mockery of someone’s body or appearance are all explicitly named as unacceptable, without exception. These standards apply to everyone on site, regardless of position or seniority.

How can a jobsite move from simply “tolerating” diversity to genuinely welcoming it?

It requires actively creating an environment where people from all backgrounds, including women, veterans, people with disabilities, and minorities, feel genuinely valued and included, not just formally permitted to be present. That shift starts with leadership consistently modeling and enforcing real respect, not just avoiding overt complaints.

If you want to learn more we have:

Discover Jason’s Expertise:

Construction’s Laws of Thermodynamics

Posted on September 17, 2026September 17, 2026 by va.jason.almas@gmail.com

Read 16 min

Nine Women Can’t Have a Baby in One Month

The first law of thermodynamics states that energy cannot be created or destroyed. Translate that directly to a jobsite: real work cannot be created or destroyed through wishful thinking either. A crew of five cannot do the work of a crew of twenty just because a schedule says so, and seventeen days of real work cannot be compressed into three simply by wanting it badly enough.

There is an old saying that captures this perfectly: one woman can have a baby in nine months, but nine women cannot have a baby in one month. The actual amount of work required does not shrink just because the deadline did.

The Real Pain: Left Alone, Every Project Drifts Toward Chaos

The second law of thermodynamics states that entropy, the tendency toward disorder, increases in any system without active intervention. Construction projects follow the exact same principle. Left alone, without real feedback loops, corrective systems, and genuine supervision, a project does not simply stay the same. It actively drifts toward more disorder, more chaos, and more randomness over time. That drift is not bad luck. It is the default direction every project heads unless someone actively fights against it.

The Failure Pattern: One Bad Decision Triggers a Chain Reaction

The failure pattern is a genuinely traceable chain reaction, and it usually starts in the same place: an overly aggressive schedule target gets adopted, often without any real buffer built in to absorb normal variation, delays, or defects. From there, the chain runs predictably. The project team, facing that unrealistic deadline, begins to panic and push, throwing more people, more crews, and more materials at the problem.

That panic-driven pushing produces trade stacking, multiple crews crowded into the same space at the same time. Trade stacking then produces oversized teams, constant context switching, and frequent changes in crew composition and leadership. That instability produces real variation and poor-quality installation. Poor quality produces rework. And once a team is consumed by rework and reaction, they stop looking ahead entirely, which produces even more starts, stops, and disorder. Each link makes the next one worse, and the whole chain accelerates the further it runs.

A few of the clearest links in that chain are worth naming directly, since recognizing them early is what makes it possible to interrupt the cascade:

An unrealistic schedule target leads directly to panic and pushing, rather than to disciplined planning.
Panic and pushing produce trade stacking, oversized crews, and constant personnel changes.
Poor quality and rework pull a team’s attention entirely into reacting to the past, leaving no capacity to plan for what comes next.

This Isn’t Bad Luck, It’s Predictable Physics

None of this is some mysterious curse that happens to unlucky projects. It is a predictable, traceable pattern that starts from an identifiable root cause, most often an unrealistic schedule adopted without real buffers, and follows a genuinely consistent chain of cause and effect from there. Recognizing the pattern for what it actually is, rather than treating each downstream symptom as its own unrelated crisis, is the first real step toward stopping it.

Why It Matters: The Only Way Out Is to Move Faster Than Entropy

This matters because a project does not get to simply opt out of this tendency toward disorder. Entropy is not a risk that might happen, it is the default direction of any unmanaged system, construction projects included. The job of real leadership is to actively outpace that natural drift toward chaos through deliberate planning, real buffers, and disciplined execution, rather than hoping disorder simply will not show up this time.

Interestingly, disorder tends to accelerate the most in the messy middle ground, projects that are neither running with near-perfect discipline nor already in total chaos. A highly disciplined, well-controlled project resists entropy through genuine planning and control. A project already in complete collapse has, in a strange way, nowhere further to fall. It is the projects caught somewhere in between, still functioning but slowly losing ground, where disorder compounds the fastest and does the most damage before anyone fully notices.

Teach the Framework: Stop the Cascade at the Root, Not the Symptom

The real fix is intervening at the root of the chain, not chasing each downstream symptom individually as it appears. Trying to solve trade stacking, rework, and disrespect toward workers as separate, unrelated problems misses that all three usually trace back to the same original decision: an unrealistic schedule adopted without real buffers in the first place.

Setting a genuinely realistic target with real buffers to absorb normal variation, protecting one-piece flow instead of batching and rushing, and refusing to let panic drive decisions when a deadline starts to feel tight are the actual interventions that stop the cascade before it ever gains momentum.

A few practical, root-level interventions make the real difference, rather than reacting to symptoms further down the chain:

Evaluate whether a proposed schedule target is genuinely realistic, with real buffers, before it ever gets adopted.
Watch for the earliest sign of the cascade, panic-driven pushing, and address it directly rather than waiting for trade stacking or rework to show up later.
Protect one-piece flow and steady, planned production rhythm even when a deadline starts to feel uncomfortably close.

Turning This Into Daily Practice

Before adopting any aggressive schedule target, ask honestly whether it includes real buffers for the variation, delays, and defects that are a normal part of any project. If panic and pushing start to show up, more crews added reactively, materials staged all at once, deadlines discussed with visible anxiety, treat that as the actual warning sign it is, not as simply the cost of doing business.

Intervening at that early stage, before trade stacking, rework, and disrespect toward the workforce have a chance to compound, is dramatically easier than trying to recover a project already several links deep into the cascade. A quick weekly check, comparing the current pace and crew composition against the original plan, often surfaces the earliest signs of this drift long before it becomes an obvious crisis.

Connecting It Back to Building People, Not Just Projects

None of this happens without leaders willing to recognize the early warning signs of this cascade and intervene at the root, rather than waiting until the downstream symptoms become undeniable. Building that discipline is exactly what keeps a project’s natural drift toward disorder from ever gaining real momentum.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams build the planning discipline and real buffers that keep entropy from taking over a project.

The Challenge

So here is the challenge worth carrying onto your next schedule review: look honestly at whether your target completion date has real buffers built in, or whether it is quietly setting the entire cascade, panic, pushing, trade stacking, rework, disorder, into motion before the project has even really begun. As Jason put it plainly, energy cannot be created or destroyed, especially with wishful thinking on a construction project. On we go.

FAQ

What does “entropy” mean when applied to a construction project?

It refers to the natural tendency of a project to drift toward disorder, chaos, and randomness over time without active intervention, much like entropy increases in any unmanaged physical system. Left alone, a project does not stay stable, it actively declines toward more disorder.

What typically triggers the cascade toward disorder on a construction project?

It usually starts with an overly aggressive schedule target adopted without real buffers to absorb normal variation, delays, or defects. That single decision tends to set off a predictable chain reaction: panic, pushing, trade stacking, oversized crews, poor quality, rework, and accelerating disorder.

Why do projects in the “messy middle” tend to decline the fastest?

A highly disciplined project actively resists disorder through genuine planning and control, while a fully collapsed project has little further room to decline. Projects caught in between, still functioning but slowly losing ground, tend to see disorder compound the fastest, often before anyone fully recognizes what is happening.

Why is it more effective to address the root cause than each downstream symptom individually?

Trade stacking, rework, and disrespect toward the workforce often appear as separate problems, but they frequently trace back to the same original decision: an unrealistic schedule adopted without real buffers. Fixing each symptom individually rarely addresses the actual source, while correcting the schedule and protecting real buffers can prevent the entire chain from starting.

What is the practical takeaway from comparing construction to the laws of thermodynamics?

Just as energy cannot be created through wishful thinking, and disorder naturally increases without active intervention, a construction project requires deliberate planning, real buffers, and disciplined execution to avoid drifting toward chaos. Recognizing this as a predictable pattern, rather than bad luck, makes it possible to intervene early and effectively.

If you want to learn more we have:

Discover Jason’s Expertise:

Foreman – Episode 1 – One-process-flow

Posted on September 17, 2026September 17, 2026 by va.jason.almas@gmail.com

Read 16 min

Two Rebar Foremen, Two Completely Different Outcomes

One rebar foreman spent his days out tying rebar directly alongside his crew, hands-on, working right beside them every hour of the day. His crew was always behind, always waiting on materials, always a step slower than they needed to be. Another foreman on similar work took a completely different approach: bringing materials ahead of time, craning rebar in before it was needed, handing out cut sheets and details before his crew ever asked for them.

That second foreman’s crews were consistently on time. Asked directly what the difference was, his answer was simple: the other foreman never stopped working alongside his crew long enough to actually prepare for what was coming next.

The Real Pain: A Crew That’s Ready Doesn’t Need a Foreman In the Moment

Here is a thought experiment worth sitting with. Imagine a crew with a completely clear, ready area to work in, materials on hand, layout complete, full training, clear information, everything genuinely ready to go. Given that, most crews would likely finish the work faster than standard bid rates, without a foreman standing over them at all.

So what is a foreman actually for? The honest answer is that a crew rarely needs a foreman during smooth, uninterrupted execution. They need a foreman the moment a roadblock hits, a question comes up, a piece of information is missing, or an unexpected condition appears. That single insight should completely reshape how a foreman spends their time.

The Failure Pattern: Foreman “In the Game” Instead of Ahead of It

The failure pattern is a foreman who works entirely inside the game, physically present alongside the crew during execution, and then mentally checks out the moment the work stops or a roadblock appears. Materials run out, a piece of information is missing, another trade is in the way, and the response is simply to demobilize and wait, rather than having already solved that problem days earlier.

A handful of specific things reliably kill productivity, and nearly all of them are things a well-prepared foreman can prevent well ahead of time:

Missing information, materials, or layout that forces a crew to stop and wait once work has already started.
Context switching and oversized team configurations that reduce focus and slow down real progress.
Rework caused by not installing something correctly the first time, often due to unclear expectations set too late.

This Isn’t About Foremen Being Lazy, It’s About Where Their Attention Goes

None of this is a criticism of foremen who work hard alongside their crews, that instinct usually comes from genuine dedication, not laziness. The real issue is where that dedicated effort actually gets pointed. A crew’s real need for a foreman shows up specifically at the moment something is missing or something goes wrong, which means the foreman’s most valuable work happens before that moment ever arrives, not during it.

The Make-Ready Checklist Every Foreman Should Own

Real preparation means confirming, days or even weeks ahead of a crew starting a task, a specific set of things. Are the right materials ordered, delivered, and inspected? Is the layout complete and accurate? Have the drawings and specifications actually been reviewed? If a lift drawing is needed, has it been created and reviewed ahead of time? Is the crew composition and training actually right for this specific task? Is the necessary equipment ordered and in good working repair? Has all predecessor work and the substrate itself actually been accepted and confirmed ready?

Every one of these questions belongs on a foreman’s radar well before a crew ever shows up to start the work, not as something to figure out once they are already standing there, ready to go, and waiting on an answer.

Why It Matters: The Data Behind the Instinct

This matters because the data backs up the instinct directly. Even the least productive quarter of workers on a typical crew tends to outperform standard bid unit rates, and the most productive quarter performs roughly four times better than that bottom group. In other words, the workforce itself is rarely the actual bottleneck.

What genuinely kills productivity is roadblocks, missing information, unplanned starts and stops, excessive context switching, oversized or constantly shifting teams, unnecessary overtime, and rework from work installed incorrectly the first time. Every one of these is something a foreman working ahead of the crew, rather than just alongside them, can directly prevent.

Teach the Framework: Ahead of the Train, Not Standing Over the Crew

The real job description of a foreman is not standing over a crew supervising moment to moment. It is working days or weeks ahead of the actual work, removing roadblocks before the crew ever encounters them, confirming genuine readiness, and making absolutely sure the crew never has to stop and wait once they arrive at the task in front of them.

This reframes what “being a good foreman” actually looks like day to day. Less time hands-on inside the immediate task, more time actively preparing what is coming next, is not a sign of disengagement. It is exactly what allows a crew to move at their genuinely productive pace instead of constantly stalling out on preventable problems.

A few practical questions help a foreman check whether they are actually working ahead of the crew rather than just alongside them:

What is my crew scheduled to be doing one week from now, and have I already confirmed everything they will need to do it without stopping?
Is there a piece of missing information, material, or equipment that I already know about but haven’t resolved yet?
Am I spending most of my time solving problems as they happen, or preventing them from happening in the first place?

Turning This Into Daily Practice

Build a habit of checking make-ready status for upcoming work days or weeks ahead of time, rather than the morning of, or worse, in the middle of the task itself. If a foreman consistently finds themselves working hands-on alongside the crew just to help them keep pace, that is usually a signal that preparation happened too late, not that more hands-on involvement is the actual fix.

Connecting It Back to Building People, Not Just Projects

None of this happens without foremen and the leaders supporting them recognizing that real value comes from working ahead of the crew, not just alongside them. Building that habit deliberately is exactly what turns a hardworking foreman into a genuinely effective one.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams build the kind of make-ready discipline that keeps crews moving at their real, productive pace.

The Challenge

So here is the challenge worth carrying onto your next project: look honestly at where your attention actually goes as a foreman, inside the immediate task alongside your crew, or days ahead of it, clearing the path before they ever arrive. As Jason put it plainly, “Focus outside the game, not just in the game.” On we go.

FAQ

Why would a crew be able to work faster without a foreman present, in the right conditions?

If a crew already has complete materials, layout, training, and information, most of the value a foreman would normally add during execution is not actually needed in that moment. This reveals that a foreman’s real value lies in preparing those conditions ahead of time, not in supervising smooth execution as it happens.

What does “focus outside the game, not just in the game” actually mean for a foreman?

It means spending real time and attention preparing for work that has not started yet, removing roadblocks, confirming materials and layout, reviewing drawings, rather than only being present and engaged once the crew is already actively working. The most valuable moments for a foreman to be involved are before a problem occurs, not just when it does.

What specific things should a foreman confirm before a crew starts a new task?

Materials ordered, delivered, and inspected, layout completed and accurate, drawings and specifications reviewed, any needed lift drawings prepared in advance, the right crew composition and training in place, equipment ordered and in good repair, and predecessor work or substrate conditions already accepted.

Why does research suggest the workforce itself usually isn’t the productivity bottleneck?

Data shows that even lower-performing workers on average tend to exceed standard bid unit rates, while top performers significantly outperform them, suggesting the workforce generally has real capacity for productivity. The real bottlenecks tend to be roadblocks, missing information, rework, and disruptions, which fall squarely within a foreman’s ability to prevent through better preparation.

How can a foreman tell if they’re spending too much time reacting instead of preparing?

If a foreman is frequently solving problems, missing materials, unclear information, unexpected conditions, in the middle of active work, that is a sign preparation happened too late. Regularly checking readiness for work scheduled days or weeks out, rather than the day it starts, helps shift attention from reacting to genuinely preventing problems.

If you want to learn more we have:

Discover Jason’s Expertise:

General Offerings

Company Offerings

Systems

SUBSCRIBE NOW !

Subscribe to our newsletters and stay updated!

Related Books

The First Planner System: The Project Planning System for Executives, Project Managers, and Superintendents in Pre-construction - Book 2

Pull Planning For Builders: How to Pull Plan Right, Respect People, and Gain Time (The Art of the Builder)

The Ten Improvements to Production Planning: What Lean Builders Can Do To Improve Short Interval Planning (The Art of the Builder)

Related Books

The First Planner System: The Project Planning System for Executives, Project Managers, and Superintendents in Pre-construction - Book 2

Built to Fail: Why Construction Projects Take So Long, Cost Too Much, And How to Fix It

Related Books

The First Planner System: The Project Planning System for Executives, Project Managers, and Superintendents in Pre-construction - Book 2

The 10 Myths of CPM: How The Critical Path Method Systematizes Disrespect for People

Calumet "K"

faq

General Training Overview

Superintendent / PM Boot Camp

Takt Production System® Virtual Training

Onsite Takt Simulation

Foreman & Field Engineer Training

Testimonials

Testimonials

agenda

Day 1

Foundations & Macro Planning

day2

Norm Planning & Flow Optimization

day3

Advanced Tools & Comparisons

day4

Buffers, Controls & Finalization

day5

Control Systems & Presentations

faq

UNDERSTANDING THE TRAINING

VALUE AND RESULTS

PLANNING AND SCHEDULING TOPICS

APPLICATION & TEAM ADOPTION

VIRTUAL FORMAT & ACCESSIBILITY

faq

GENERAL FAQS

CURRICULUM & OUTCOMES

LOGISTICS & FORMAT

PRICING & VALUE

SEO-BASED / HIGH-INTENT SEARCH QUESTIONS