Why Roofing Project Managers Lose Control of Jobs—and How to Fix It
- John Kenney
- 2 hours ago
- 7 min read
Most roofing projects do not fall apart all at once.
They drift.
A material issue is not resolved quickly.
A customer request is handled verbally.
A subcontractor starts before the scope is fully confirmed.
Labor runs over the estimate for several days before anyone reviews it.
The schedule changes, but the crew, supplier and customer are not all working from the same information.
None of these problems may seem severe by itself.
Together, they create a project that is no longer being managed.
The project manager becomes reactive.
Instead of directing the job, they spend the day answering problems created by decisions that were delayed, undocumented or never made.
Project managers rarely lose control because they do not care about the work.
They lose control because the company has not given them a dependable process for planning, measuring and correcting the project.
Here are the most common reasons roofing project managers lose control of jobs and what contractors can do to fix them.
They Start Managing After the Job Starts
A project manager should not begin planning when the crew arrives.
By then, the most important decisions should already be made.
The project manager needs time to review the contract, estimate, scope, exclusions, labor budget, material requirements, equipment, subcontractors, schedule and customer commitments.
They should know where the project carries risk.
They should understand how the estimator expected the work to be performed.
They should also confirm that the original assumptions still match actual job conditions.
When this review does not happen, the project manager begins the job by discovering information that should have been transferred earlier.
That creates immediate pressure.
Materials may already be ordered.
The crew may already be scheduled.
The customer may already expect a start date.
Good project management begins before mobilization.
The Schedule Is Too General
A start date and completion date do not create a project schedule.
The project manager needs a working plan that identifies the sequence of major activities and the resources required to complete them.
That plan should account for:
Material delivery
Equipment
Crew availability
Subcontractors
Inspections
Customer coordination
Weather exposure
Phased work
Occupied areas
Closeout requirements
A general schedule may look acceptable during the kickoff meeting, but it does not help when two crews, a crane, a supplier and a building owner must all be coordinated on the same day.
The schedule should be detailed enough to direct the work but flexible enough to adjust when conditions change.
It also needs to be communicated.
A schedule that exists only in the project manager’s head is not a schedule the rest of the team can follow.
Daily Documentation Is Incomplete
Many project managers underestimate the value of daily documentation until a problem develops.
Then they begin searching for photographs, delivery tickets, labor information, weather records, emails and field notes that were never collected properly.
Daily reports should provide a clear record of what happened on the project.
They should capture:
Crew size and labor hours
Work completed
Material received and used
Equipment on site
Weather conditions
Delays
Customer requests
Other trades affecting production
Safety or quality concerns
Photographs of progress and conditions
The purpose is not to create paperwork for its own sake.
Documentation gives the project manager evidence.
It supports billing, change orders, schedule discussions, warranty records and internal job-cost reviews.
It also forces the team to look at the project every day rather than relying on memory at the end of the week.
Change Orders Are Handled Too Late
Unmanaged change is one of the fastest ways to lose control of a project.
A customer asks for additional work.
The field discovers damaged decking.
Another trade creates a delay.
A manufacturer requirement changes the installation.
The crew is instructed to proceed, and the paperwork is expected to catch up later.
Too often, it never does.
The project manager should have a clear process for identifying, documenting, pricing and authorizing changes.
Field employees should know that additional work must be reported before it is performed whenever conditions allow.
The project manager should then document the condition, notify the customer and establish whether the work affects price or schedule.
Not every change requires a complicated process.
Every change requires a visible decision.
When project managers allow changes to remain informal, the company absorbs the cost and accepts the schedule impact.
Labor Is Reviewed After the Damage Is Done
A project manager cannot control labor by reviewing it at the end of the job.
Labor performance must be measured while the work is active.
Compare actual labor hours with the estimated hours for the work completed.
Do not wait until the entire project exceeds budget.
Break labor into major activities.
If tear-off carries 500 estimated hours, the project manager should know how many
hours were used when tear-off is 25 percent, 50 percent and 75 percent complete.
That gives the team time to investigate.
Is production lower than estimated?
Is access limiting the crew?
Is material staging inefficient?
Is crew size wrong for the work?
Is rework occurring?
Was the estimate based on different conditions?
The goal is not to blame the crew or estimator.
The goal is to identify the cause early enough to take action.
The Project Manager Becomes the Messenger Instead of the Decision-Maker
Some project managers spend most of their time passing information between the customer, superintendent, estimator, supplier and company owner.
They are involved in every conversation but are not authorized to make routine decisions.
That slows the project and weakens accountability.
A project manager should have clearly defined authority.
They need to know what they can approve, what requires management review and when a decision must be escalated.
Authority may include purchasing within approved budgets, coordinating labor, scheduling subcontractors, directing project communication and initiating change-order procedures.
Without defined authority, the project manager becomes dependent on the owner or operations manager for every answer.
The project cannot move faster than the person everyone is waiting on.
Authority must be paired with accountability.
Project managers should not have unlimited control.
They should have enough authority to manage the responsibilities assigned to them.
Communication Is Frequent but Not Clear
More communication does not always mean better communication.
Project managers can spend the entire day on calls, emails and text messages while important information remains unclear.
Effective communication answers four questions:
What happened?
What does it affect?
What decision is required?
Who is responsible for the next action?
For example, saying that a material delivery is delayed is not enough.
The project manager needs to determine whether the delay affects crew scheduling, equipment, weather exposure, customer access or the completion date.
Then the affected parties must receive the same information.
Communication should reduce uncertainty.
It should not simply transfer the problem to someone else.
Subcontractors Are Not Managed to the Same Standard
Subcontracted work still belongs to the roofing contractor.
The customer does not separate the subcontractor’s performance from the contractor’s responsibility.
Project managers need to confirm subcontractor scope, schedule, insurance, manpower, material responsibility, documentation and quality expectations before work begins.
They should also verify progress and address deficiencies quickly.
A vague scope creates disputes.
A weak schedule creates delays.
Poor documentation creates billing problems.
Lack of oversight creates quality issues.
Subcontractors should be treated as an extension of the project plan, not as a separate operation outside the project manager’s control.
Project Managers Do Not Have Current Cost Information
A project manager cannot protect margin without knowing how the job is performing financially.
They should have visibility into the major cost categories they are expected to control.
That may include:
Labor
Materials
Equipment
Subcontractors
Disposal
Freight
Permits
Change orders
Remaining cost to complete
The information does not need to be presented as a complicated financial report.
It needs to be current, understandable and connected to the project plan.
If cost information arrives weeks after the work occurred, it may explain the loss but cannot prevent it.
Project managers need enough financial visibility to recognize when performance is moving away from the estimate.
Closeout Is Treated as an Afterthought
A project is not finished when the installation is complete.
Punch-list work, inspections, warranties, photographs, customer acceptance, final billing, lien releases, operations manuals and internal cost reviews still need to be completed.
When closeout is not planned early, these items remain unresolved for weeks or months.
That delays payment.
It consumes management time.
It also keeps the project open financially, making it harder to determine the actual result.
The project manager should create the closeout plan before the job begins.
They should know what documentation will be required, who is responsible and when each item must be submitted.
A controlled closeout protects both cash flow and the customer relationship.
Build a Weekly Project-Control Routine
Project managers need a regular operating rhythm.
A weekly project-control review should cover:
Current schedule
Work completed
Labor performance
Material status
Equipment
Subcontractors
Pending decisions
Change orders
Billing
Customer issues
Quality concerns
Estimated cost to complete
Closeout requirements
The review does not need to become a long meeting.
It needs to be consistent.
The project manager should leave with clear priorities, assigned actions and deadlines.
This routine also gives management visibility without forcing the owner to become involved in every detail.
Training Must Go Beyond Software
Software can organize project information.
It cannot replace project-management judgment.
A project manager must understand planning, contracts, labor, communication, documentation, customer expectations, cost control and field execution.
They need to know how the parts of the project affect one another.
Uploading photographs is not the same as documenting a condition correctly.
Entering a schedule is not the same as managing the sequence of work.
Reviewing a budget is not the same as understanding why production is falling behind.
Technology supports the process.
Training develops the person responsible for using it.
Control Comes From Discipline
Project control does not mean that nothing goes wrong.
Roofing projects will always face weather, concealed conditions, material delays, labor issues and customer changes.
Control means the project manager recognizes the issue, understands the effect, makes or escalates the decision, documents the action and adjusts the plan.
That requires discipline.
It also requires a company structure that supports the project manager with clear expectations, authority and accurate information.
A strong project manager should not spend every day putting out fires.
They should be preventing avoidable problems, planning for known risks and identifying changes before those changes damage the project.
When project managers lose control, the answer is not always to replace the person.
Sometimes the company needs to improve the process around them.
Cotney Consulting Group helps roofing contractors strengthen project-management systems, train project managers and establish the planning, reporting and accountability needed to execute work consistently and profitably.
Comments