# Order your builder follow-up queue with recorded evidence

Builder lead scoring orders a daily work queue from recorded next actions, agreed response points and missing reviews. It shows the reason each inquiry needs attention and the evidence behind it. Keep qualification and pipeline stages separate. A queue position assigns work. It does not establish site feasibility or accept a project.

## Why do hot, warm and cold labels fail custom builders?

Those labels compress a complicated project into one salesperson's impression. A buyer may be ready to act and still need a lot. Another may own a site with constraints that need careful review. A prospect asking detailed allowance questions may be well informed, or may be comparing processes before picking a location. None of those conditions fits inside a temperature.

Useful scoring starts with your recorded next actions. It surfaces a promised reply that is due, a document waiting for review, an overdue callback. Qualification decides fit. The queue records which approved task needs attention first.

The scoring framework connects to your [leads and CRM records](/articles/leads-and-crm/). It does not live in a private spreadsheet with different definitions.

### What is scoring allowed to do?

Order a review queue, flag missing qualification and surface a meaningful change, such as a lot going under contract or a plan set arriving. It can also catch a record with strong fit and no next action. It cannot approve a site, confirm a plan, set allowances, reserve a start window or decide contract readiness.

## Which conditions should a builder score?

Conditions tied to your [operating profile](/glossary/operating-profile/). The same inquiry fits one builder and not another because service area, build type, lot pipeline, design model and current field capacity differ. Write the criteria before you assign labels.

| Condition | Evidence to record | What it changes |
| --- | --- | --- |
| Service fit | Verified project location and your current working area | Whether a fit review continues |
| Lot condition | Owned, under contract, identified, searching or builder-controlled | Shapes site and timing questions |
| Plan condition | Builder plan, outside plan, concept, full set or no direction yet | Sets the design conversation |
| Project type | One-off custom, infill, teardown, spec interest or another defined lane | Tests operating fit |
| Decision access | Known decision makers and an agreed next conversation | Prevents one-sided follow-up |
| Requested action | Specific request: plan review, lot conversation, process meeting | Sets urgency and ownership |
| Activity quality | Meaningful reply, document supplied, meeting held or verified pause | Shows movement without counting empty clicks |

Do not score personal characteristics, protected information, writing style, neighborhood assumptions or inferred wealth. Record only what you need for a legitimate project-fit and follow-up decision. Check data-use and automated-routing requirements with your qualified advisers before you add a field or a rule.

## How should you order the daily follow-up queue?

Start with the next action recorded during qualification. Order work by agreed response points, overdue tasks and unresolved [builder reviews](/guides/builder-reviews-program/). Show why each item appears. Keep records with missing evidence in a visible verification queue instead of assigning an invented readiness score.

1. **Read the recorded fit outcome.** Use the qualification result and the open questions your team already checked. Do not rebuild qualification inside a priority score.

2. **Name priority reasons.** Promised response due, buyer document received, overdue callback, review blocked, missing intake facts.

3. **Define queue evidence.** Record the task, the agreed response point, the evidence source and the person who checked it.

4. **Attach the next action.** Every queue item gets an owner and a concrete task. Its pipeline stage stays where it is.

5. **Keep unknowns visible.** Missing lot status stays missing. It does not become a negative assumption.

6. **Test past records.** Run the model against a varied set of inquiries and look for where it produces an unreasonable order.

7. **Review changes.** When your lot pipeline, service area, plan library or capacity changes, update the model and the runbook together.

The intake questions behind the model are in [qualifying custom home leads](/articles/leads-and-crm/qualifying-custom-home-leads/). Keep the first form short and let a person fill in the nuanced conditions during the conversation.

## How should scoring interact with the sales pipeline?

Score and stage answer different questions. A queue position and its priority reason identify the next work. A pipeline stage records the current observable sales condition. A buyer can be high priority and still in fit review because a lot document needs attention today. Another can be far along in conversation and paused by a site decision.

Do not let score changes move records into plan review, preconstruction or contract-related stages without the required evidence. Use the stage definitions in [builder sales pipeline stages](/articles/leads-and-crm/builder-sales-pipeline-stages/), then configure the system you own through the [Lead attribution stage](/process/lead-attribution/).

### How should long-lead buyers be handled?

A distant start does not make a buyer unimportant. If the project and the geography fit but land, design or timing is unresolved, record the missing condition and put the record in a reviewed nurture path. The next action might be a lot-readiness guide, a plan-process explanation or a scheduled check-in, not repeated sales pressure.

## Where can automation help, and where should it stop?

Claude and Codex agents on our side extract submitted facts, flag missing fields, suggest a queue position and explain which recorded conditions drove the suggestion. A person reviews the source material and approves any change. No agent infers capacity, finances, site feasibility, motivation or personal circumstances from tone or browsing behavior.

Test the model for silent drift. Field definitions change, forms get revised and teams start using labels differently. Review records that were prioritized, deferred and marked nonfit. Look for missing facts, inconsistent decisions and patterns that might exclude viable projects for reasons unrelated to the [operating profile](/glossary/operating-profile/).

The [builder CRM guide](/guides/builder-crm/) covers ownership, permissions, exports and workflow testing. Keep the priority reason beside its source note so the assigned person can check it before acting.

## What should change a lead's priority?

### Should website activity increase a lead score?

Website activity affects a builder work queue only when its meaning has been reviewed. Page views alone do not establish project readiness, lot control or service fit.

### Can a low score close a lead automatically?

A low lead score should not close a builder inquiry on its own. Have a person review missing information, document the fit reason and choose an appropriate response.

### How often should scoring criteria change?

Review lead scoring criteria when the operating profile changes and during record audits. Update queue definitions, automation and the runbook together so priority reasons stay traceable.

### Should referral leads get extra priority?

A referral can need prompt relationship handling without proving project readiness. Set its queue position from verified project facts, the promised response and the next action due.