Plan Ahead: Production Planning Meeting Before a Roofing Job

A roofing production planning meeting should turn a sold job into a field-ready plan. It is the handoff between sales, estimating, dispatch, materials, safety, customer communication, and the crew that will actually do the work.

The meeting does not need to be long. It does need to be specific. A good planning meeting answers the questions that create jobsite confusion when no one owns them: what work is authorized, what access is available, what materials must be on site, what safety lane applies, what weather could change the plan, what photos are required, what the customer has been told, and who gets called when the first blocker appears.

Use the meeting to produce a one-page plan:

If the meeting ends without that plan, the team had a discussion, not a production handoff.

Reject The Raw Claims

The raw backlog draft behind this topic was not safe to publish. It claimed fixed profit improvements, penalties, productivity benchmarks, code rules, labor costs, supplier discounts, and software outcomes without a reliable source package. It also treated legal, safety, engineering, insurance, and contract issues as if they could be solved by a meeting template.

Those claims are not necessary. A source-bounded public page can be stronger by staying practical:

• identify the job lane;
• confirm access;
• route safety and weather questions;
• verify material ownership;
• separate observations from promises;
• document blockers before crews arrive;
• connect RoofPredict context to follow-up rather than decisions it should not make.

The value is not a guaranteed savings number. The value is fewer unknowns before the first truck leaves.

Source Boundaries

The source base for this workflow supports safety, weather, and RoofPredict positioning boundaries. It does not support fixed ROI, universal timing, code approval, warranty approval, engineering decisions, or claim outcomes.

Use this as operating guidance. It is not legal advice, safety training, engineering advice, insurance advice, warranty advice, or a code-compliance determination.

The Meeting Should Be Before The Job Feels Final

The best time for the production planning meeting is after the job has enough information to schedule and before the schedule becomes expensive to change. If the team waits until the morning of the job, missing scope, access, material, and customer details become field problems.

The meeting should happen early enough to answer:

• Does the contract or work order match what production thinks it is doing?
• Are there open change orders, supplements, customer decisions, or exclusions?
• Does the crew understand the first-day sequence?
• Are materials available, correct, and assigned to one owner?
• Is access clear?
• Are safety concerns routed before arrival?
• Is weather likely to affect staging, access, roof work, heat exposure, or customer timing?
• Does the customer know what will happen first?
• What photos and notes must be uploaded?

The meeting is not a substitute for contract review, permit review, engineering, manufacturer guidance, or safety planning. It is the place where the team confirms whether those reviews are complete or still blocking the job.

Keep Attendance Small

Too many people make the meeting vague. Too few people make it incomplete.

Use this core group:

If a person is only there to listen, send them the written plan after the meeting. The meeting should be built around decisions, not attendance.

The 45-Minute Agenda

A production planning meeting can be shorter or longer depending on the job, but a 45-minute structure works for many residential and light commercial jobs.

The closeout matters. If a blocker has no owner and deadline, it is not controlled.

Scope And Exclusions

Start with the job lane. The crew should know whether it is an inspection, repair, maintenance visit, replacement, tarp, warranty visit, callback, or closeout. Each lane has different promises and documentation needs.

Then separate four categories:

1. approved work;
2. excluded work;
3. uncertain work;
4. work that requires a supervisor, customer, insurer, manufacturer, engineer, or permit decision.

Example:

"Approved work is rear-slope pipe boot replacement and surrounding photo record. Excluded work is full roof replacement, interior repair, and insurance coverage discussion. Uncertain item is soft decking near the boot. If decking is found, stop and call the service manager before opening scope."

That kind of scope statement prevents the crew from inheriting a vague sales conversation.

Access And Site Setup

Access should be handled before the job starts. The planning meeting should confirm:

• parking;
• driveway limits;
• gate code;
• ladder setup area;
• roof access method;
• material drop area;
• dumpster or debris location;
• customer contact;
• pets;
• tenant or property manager notice;
• fragile landscaping;
• neighbor or shared driveway issues;
• interior access if needed;
• areas that should not be accessed.

The access section should include a stop point. If the ladder setup area is unsafe, if a gate is locked, if the customer is not home for required interior access, or if weather changes the site condition, the crew should know who to call before improvising.

Safety And Weather

Safety belongs near the middle of the meeting because it affects scope, access, materials, crew size, and schedule.

OSHA resources support treating fall hazards, PPE, heat, and safety management as serious planning topics. A production planning meeting can surface those topics, but it does not replace the employer's safety program, required training, competent-person decisions, or site-specific planning.

Use a simple safety review:

The National Weather Service safety page is useful for hazard categories. It does not decide whether a roof is safe. The company safety process and field supervision still own that decision.

Materials And Tools

The material section should name one owner. Do not let "we think it is ordered" survive the meeting.

Confirm:

• exact material or work-order item;
• color, profile, size, accessory, or specialty part;
• delivery date and location;
• who checks delivery;
• what happens if the order is short;
• which tools, ladders, fasteners, sealants, or specialty equipment must be loaded;
• which item is the first-day blocker.

For a repair job, the blocker may be one pipe boot, one color-matched shingle bundle, one sealant, or one access tool. For a larger job, the blocker may be delivery timing, staged accessories, disposal, or crew equipment. The meeting should identify the blocker before the crew finds it in the driveway.

Hold Points

Every production plan should name the hold points. A hold point is a condition where the crew pauses instead of making a field decision alone.

Common hold points:

• the customer asks for work outside the approved scope;
• the crew finds decking, framing, moisture, or access conditions that were not in the work order;
• material delivered to the site does not match the approved color, profile, or accessory list;
• weather changes the access or roof-work plan;
• a neighbor, tenant, property manager, or HOA creates an access conflict;
• interior access is unavailable when interior documentation is required;
• a safety concern appears after arrival;
• a repair area is larger than expected;
• the photo record cannot be completed from a safe position.

Write the hold point in plain language:

"If the crew finds soft decking, stop and call the production manager before opening the repair area."

That sentence is better than a broad warning because it says what condition matters, what action to take, and who owns the decision. Hold points protect the crew from guessing and protect the customer from surprise scope changes.

Documentation

Production planning should decide what record the company needs before work starts.

Common documentation outputs:

• pre-work context photos;
• access or staging photos;
• material labels;
• before photos;
• progress photos where useful;
• after photos;
• exception notes;
• customer approval notes;
• supervisor review notes;
• closeout photos and cleanup photos.

The photo record should use factual labels. "South slope, before repair, pipe boot cracked at visible upper edge" is better than "storm ruined the roof" unless a qualified reviewer has made that determination. Photos show observations. They do not decide cause, coverage, warranty, code compliance, or replacement need by themselves.

RoofPredict can support this lane by tracking photo status, report status, route priority, property context, storm history, roof age, and follow-up owner. It should not be framed as the decision-maker.

Change Communication

The planning meeting should also define how change gets communicated. Roofing jobs change for normal reasons: weather moves in, a customer is unavailable, a material is short, a roof area is unsafe, or a hidden condition appears. The problem is not that change happens. The problem is an undocumented change with no owner.

Use a simple rule:

1. field lead identifies the change;
2. field lead pauses the affected work if needed;
3. manager or estimator reviews the scope impact;
4. customer update owner sends bounded language;
5. job system records the decision and next step.

Example:

"The crew found a larger damaged area than the work order covers. We are pausing that area and sending it to the service manager for review. We will update you before any added work is approved."

That update is clear without promising price, coverage, warranty, cause, or completion timing before the right person reviews the file.

Customer Communication

The customer update owner should leave the meeting with exact language.

Before job start, the customer may need:

• arrival window;
• parking or access request;
• pet or gate reminder;
• what work is scheduled first;
• what areas may need interior access;
• what will happen if weather changes;
• what photos or records will be provided;
• who to call during the job;
• what has not been approved yet.

Avoid promises the production team cannot control:

• "the roof will be finished no matter the weather";
• "insurance will cover it";
• "the warranty will approve it";
• "the inspection will prove storm damage";
• "we can add that while we are there";
• "the crew can decide on site."

Use bounded language:

"The crew is scheduled for the approved repair lane. If they find decking, access, weather, or scope conditions outside the work order, they will pause and route it to the service manager before expanding the work."

That sentence gives the customer a clear expectation and protects the crew from open-ended promises.

RoofPredict Workflow Fields

RoofPredict can help connect the planning meeting to action. Useful fields include:

• job lane;
• roof age context;
• storm history context;
• access status;
• safety review status;
• material readiness;
• photo requirement;
• customer update status;
• first blocker;
• next owner;
• next check-in time.

The strongest workflow is simple: every field should either help a crew start cleanly, help a manager review the file, or help a customer understand the next step. If a field does none of those things, leave it out.

One-Page Planning Template

Use this as the final meeting output:

Keep the template plain. A simple plan that gets used is better than a detailed plan no one opens.

Manager Review Questions

After the job, review whether the planning meeting worked.

Ask:

1. Did the crew know the job lane?
2. Did the field team know what was excluded?
3. Were access issues handled before arrival?
4. Were safety and weather questions routed to the right owner?
5. Were materials complete before labor was released?
6. Were photos and notes uploaded in the right place?
7. Did the customer receive the correct pre-job and exception updates?
8. Did RoofPredict or the job system show the current status?
9. Which blocker should have been caught earlier?

Use the answers to improve the next meeting. The goal is not a perfect meeting. The goal is a cleaner start and fewer unmanaged surprises.

FAQ

When should a roofing production planning meeting happen?

Hold it after the scope is accepted and before materials, crew assignments, access plans, and customer communication are treated as final. The meeting should happen early enough to fix missing information before the crew arrives.

Who should attend a roofing pre-job planning meeting?

Keep the group small: production manager, crew lead or foreman, estimator or salesperson when scope questions remain, dispatcher, materials owner, safety owner, and customer communication owner.

Should the meeting decide safety requirements?

No. It should surface safety questions and confirm who owns the company safety process. Site-specific fall protection, PPE, heat, weather, and stop-work decisions belong to qualified supervisors and the employer's safety program.

Can RoofPredict build the production plan automatically?

RoofPredict can help organize roof age, storm history, property context, route priority, report status, customer notes, and follow-up ownership. The company still owns scope, safety, materials, crew assignments, code questions, and customer promises.

What should the meeting produce?

It should produce a short written plan: job lane, first-day sequence, access notes, material owner, weather lane, safety escalation, documentation checklist, customer update owner, blockers, and next check-in time.