# Show how an addition relates to the existing home. A home addition project page should explain how documented new work relates to the existing house. Describe the household brief, then distinguish retained, changed and new areas using approved project records. Tie public drawings to confirmed publication permission. Keep unverified conditions, occupied-site arrangements and project dates outside the story until the responsible reviewer confirms them. ## What should a home addition project page explain first? Start with the household brief and the scope you can document. Explain which daily-use need shaped the project. Then show how the demonstrated addition relates to the existing home. Keep the account specific to that project. A photograph of a completed room cannot explain every boundary. Identify what the project records say about that room and its connection to nearby spaces. Do not describe an existing room as new because its finishes appear in a final photograph. Place this explanation within your [sales-process library](/articles/sales-process/). A project story gives future buyers a way to understand past work. It should not imply that your team can repeat the same solution on every home. Availability, scope and project fit require their own current review. Choose the story's status before writing. A proposed addition, work under construction and completed work need different language. If the records establish only a proposal, describe the proposal. Do not use a rendering as evidence that the work was built. ## How do you define retained, changed and new? Use a written legend beside the scope table. Retained means the identified part remains within the story's documented scope. Changed means the record describes an alteration to an existing part. New means the record identifies added work. These labels are editorial categories. They do not establish technical suitability, approval status or legal obligations. Have the responsible project reviewer check their application against the approved records. Keep the source sheet and revision beside each entry. | Area and category | Approved record | Public wording and limits | | --- | --- | --- | | [Existing area] Retained | [Sheet, revision, reviewer] | [What remains] Open limit: [not reviewed / none identified] | | [Existing connection] Changed | [Sheet, revision, reviewer] | [Documented alteration only] Open limit: [missing information] | | [Added area] New | [Sheet, revision, reviewer] | [Documented added scope] Open limit: [unconfirmed detail] | | [Unclear boundary] Unresolved | [Record needed] [Responsible reviewer] | Omit the unsupported statement. | Describe exactly what each row covers. “Retained front room” does not mean every component of that room remained untouched. If the records support only a layout statement, keep the wording about layout. Do not extend the label to structure, systems or finishes without evidence. Apply the same boundary to new work. An added room may connect to altered existing space. Name both categories where the records support them. Avoid making the reader infer the boundary from a change in paint color or furniture. ## Which records should control the public scope story? Identify the approved project records used for the story. Record the sheet title, revision and purpose. Confirm what “approved” means for that source. Approval for publication and a project review are separate decisions. Ask the responsible reviewer whether the drawing describes the project stage you intend to discuss. A design drawing might explain an intended relationship without establishing completed work. If later records change the scope, use the reviewed record appropriate to the story. Do not resolve conflicting drawings through the marketing draft. List the conflict and hold the affected sentence. A short account with a clear boundary is more useful than a detailed account assembled from incompatible revisions. The [builder proposal guide](/articles/sales-process/presenting-a-builder-proposal/) explains how source revisions and scope questions support a decision. Use that discipline for the project story. Keep contractual interpretation and technical conclusions with the qualified reviewers responsible for those questions. ## How do you confirm permission before showing drawings? Confirm publication rights with the responsible party before displaying a drawing or an excerpt. Record the permitted material and use. Possessing a project file does not answer who can authorize its public display. Keep the publication decision separate from the scope review. A reviewer may confirm what a drawing shows without controlling publication rights. A permission record may authorize display without confirming that the drawing matches completed work. Your story needs the appropriate answer to both questions. Review the excerpt for identifying information. Remove material outside the approved public scope through the responsible publication process. Do not publish an address, private household note or internal comment because it appears on the same sheet. If permission remains unknown, hold the drawing. You can draft a text story from approved public facts while the permission question remains open. Do not replace the held material with an invented plan that appears to represent the real home. ## How should the page describe the household brief? Describe the activity the household wanted to support. For example, a fictional brief might request a separate place for work near an existing shared room. Keep that request distinct from the final documented scope. A request explains intent; a reviewed project record supports what the page says happened. Avoid private explanations that the household has not approved for publication. Room-use language can explain a brief without disclosing health, family or employment details. Confirm the public wording with the responsible project contact. Keep occupied-site arrangements out of the story unless the records support them and publication is authorized. An addition does not tell the reader whether anyone lived in the home during work. It also does not establish access arrangements, temporary facilities or disruption controls. The [builder and buyer expectations guide](/articles/sales-process/builder-vs-buyer-expectations/) covers responsibility and communication boundaries. Use your actual project records for any statement about those arrangements. Do not turn a past arrangement into a general promise for future additions. ## What belongs in a copyable addition project-story template? Use this template after the source and permission checks. Bracketed fields require confirmed information. Delete an unsupported public sentence rather than filling its field with an assumption. Keep the missing fact in the private review record. ADDITION PROJECT STORY Story status: [proposed / under construction / completed] Status source: [record and reviewer] Household brief approved for publication: [daily-use goal] EXISTING HOME Retained area: [specific boundary] Supporting record: [sheet and revision] Public description: [approved statement] CHANGED CONNECTION Altered existing area: [specific boundary] Supporting record: [sheet and revision] Public description: [approved statement] NEW WORK Added area: [specific boundary] Supporting record: [sheet and revision] Public description: [approved statement] PUBLIC MATERIAL Drawing excerpt: [identifier / held] Publication permission: [responsible party and permitted use] Caption: [meaning and project status] Text alternative: [information conveyed by the image] REVIEW LIMITS Unconfirmed details: [list] Occupied-site arrangements: [verified statement / omit] Project dates: [verified statement / omit] Technical findings: [qualified source / omit] Final public-copy reviewer: [role] Next review trigger: [source or permission changes] Keep a copy of the reviewed public draft with its source references. When the project story changes, check the table, caption and introductory paragraph together. A revised drawing reference should not leave the old scope description in the page. Your [written build process](/guides/writing-down-your-build-process/) can explain how those reviews occur. Use the [Operating profile](/process/operating-profile/) to identify the actual roles and source records. The template organizes an editorial review. It does not create a construction service or replace professional project work. ## What would a fictional addition story look like? This example is fictional and unnamed. It illustrates the retained, changed and new legend. It describes no real home, builder or completed achievement. The assumed records exist only inside this teaching example. The household brief calls for a separate work room connected to an existing shared room. In this fictional scope record, the shared room's identified layout remains. The connection is altered, and the work room is new. The legend separates those three parts of the proposal. This is a proposed relationship. Completion, dimensions, materials, occupied-site arrangements, project dates and approvals are unknown. No project drawing is reproduced. Publication rights for any future drawing remain to be confirmed. The example keeps the household goal visible without claiming that the proposal solved it. It names an altered connection without describing its construction. It states the proposal status in the same excerpt as the scope. In a real story, replace each assumed record with a checked source. If the record does not identify which part is retained, hold that label. If the project is complete, confirm the completed condition before changing the story's status. ## How should drawings and text work together? Keep the written legend beside any approved illustration. Describe what each category means without relying on color alone. Use the same words in the caption and table. A reader should be able to understand the scope boundary from the text. The [W3C informative-image guidance](https://www.w3.org/WAI/tutorials/images/informative/) explains that text alternatives convey an image's meaning in context. Apply that principle to a simple approved illustration. It does not verify the building, the scope labels or the project status. If a drawing carries information beyond a short text alternative, keep that information in reviewed page text. Do not compress unresolved project details into image wording. No visual treatment can supply the missing source or publication permission. ## How do you prepare the story for publication? 1. Confirm the project stage and public household brief. 2. Check each scope row against its approved record. 3. Resolve conflicting revisions with the responsible reviewer. 4. Confirm permission for every proposed public drawing. 5. Match the legend, caption and text alternative to the approved content. 6. Hold unsupported details and record the final public-copy review. If the homeowner has not chosen a construction path, use the [renovation or rebuild inquiry worksheet](/articles/sales-process/renovate-or-rebuild-builder-page-content/). That worksheet prepares an open comparison. This project-story template explains a specific documented addition scope. ## What do builders ask about addition project pages? ### Can an addition page use only finished photographs? An addition page can use approved photographs, but photographs alone may not explain retained, changed and new scope. Use checked records and a written scope table for those distinctions. ### Does a retained label mean no work occurred there? A retained label on an addition page applies only to its stated boundary. A retained layout does not establish that every finish, system or component remained untouched. ### Can we say the household stayed during construction? State occupied-site arrangements on an addition page only when the project record confirms them and publication is authorized. Otherwise omit the claim and keep the arrangement unknown. ### Who approves a drawing for the addition story? Confirm drawing publication rights with the responsible party. Separately ask the responsible project reviewer to check the drawing's scope and status before using it in an addition story.