15-Minute Roofing Sales Meeting: Agenda and Example

Run the roofing sales meeting from a short list of blocked work and promises due today. In 15 minutes, name who will resolve each exception and when. Leave full pipeline reviews and individual coaching for their own meetings.

The 15-minute roofing sales meeting agenda

The sales meeting agenda tool can produce a blank team-specific version. This article explains how to run it without turning the meeting into reporting theater.

The board before the meeting and the decisions after it

This fictional example starts at 8:00 and ends at 8:15. The facilitator reads six exceptions from current work records rather than asking every rep to narrate yesterday.

Before: appointment conflict

Two visits are 71 miles apart with a 30-minute gap. The second customer has not agreed to a new owner.

Before: missing inspection summary

A customer was promised an update by noon. “Waiting on inspection” has no named reviewer.

Before: incomplete handoff

A signed job has an empty product-selection field. Sales says the customer chose a color, but no controlling record is linked.

After: three concrete decisions. Dispatcher Leah asks the second customer to approve reassignment and records the answer by 9:00. Manager Ellis reviews the missing inspection summary by 10:30 so the rep can meet or revise the noon promise. Rep Jordan obtains and links the verified product selection by 11:00; production release stays pending until the receiving owner accepts the record.

The reassignment depends on the customer’s answer; the handoff depends on a verified selection. Neither is complete when the task is assigned. Use the handoff guide for the receiving record.

Read-back: “Leah owns customer-approved reassignment by nine; Ellis owns the review by ten-thirty; Jordan owns the verified selection by eleven. Production is still pending.” Each owner confirms or corrects the statement. A proposed action that no one accepts remains an unresolved exception.

At the next check: Leah records “customer declined reassignment,” so the manager changes the schedule rather than closing the item as completed. Ellis attaches the reviewed summary. Jordan links a text that conflicts with the signed selection, so the receiving owner returns the handoff for clarification. Two honest unresolved records are more useful than three unsupported green checks.

Park investigations with a named owner and report-back time. The group does not need to replay the rep’s whole conversation to assign a coaching review.

Prepare the board before the meeting

The manager or CRM owner should open a short exception view:

• safety, service, privacy, consent, or customer-risk escalations;
• customer updates and appointments due today;
• records with no owner or next action;
• blocked stage transitions;
• territory, travel, weather, and workload conflicts;
• handoffs missing required fields; and
• coaching actions due.

Use existing records. If the CRM cannot show today’s exceptions, assign a workflow repair rather than asking reps to build daily slides.

Use five facilitation rules

When the list is too long: route urgent service and customer promises first. Assign the remaining exceptions for smaller follow-ups; do not compress every item into a vague update. Consistently overloaded agendas can indicate insufficient dispatch or manager capacity.

1. Facts before opinions: identify the record, stage, customer commitment, and missing decision.
2. One owner: “sales and production” is not an owner.
3. One due time: “ASAP” is not a commitment.
4. Park investigation: assign a smaller group and report-back time.
5. No public coaching trial: route individual development to a one-on-one or practice session.

The manager should stop deal storytelling with a routing question: “What decision is blocked, who can make it, and by when?”

The 8:15 decision record

This record is short because it captures decisions, not transcripts. The sales-to-production handoff process owns the downstream stage gate.

What does not belong in the 15-minute meeting

Full pipeline narration

Review stage definitions, aging, source cohorts, and forecast inputs in a scheduled pipeline review. The daily meeting should only route current exceptions. That scheduled review is also where CRM adoption metrics belong.

Individual performance correction

Do not surprise a rep with a public score or vague criticism. Use the sales manager one-on-one tool and bring the underlying work.

A complete training session

The meeting may name the skill and assign practice. The sales daily huddle tool can create a separate short drill, while longer development belongs in the training program. Recorded-call review has its own weekly rhythm, described in the call review cadence.

Announcements and leader monologue

Send reference information asynchronously when no team decision is required. Use meeting time for coordination.

Run the same format remotely or in person

For remote and hybrid teams, display the shared exception board, not a gallery of webcams. Speak in the same order, record decisions in the source system, and allow a clear path for private or sensitive escalation. The remote sales management guide owns the broader operating system, and training roofing sales reps remotely covers onboarding for the same teams.

Audit the meeting itself

Keep the KPI scorecard outside this meeting. Read back decisions here; review performance trends with the full data elsewhere.

Frequently asked questions

Should a roofing sales team meet every day?

A brief daily exception meeting can help during active operations, but the right frequency depends on team size, season, lead flow, and whether the shared records already route work. Do not meet by habit when no coordination job exists.

Who should attend?

Only roles needed to route the day’s exceptions. Production, service, finance, or dispatch owners can join the relevant segment or receive an assigned action rather than sitting through the entire meeting.

What if meetings always run longer than 15 minutes?

Identify whether the team is reconstructing missing CRM data, coaching publicly, solving complex incidents, or reading announcements. Repair the source problem and move those jobs to the appropriate format.

End with owners, not updates

At the next check, review the result—not whether someone clicked “done.” A declined reassignment or conflicting product selection stays open until an authorized owner resolves it. That follow-through is what makes the short meeting useful.