A sold roofing job is not really safe until it is scheduled, permitted, documented, and moving toward install.
That gap between signed approval and production is where too many roofing companies leak time.
The homeowner thinks the job is handled. The sales rep thinks production has it. Production is waiting on permit status. The office is missing a document. The owner gets pulled into a text thread asking what is stuck.
A roofing permit follow-up SOP gives every sold job a clear CRM stage, permit owner, document checklist, customer update, and scheduling handoff. The goal is simple: stop approved roofing jobs from sitting in limbo because nobody is watching the admin details.
Why roofing permit follow-up gets messy
Roofing permit follow-up breaks down because the work sits between sales, admin, production, and the customer.
Sales may collect the signed agreement but forget a color selection. Admin may submit the permit but not update the job record. Production may wait for approval but not see that the permit was cleared yesterday. The customer may ask when the crew is coming, and nobody has a clean answer.
For US roofing contractors, this is where cash flow slows down. The company already won the job, but the job cannot move because the process after approval is loose.
The roofing permit follow-up SOP
Keep this process simple enough that a trained VA or office coordinator can run it every business day without making production decisions.
Step 1: Create a sold job permit stage in the CRM
Do not leave sold roofing jobs in a generic closed won stage with no next action.
Create CRM stages that show the real path from approval to install. Useful stages include sold pending documents, permit packet needed, permit submitted, permit pending, permit approved, production handoff, install scheduled, and ready for crew.
Every sold roofing job should include the customer name, property address, sales rep, contract date, roof type, material selection, permit requirement, document status, permit submitted date, permit approval date, production owner, customer update date, and next task.
The CRM should answer one question fast: what is blocking this job from being scheduled?
Step 2: Use a permit packet checklist
Permit problems often start before the permit is even submitted.
A simple permit packet checklist can prevent a lot of back and forth. Depending on the local market, the checklist may include signed contract, scope, property address, owner information, product details, color selection, photos, measurements, HOA notes, insurance documents, and required city or county forms.
The VA should not guess permit requirements. The VA should check the approved internal list, flag missing items, and assign the right person to fill the gap.
Step 3: Set permit follow-up tasks before submission
A permit should never be submitted without the next follow-up task already scheduled.
Use a simple rhythm:
- Submit the permit and log the submission date.
- Add the permit number or portal reference if available.
- Set the next follow-up date based on the local process.
- Assign the follow-up owner.
- Update the customer if the timeline affects scheduling.
This is not about annoying the permitting office. It is about keeping your company from forgetting which jobs are waiting, approved, or missing action.
Step 4: Give customers a clear update before they ask
Homeowners get frustrated when they sign the agreement and then hear nothing.
Use a simple update after the permit packet is submitted:
“Hi [Name], your roofing permit packet has been submitted for [address]. We are tracking approval and will update you when the permit clears or if the office needs anything else before scheduling.”
When the permit is approved:
“Hi [Name], the roofing permit for [address] has been approved. Our production team is reviewing scheduling and will confirm the next step.”
The update should not overpromise an install date. It should show the job is being watched.
Step 5: Separate permit approval from production scheduling
Permit approved does not automatically mean install scheduled.
Once approval is confirmed, the record should move to production handoff with a clean summary: permit approved date, customer notes, material status, access notes, special instructions, payment status if relevant, and the next scheduling task.
A trained VA can prepare the handoff, clean the CRM record, attach the permit note, and flag missing information. Production still owns scheduling decisions. The VA owns the admin trail that makes scheduling easier.
What this looks like in real life
A roofing company sells eight roof replacements in one week.
Messy version:
Three jobs are waiting on permits, but nobody knows which ones were submitted. One homeowner calls asking for an install date before the permit is approved. A sales rep has the color selection in a text message. Production finds out late that one city form is missing. The owner spends Friday afternoon chasing details instead of managing the business.
Clean version:
Every sold job moves into BoostOps CRM with a permit stage and checklist. The VA checks each record daily, logs submitted dates, adds follow-up tasks, flags missing documents, sends approved customer updates, and moves approved jobs into production handoff. The production team sees what is ready, what is waiting, and what needs attention.
Same jobs. Less chaos.
The owner should not be the permit tracker
If the owner has to remember which roofing permits are pending, the company has outgrown its admin process.
That is low-value work for the owner. It also creates risk because one missed update can delay production, annoy the customer, and create a scheduling scramble.
A trained VA plus BoostOps CRM gives the team one place to track permit status, missing documents, customer updates, scheduling handoffs, and next tasks. The VA keeps the record clean while the production team handles field decisions.
BoostOps CRM is available at $199/month. If you need the person and the system, BoostOps also places a full-time Filipino VA with a fully set up CRM for $11.86/hour, billed monthly for a full-time VA.
Start simple
Do not build a complicated production department before the basics are handled.
Start with this daily roofing permit follow-up checklist:
- Review every sold roofing job that is not scheduled.
- Confirm the job has one CRM record and the right permit stage.
- Check whether the permit packet is complete.
- Log the submitted date, permit number, and portal note when available.
- Set the next follow-up task before closing the record.
- Send the approved customer update when status changes.
- Move approved jobs into production handoff.
- Flag missing documents, color choices, HOA notes, or payment steps.
- Send the owner or production manager a short stuck-job summary.
Run that checklist every business day for two weeks. Then tighten your stage names, permit checklist, and customer update scripts.
For related cleanup, connect this to the roofing storm lead intake SOP, the roofing insurance supplement follow-up SOP, and the home service dispatch cleanup SOP.
The goal is simple: every approved roofing job has a permit status, a document owner, a customer update, and a clean production handoff.
FAQ
What is a roofing permit follow-up SOP?
A roofing permit follow-up SOP is a repeatable process for tracking sold roofing jobs through permit packet completion, submission, follow-up tasks, customer updates, approval, and production handoff.
How should roofing contractors track permit status?
Roofing contractors should track permit status in a CRM stage tied to each sold job. The record should show submission date, missing documents, permit number when available, next follow-up date, customer update status, and production handoff owner.
Can a virtual assistant help with roofing permit follow-up?
Yes. A trained VA can check permit packets, update CRM stages, assign missing document tasks, send approved customer updates, log submitted and approved dates, and prepare the production handoff.
What should happen after a roofing permit is approved?
After a roofing permit is approved, the job should move to production handoff with the permit approval date, customer notes, material status, access details, special instructions, and the next scheduling task clearly documented.
Fix roofing permit follow-up before sold jobs stall
Sold roofing jobs should not depend on owner memory or scattered texts.
BoostOps can help set up the CRM, build the SOP, and staff the trained VA who keeps roofing permit follow-up organized from signed agreement to production handoff.
Book a BoostOps discovery call and we will map where approved roofing jobs are getting stuck before install.