# Keep safe-room claims within documented project scope.

A safe-room project page needs evidence for the proposed label before that label enters public copy. Collect the intended use, system records and responsible qualified reviewer. Keep local review status separate from editorial permission. If the project file contains only a room name, hold the protective claim until its basis is resolved.

## What must a safe-room publication brief establish?

Begin with the sentence you want to publish. “This project includes a safe room” communicates more than a location on a floor plan. Ask the responsible qualified reviewer what that wording would mean for the particular project. Request the supporting documents before using the label in a heading or caption.

Separate the room's intended use from its current evidence status. A source may record a requested purpose without establishing the design or installed scope. Preserve that difference in the internal brief. Do not turn a design request into a completed feature through a change of verb.

This article concerns publication evidence. It provides no shelter selection, construction or emergency-action guidance. Keep questions about suitability and protective use with responsible qualified professionals. AgAI Labs' role here is to explain the content process, rather than make those technical decisions.

Use the [positioning library](/articles/positioning/) for the broader project story. This page addresses one unusually consequential label. A room description should survive review on its own before it becomes a buyer-facing distinction or a filter applied across your project gallery.

Keep the scope tied to one identified project and revision. A record for another house, another room or another product does not answer this publication question. Request a direct explanation of how each supplied record applies to the proposed sentence.

If the team cannot identify the responsible reviewer, keep the label held. Ask project leadership to assign that responsibility. Do not ask a content writer to settle the missing technical judgment by comparing public photographs or borrowing another project's wording.

## Which labels and records should stay separate?

Keep a room label, a product description, a project design record and a local review response in distinct fields. Each answers a different question. Ask the qualified reviewer which record controls the proposed claim. Do not let a familiar title replace the missing connection between the record and the room.

| Evidence presented | Question for review | Boundary for the writer |
| --- | --- | --- |
| Room name on a plan | What intended use does the current project record establish? | Do not turn the name alone into a protective-use statement. |
| System or product document | Does this exact record apply to the proposed room and project version? | Do not transfer generic product wording to the whole room. |
| Qualified design review | What specific project claim does the responsible reviewer confirm? | Keep the public wording within that confirmed scope. |
| Local review response | Which authority, jurisdiction and project scope does the response concern? | Keep unresolved status explicit; do not invent an approval. |
| Editorial permission | Is the exact sentence cleared for public use? | Record this separately from technical or local decisions. |

The table is an editorial comparison, not an approval checklist from a public agency. Use it to prepare questions for the people responsible for the project. It supplies no design criteria, rating, occupant capacity or statement that a particular room provides protection.

The Indiana Department of Homeland Security states that neither it nor FEMA certifies or recommends particular contractors or products. Its [Residential Safe Room Program page, Installing a Safe Room section](https://www.in.gov/dhs/emergency-management-and-preparedness/mitigation-and-recovery/idhs-residential-safe-room-program/), warns against claims of such certification or approval. Do not attach those labels to a contractor or product in your copy.

The same page's Questions to Think About section raises local permit and location questions. Use it as context for asking your responsible reviewer. It establishes no North Carolina rule, local project approval or program availability. Keep all those matters outside the public claim unless separately established.

Keep ordinary space descriptions equally bounded. The [basement scope guide](/articles/builder-websites/basement-plan-page-content/) separates finished and future space. A basement label does not establish protective use. Neither does a garage location, a concrete wall or an isolated reference to a construction material.

## What belongs in the copyable evidence worksheet?

Copy these fields into the project content brief before drafting a safe-room feature. This worksheet is an original editorial proposal. It is not an official requirement or a technical determination. Keep unknown answers marked unknown, with the specific question needed for review.

**Requested label:** [exact proposed public term and sentence]

**Intended use source:** [project document, revision and relevant locator, or unknown]

**System/product record:** [applicable record and connection to this project, or unknown]

**Responsible qualified reviewer:** [confirmed role and scope of the requested review]

**Local review status:** [confirmed jurisdiction and applicable response, or unresolved]

**Allowed wording:** [exact reviewed sentence, or held pending named evidence]

In the requested label field, include the proposed headline as well as the body sentence. A narrow paragraph can sit below a heading that still implies too much. Submit both to the reviewer. Keep image captions, plan labels and downloadable summaries in the same wording review.

In the intended use field, identify the source that actually describes the purpose. If you have only a plan label, say so internally. Do not invent a design brief or treat a sales note as technical confirmation. Ask which current record should resolve the ambiguity.

In the system/product field, preserve the exact document reference. Ask the responsible reviewer to confirm whether it applies to this project version. Keep an unidentified brochure outside the supporting evidence. Do not infer compatibility between a room, a component and a design from similar names.

In local review status, record the source of any answer rather than the team's expectation. Keep a submitted question distinct from a response. An editorial sign-off does not fill this field. If the status remains unresolved, preserve that fact in the internal publication decision.

In allowed wording, store the final sentence rather than a general “approved” note. Record the scope of the review beside it. If no sentence is supported, write “held.” Keep the missing evidence request attached so the next editor knows what remains unresolved.

## How should you review drawings and public descriptions?

Review the feature as a set of connected statements. A room name can appear in a plan image, a page heading, a gallery caption and a downloadable summary. Check each location before publication. Do not leave a protective label visible in artwork while holding only the accompanying paragraph.

1. **Collect the proposed wording.** Include headings, image labels and captions for the identified project.

2. **Request applicable evidence.** Ask for intended use and system records with their source revisions.

3. **Assign qualified review.** Ask project leadership to confirm the responsible role and review scope.

4. **Separate local status.** Record the applicable authority's response or the unresolved question.

5. **Confirm publication rights.** Request clearance for every proposed public drawing.

6. **Hold unsupported labels.** Publish only the wording that the reviewed records support.

Use the [plan library guide](/articles/builder-websites/plan-library-pages/) to identify whether the page represents a current starting plan or a project example. Keep that status beside the drawing. A feature associated with one project should not become an implied inclusion across the library.

For cleared complex drawings, provide an explanation of their essential information in text. The [W3C complex images tutorial](https://www.w3.org/WAI/tutorials/images/complex/) describes short text alternatives and longer descriptions. Its presentation guidance does not verify a room's design or protective use.

Keep drawings private until publication permission is confirmed. The Copyright Office's [Circular 41, Authorship and technical-drawing note](https://www.copyright.gov/circs/circ41.pdf), distinguishes architectural works and technical drawings. It grants no rights to use a particular project sheet. Ask the responsible rights holder or authorized party.

Use the [build quality article](/articles/positioning/communicating-build-quality/) for organizing evidence about documented work. Keep those records within their original purpose. A construction photograph or general quality record cannot fill an unanswered safe-room design question in your publication brief.

## What should you publish when the room name is the only evidence?

Consider a clearly fictional, unnamed plan. One room carries a safe-room label, but the folder supplies no design or product record. No qualified review, installed scope or local response is confirmed. This writing exercise establishes no protective use and describes no actual project offered by AgAI Labs.

Keep the claim held. Do not publish the labeled drawing while describing the missing evidence as a minor caption issue. Request a cleared public version or omit the affected drawing. Preserve the original source internally so the reviewer can identify the unresolved label.

**Fictional internal evidence request:** “Please identify the current intended-use record for the room labeled safe room. Supply the applicable design and system/product records. Confirm the responsible qualified reviewer and local review status. Please state which exact public wording, if any, those records support.”

The request does not ask the reviewer to endorse a predetermined marketing sentence. It leaves room for the answer that no protective claim is supported. If the response remains incomplete, retain the held status. Do not replace the requested records with a general source about safe rooms.

**Fictional public-page excerpt:** “This project summary omits the room whose intended use remains unconfirmed. The public plan view will be reconsidered after the project team resolves the source label.”

The excerpt illustrates a limited publication note. You could instead omit the unresolved feature from the page entirely. Neither option identifies the room as usable for protection. Do not invent a different room purpose merely to complete the page.

The [FTC truth-in-advertising overview](https://www.ftc.gov/news-events/topics/truth-advertising) calls for truthful, nonmisleading claims with appropriate evidence. Check the whole page against that principle. A disclaimer at the bottom should not carry the burden of correcting an unsupported feature heading.

If the room's wall record mentions ICF, use the paired [ICF project-page guide](/articles/positioning/icf-home-project-page-content/) for that separate assembly description. Keep its confirmed wall-zone wording distinct from the held room-purpose claim. One source must not silently answer both questions.

Retain the final publication decision with your editable site records. The [Owned website stage](/process/owned-website/) describes that ownership. When new project evidence arrives, reopen the exact sentence and affected drawing labels before changing the public page.

## Which safe-room publication questions need separate answers?

### Can a plan label alone support a safe-room feature?

A safe-room label alone should remain held as a public protective claim. Request the project's intended-use record, applicable design and system records, and responsible qualified review. Keep unresolved local review status separate from editorial permission.

### Does a basement or ICF wall establish protective use?

A basement location or documented ICF assembly does not establish a room's protective use. Keep those descriptions within their own confirmed scope. Request separate project evidence before publishing a safe-room claim.

### Can the page call a product FEMA approved?

Do not call a contractor or product FEMA approved or FEMA certified. Indiana's agency guidance warns against those claims. Keep any project review discussion tied to its actual source and scope without turning it into a product endorsement.

### What if only part of the evidence request is answered?

Keep a safe-room claim held when the supplied records do not support its exact wording. Preserve the unanswered project questions internally. Omit affected labels and drawings from the public version until their content and publication rights are resolved.