Different Roles Require Different Judgment
- Dustin Bush
- Jul 12
- 5 min read
Foremen, superintendents, and project managers all contribute to the same project result.
But they do not operate on the same time horizon. They do not control the same information. They do not solve the same problems.
A strong civil construction organization cannot develop all three roles through one generic leadership program.
Each role needs its own judgment-development path, practical tools, and clear responsibilities. Those paths must remain connected through reliable field-to-office handoffs.
Experience Alone Is Not a Development System
Civil contractors often promote people because they are dependable, productive, and technically capable.
A strong operator becomes a foreman.
A successful foreman becomes a superintendent.
A project engineer or assistant PM is given responsibility for a project.
Then the company expects experience to teach them the rest.
Experience matters. It exposes leaders to real field conditions, difficult decisions, people problems, production pressure, change, risk, and opportunity.
But experience alone does not guarantee better judgment.
Without a system for reviewing decisions, extracting lessons, establishing standards, and applying those lessons again, people can repeat the same year of experience ten times.
The objective is not simply to expose leaders to more situations.
The objective is to help them recognize what matters, make stronger decisions, communicate clearly, and create repeatable results.
Foremen Lead the Day
The foreman’s primary operating window is today.
A civil foreman must turn plans, layout, equipment, materials, direction, and field conditions into a clear day for the crew.
Before production begins, the foreman should know:
What the crew is building
Where the work begins
What the production target is
What equipment and materials are required
Whether the layout and information are ready
What quality checks must happen
What condition should stop the work
What must be documented before the crew leaves
The foreman is often the first leader to see the truth about field conditions.
The plan may not match the site.
Layout may be missing.
Material may not be available.
Access may be blocked.
Existing work may be at risk.
The crew may be asked to proceed without enough information.
The foreman’s responsibility is not to guess or quietly work around every problem.
It is to recognize the condition, protect the crew and the work, communicate the facts, and ask for direction early enough for someone to help.
The goal is not paperwork.
The goal is to tell the truth early enough for someone to help.
Superintendents Drive Production
The superintendent must look beyond today.
A superintendent coordinates several crews, work areas, and upcoming activities. The role requires judgment across sequence, labor, equipment, materials, survey, access, safety, quality, and outside coordination.
The superintendent should be asking:
Which work areas are actually ready?
What must happen before each crew can start?
Are the plans and details usable?
Is survey available?
Are materials approved and on site?
Is the correct equipment assigned?
Are predecessor activities complete?
Are other trades or utilities blocking the sequence?
Does each foreman understand the target?
Who owns each unresolved constraint?
When must each issue be resolved?
A schedule shows when work is expected to happen.
A production-readiness system shows whether it can happen.
That distinction matters.
If the superintendent discovers a constraint when the crew arrives, the opportunity to prevent the disruption has already been lost.
Strong superintendents do more than react quickly. They look far enough ahead to identify constraints, assign ownership, follow up, and protect upcoming production.
Project Managers Control the Record
The project manager operates across the broader project.
The PM connects the contract, scope, plans, schedule, cost, documentation, changes, decisions, risk, and opportunity.
When a project condition changes, the PM should determine:
What was originally required or priced
What is now being encountered or requested
What documents establish the difference
Who owns the issue
What work is affected
What decision is needed
When direction is required
What time, cost, production, quality, or sequence impact exists
What remains open
The PM does not create those facts alone.
The foreman sees the field condition.
The superintendent evaluates how it affects production and sequence.
The PM connects those facts to the project record and drives the issue toward a decision.
Field facts without documentation can disappear.
Documentation without clear field facts becomes noise.
Strong project control connects the two.
The Handoffs Are the Operating System
Separate development paths should not create organizational silos.
The three roles must connect through clear handoffs:
The foreman identifies the field condition.
The superintendent evaluates the effect on production and sequence.
The PM evaluates scope, ownership, documentation, cost, schedule, risk, and opportunity.
Direction moves back to the superintendent and foreman.
The team confirms what changed, who owns the next action, and what happens next.
The final outcome is reviewed and turned into a lesson, standard, or system when appropriate.
When those handoffs fail, problems remain open.
The field assumes the office is handling the issue.
The office assumes the field found a workable solution.
The work moves forward without a clear decision.
Later, the team tries to reconstruct what happened from memory.
That is where confusion becomes cost.
Each Role Requires Different Judgment
Foreman development should focus on:
Daily planning
Crew communication
Field documentation
Quantity awareness
Blueprint use
Stop-and-ask judgment
Quality checks
Equipment and tool control
Immediate issue reporting
Superintendent development should focus on:
Multi-crew planning
Production sequencing
Constraint removal
Equipment and labor coordination
Survey readiness
Material readiness
Production tracking
Foreman development
Strategic communication with the PM
One- and two-week planning
Project manager development should focus on:
Contract and scope review
Basis-of-bid comparison
Project documentation
Written direction
Change recognition and management
Schedule and cost awareness
Open-item control
Decision follow-up
Risk and opportunity analysis
Field-to-record communication
The tools should be different because the responsibilities are different.
But the operating language must connect.
Judgment Must Become Repeatable
The purpose of development is not to give people more information.
Construction already has plans, specifications, schedules, reports, software, checklists, meetings, and procedures.
The harder problem is knowing:
What matters now
What can wait
What should stop the work
What requires written direction
Who owns the next action
What creates risk
What creates opportunity
What must be verified
What lesson should become a standard
That is judgment.
A judgment-development system turns experience into something the organization can reuse:
Experience → Judgment → Action → Repeatable Results
When a problem exposes a missing standard, leadership should not stop after correcting the immediate event.
Use the full chain:
Trigger → Lesson → Action → System → Result
That is how individual experience becomes company capability.
One Stronger Field Organization
A contractor does not become stronger by asking every leader to do everything.
It becomes stronger by defining responsibilities, developing the judgment required for each role, and creating reliable handoffs between them.
Foremen lead the day.
Superintendents drive production.
Project managers control the record.
Different roles require different judgment.
Together, they create one stronger field organization.
The One Level Higher Foreman Starter Pack is currently available as a free resource. Superintendent and Project Manager Starter Packs are in development.
Explore One Level Higher at:
Comments