EGRET · FLORIDA CONTRACTOR INTELLIGENCE

Florida Contractor Estimate Follow-Up Workflow: Assign Ownership and Set the Next Step

Published November 4, 2026

A sent estimate should never sit without an owner and a defined next action. Use this workflow to keep follow-up consistent across salespeople, estimators, project managers, and office staff.

1. Assign one estimate owner

Choose one person who is responsible for moving the estimate toward a clear outcome. Avoid shared ownership, which can make it unclear who should contact the customer.

Record:

  • Estimate owner
  • Customer and project
  • Estimate amount
  • Date sent
  • Current status
  • Next action
  • Next-action date
  • Preferred contact method
  • Last customer interaction

The owner does not need to complete every task personally. The owner is responsible for making sure the next task is assigned and completed.

2. Set the next step when the estimate is sent

Before closing the estimate record, select one concrete next action:

  • Confirm the customer received the estimate
  • Answer scope questions
  • Review options or alternates
  • Request a decision
  • Prepare a requested revision
  • Record approval
  • Record rejection and the reason
  • Place the opportunity on hold at the customer’s request

Avoid vague notes such as “follow up later.” A useful next step identifies the action, owner, and date.

Example:

  • Weak: Follow up with customer
  • Strong: Jordan to call the customer on the selected date to confirm receipt and ask whether any scope items need clarification

3. Verify the estimate before contacting the customer

The owner should review the record before each follow-up.

Pre-contact checklist

  • Confirm the correct estimate version was sent
  • Review the included scope
  • Review exclusions, options, and alternates
  • Check previous calls, messages, and notes
  • Identify unanswered customer questions
  • Confirm whether a revision is already pending
  • Decide what outcome to request from the conversation

This prevents the customer from receiving a generic message when the record already shows a specific concern or request.

4. Match the follow-up to the estimate’s condition

If receipt has not been confirmed

Ask whether the customer received and could open the estimate. If not, verify the contact information and resend the correct version. Record the result and set the next action.

If the customer is reviewing the estimate

Ask whether the scope is clear and whether any decision-maker needs additional information. Do not create a revision unless the customer identifies a requested change.

If the customer has questions

Capture each question separately. Assign technical, pricing, or scheduling questions to the appropriate team member, while keeping one person as the estimate owner.

If the customer requests changes

Document the requested changes before editing the estimate. Mark the current version as awaiting revision, assign the revision, and identify who must review it before it is resent.

If the customer is ready to proceed

Record the approval and hand off the project using the company’s internal process. Include the approved estimate version, customer commitments, open questions, and relevant communication notes.

If the customer declines

Record the rejection and the customer’s stated reason without guessing. Useful categories can include scope, price, timing, selected another contractor, project postponed, or no reason provided.

If the customer does not respond

Record the contact attempt and select another specific action. If the team decides to stop active follow-up, change the internal status rather than leaving the estimate in an active queue indefinitely.

5. Use a simple decision tree

After every contact attempt, ask:

  1. Was the customer reached?
  • If no, record the attempt and assign the next action.
  • If yes, continue to the next question.
  1. Does the customer need clarification?
  • If yes, assign the question and define who will respond.
  • If no, continue.
  1. Did the customer request a change?
  • If yes, document the change and assign the revision.
  • If no, continue.
  1. Has the customer made a decision?
  • If approved, record approval and initiate the internal handoff.
  • If rejected, record rejection and the stated reason.
  • If undecided, record the obstacle and set the next action.

6. Standardize follow-up notes

Use a consistent note format so another team member can understand the situation without reading the entire history.

Note template

  • Contact method:
  • Person contacted:
  • Outcome:
  • Customer questions or objections:
  • Information promised:
  • Assigned team member:
  • Next action:
  • Next-action owner:
  • Next-action date:

7. Review open estimates as a team

During an estimate review, focus on records that lack ownership, a next action, or a clear status.

Review checklist

  • Does every sent estimate have one owner?
  • Does every active estimate have a specific next action?
  • Is the next-action date recorded?
  • Are customer questions assigned?
  • Are requested revisions separated from the original version?
  • Are approved and rejected estimates marked accordingly?
  • Are inactive opportunities removed from the active follow-up queue?
  • Are handoff notes complete for approved work?

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.

8. Define completion

Estimate follow-up is complete when the record has one of these outcomes:

  • Approved and handed off
  • Rejected with the stated reason recorded
  • Placed on hold with the customer’s situation documented
  • Closed from active follow-up under the company’s internal process

The core rule is simple: every sent estimate needs one accountable owner, one current status, and one explicit next step.