A builder says which projects fall outside its process by naming project conditions, never by describing people. Clear exclusions cover location, lot control, plan path, decision readiness, scope and communication expectations. The best wording lets a reader compare their project to the boundary, gives the operating reason and offers the right next step when one exists.
Why publish exclusions at all?
Silence does not keep poor-fit work out of the pipeline. It moves the conflict into a longer phone call, a design meeting or a proposal the team should never have written. By then staff have spent hours interpreting an inquiry the first page could have settled.
An exclusion earns its place when it protects a real operating boundary. One builder works only in communities where the team can support field supervision. Another takes owned-lot projects only after a defined feasibility review. A plan-focused operation adapts its library and does not reproduce an outside plan. These are not marketing postures. They are conditions for doing sound work.
Exclusions show buyers the capacity, process and limits your team has reviewed. The positioning library treats that clarity as part of a complete fit statement, not a disclaimer in small type.
Protect the team and the buyer
A poor fit costs both sides. The office keeps chasing missing information. The field gets late revisions. The buyer expects open-ended choices after release dates have passed. A clear boundary gives both parties an earlier chance to stop or redirect.
Which boundaries are worth stating?
The ones you can explain, observe and apply the same way every time. Do not turn a past frustration into a rule aimed at a type of person. A boundary describes a project, a lot, a budget band or a scope. It never describes who the buyer is. Review the contract path, the plan workflow, the service area, the lot pipeline, the selection schedule and field capacity. Every boundary connects to one of those sources.
| Boundary | Weak wording | Useful wording |
|---|---|---|
| Service area | We only take select projects | We build where our field team can keep the stated supervision and trade coverage |
| Plan path | We do not use outside ideas | Our process starts with our plan library and a documented adaptation review |
| Lot status | You must have everything ready | Owned-lot work begins after access, utilities and available site information can be reviewed |
| Selections | Indecisive buyers are not a fit | Selections are approved by the dates tied to ordering and field sequence |
| Scope | No small jobs | We accept projects that use our full design and construction process |
| Communication | No difficult clients | Questions and approvals are recorded through the project communication path |
Before you publish, have staff apply each proposed boundary to a recent inquiry. Record any wording that produces two different acceptance decisions. Questions from buyer agents go to your listing agent. Name that contact on the communication page, in the same plain terms, so an agent knows who answers for a listed house.
How do you write a firm boundary without sounding hostile?
Lead with what the process is built to support. Then state the condition it cannot support and why that matters. Keep it factual. Do not apologize for an operating choice that protects supervision, document control or decision sequence.
- Name the supported path. The lot, plan, scope or decision condition the builder handles well.
- State the boundary. Direct language about the work that falls outside that path.
- Give the operating reason. Field coverage, plan control, trade coordination or another real constraint.
- Clarify exceptions. If one exists, who reviews it and what information it needs.
- Offer a next step. A site package, a plan review or another useful input when the issue can be resolved.
- Test the wording. Sales and production apply it to real inquiries and compare their decisions.
Keep the reason short in public copy. The internal positioning brief carries the detail, including the evidence and the approving role. The Positioning stage records both project fit and exclusions so the website, the forms and the sales team run on the same rules.
Where do the exclusions appear?
Wherever they answer a real buyer question. Service area goes on location and inquiry pages. Plan-path boundaries go beside the plan library or the design process. Selection expectations go on the build process page. Lot requirements go on lot and feasibility pages.
Use the form as a second explanation
The intake form collects the facts behind the boundary: lot status, location, plan status, intended project path and decision authority. Do not ask buyers to declare themselves a fit, and do not ask about anything other than the project. Their answers give the team enough context to review it.
Confirmation messages keep received and accepted apart. Receiving a plan set does not mean you approved the plan path. Receiving an address does not mean the lot is feasible. Plain status language keeps the form from making a promise.
How does the team handle exceptions?
As decisions, not quiet workarounds. Name the role that can approve one, the evidence required and the reason it stays compatible with operations. If the team keeps approving the same exception, the stated boundary is incomplete.
Track exception categories without storing personal detail you do not need. A repeated location exception means the service area needs review. A repeated plan exception means a second legitimate design path exists. A stream of requests for work the company never does means the website is sending the wrong signal.
Keep exclusions aligned with project fit
The article on defining project fit is the positive side of the same decision. The article on competing with production builders explains process differences without attacking another delivery model. For a deeper source on buyer-facing process language, use the build process guide.
AI agents compare approved boundary language across pages, forms and follow-up drafts and flag conflicts for review. People approve the rule, decide exceptions and confirm the published wording still matches field capacity. An agent never declines a project from a public profile alone.
What else should fit boundaries settle?
Will exclusions drive away good buyers?
Not when they state project conditions and operating reasons. Review the questions that come in to check whether readers understand the published project language.
Should we list every project we decline?
No. Publish the boundaries that help buyers assess fit. Detailed decline reasons and exception guidance stay in the internal positioning brief.
Can we say we are not the cheapest option?
You can, and it tells the buyer almost nothing about scope. Describe your process and project requirements instead.
What if our boundaries change with capacity?
Review the affected boundaries, pages and forms. Record the revision and give sales and production the same current version.