Month: August 2026

What Are Standing Tactical Orders in Construction Leadership?

There is a question worth asking about every project, every company, every team: what happens when the leader is not there? Not what is supposed to happen. What actually happens based on what the team already knows, already believes, and already does by default.

If the answer is unclear, the team does not have standing tactical orders. And the absence of standing tactical orders is the absence of a culture that can sustain itself without the leader in the room.

Where the Concept Comes From

General Patton is one of the most studied military commanders in American history and one of the most controversial. But from a tactical standpoint, his results are difficult to argue with. His army moved faster and was more effective than any comparable force of the era. A significant reason for that performance was written standing tactical orders a clear, documented set of principles that every officer and soldier knew, that governed decisions at every level, and that allowed the organization to move with speed and consistency even without direct command in the moment.

Patton wrote his orders down. Everybody knew them. Communication moved faster because the culture had internalized what the commander wanted before the commander had to ask for it.

That model does not belong only to military history. It belongs on every construction project.

What Standing Tactical Orders Are

Standing tactical orders are the documented principles that govern how a leader’s team operates what they prioritize, how they make decisions, what the default behavior is when circumstances are unclear or the leader is unavailable. They are not a policy manual. They are not a list of rules. They are the philosophy of leadership expressed as operational commitments that the team has internalized deeply enough to act on without being prompted.

Every leader who takes this seriously will have their own version. The specifics will differ based on project type, company culture, team composition, and the leader’s own experience and values. What will not differ is the function: standing tactical orders tell the team what right looks like, in enough detail and with enough clarity that they can reproduce it without waiting for instruction.

Here is what one superintendent’s first draft of standing tactical orders looked like imperfect, duplicative in places, and entirely honest:

1. Build the team first: Before the production plan, before the schedule, before the procurement log build the team. Connect the people. Make sure every person on the project knows who they are working alongside and what they are collectively trying to accomplish. Without the team, everything else is coordination, not production.
2. Break teams into smaller, nimble units: Large, lumbering project structures move slowly and respond poorly. Smaller functional units each with their own assistant superintendent, their own meeting cadence, their own accountability structure can pivot, respond, and improve faster than a single monolithic team. Napoleon’s tactical genius was not in the size of his armies but in how he structured them for speed.
3. Win the war before going to battle: Sun Tzu made this clear: amateur generals go to battle and then seek to win. Great generals win before the battle begins. In construction, this means pre-planning, pre-planning, pre-planning. The project that starts with a macro-level Takt plan, a pull-planned phase sequence, pre-construction meetings done, and the supply chain aligned that project has already won most of its battles before the first crew mobilizes.
4. Keep stability in the field: Perfect cleanliness, safety, and organization held as the number one priority, not something to achieve when things calm down. A clean, safe, organized site is not the output of a well-run project. It is the prerequisite.

 

5. Root out bad attitudes and behaviors: In any organization, roughly a third of people are fully bought in, a third are neutral, and a small percentage five to fifteen percent will actively work against the culture. Not because they are bad people, but because of bad behavior or circumstances that have shaped them to respond that way. Hurt people hurt people. Those behaviors do not belong on the project. Address them without punishment but without tolerance because the culture of the whole depends on protecting it from the behaviors that erode it.
6. Fanatically remove roadblocks and clear the way out ahead: This is the production discipline that keeps the Takt plan alive. Not reactive roadblock management proactive, upstream, fanatical clearing of the path before the train arrives. Every day.
7. Lead with communication and transparency: The team cannot see the plan unless the plan is communicated. The team cannot trust the system unless the system is transparent. Leadership is not authority it is clarity, delivered consistently and honestly, until the team can see as a group, know as a group, and act as a group.

Why Standing Tactical Orders Enable Decentralized Command

One of the most powerful outcomes of standing tactical orders is that they enable decentralized command the fourth law of the builder’s planning method. When the team knows the standing tactical orders deeply enough to act on them independently, they do not need the leader in the room for every decision. The superintendent walking a different part of the site, the project manager in a meeting, the general superintendent on another project none of that creates a leadership vacuum if the team has internalized the orders.

The question to test this is simple: does everyone on the project site know the standing tactical orders and what to do as a default when the leader is not there? If the answer is yes, the culture is self-sustaining. If the answer is no, the project is dependent on the leader’s physical presence in a way that creates fragility because leaders cannot be everywhere at once, and projects do not stop moving when the leader steps away.

How to Create Standing Tactical Orders

This is the part where the work is personal. The principles above are examples a starting point from a superintendent’s first draft, not a template to be copied exactly. Standing tactical orders that work are the ones the leader has actually thought through, believes in deeply enough to defend, and has communicated clearly enough that the team can repeat them without looking them up.

Here are the questions that shape effective standing tactical orders:

What does this team do first, always, before anything else? What is the non-negotiable standard that governs the environment cleanliness, safety, organization? What does the team prioritize when two important things are competing for attention? How does the team make decisions when the leader is absent? What behaviors are absolutely not tolerated, and what happens when they surface? How does the team communicate with what frequency, in what format, to whom?

The answers to those questions are the standing tactical orders. They do not have to be perfect on the first draft. The superintendent’s first draft had duplications and was slightly out of order. That draft still governed a project team that operated with clarity and consistency because the leader believed in what was written and communicated it until the team internalized it.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

The Challenge

Write the standing tactical orders for your project, your team, or your company this week. Not a mission statement operational principles that the team can act on as a default. Publish them. Communicate them in the morning worker huddle. Post them in the trailer. Ask team members to recite them. And then watch what happens to the project’s capacity to sustain itself, solve problems, and protect its culture even when the leader is somewhere else.

The best commanders do not win through their constant presence. They win by building teams that carry the standards forward without being asked. That is what standing tactical orders make possible.

As Taiichi Ohno says, “Without standards, there can be no improvement.”

On we go.

Frequently Asked Questions

What is the difference between standing tactical orders and a company policy document?
Policy documents govern compliance. Standing tactical orders govern culture. A policy tells people what they are not allowed to do. Standing tactical orders tell people what the leader expects them to do by default how to make decisions, what to prioritize, what the standard looks like so that the team functions with clarity and consistency without requiring constant direction.

How detailed should standing tactical orders be?
Detailed enough to be actionable, concise enough to be memorable. A list of seven to ten principles that every team member can recall and apply is more valuable than a comprehensive document that no one reads. The test is whether someone new to the team could read the orders and immediately understand how this leader runs a project.

How do standing tactical orders connect to decentralized command?
They are the enabling mechanism. Decentralized command only works when every member of the team understands the mission and the standards well enough to make good decisions in their sphere independently. Standing tactical orders communicate those standards explicitly and repeatedly until they are internalized at which point the team can act without waiting for permission, and the leader can trust that the culture holds even when they are not in the room.