Construction isn't that difficult. Every person on a project plays their part by answering a few questions, over and over.
That isn't a knock on the work. Getting those answers right takes years on site. But the questions themselves repeat on every job, and on most jobs they're never written down. They live in the heads of the people asking them.
Walk through the roles one at a time and you'll see it.
The estimator.
The estimator's question is simple to say and hard to do. Everything I can physically see on the drawings, and every note I can read: has it been accounted for in the estimate?
- Have I allowed for the time implications?
- Have I allowed for the cost implications?
- Have I allowed for the quality implications, which flow into everything else?
- Has the cost been assigned to the activity?
The project manager.
The project manager picks up that estimate and checks it against their own experience. Then, once the job is being built, the question shifts from "is it priced?" to "is it happening?"
- Are the expected outcomes going to be achieved?
- Has anything been missed?
- If it has, can it be claimed, so the loss is recovered?
The project team.
The project team has one job: deliver the element, such as a structural element. Around that job sit the questions that keep the money moving.
- Are the costs being captured?
- Are the scopes confirmed?
- Are the subcontractors paid?
- Has the progress claim gone to the client on time?
- What's the next activity, and is it pre-planned?
The foreman.
The foreman also has one job. It's the work in front of them, on the drawings, right now.
- Is what I'm building in the right location, at the right height?
- Do I have every element in this detail to complete the design?
- Do I need to order or schedule anything to make it happen?
- Have I told the right people what's been completed?
- Has safety been managed? Has quality been managed?
- Do the subcontractors understand the work, so no time is wasted?
Answer those, then answer them again for the next detail. It's an iterative loop, and it can be mapped.
The construction manager.
The construction manager asks the same kind of questions across every project at once. Much of this sits with the project manager too. Both use their experience to look ahead.
- Is every project running on time?
- Can I see problems coming before they arrive?
- Are the crews allocated correctly to each project and its work?
- Do I have more projects lined up?
- Is there a substitution or an engineering alternative worth proposing?
- What can I suggest from my experience that would benefit the project as a whole?
Safety.
Before the work starts, safety asks:
- Do we know what work is being done?
- Do we have the relevant paperwork for it?
- Have we identified the hazards?
- Has everyone understood what they need to do?
- Are the people doing it qualified?
- Can we complete the work safely, or do other controls need to be in place?
Quality.
Quality asks whether the job is being built the way the documents say, and whether you can prove it.
- Are the correct materials being used?
- Is the correct process being followed, as per the drawings?
- Is the paperwork being collected at every step the contract stipulates?
- Can we compile and issue that paperwork at the cadence the contract documents require?
The questions are the system.
Put the roles side by side. Nobody is inventing their job from scratch each morning. They're asking the same questions at the same points, project after project.
And the answers connect. The estimator's allowance is what the project manager checks. The foreman's completed work is what goes into the progress claim. Safety and quality paperwork runs through every step.
While those questions live only in people's heads, the loop holds as long as the right person is there to ask them. Write them down, attach each one to the moment it needs answering, and send the answer to the person who acts on it. Then the loop runs the same way on every job.
That's what makes it something you can systematise. Structure first. Tools after.
Where to start this week.
Pick one role on your current job. Write down the questions that person asks before, during and after an activity. Next to each one, note where the answer goes and who acts on it.
That list is the start of your system.
Common questions
Does this mean construction roles are simple?
No. The work takes skill and years of experience. The point is that each role's thinking follows a short set of repeatable questions, and that's what makes it possible to structure.
Why do the roles overlap?
Because a project is one loop. The estimator's allowances become the project manager's checks, the foreman's completed work feeds the progress claim, and safety and quality run through every step.