Roofing CRM workflow pattern map

Most roofing companies already own the pieces: a CRM, a calendar, an estimating tool, job software and a review platform. What they rarely have is one picture of how a homeowner moves between them, who is responsible at each handoff, and which record proves where a signed job started.

This map is that picture. It is a pattern, not a client case study: an anonymized architecture drawn from hands-on CRM and automation work, with no client names and no metrics. Use it as a checklist for your own setup, or as a starting sheet when you plan a new account.

1. Print it (the button above saves a clean PDF) and write your own tool name next to each stage.
2. Name one owner per stage. A person or a role, not "the office". If two people think they own a stage, nobody does.
3. Check the fields. For each stage, confirm the listed fields exist in your system and are filled in when the stage starts, not weeks later.
4. Mark the gaps. Any stage with no owner system, no trigger or no checkpoint is where leads go missing.

The pattern assumes GoHighLevel as the CRM because that is where we work most, but the stages hold for any CRM with pipelines, calendars and workflows.

Two rules make the table work. Each field is written by one system only, and the job ID links the CRM contact to the job record so neither side has to match on names.

Contact to first reply. The first reply is only as fast as the slowest intake path. A lead form that lands in an inbox instead of the CRM skips every later stage. Send all channels into one intake path before you tune any message.

Inspection to estimate. The inspection result is often written on paper or in a phone note. Decide where the outcome is recorded (estimate needed, not a fit, insurance follow-up) and make that field required before the stage can move.

Estimate to job. This is the handoff between two systems. Pick one event that means "signed", such as a status in the estimating tool, and let only that event create the job. Manual job creation alongside an automatic one is how duplicates start.

Job to review. The review request should wait for a real "closed" signal from production, not a fixed number of days after the estimate. Homeowners asked for a review while crews are still on the roof tend to say so in public.

• The source is overwritten. A later form fill or import replaces the first source, so attribution credits the last click. Store the first source in its own field that nothing else writes to.
• A field changes and nobody knows why. Reminders arrive at the wrong hour, or a stage jumps backward. Check the CRM's audit history for the record before editing any workflow; often a form or an integration is writing to the same field.
• Two calendars, one inspector. Bookings from the CRM and from someone's personal calendar collide. Keep one calendar as the source of availability.
• Follow-up that never stops. A homeowner who signed, declined or asked to pause still gets estimate reminders. Every follow-up sequence needs exit conditions tied to the decision field.
• Sync without an ID. Records are matched on name or address, so a typo creates a second job or links the wrong homeowner. Match on IDs and keep a log of each sync.
• Referrals with no tag. A referred homeowner looks like a direct call. Give referrals their own link or source value so they show up in attribution.
• Automation that speaks for the business. A bot or template promises dates, prices or insurance outcomes. Keep those topics with a person and keep automated wording to confirmations, reminders and booking.
• No owner for the exceptions. Leads that fit no rule (outside the service area, commercial roofs, repeat customers) sit untouched. Route them to one named person.

Roofing businesses differ in where the inspection happens, who writes estimates and how insurance work flows, so treat the stages as defaults. A retail-only roofer may merge inspection and estimate into one visit. A storm-restoration team may add a stage for insurance paperwork between estimate and job. Keep the same columns for any stage you add: owner system, fields, automation and the human checkpoint.

If you want a deeper look at the roofing side, the roofing industry page covers routing and field ownership in more detail, and the GoHighLevel service page explains how we audit and repair accounts.