The Roofing Project Handoff: Where Profit Is Protected or Lost
- John Kenney
- 5 days ago
- 7 min read
A roofing project can be won in estimating and lost in the handoff.
The estimator may understand the job completely.
They know what was included, what was excluded, where the production risks are, which assumptions were made and where the margin is most vulnerable.
But if that knowledge does not move clearly into operations, the project manager and superintendent are starting with only part of the picture.
That is where problems begin.
Materials get ordered incorrectly.
Labor expectations are misunderstood.
Access limitations are discovered too late.
Subcontractor scopes are unclear.
Change-order opportunities are missed.
The field begins making decisions without knowing how the job was originally priced.
A proper handoff is not an administrative meeting.
It is the point where the company transfers responsibility for protecting the estimate.
The Estimate Is More Than a Number
Many contractors treat the estimate as a final sales document.
Once the contract is signed, the file is passed to operations and the estimator moves on to the next opportunity.
That approach leaves too much behind.
A good estimate contains the contractor’s original plan for performing the work.
It includes labor assumptions, material quantities, equipment, subcontractors, production rates, job conditions, risk allowances and margin expectations.
Operations needs to understand that plan before changing it.
The project manager does not need to agree with every assumption.
In fact, the handoff may reveal areas that need to be adjusted.
But those adjustments should be deliberate.
They should not happen because the project team did not know what estimating intended.
The Handoff Must Happen Before Mobilization
The handoff meeting should occur as soon as practical after contract execution and before major purchases, scheduling commitments or field mobilization.
Waiting until the project is about to start reduces the value of the meeting.
By then, materials may already be ordered.
Crew schedules may be committed.
Subcontractors may have been contacted.
Customer expectations may have been established without a complete operational review.
The earlier operations becomes involved, the more opportunity the team has to identify conflicts and protect the original margin.
For larger or more complex projects, an initial handoff may need to be followed by a preconstruction meeting closer to mobilization.
The first meeting transfers the estimate.
The second confirms the execution plan.
1. Contract Scope and Exclusions
The first part of the handoff should answer a basic question:
What exactly did we agree to perform?
Review the signed contract, proposal, specifications, drawings, addenda and accepted alternates.
Do not assume everyone interprets the documents the same way.
The team should understand the roof areas included, systems being installed, warranty requirements, demolition scope, temporary protection, sheet-metal work, insulation, decking, drainage, accessories and closeout obligations.
Exclusions are equally important.
If interior protection, deck replacement, electrical work, hazardous-material handling, temporary water, permits or premium-time work were excluded, operations must know that before the customer or field team assumes otherwise.
An exclusion that is not communicated can quickly become unpaid work.
2. Estimate Assumptions
Every estimate contains assumptions.
Some are obvious.
Others exist only in the estimator’s notes or memory.
The handoff should identify assumptions related to production, access, staging, material loading, tear-off conditions, deck condition, crew size, working hours, weather, phasing and customer coordination.
For example, the labor estimate may assume that materials can be loaded directly to the roof.
If the project manager later discovers that crane access is limited and materials must be moved through the building, the labor plan changes immediately.
That does not automatically mean the estimate was wrong.
It means the assumption must be validated before work begins.
Assumptions are manageable when they are visible.
They become dangerous when operations discovers them in the field.
3. Labor and Production Expectations
Labor is often the largest variable on the job.
The project team should know how many labor hours were included, the estimated production rates and how the estimator expected the work to be sequenced.
This review should be specific.
Do not simply say that the job carries 2,000 labor hours.
Break the hours down by major activity.
How many hours were included for mobilization?
Tear-off?
Deck repair?
Insulation?
Membrane installation?
Flashing?
Sheet metal?
Cleanup?
Closeout?
The superintendent and project manager should then compare those expectations with the crew plan.
If the field team believes the estimated production cannot be achieved, the concern should be raised before the job starts.
That gives management time to change the plan, adjust crew composition, improve staging or determine whether the estimate needs additional protection.
4. Materials, Equipment and Subcontractors
The handoff should include a full review of major material quantities and purchasing assumptions.
Confirm the specified manufacturer, system, thicknesses, attachment method, insulation package, fasteners, adhesives, accessories and warranty requirements.
Review waste factors and any material subject to long lead times or price volatility.
Equipment also needs to be discussed.
Cranes, lifts, dumpsters, generators, safety systems, temporary storage and specialized installation equipment can materially affect the job.
The team should understand what was included, for how long and under what conditions.
Subcontractor scopes must be equally clear.
Who is responsible for sheet metal, electrical work, deck replacement, mechanical coordination, asbestos, interior protection or specialty access?
A vague subcontractor scope creates gaps.
Those gaps usually become the roofing contractor’s cost.
5. Schedule and Customer Commitments
Estimating and sales sometimes make commitments that operations has not reviewed.
The handoff must identify promised start dates, completion dates, phasing requirements, restricted work hours and coordination obligations.
The project manager should also understand what the customer expects regarding communication, meetings, reports, daily updates and site access.
This is especially important when the project involves occupied buildings, schools, healthcare facilities, manufacturing plants or high-security sites.
A schedule that works on paper may not work operationally.
The handoff is the time to test it.
If the contract calls for performance that cannot realistically be achieved, management needs to address that before the project begins—not after the first delay.
6. Known Risks and Opportunities
Every project contains areas where profit can be lost and areas where additional value can be created.
The estimator should identify both.
Risks may include uncertain deck conditions, concealed damage, difficult access, limited staging, weather exposure, occupied areas, unusual warranty details, coordination with other trades or incomplete design information.
Opportunities may include unit-price work, deck replacement, additional insulation, drainage corrections, sheet-metal upgrades or customer-requested changes.
The project manager should know what conditions require documentation and when a change order must be initiated.
Field teams also need clear direction.
They should not perform additional work simply because the customer asked.
They should document the condition, notify management and follow the company’s change-order process.
The handoff should define that process before the first opportunity appears.
7. Financial Targets and Reporting Expectations
Operations should understand the financial expectations for the project.
That does not mean every employee needs access to all pricing information.
But the project manager should know the estimated gross profit, major cost categories, labor budget, material budget, equipment allowance, subcontractor costs and contingency.
The project manager should also know how often the job will be reviewed.
Will cost reports be updated weekly?
Who is responsible for forecasting remaining labor?
How will committed material and subcontractor costs be tracked?
When will management review work in progress?
A budget that is never compared with actual performance is not a management tool.
It is history waiting to happen.
Assign Responsibility Before the Meeting Ends
A handoff meeting should conclude with clear action items.
Every unresolved issue needs an owner and a due date.
Who is confirming material availability?
Who is reviewing the contract schedule?
Who is finalizing the subcontractor scope?
Who is arranging equipment?
Who is validating access?
Who is setting the customer communication plan?
Do not end the meeting with general statements such as “operations will handle it.”
Assign the responsibility to a specific person.
That one step prevents many issues from disappearing between departments.
Document the Handoff
The handoff should be documented using a standard form or checklist.
The format does not need to be complicated.
It should capture the key information reviewed, unresolved issues, assigned actions and decisions made during the meeting.
That record gives the project team a reference point and helps management confirm that the process was completed.
It also creates consistency.
Without a standard handoff process, each estimator and project manager will transfer information differently.
Some jobs will receive a thorough review.
Others will receive a forwarded email and a few minutes of conversation.
Profit should not depend on who happens to be involved.
The Handoff Is a Management Process
The best handoff meetings are not controlled by one department.
Estimating explains how the job was priced.
Operations explains how the job will be built.
Management ensures the two plans align.
The purpose is not to criticize the estimate or allow operations to rebuild the job from the beginning.
The purpose is to create one shared plan before money is spent and commitments are made.
When handoffs fail, companies often blame the estimator, project manager or superintendent individually.
The larger problem is usually the absence of a dependable process.
Good people cannot consistently overcome missing information, unclear responsibility and last-minute planning.
Protect the Profit Before the Work Begins
The project handoff is one of the most important operational controls in a roofing company.
It connects sales, estimating, purchasing, project management and field execution.
It gives the team a chance to identify risk before it becomes cost.
It allows assumptions to be tested.
It establishes expectations.
It creates accountability.
Most importantly, it protects the plan that produced the original margin.
Once the crew is on the roof, the cost of solving a problem becomes much higher.
The best time to protect project profit is before the project begins.
Cotney Consulting Group works with roofing contractors to strengthen estimating-to-operations handoffs, project management systems, and field accountability. A clear handoff process gives every department the information and direction needed to execute the work profitably.