# Publish standard specifications without creating buyer confusion

A builder standard specs page says what is included, what runs through an allowance, what is an option and what was a one-off selection, in the same words your spec sheet and selections tracker use. It labels every photo as standard, option or selection and names who maintains each section. It does not promise the same house on every lot.

## What should a standard specifications page accomplish?

The page gives a serious buyer a reliable view of how you organize scope before the detailed project review. It heads off the assumption that everything in the gallery, the model or the Parade house comes with every build.

Build it from the current spec sheet, the [allowance schedule](/glossary/allowance-schedule/) and the option records. Sales copy must not become a second version of the truth. If the office, the estimator and the field use different labels for the same item, settle that before you publish.

The [builder websites articles](/articles/builder-websites/) connect this page to the plan, process and project pages that rely on the same definitions.

### Which scope categories need distinct labels?

- **Standard scope:** work described in the current applicable specification.

- **Allowance:** a defined method for carrying a buyer decision that has not been fully selected.

- **Option:** an alternate feature or configuration reviewed through the builder’s stated process.

- **Project selection:** an approved choice recorded for a particular build.

- **Project-specific condition:** work driven by the plan, lot, review authority or another job condition.

Use these labels only if your documents use them. Do not invent cleaner terms that vanish once the buyer reaches preconstruction.

## How should the page organize the scope?

Follow the way buyers read the house and the way staff can keep it current. A room-by-room tour reads friendly and repeats the same flooring, trim and fixture rules five times. A structure by system is easier to update and can still point each item at the rooms it affects.

| Section | What to explain | Common source |
| --- | --- | --- |
| Site and foundation | Scope boundary and project-specific review | Specification and site criteria |
| Exterior assembly | Materials, selections and elevation dependencies | Plans and exterior schedule |
| Interior finish | Standard method, allowances and option path | Finish specification |
| Kitchen and bath | Cabinet, surface, fixture and appliance responsibilities | Allowance and selection records |
| Building systems | System scope and plan-dependent conditions | Technical specification |
| Closeout | Documentation, orientation, punch and aftercare handoff | Completion checklist |

Keep the summary readable and hand over the current document during the project. The website is not a substitute for the spec attached to a given contract.

## How do you explain allowances without misleading buyers?

For each public allowance category, show its boundary, its selection step and the record that confirms it. The [allowance schedule](/glossary/allowance-schedule/) glossary entry defines the term. This page organizes the public scope labels and plan variants buyers see beside images and specs.

1. **Name the category.** Use the same category name in the schedule, selection tracker and website.

2. **State the boundary.** Explain what the category addresses and what related work sits elsewhere.

3. **Identify the decision point.** Show when the buyer receives guidance and when approval is needed.

4. **Name the record.** State where the final selection and any approved effect are captured.

5. **Keep project figures private.** Direct buyers to the current project documents rather than publishing values that change by plan or scope.

The [builder process page](/articles/builder-websites/builder-website-process-page/) should say the same thing. Two descriptions of allowances create an expectation problem before the first selections meeting.

## How should photographs and options be labeled?

Every image has a job. If it shows a standard condition, confirm the condition is still current and applies on this page. If it shows an option or a project selection, label it beside the image, not in a note at the bottom.

Link important examples to their project pages. A cabinet layout, a trim detail or a porch connection means more when the buyer can see the plan and the project behind it. The [project gallery page article](/articles/builder-websites/project-gallery-pages-that-sell/) covers captions.

### What should you avoid publishing?

Skip supplier promises you do not control, product details nobody maintains and words like premium or high quality with no definition a buyer can inspect. Do not show a finish as standard because it was in the last house. Check it against the current spec and label any project selection next to its photo.

### How does the specifications page connect to plans?

Plan pages and the specs page point at each other. A plan changes exterior materials, structural options, building systems and what gets selected. The [plan library article](/articles/builder-websites/plan-library-pages/) shows how to label design status and revision boundaries.

When specs vary by plan series, community or project type, give each variant its own scope. Do not merge several standards into one attractive list. A buyer should be able to tell which spec path applies without assuming the longest list is theirs.

## Who maintains the page after publication?

Assign ownership by section. Preconstruction owns allowance wording, design owns finish categories, the superintendent owns construction methods, warranty owns closeout language. One publishing owner coordinates approved changes and records the effective revision.

Review the page when the spec changes, when an option becomes standard, when a supplier change alters the public description or when the selections workflow changes. The [Operating profile stage](/process/operating-profile/) records the source system and its owners.

## Questions about builder specs pages

### Should we publish the full specification document?

Your builder website can summarize the approved specification source at a level the team can maintain. Direct project-specific scope decisions to the current controlled document.

### Can we show brand or product names?

Use generic product categories on the public specifications page. Keep supplier and brand details in approved project documents, and explain how the team confirms substitutions or scope changes.

### How often should specifications be reviewed?

Review public builder specifications whenever the source specification, allowance schedule, option record, selection workflow or closeout process changes. Assign a recurring check as a backstop.

### What if standards differ across plans?

When builder standards differ by plan, label each specification variant and connect the plan to its applicable scope. Avoid combining variants into one apparent inclusion list.