# Explain the documented crawlspace assembly and its limits.

A sealed crawlspace project page should describe the assembly supported by current project records and explain what remains unknown. Confirm components, conditioning evidence and review scope separately. Use the source's terminology without treating sealed, insulated and conditioned as interchangeable. Keep site suitability, local requirements and maintenance responsibility with the responsible project reviewers.

## What does the crawlspace terminology establish?

Begin with the words in the project's current source. If the drawing says “sealed crawlspace,” preserve that wording until its responsible reviewer explains the intended scope. Do not add “conditioned” because it sounds more complete. A public page should help buyers understand the documented assembly without expanding the source.

The [PNNL Building America Solution Center guide to unvented, insulated crawlspaces](https://basc.pnnl.gov/resource-guides/unvented-insulated-crawlspaces) discusses vapor-retarder coverage, perimeter insulation, air sealing, access details and conditioning or drying provisions. Its Scope, Description and Ensuring Success sections provide questions for project review. They do not establish which components exist in your home.

Use those subjects as separate evidence requests. Ask where the current record describes each component and whether field evidence confirms it. An assembly label can begin that conversation. It cannot answer every component question on its own.

The guide also calls for local-authority checks and discusses project conditions affecting the work. Keep local requirements and site suitability unresolved until responsible project review addresses them. Do not convert a general resource into a current permit conclusion or a statement that a particular site suits the assembly.

Within the [positioning library](/articles/positioning/), this article covers the public description of crawlspace scope. It does not provide installation instructions. Your buyer-facing page can explain documented features without telling a reader how to design, alter or inspect a foundation system.

Keep the project reference visible in the writing brief. A documented feature in one home remains a feature of that home. Before describing a builder-wide standard, obtain sources covering that wider promise and confirm how exceptions will be explained.

## Which records should support the assembly description?

Separate the plan specification, field evidence, review record and maintenance source. These are proposed editorial categories. They help a writer see what a sentence depends on. They do not replace the technical records or establish that a particular review is sufficient.

| Record | Question for the responsible reviewer | Public wording limit |
| --- | --- | --- |
| Plan specification | Which assembly and revision does the design describe? | Identify the specified approach without presenting intent as verified completion |
| Field evidence | Which components and locations does this record confirm? | Describe the documented work without extending a photograph to unseen areas |
| Review record | What did the review cover, and what remains excluded? | State the reviewed scope without implying a broader approval |
| Service or maintenance source | Which current document assigns upkeep and service responsibility? | Explain confirmed responsibilities without inventing intervals or warranty terms |

A liner photograph documents a visible area at a particular moment. Ask what other records connect that view to the assembly description. The photograph alone leaves conditioning, concealed details and review scope unresolved. Do not label it proof of a complete system.

For insulation, request the applicable specification and the field record supporting the proposed sentence. For conditioning, request the responsible system description and its verification record. Keep equipment ratings, dimensions and installed extent unknown until the actual project documents establish them.

When records conflict, stop the dependent sentence. A field note might describe a change that an earlier plan does not contain. Ask the responsible reviewer which source controls the public description. Keep the explanation of that decision in the private brief.

Use the [builder proof-point register](/articles/positioning/builder-proof-points/) to connect the approved sentence to its sources. Keep any energy statement under a separate review. The [energy performance evidence guide](/articles/positioning/energy-performance-builder-proof-content/) explains why an assembly description does not automatically support a measured performance claim.

Ask about maintenance before writing that the assembly is easy to own. Identify the actual [handoff](/process/handoff/) document and the role responsible for explaining it. Leave service arrangements unknown when no source establishes them. Do not invent a maintenance schedule to make the project page feel finished.

## How would a fictional crawlspace excerpt handle unknowns?

Consider an unnamed, entirely fictional project folder. Its imaginary plan note uses “sealed crawlspace.” A photograph shows part of a liner. No conditioning record, completed assembly review or maintenance assignment accompanies it. Dimensions, insulation details and installed scope remain unknown. The example establishes no actual construction work.

The draft page says, “A fully conditioned crawlspace stays dry and lowers your bills.” Hold that sentence. The fictional evidence does not confirm conditioning or support either outcome. Adding a limitation at the bottom would leave the headline's unsupported message intact.

**Fictional public excerpt:** “The current plan note identifies a sealed crawlspace for this project. The available photograph shows part of the liner. Conditioning, the complete installed assembly and maintenance responsibility have not been verified for this page.” This is an editing example, not approved wording for an actual home.

A real project page may be more useful after the missing records arrive. You can hold the feature paragraph while publishing other verified project information. The private brief should identify the unanswered questions so the next writer does not rebuild the claim from the same photograph.

The [FTC truth-in-advertising overview](https://www.ftc.gov/news-events/topics/truth-advertising) describes truthful, nonmisleading advertising and evidence when appropriate. It does not approve a crawlspace claim or establish a technical result. Keep the proposed wording tied to the actual source and its reviewed limits.

If you later add an informative image, follow the [W3C informative-images guidance](https://www.w3.org/WAI/tutorials/images/informative/) for text alternatives that reflect its purpose in context. Example 2 concerns an image supplementing adjacent text. Image presentation guidance does not validate construction scope or grant publication rights.

Review the photograph's proposed caption with its visible content. Keep unseen components out of the description unless a separate source supports them. Record image permission independently. This article supplies no project photograph, drawing or permission for actual reuse.

## What belongs in a crawlspace scope brief?

Copy the worksheet below into a project content assignment. It is an original editorial proposal for source organization. It is not a design checklist, code document or maintenance instruction. Complete the fields from project records and responsible review rather than general expectations about this type of foundation.

```
Crawlspace scope brief
Source terminology:
Component evidence:
Conditioning evidence:
Review limitation:
Maintenance source:
Public wording approval:

Public project label:
Private source and revision:
Specified versus verified scope:
Unresolved component questions:
Approved public excerpt:
Qualified project reviewer:
Permission for source excerpts:
Review trigger:
```

Preserve the exact source terminology in the first field. In component evidence, list the document or field record supporting each feature you plan to name. If only part of the work is documented, describe that boundary. A broad “confirmed” label conceals the question the writer still needs answered.

Keep conditioning evidence separate even when the plan note uses a compound label. Ask which record supports that part of the description. In review limitation, record what the reviewer examined and what they did not address. Do not translate a narrow review into a general assurance.

1. **Record source terminology.** Copy the assembly label from the current project document.

2. **Match component evidence.** Identify the record supporting each proposed feature description.

3. **Check conditioning evidence.** Ask the responsible professional to explain its documented scope and status.

4. **Preserve review limits.** Keep exclusions and unresolved project questions beside the draft sentence.

5. **Confirm the maintenance source.** Record the current document and assigned responsibility.

6. **Approve public wording.** Review the excerpt, metadata and captions together before publication.

Use approved distinctions in the [Positioning stage](/process/positioning/). Keep technical decisions with the responsible project professionals. A content brief organizes their explanation; it does not decide the assembly, choose equipment or establish suitability for the lot.

Record the next review trigger as a concrete source change. A revised plan, changed field condition or replacement handoff document may alter the sentence. Recheck the public wording against the current record before carrying it to another project page.

## Which questions should reach the responsible professional?

Send questions that name the missing source or unclear term. “Can we say conditioned?” needs a documented answer, not a marketing preference. Ask the responsible professional to explain the difference between the proposed wording and what the available records establish.

- Which current source defines the crawlspace assembly for this project?

- Which components have verified field evidence, and which remain unconfirmed?

- What record supports the proposed conditioning description?

- What did the assembly review cover, and what did it exclude?

- Which site or local-authority questions remain unresolved?

- Which handoff document assigns service and maintenance responsibility?

Keep answers separate when different professionals own different subjects. A publication approval does not settle technical design. A component description does not resolve permit status, environmental conditions or structural questions. Obtain the applicable project review before stating those conclusions.

For page placement, use the [custom-builder website page guide](/guides/custom-builder-website-pages/). Put the assembly explanation within the relevant project's scope. Avoid moving it into a standard-features list unless a separate source establishes that wider inclusion.

Keep health language outside this assembly summary. If a proposed paragraph connects the crawlspace to indoor air, use the companion [indoor air quality claim guide](/articles/positioning/indoor-air-quality-builder-claim-content/) for a separate evidence review. A liner image does not establish radon protection, occupant health, dry conditions or lower bills.

## Which crawlspace copy questions need separate answers?

### Can sealed and conditioned mean the same thing in project copy?

Use the terminology supported by the current project records. Confirm conditioning separately before adding that description to a sealed crawlspace claim. Ask the responsible professional to explain the assembly's documented scope and unresolved details.

### Does a liner photograph prove a complete crawlspace system?

A liner photograph supports a description of what its visible area shows. Obtain separate records for concealed components, conditioning and reviewed assembly scope. Keep unsupported whole-system statements out of the project page.

### Should a project page promise a dry crawlspace?

Do not turn a documented assembly feature into an unsupported promise of dry conditions. Describe the verified scope and its limits. Keep site conditions, technical assessment and actual project outcomes with qualified review.

### What should the page say when maintenance responsibility is unknown?

Leave maintenance responsibility unresolved in the private crawlspace scope brief. Request the current handoff or service source before assigning duties in public copy. Do not invent service intervals, coverage or an owner's obligations.