# Write builder website copy from the documents that run the job

Good builder website copy comes from the documents that run the job: the plan set, the spec sheet, the [allowance schedule](/glossary/allowance-schedule/), the selections tracker, project notes, the warranty procedure and your lot criteria. Turn those facts into buyer answers. Keep standard work separate from options. Send every claim back to the person who owns the document.

## Why does most builder copy sound interchangeable?

Because it was written from a brand questionnaire. Quality, craftsmanship and communication fit any builder in the Triangle. They do not tell a lot owner what you review, how a plan changes, when a selection locks or what happens when the soils report changes the scope.

Useful copy starts where the decisions happen. Read the plan notes, the spec categories, the [allowance schedule](/glossary/allowance-schedule/), the preconstruction checklist, the selections tracker, the draw letter and the warranty intake form. Interview the people who use them. The site does not publish those documents, but every explanation should trace back to one.

The [builder websites articles](/articles/builder-websites/) give each answer a page to live on.

### Replace adjectives with operating detail

Instead of “personal process,” say where the buyer makes decisions and who records them. Instead of “flexible plans,” say which requests get design review and when. Instead of “responsive warranty,” show the intake path and what the service team needs to review an item.

## Which source documents should the writer use?

Build a claim-to-source table before you draft. For each public sentence, record the source revision and the approving role. The process page gets its own sequence check; this table checks individual statements across every page type.

| Source | Website answer it supports | Reviewer |
| --- | --- | --- |
| Plan set and plan register | Design identity, room relationships and revision boundaries | Design or plan owner |
| Specification source | Standard scope, categories and project distinctions | Estimating or operations |
| Allowance schedule | How placeholder amounts and selections are handled | Estimating and selections |
| Preconstruction checklist | What must be resolved before field work begins | Operations |
| Project notes | Site conditions, plan changes and photographed details | Field and design leads |
| Warranty procedure | How service items are submitted, reviewed and tracked | Warranty owner |

When two sources disagree, stop the draft there. The conflict usually means an outdated sheet, an exception nobody wrote down or a gap between office language and field practice. The website cannot pick which version governs.

## How should the page answer a buyer's question?

Make the question the heading. Answer it in the first sentence. Then give the conditions, the distinctions and the next question. A buyer can scan it, and a search or answer engine gets one clean passage to quote.

1. **State the direct answer.** Say what the builder does in plain language.

2. **Name the inputs.** Identify the lot, plan, selection or record needed to make the decision.

3. **Explain the gate.** Show who reviews the input and what makes the step ready to move.

4. **Separate the states.** Distinguish standard, optional, selected, approved, ordered and installed where those labels matter.

5. **Handle exceptions honestly.** Say when a project-specific review is required without promising the outcome.

6. **Link the next answer.** Move the reader to a relevant plan, project, process or intake page.

The article on [builder website process pages](/articles/builder-websites/builder-website-process-page/) applies this method to the full build sequence. The broader [guide to writing down the build process](/guides/writing-down-your-build-process/) explains how to capture the source before simplifying it for buyers.

## How do you write about plans, projects and specifications accurately?

Label what the buyer is looking at. A plan is a repeatable offering, a starting point or a completed example. A photographed feature is standard, optional, buyer selected or one-off. A project is active, available, completed or sold. Without the label, a buyer reads the photo as a promise.

### Keep claims beside their qualifications

If an elevation includes an option, say so next to the image. If a project used a modified plan, say so on the project page. If a spec varies by contract or community, do not bury that on another page.

The [standard specs page article](/articles/builder-websites/standard-specs-page/) goes deeper on this. Compare each scope statement with the plan or spec revision in force before you approve the wording.

## How should drafting and review work?

Assign reviewers by subject. Sales reads fit language and buyer questions. Operations reads sequence and gates. Design reads plan and selection language. The superintendent reads construction descriptions. The warranty owner reads service intake. One editor then checks that the pages agree with each other.

Our agents sort the approved sources, draft sections, compare plan names, flag inconsistent labels and check internal links. People set the page purpose, settle conflicts and approve every output. No agent invents a missing project fact or decides which document is current.

That review discipline is part of the [Owned website stage](/process/owned-website/). You keep the copy, the source files and the publishing system, with the notes that make the next update possible.

After approval, read the page beside its source and mark anything the source does not support. Then read it as a buyer arriving with a lot, a rough plan idea or a Parade conversation. Note what is missing and replace office shorthand with the document or decision it stands for.

## Questions about writing builder website copy

### Can the writer interview us instead of reading our documents?

Builder website writers should combine interviews with source documents. Interviews explain practice; documents expose labels, decision gates and conflicting versions that memory may miss.

### Should website copy include every process detail?

Builder website copy should explain fit, responsibilities and next steps. Keep controlled construction instructions and contract records in the systems used to manage each project.

### Who approves claims about photographed projects?

A reviewer with direct project knowledge should approve photographed-project claims. Check the plan relationship, site context, selections and current project status before publishing the copy.

### Can AI agents write the first draft?

AI agents can draft builder website copy from approved sources and a defined page brief. People must check accuracy, privacy, operating meaning and final wording before publication.