# Show what a main-level primary plan means for daily living.

A main-level primary plan page should explain where the primary suite sits and how it connects to everyday rooms. Show arrival, laundry, living spaces and guest routes. Separate confirmed room relationships from optional layouts and unknown access details. This AgAI Labs guide gives you a writing worksheet for that review.

## What does a main-level primary label tell a buyer?

Use the label to identify the primary suite's level in the specific plan you publish. Then explain the surrounding rooms. A bedroom location alone leaves the buyer guessing about the rest of a normal day. Start with the route between arrival, the kitchen, the primary suite and laundry.

Keep three descriptions separate. Primary-suite location identifies a room relationship. A single-story description addresses the home's overall arrangement. Verified access features describe particular conditions that need their own evidence. Do not turn the first description into the other two because the plan looks convenient.

A plan can place the primary suite downstairs while showing additional rooms upstairs. Your page should say what those rooms contain. If the laundry location is unconfirmed, state that beside the room summary. Avoid calling the whole home suitable for living on one level until the documented arrangement supports that description.

Keep the broader comparison in your [plan library](/articles/builder-websites/plan-library-pages/). This individual page should explain one arrangement in enough detail for a buyer to ask a specific question. Use the same plan name and status across the library card, drawing caption and page heading.

Use the [builder websites library](/articles/builder-websites/) to connect this page with the surrounding publishing guidance.

## Which room routes belong in the content matrix?

Trace a routine through the approved public drawing before drafting the paragraph. Name the starting space, destination and rooms along the route. Record what the drawing establishes and what needs another source. The following matrix is a proposed editorial worksheet, not a technical assessment of a home.

| Routine | Question to answer | Evidence to request | Boundary to publish |
| --- | --- | --- | --- |
| Arrival | How does the arrival space connect to the primary suite? | Public plan showing the relevant entry and connecting rooms | Identify the entry shown; leave thresholds and site conditions unconfirmed. |
| Sleeping | What rooms sit beside the suite? | Current room labels and adjoining spaces | Describe adjacency without promising quiet or acoustic separation. |
| Laundry | Where does laundry happen relative to the suite? | Verified laundry location for the displayed revision | Separate the shown location from an optional alternative. |
| Daily living | What connects the bedroom, kitchen and living room? | Confirmed circulation shown in the public drawing | Describe the route without inventing clearances or distances. |
| Guest separation | Where do guests sleep and use shared rooms? | Bedroom, bath and shared-space relationships | Name which areas are shared and which remain unresolved. |

Write each row as a complete answer before combining rows into prose. “Laundry nearby” is too vague for the source record. “The current drawing places laundry off the hall between the kitchen and primary suite” is useful when that relationship is shown.

Ask the reviewer to follow the route from each entry you describe. A front-door route and a garage route can raise different questions. Do not substitute one for the other. If the public drawing omits the garage connection, leave that route open for discussion.

Give guest separation the same care. Bedrooms on another level do not explain where visitors gather, wash or store belongings. Describe only the relationships your drawing supports. For a separate household-use discussion, link to the [multigenerational plan-page guide](/articles/builder-websites/multigenerational-home-plan-page-content/).

## How do you describe the drawing without hiding its limits?

Place a written room-route explanation near the plan image. Explain the relationships a reader needs to understand, including which spaces sit on another level. Give the image a short identifying description. Avoid packing the full tour into a small caption or a string of room names.

The [W3C complex-images tutorial](https://www.w3.org/WAI/tutorials/images/complex/) describes short and longer text alternatives for complex images. Its long-description guidance recommends making essential image information available in text. Apply that principle to the public plan explanation, with a clear connection between the drawing and its description.

For example, begin with the depicted level and the plan revision. Continue through the arrival and living spaces toward the primary suite. State where the route depends on another sheet. This is a description of the published image, not a claim about the home's physical accessibility.

Keep an optional arrangement visibly separate from the starting drawing. If an option moves laundry, give it its own approved description. A visitor should not need to inspect a small footnote to discover that the paragraph and image describe different layouts.

## What would an honest public plan-page excerpt look like?

The following excerpt is fictional and unnamed. It illustrates editorial wording only. It describes no actual plan, builder, project or available offering. Its room relationships are invented for this example, and its uncertainty labels are part of the writing exercise.

**Plan status: illustrative layout under discussion.** The example drawing places the primary suite on the main level. The kitchen and living room share that level. Additional sleeping rooms appear upstairs. The drawing does not establish the entry conditions for a particular lot.

**Everyday route:** The illustrated front entry opens to a hall leading toward the living room. The kitchen connects to that shared living area. A separate hall leads to the primary suite. Confirm the route from any garage with the applicable drawing before comparing arrival patterns.

**Laundry:** The example starting layout shows laundry on the main level. An optional laundry arrangement is proposed but has not been confirmed for publication. Treat that alternative as a question for plan review, rather than an included feature.

**Guest use:** The example puts guest sleeping rooms upstairs while retaining shared living spaces downstairs. Bathroom relationships need confirmation. Entry thresholds, clearances, lot fit and any access requirements remain unresolved.

Notice how the excerpt gives the reader something concrete without filling every gap. It names the shown rooms and separates a proposal from a confirmed layout. Replace every fictional relationship with source-backed wording before using this structure on a real page.

Use photographs only when their connection to the displayed plan is verified. A finished room from a modified house can imply a feature absent from the starting plan. The [project gallery guide](/articles/builder-websites/project-gallery-pages-that-sell/) explains how scope labels and captions keep that connection clear.

## How should you verify the page before publication?

Use one review sequence for the drawing, narrative and inquiry context. Keep the approval record outside the public page. Publish the revision and status information a buyer needs, while retaining the source trail for the next editor.

1. **Identify the plan.** Record the exact source filename, revision and person responsible for confirming the layout.

2. **Confirm publication permission.** Obtain approval for the particular public drawing and any accompanying photographs or excerpts.

3. **Check the room routes.** Compare every matrix row with the same approved revision.

4. **Separate alternatives.** Identify each optional arrangement and the source that supports its public description.

5. **Check lot context.** Ask the responsible project team which entry, orientation or site statements can appear publicly.

6. **Read the assembled page.** Confirm that image captions, text and linked project examples describe the intended arrangement.

Lot context needs its own answer. A public starting plan does not settle the arrival conditions of an unnamed future site. If no lot has been reviewed, say the page describes a starting layout and leaves site-specific questions for project review.

Publication permission also needs a specific record. Do not infer permission from possession of a drawing file or an image on another page. Ask for the approved public version. If that version is unavailable, hold the drawing and write only the summary your sources support.

The [Owned website stage](/process/owned-website/) provides the broader site context for plan pages. Keep the plan source and its approval record available to whoever maintains your public copy. A changed room label should trigger a check of the associated description.

## What can you copy into a plan-page content brief?

Use this brief to gather the source material before asking someone to write the page. Each blank is a request for evidence. An empty field stays unresolved until the responsible reviewer supplies an answer.

Plan name and public status:

Approved source file and revision:

Public drawing permission record:

Primary-suite level:

Other occupied levels and their rooms:

Front-entry route to primary suite:

Garage-entry route, if documented:

Laundry location in this revision:

Kitchen and daily-living connections:

Guest sleeping, bath and shared-space relationships:

Optional layouts with separate source records:

Lot-specific facts approved for publication:

Unknown access or entry details:

Approved project images and scope labels:

Responsible layout reviewer:

Publishing owner and next review trigger:

After completing the brief, draft the opening answer from confirmed fields only. Put optional features beside their labels. Write an explicit unresolved sentence where a missing fact could change the reader's understanding. Keep the remaining internal questions in the review record.

Read the draft alongside another plan in your library. Check whether both pages use “main level” consistently and explain additional levels clearly. Keep the wider page set aligned with the [custom builder website pages guide](/guides/custom-builder-website-pages/).

Choose a maintenance trigger tied to the source material. A revised plan, a changed option or withdrawn image permission should reopen the relevant section. Do not preserve an old claim because it appeared in an earlier approved draft.

## What else should a main-level primary page answer?

### Does a main-level primary mean the house is single-story?

A main-level primary label identifies the primary suite's level. Describe other levels separately, using the current plan. Do not label the whole house single-story when the published layout includes additional occupied levels.

### Can the page claim the home is accessible?

A main-level primary page should leave physical access claims unresolved without feature-specific evidence and qualified project review. A bedroom on the main level does not establish entry conditions, dimensions or suitability for a particular person's needs.

### How should an optional laundry location appear?

An optional laundry location belongs beside a clear option label and its supporting drawing. Keep the starting layout's laundry description separate. Leave an unconfirmed alternative as a question for plan review.

### What should happen when the public plan revision changes?

A changed public plan revision should prompt review of room-route text, captions, option labels and linked project examples. Confirm that all public descriptions refer to the intended revision before publishing the replacement.