How to Manage a Construction Project (Without It Managing You)

How to manage a construction project starts with one decision: are you in the job, or are you running it? They are not the same thing. If you are on the tools all day, no one is watching the schedule, chasing the subs, or reading the contract. The project is running you.

Most contractors who struggle with project management are not bad at construction. They are good at it - so good they never step back from it. The work gets done. The margin disappears. The next job starts before the last one is invoiced.

This is really a conversation about construction arbitrage - the model where you, as the general contractor (main contractor in the UK), hold the contract and your subs do the work. In that model, project management is not a nice-to-have. It is the entire job. The margin is yours because you are keeping the whole thing moving. Stop doing that and the margin disappears with you.

How to manage a construction project before day one

Most problems on a construction project are created before day one. A vague scope. No signed drawings. No payment schedule. No defined process for changes. These are the conditions that turn a straightforward job into three months of arguments.

Before anyone arrives on site, confirm five things in writing: the full scope of works, a set of signed drawings or a detailed specification, a payment schedule tied to milestones, a process for variations, and a defined end point - what 'finished' actually means for this specific job.

If the contract and scope are not locked before work starts, read the guide on how to write a construction contract before you take on the next one. A well-written contract prevents most of the conversations this post is about having to have.

Managing subcontractors: one chain of command

The most common breakdown on a multi-trade project is this: two subs start working around each other, the client starts directing one of them, and no one is quite sure who is responsible for what. That is a project management failure, not a trades failure.

The fix is simple. One chain of command: all site direction goes through you. The client speaks to you. You speak to the subs. The subs do not take instructions from the client directly - ever. Write that into your subcontract, say it at the briefing before the job starts, and enforce it if anyone crosses it.

• Written scope per trade. Every sub gets a written scope of what they are responsible for, not just a verbal briefing. Ambiguity between trades is where the arguments live.
• A clear sequence. Who is on site when, in what order, and who clears before the next trade arrives. Sequencing is the difference between a job that flows and one that has three trades stepping on each other.
• One communication channel. A WhatsApp group, a project tool, email - pick one. A sub who texts you, emails someone else, and calls your foreman is not getting consistent information. That costs you.
• A weekly check-in. Five minutes on the phone or in person. What is on track, what is not, what they need from you this week. You do not have to be on site every day to stay in control. You do have to stay in contact.

For the full guide on finding and vetting the right subs in the first place, read how to find good subcontractors.

Client communication: one update that stops ten calls

Most of the calls a contractor gets mid-project are not because the client is difficult. They are because the client has no idea what is happening on their job. You know. You have been there. They have not. Fill that gap before they do.

When I was running maintenance for housing associations in London, the site foreman sent a single update at the end of every working day - one photo, two lines. What we completed, what starts tomorrow. The same clients who used to call four times before lunch stopped calling entirely. Nothing else changed.

Clients who feel informed stop chasing. Clients who are left guessing start controlling.

One thing contractors get wrong: they give updates on effort, not progress. 'The lads were on site all day' tells the client nothing. 'First fix plumbing is complete on floors one and two - third floor starts tomorrow' tells them exactly where they are. Progress updates. Not activity updates.

Variations and scope changes: the written rule

Scope creep is the single biggest reason contractors finish jobs with less money than they expected. A client asks for something small. You say yes because it seems easy. Then another small thing. Then another. By the time you invoice, you have done $5,000 worth of extra work that no one agreed to pay for.

(Figures in USD - the model and the math are identical in any currency.)

The written rule is simple: nothing outside the signed scope gets done without a written variation - even a $200 extra. Not because you are being difficult. Because once you establish that extra work has a cost, clients stop treating your time as an afterthought.

A variation does not have to be formal. A WhatsApp message confirming the extra and the cost, with the client replying 'yes', is a paper trail. Silence is not approval. 'I mentioned it verbally' is not approval. Get something in writing before you spend a day on it.

For the full breakdown on handling variations correctly, the post on how to handle change orders in construction covers it in detail.

Delays: document them the same day

Delays happen on almost every project. What separates competent project managers from poor ones is not whether delays happen. It is how fast they are documented and who they are attributed to.

If a delay is the client's fault - a late decision, missing access, changed spec - record it the same day in writing. That record is the basis for extending the timeline and recovering any associated costs. Leave it undocumented for two weeks and you look like you are making it up later.

If the delay is your sub's fault, deal with it directly and fast. Have the conversation, agree a recovery plan, put it in writing. A sub who is consistently behind on one job will be behind on every job unless the consequence is clear.

Snagging, handover and the final payment

The end of a project is where the money either comes in or gets stuck. Most retention disputes and withheld final payments start because the client walked the job before you did and found things you should have caught first.

Walk the job yourself before the client handover. Write your own snagging list. Fix the issues. Then invite the client for the formal walkthrough. A contractor who hands over a clean job - no issues they have not already addressed - gets paid faster than one who waits for the client to find the problems.

At handover, provide: a clear final invoice, any warranties or certifications for work completed (electrical, structural, commissioning - whatever your jurisdiction and trade require), and a brief record of the job from start to finish. That record is also your protection if anything is disputed later.

If your payment schedule is not structured properly going into the job, no amount of good project management saves you at the end. The guide on how to ask for a deposit as a contractor covers how to set up the payment terms before work starts.

The operator's job: managing the margin, not the mortar

Here is the part no one tells you when you make the jump from on the tools to running the business: the project does not need you to be the best tradesperson on site. It needs you to be the most organized person connected to it.

The margin in a construction project comes from the gap between what you charge the client and what you pay the subs and suppliers. That gap only stays healthy if the job stays on scope, on schedule, and in budget. When those three things slip, the margin is the first thing to go.

That is what construction arbitrage looks like from the inside. You hold the contract. You manage the relationship. Your subs deliver the work. And you run the whole thing tightly enough that the gap between the client's invoice and your costs is real money - not just what it was on paper before the job started.