A rainwater harvesting page should describe the documented collection area, conveyance, storage and intended outlet use for the applicable project. Separate installed components from future options. Keep irrigation descriptions distinct from drinking-water claims. Route water-quality, treatment and connection questions to qualified reviewers before approving wording about what the system can supply.
What is the rainwater intended to supply?
Start with intended use rather than the appearance of the storage container. Ask which current project document identifies that use. A collection feature needs a clear description of its purpose before it belongs in a public specification. Do not expand an irrigation reference into a household water-supply statement.
Keep each documented use separate. A record that identifies a landscape outlet does not establish another outlet's purpose. If the intended use remains unresolved, write that question in the internal worksheet. Do not turn the existence of stored water into a list of possible household uses.
Use the standard specifications page guide to keep project scope labels consistent. A system installed on one project does not establish a builder-wide inclusion. A future collection option should remain separate from an installed system description.
The CDC's Collecting Rainwater and Your Health guidance, Overview and Health risks connects water quality with intended use. It also explains that rainwater can contain harmful germs or chemicals despite looking clean. A clear-water photograph cannot support a drinking-water claim.
State the documented use in ordinary language. Avoid a broad phrase such as whole-home water when the record supports only a limited outlet. Keep the public label tied to the actual reviewed use. Do not describe water as potable without applicable project evidence and qualified review.
Which parts of the collection system are documented?
Trace the system description from the collection area to its recorded use. This is a reading exercise for the project records, not a design procedure. Ask the responsible reviewer to identify any missing connection in the description. Do not draw an imagined route through concealed work.
Name a collection area only when the applicable document identifies it. Keep area dimensions out of the page unless an approved source supplies them. Do not assume that every roof surface feeds the system because one downspout appears beside a tank.
Record conveyance separately from storage. Describe only components supported by the current scope and installation records. When the source mentions a pump, control or treatment component, ask whether it is installed, specified or merely proposed. Keep those statuses visible in the working sheet.
| System part | Record to request | Inference to avoid |
|---|---|---|
| Collection area | Approved identification of the contributing area | Every visible roof area contributes |
| Conveyance | Applicable routing and component record | A photograph proves concealed connections |
| Storage | Confirmed equipment identity and installation status | Appearance establishes capacity or water quality |
| Outlet use | Recorded destination and intended purpose | One outlet establishes every permitted use |
| Future option | Separate proposal with its unresolved questions | Space or intent establishes installed equipment |
Use the table to find missing answers before drafting. It does not specify a complete system or assign engineering responsibility. The project reviewer must decide which documents apply. Preserve distinctions between design intent, equipment selection and confirmed installed scope.
What can project images contribute?
A reviewed image can illustrate a documented component. Give it a visible caption explaining the component and status. The project gallery guide connects that caption to its project decision. A photograph should not carry an unsupported claim about water quality.
W3C's informative images tutorial, Overview describes text alternatives in relation to an image's information purpose. Describe the approved information the image contributes. Keep private plans and uncleared equipment records outside public media.
Which questions belong with qualified reviewers?
Separate a public system description from conclusions about treatment, water quality and connections. Gather each question before requesting a technical review. Ask what evidence the reviewer needs for this particular intended use. Leave the answer unresolved until the applicable evidence and responsible review are available.
Ask the qualified system reviewer whether the recorded components match the documented use. Request confirmation of the relevant water-quality review and its limits. Do not copy a treatment recipe from general guidance or another project. A component name alone should not become a statement that the water is suitable.
Ask the responsible plumbing reviewer about connections between the rainwater system and other water systems. CDC's Mixing rainwater and treated water section explains the contamination concern. Refer questions about testing, treatment and use to the health department, as the guidance recommends.
For local requirements, ask the applicable authority which collection, connection and intended-use questions require review. Record the jurisdiction, verification date and responsible role privately. This article establishes no local permission or project approval. Do not present a general educational source as an approval document.
Keep the review questions concrete: which intended use was evaluated, which system record was reviewed, and what remains unresolved? Ask the reviewer to distinguish a recommendation from a completed determination. Do not replace an unavailable answer with language about sustainable living or self-sufficiency.
How do you handle a different future use?
Treat a proposed new use as a separate question. Ask which equipment, connection, water-quality and authority reviews apply before describing that use publicly. Do not imply that a system intended for irrigation can serve another purpose after an unspecified adjustment.
If a buyer asks about drinking water, record the question without promising feasibility. Preserve the current documented use in the public description. An inquiry about a future possibility does not change installed scope or establish that the possibility has received approval.
How do you complete a rainwater system worksheet?
Copy this proposed editorial worksheet into your internal project review. Use one record per documented system. The fields organize information for website copy. They are not an official form, a water-quality assessment, a design specification or a substitute for qualified technical review.
Rainwater system worksheet Collection area: Identified surface; revision; unresolved boundary Storage record: Equipment identity; status; supporting record Intended use: Recorded outlet; purpose; limits; confirmation source Components: Collection; conveyance; storage; outlet; each status Water-quality question: Intended use; evidence needed; unresolved condition Reviewer: Qualified role; question; verification date; decision Approved public label: Factual sentence; scope limit; approving role
- Find the current record that identifies the rainwater system's intended use.
- List the documented collection area and conveyance path.
- Match storage equipment to its recorded installation status.
- Record each outlet's documented use separately.
- Separate future options from installed components.
- Send water-quality, treatment, connection and local-rule questions to the responsible reviewers.
- Approve the public label against the resulting project record.
In the collection field, identify the source without reproducing a private drawing. If you cannot establish the contributing surface, preserve that gap. Do not calculate an area from a website photograph. The public description can wait for a reliable record.
In the storage field, separate equipment identity from capacity. Leave capacity unknown when no approved source supplies it. In the component field, record the status of each item independently. One completed component should not make an entire proposed system appear installed.
In the reviewer field, name the responsible role and the question it must answer. A blank field means the review still needs an assignment. Keep any authority correspondence distinct from a product document. Neither should silently substitute for the other.
The Owned website stage can carry the approved public label and its review history. Preserve the private evidence separately. If the intended use changes, return that label for review before changing the public description.
What should a public rainwater excerpt say?
Consider a fictional, unnamed project created only to demonstrate the worksheet. Its invented installation record identifies collection from a recorded roof area, conveyance to storage and an outlet for ornamental landscape irrigation. A separate proposal mentions additional storage. No drinking-water assessment or future-use approval is supplied.
The worksheet records the identified collection area without dimensions. It lists the documented conveyance, storage and irrigation outlet as installed in this fictional record. It marks the additional storage as proposed. Water quality, treatment details and local approval remain unknown.
Fictional public excerpt: This example's recorded rainwater system collects from the identified roof area and supplies an ornamental landscape irrigation outlet. Additional storage remains a proposed option. This description makes no drinking-water claim and establishes no permission for another use.
This example describes an invented record, not an actual installation or an AgAI Labs construction project. Do not reuse its component statuses as defaults. Ask the reviewers to resolve the outstanding questions before approving equivalent wording for a real project.
The FTC's Truth In Advertising guidance requires truthful, non-misleading claims. Check the excerpt alongside its heading and images. A careful system paragraph should not sit beneath a heading that promises a household water supply.
Keep this feature within the custom builder website page structure. It belongs with the applicable project and specification. Avoid copying it into every plan description. Buyers need to see where the documented system applies.
The tankless water heater scope guide addresses separate equipment and installer questions. Keep rainwater intended-use records distinct from water-heating records. Find the wider project context in the builder website article collection.
What else should a rainwater page explain?
Does clear collected water support a drinking-water claim?
Clear appearance does not establish that collected rainwater is suitable for drinking. Keep a builder page tied to the documented intended use. Send water-quality and testing questions to qualified reviewers and the relevant health department.
Can a tank photograph establish storage capacity?
A tank photograph does not establish a project's storage capacity. Request the approved storage record and confirm which equipment it identifies. Leave dimensions and capacity out of public copy when the applicable source remains unavailable.
Should a future outlet appear as installed scope?
A proposed rainwater outlet should remain separate from installed scope. Record its intended use and unresolved reviews in the private worksheet. Do not imply that another use is approved because part of the collection system already exists.
Who should answer treatment and connection questions?
Send rainwater treatment and connection questions to the responsible qualified reviewers. Ask the applicable authority about local requirements. A website worksheet organizes those questions; it does not provide a treatment recipe, water-quality determination or project approval.