Florida Roofing Contractor Workflow: From Lead to Final Payment Without Losing the Next Step

A reliable roofing workflow gives every project a clear owner, current status, and next action. Use the following stages as an operating checklist for sales, estimating, production, billing, and closeout. Regulatory, permitting, inspection, and compliance guidance is excluded because those requirements are not addressed here.

1. Capture and qualify the lead

Create one lead record as soon as an inquiry arrives.

Record:

• Customer name and contact information
• Property address
• Preferred communication method
• Source of the inquiry
• Requested roofing work
• Known roof condition or reported problem
• Relevant photos or documents supplied by the customer
• Assigned team member
• Next action and next-action date

Qualification checklist:

• Confirm the property address.
• Confirm that the customer wants an inspection, repair estimate, replacement estimate, or another defined service.
• Identify who will participate in the purchasing decision.
• Note any access instructions.
• Record the customer’s stated priorities and concerns.
• Schedule or decline the opportunity.

Decision point: Is the opportunity a fit?

• Yes: Advance it to appointment scheduled.
• More information needed: Assign a specific follow-up action.
• No: Record the reason and close the lead.

Do not leave a lead in an undefined status. Every open lead should have an owner and next action.

2. Prepare for the site visit

Before the appointment, review the lead record and prepare a consistent field checklist.

Pre-visit checklist:

• Verify customer and property details.
• Review reported issues and previous communications.
• Confirm access instructions.
• Prepare the inspection and photo checklist.
• Identify measurements, material details, and customer questions that need to be captured.

3. Document the site visit

Keep observations separate from customer statements. Label photos and notes so another team member can understand them without relying on memory.

Capture:

• Areas reviewed
• Visible conditions
• Measurements used for estimating
• Material and color preferences discussed
• Property access considerations
• Customer questions
• Photos organized by area or roof section
• Items requiring clarification before estimating

Before leaving:

• Review the customer’s requested scope.
• Confirm contact information and communication preference.
• Explain the next step without promising an unsupported outcome.
• Assign responsibility for preparing the estimate.

Decision point: Is the file complete enough to estimate?

• Yes: Move it to estimate preparation.
• No: Create a missing-information task and keep the opportunity out of the sent-estimate stage.

4. Build and review the estimate

Prepare the estimate from documented scope rather than memory or informal messages.

Estimate file checklist:

• Customer and property information match the lead record.
• Scope is organized into clear work items.
• Included and excluded work is distinguishable.
• Selected materials and options match the discussion.
• Photos, measurements, and notes support the scope.
• Pricing and payment terms receive an internal review.
• Any unresolved assumptions are identified before sending.

Internal decision point: Is the estimate ready for the customer?

• Approved internally: Send it and record that action.
• Needs revision: Return it to the assigned estimator with a specific correction.
• Blocked: Record what information is missing and who owns the next action.

5. Manage the sent estimate

Sending an estimate is not the end of the sales stage. The record should show whether the estimate is awaiting review, approved, rejected, or being revised.

Follow-up checklist:

• Record that the estimate was sent.
• Keep the estimate amount attached to the opportunity.
• Record customer questions and requested changes.
• Create a new version when the scope or price changes.
• Preserve prior versions for internal reference.
• Record the approval or rejection rather than relying on an informal assumption.

Egret raises an “estimate aging” alert for an estimate that was sent three or more days ago and is neither approved nor rejected, and the alert shows the estimate amount.

Decision point: What happened to the estimate?

• Approved: Confirm the accepted version and begin job setup.
• Revision requested: Document the requested change and return it for review.
• Rejected: Record the reason and close the opportunity.
• No decision: Keep a named follow-up action assigned.

6. Convert the approved estimate into a job plan

Do not treat approval as automatic production readiness. Create a handoff that production can execute without reconstructing the sale.

Sales-to-production handoff:

• Confirm the approved estimate version.
• Confirm the customer and property details.
• Transfer the agreed scope and selections.
• Attach relevant measurements, photos, and notes.
• Identify customer-visible commitments.
• Record access and communication instructions.
• Assign the production owner.
• List unresolved selections or questions.
• Define the next production action.

Decision point: Is the job ready to schedule?

• Yes: Move it into the production queue.
• No: Keep it in a preparation status with each open item assigned.

7. Prepare the production file

A crew-ready file should make the approved work easy to identify.

Production checklist:

• Approved scope is clearly marked.
• Current material and color selections are documented.
• Property notes and access instructions are available.
• Measurements and relevant photos are attached.
• Assigned crew or production contact is recorded.
• Customer communication responsibility is assigned.
• Scope changes have a defined review path.

Avoid mixing preliminary options with the final approved scope. Clearly identify superseded documents.

8. Control changes during the job

When a customer request, site condition, or scope question appears, document it before treating it as part of the active work.

Change workflow:

1. Record the requested or observed change.
2. Attach supporting notes and photos.
3. Identify the effect on scope and price.
4. Route the change for internal review.
5. Present the revised scope to the customer.
6. Record the customer’s decision.
7. Update production instructions only after the accepted version is identified.
8. Retain the prior scope for reference.

Decision point: Is the change accepted?

• Yes: Update the active job scope and billing information.
• No: Keep the original scope active.
• Pending: Do not allow field notes alone to become the controlling scope.

9. Track production status and issues

Use a small set of clearly defined statuses rather than relying on free-form notes.

Possible operational statuses include:

• Preparing
• Ready to schedule
• Scheduled
• In progress
• Waiting on customer decision
• Waiting on material or internal action
• Work complete pending review
• Ready to invoice

For every blocked job, record:

• What is blocking progress
• Who owns the resolution
• The next action
• The most recent customer communication

10. Review work completion

Before moving a project to billing, conduct an internal completion review.

Completion review checklist:

• Compare completed work with the active approved scope.
• Confirm accepted changes are included.
• Organize completion photos and field notes.
• Record unresolved customer questions.
• Confirm production documentation is complete.
• Identify remaining billing items.

Decision point: Is the job ready to invoice?

• Yes: Move it to billing.
• No: Create an assigned correction or documentation task.

11. Issue and track the invoice

The billing record should connect the invoice to the approved scope and accepted changes.

Invoice checklist:

• Customer and property details are correct.
• Invoice aligns with the approved work and accepted changes.
• Prior payments or credits are reflected accurately.
• Payment terms are clear.
• The invoice amount has been reviewed.
• The sent invoice is recorded in the project file.

Egret raises an “invoice overdue” alert for a sent invoice whose due date has passed, and the alert shows the invoice amount.

Invoice decision point: What is the current status?

• Paid: Record the payment and continue to closeout.
• Partially paid: Record the payment and remaining balance.
• Customer has a question: Assign the question to the appropriate owner and document the response.
• Past due: Assign a collection follow-up and keep the balance visible.

12. Close the project record

Final payment should trigger a closeout review, not an immediate disappearance from the active workflow.

Closeout checklist:

• Record final payment.
• Confirm the balance is resolved.
• Confirm the final approved scope is identifiable.
• Organize estimates, accepted changes, invoices, payments, photos, and communications.
• Resolve or assign any remaining customer question.
• Mark the project closed only after the record is complete.
• Record the final outcome and any internal lessons.

Egret provides a customer portal reached through a private link. It shows only project information and files marked customer-visible, and it does not expose internal job costs or margins.

Before marking a file customer-visible, review it to ensure it is intended for customer access.

Daily pipeline review

Review open work by exception instead of reading every project from the beginning.

Sales review:

• New leads without an owner
• Leads without a next action
• Appointments requiring preparation
• Site visits missing documentation
• Estimates waiting for internal review
• Sent estimates without a recorded decision

Production review:

• Approved jobs missing a handoff
• Jobs blocked by an unresolved question
• Jobs with pending scope changes
• Work marked complete but not reviewed
• Jobs ready to invoice

Billing review:

• Completed work not yet invoiced
• Sent invoices with customer questions
• Past-due invoices
• Payments not yet connected to the correct invoice
• Paid projects awaiting closeout

The no-lost-next-step rule

For every open lead, estimate, job, or invoice, require these four fields:

1. Current status
2. Named owner
3. Next action
4. Next-action date

If one of those fields is missing, the item is not fully managed. This simple control makes stalled work visible at each handoff from lead intake through final payment.