A basement plan page should identify finished space, unfinished space and proposed future layouts separately. Attach each label to the applicable drawing revision and scope record. Describe only what those records confirm. Give buyers a level-by-level legend so a future possibility never reads as work included in the current starting plan.
What does a basement plan page need to distinguish?
Begin with the version you are describing. A starting plan, an individual house under construction and a completed example need different introductions. Say which one the page represents before describing the basement. A buyer should not have to compare photographs to discover that the drawing shows another scope.
Keep finish status separate from design intent. A room label can describe a proposed arrangement without confirming finished work. Likewise, a photograph of one completed basement does not establish what another plan includes. Give the current scope its own plain statement beside the drawing.
Use the plan library guidance to establish the overall plan status. Then add basement-specific detail here. Keep the public name and revision consistent across the plan card, individual page and inquiry record. Do not combine different revisions into a single apparently complete illustration.
If records disagree, identify the unresolved item before publication. For example, a finish schedule may cover one area while a presentation drawing shades the whole level. Ask the responsible project reviewer to reconcile them. Until that happens, describe the unsupported finish scope as unconfirmed.
How can a status table explain the current scope?
Use a separate row for each basement area that has a different status. Avoid a single label such as “finished basement available” when the records distinguish several conditions. The table below is an editorial framework. Populate it from your approved records rather than treating its categories as construction findings.
| Status | What the page should explain | Evidence to confirm |
|---|---|---|
| Current finished scope | Name the areas and finishes explicitly included in the version shown. | Applicable scope record, finish description and drawing revision. |
| Current unfinished space | Identify the areas described as unfinished and the work the record confirms. | Current specification and corresponding plan labels. |
| Documented alternate layout | Explain how the alternate differs and how a buyer requests review. | Separate option record and its applicable revision. |
| Proposed future layout | Label the arrangement as an illustration outside the current included scope. | Approved public concept and a statement of its limits. |
| Unconfirmed | State the missing information without filling the gap with an assumption. | Named review responsibility and the unresolved question. |
Describe specific work only when its source supports the wording. “Unfinished” alone does not tell the buyer which components are present. If that detail is unknown, leave it unknown. Do not infer preparation for later work from a symbol or a room name.
Connect the table to the applicable standard specifications page. If the public specification covers several plan variants, identify the relevant variant. A general finish list should not override the narrower scope statement beside this basement drawing.
Keep comparisons on the same basis. If you publish area figures elsewhere, ask the responsible reviewer to confirm their definitions and source revisions. Do not calculate habitable area, bedroom counts or finished totals from a marketing image. Omit figures that your team cannot reconcile.
What belongs in a copyable level-by-level scope legend?
Use this worksheet for each level shown on the plan page. Copy the blank fields into your content brief. Keep the detailed source records internally, and publish the approved summary. This is a proposed writing tool, not a technical review method or an official document standard.
- Public plan name: [confirmed name]
- Page represents: [starting plan / project / completed example]
- Public drawing label: [confirmed label]
- Drawing revision and source date: [record reference]
- Scope record and effective date: [record reference]
- Level: [same wording as drawing]
- Area or zone: [same wording as drawing]
- Current finish status: [confirmed status / unconfirmed]
- Included work: [source-backed summary / unknown]
- Unfinished work boundary: [source-backed summary / unknown]
- Alternate layout: [separate record / none confirmed]
- Future illustration: [label and explicit exclusion / none]
- Photograph relationship: [version shown / not applicable]
- Unresolved buyer question: [question / none identified]
- Public wording reviewer: [responsible role]
- Publication rights confirmation: [record / unresolved]
- Next review trigger: [source revision or scope change]
Repeat the level and area fields when one level contains several statuses. Do not rely on a color wash to carry the distinction. Put the status in words beside the relevant drawing and in the text legend. Keep the labels consistent when the drawing becomes a downloadable file.
A source date and a website update date answer different questions. Record when the underlying plan was issued and when the website summary was checked. If a source date is missing, ask for it. Do not use the upload date as an invented drawing issue date.
Give each unknown a precise boundary. “Basement details pending” leaves too much unclear. “Finish scope for the area labeled storage remains unconfirmed” identifies the gap without suggesting that other areas are unresolved. Review the rest of the legend against its own evidence.
How should drawings and future layouts be presented?
Place the current drawing first. Put a proposed future arrangement in a separate, clearly labeled view. Repeat its status in the caption and accompanying text. Keep the current scope table visible near both views so readers can compare them without remembering a distant note.
For an information-rich image, W3C recommends a short text alternative and a longer description of its essential information. Its complex images tutorial describes ways to provide that explanation. Apply this to the drawing’s labels and relationships. It establishes no building-design approval.
Write the description from the approved public drawing. Name the level, labeled areas and status boundaries. If arrows show a connection, explain that connection in words. Keep speculative furniture, possible room uses and confirmed scope distinct. Do not add technical interpretations absent from the source.
Confirm publication rights before using a drawing. The U.S. Copyright Office distinguishes architectural works from technical drawings in Circular 41, pages 1 and 3. The circular does not establish permission for your plan. Request confirmation from the responsible rights holder or authorized party.
Keep project feasibility questions with the qualified project reviewer. A public diagram cannot settle bedroom status, moisture performance or permission for a later conversion. Phrase those as questions requiring review. Do not turn “future layout shown” into “ready to finish” without confirmed supporting scope.
What would a clear fictional plan-page excerpt say?
The following example is fictional and unnamed. It illustrates wording only. No dimensions, area totals, approval status, dates, pricing or construction performance have been supplied. The example does not describe a home offered by AgAI Labs or establish a builder’s standard scope.
Basement scope for the version shown: This fictional starting-plan record describes an unfinished basement area. No finished basement rooms are confirmed in the supplied scope summary. The current public drawing revision and issue date remain unconfirmed.
Future arrangement: A separate concept shows possible room divisions. Those divisions are outside the current included scope described here. The concept does not confirm future room use, bedroom status or permission to complete the work.
Photograph note: No matching project photograph has been supplied. Images from another completed house should not represent this version without a confirmed explanation of the differences.
Question for your plan discussion: Identify the basement area you mean and describe the activities you hope to accommodate. Ask which current records apply before discussing a different finish scope.
The example keeps unknowns visible instead of inventing a polished specification. In a real page, replace each statement only after reviewing its source. If the record confirms finished areas, name them individually. Retain a separate row for unfinished areas and any proposed future arrangement.
Use the same approach for other secondary spaces. The bonus room plan page guide explains present finish status, access and documented options. Keep the basement page focused on level-by-level scope rather than expanding it into a general room-use article.
How do you publish and maintain this distinction?
Review the page as a buyer would read it: heading, drawing, caption, scope table and photograph. Check every item against the same version. Then follow the inquiry path to confirm that the receiving team can identify the plan and basement area.
- Collect the current public drawing, scope record and any separate option records.
- Match each basement area to its confirmed finish status.
- Write the legend and record unresolved details.
- Separate future illustrations from the current plan view.
- Confirm drawing rights and review source-dependent wording.
- Check the published page whenever an underlying record changes.
Keep the editable page and approved public drawing in accounts you control. The Owned website stage describes that ownership. Assign a publishing role that can replace obsolete downloads when the source changes. Preserve the internal record of what changed and why.
Connect this page to the rest of the plan journey using the custom builder website page guide. The builder websites article collection provides the broader reading path. Review plan cards and project captions when the basement summary changes, since buyers may enter through either.
What else should a basement plan page explain?
Can a proposed basement room count as a bedroom on the page?
A basement plan page should not infer bedroom status from a proposed room label. Request confirmation from the qualified project reviewer before publishing a bedroom claim. Keep unsupported room status explicitly unconfirmed.
Should a finished project photo appear beside an unfinished starting plan?
A finished basement photograph needs a caption that identifies its relationship to the starting plan. Explain confirmed scope differences beside the image. If those differences are unknown, hold the photograph until the team can describe them accurately.
Does an unfinished basement promise a later conversion?
An unfinished basement label describes only the source-backed current status. It does not confirm later conversion permission, future use or construction performance. Route those questions to qualified project review rather than answering from the marketing drawing.
Which date should accompany the basement drawing?
A basement drawing should carry its confirmed source revision and issue date. Keep the website review date separate. If the source date is missing, identify that gap rather than substituting the website upload date.