A pool project page should explain which pool components your documented scope includes and who handles the adjoining work. Separate the shell, deck, equipment and landscape packages. Label completed work, proposed designs and future options beside each description. Send lot feasibility, barrier and access questions to the qualified project reviewers.
What should buyers understand about the pool package?
Start with the boundary of the project you are showing. A buyer should know whether you built the house, coordinated the pool, installed a particular package or documented work by others. Use the responsibility recorded for that project. A finished backyard photograph cannot settle those distinctions.
Give the water feature its own description before discussing the surrounding setting. Identify the pool shell as a separate component. Then explain which deck work, equipment package and landscape work belong to the documented scope. Keep furniture, planting and neighboring structures outside your inclusion list unless the records support their inclusion.
Describe a completed example as a completed example. Avoid making its features sound like an inclusion on every future house. Your standard specifications page can explain the broader scope categories. The pool page should identify the category that applies to this particular job.
Put the useful answer near the first view of the project. For example, state that the page separates construction packages and identifies items awaiting confirmation. Do not begin with an equipment list whose installation status remains unknown. A prospective buyer first needs to understand what you are presenting.
How do you separate water, deck, equipment and landscape work?
Use a component comparison that follows the documents rather than the photograph. The table below proposes editorial fields for your page brief. It is not a construction specification. Replace its generic document references with the records your team maintains.
| Package boundary | Evidence and buyer question |
|---|---|
| Pool shell. Separate recorded pool work from surrounding construction packages. | Which pool work belongs to this project? Check the applicable pool scope and completion record. |
| Deck. Identify the described surrounding surface and its scope owner. | Which surfaces are included? Check the deck scope and relevant drawing. |
| Equipment. Separate specified equipment from verified installed equipment. | Is the equipment installed or proposed? Compare the equipment schedule with the installation record. |
| Landscape. Identify adjoining work by others without claiming responsibility for it. | Who handles planting and related work? Check the landscape scope and responsibility record. |
Record the interfaces as well as the components. If the pool and deck descriptions meet at one edge, ask who confirms that boundary in the documents. If equipment connections belong to another scope, record the responsible role. Do not supply an installation method to fill a missing scope description.
Use one evidence reference for each inclusion statement. An equipment schedule can support a specified package. It cannot establish installation by itself. A photograph can illustrate a visible surface. It cannot establish an unseen product identity, connection or performance characteristic.
Where documents disagree, leave the disputed statement out of public copy until the project team resolves it. Keep the question specific: which package includes this surface, or which record confirms this equipment? A general request to approve the whole backyard makes the missing fact harder to locate.
Link the pool entry to its parent project record. The project gallery guide explains how captions connect a visible feature to a documented decision. Keep the pool scope table focused on package responsibility.
How should you label installed work and future options?
Use separate labels for completed work, specified work awaiting installation confirmation, a rendering and an unconfirmed future option. These are proposed publishing categories. Match the exact terms to your records before using them. Do not turn an unresolved item into an offered option.
Keep the label beside the material it qualifies. A rendering caption should identify the image as a rendering and describe which features remain proposals. A completed-project caption should identify the documented scope behind the view. Do not rely on a distant disclaimer to explain a prominent image.
A photograph cannot establish that a similar pool fits another lot. Keep a buyer's site question separate from the completed example. Ask the qualified project reviewers to assess the proposed location, access and related site constraints. Avoid suggesting that an empty area in a yard proves feasibility.
The Federal Trade Commission's truth-in-advertising overview states that advertisements must be truthful and must not mislead. Use that evidence boundary when choosing labels. A photograph does not establish that every depicted component belongs to your offer.
What if drawings explain the package more clearly?
Publish only material cleared for public use. The U.S. Copyright Office's Circular 41 distinguishes an architectural work from its technical drawing. Treat permission to publish particular drawings as a separate question for the rights reviewer.
If a cleared drawing carries essential scope information, explain that information in the page text. The W3C complex-images tutorial describes short identification and a longer text alternative for complex images. Describe the package relationships the drawing conveys. Keep private drawing references in your internal brief.
What belongs in a copyable pool scope worksheet?
Copy the following worksheet into your editorial brief. Make one row for each component or unresolved interface. The worksheet is an editorial proposal, not an official form. Blank evidence fields remain open questions until the responsible reviewer supplies the record.
Pool scope worksheet Component: Evidence: Inclusion status: Responsible scope: Public label: Unresolved question:
Use the component field narrowly. Write pool shell, deck, equipment or landscape before adding a more specific description supported by the documents. In the evidence field, record the document title, revision and relevant section. The public page does not need confidential file names.
Keep inclusion status separate from responsible scope. A component can appear in the overall project record while sitting outside your contract. Record who owns the described work without exposing private contact details. In the public label field, write the sentence you intend buyers to read.
Use the unresolved question field to identify the next decision. Ask whether an item is included, whether installation is confirmed or whether publication permission exists. Avoid combining unrelated questions. The record should tell the next reviewer exactly which fact would change the public wording.
How would a fictional project use these fields?
Consider a fictional, unnamed project used only to illustrate the worksheet. Its invented records document a completed pool shell and deck. A separate landscape package remains outside the builder's scope. A rendering shows a possible equipment addition that has no confirmed installation record.
The writer creates separate rows for those packages. The shell and deck rows refer to the fictional completion records. The landscape row identifies separate responsibility. The possible equipment addition stays out of the installed-work list. The example establishes no real project, product, approval or builder capability.
A short public-page excerpt for that fictional example could read:
This completed example documents the pool shell and deck within the recorded project scope. Landscape work belongs to a separate package. The rendering depicts a possible equipment addition whose installation is unconfirmed. A proposed pool on another lot needs its own project review.
Do not reuse that excerpt as a real project claim. Replace every fictional condition with verified records before drafting a live description. If a poolhouse appears beside the pool, give its rooms a separate brief using the poolhouse project page guide.
Which questions need qualified review before publication?
Send barrier, access and local-rule questions to the qualified project team and the relevant local authority. Do not publish installation instructions or a compliance conclusion from photographs. Identify which question concerns the pool package and which concerns a connection to another structure.
The Consumer Product Safety Commission's residential pool barrier booklet explains on printed page one that its guidelines are not mandatory CPSC requirements. That page directs readers to check local requirements with local authorities. Use it as context for review, never as approval of a particular installation.
- Assemble the package records. Separate pool, deck, equipment and landscape documents.
- Confirm responsibility. Have each scope owner check the proposed inclusion wording.
- Identify open site questions. Route feasibility, barrier and access questions to qualified reviewers.
- Check image labels. Distinguish installed work, renderings and unconfirmed future options.
- Compare the excerpt with the records. Remove any claim that depends on a missing answer.
Keep publication permission separate from technical review. A cleared image does not settle project approvals. A completed scope record does not grant drawing rights. Record each decision against the statement it supports rather than marking the entire folder ready.
The builder websites article set connects these project descriptions to the rest of your site. Place the approved pool page within the structure described in the custom builder website pages guide. The Owned website stage covers the website assets and accounts you retain.
What else should a pool project page explain?
Does a pool photograph show what every build includes?
A pool photograph illustrates one view of one project. Check the applicable scope records before describing the shell, deck, equipment or landscape work as included. Label project selections separately from any documented builder standard.
Can a rendering show a future pool option?
A pool rendering can illustrate a proposal when publication permission exists and its status is clear. Label unconfirmed features beside the image. Do not describe the rendering as an installed package or a confirmed option for another lot.
Who answers pool barrier and access questions?
Qualified project reviewers and the relevant local authority should address pool barrier and access questions. A marketing page should identify unresolved questions without prescribing installation details or declaring compliance from a photograph.
Should a poolhouse sit inside the pool scope description?
A poolhouse needs its own documented building scope. Link it to the pool project. Distinguish its rooms, entries, fit-out and utility questions from the pool shell, deck and equipment packages.