Greywater recycling in buildings
How RD 1085/2024, UNE-EN 16941-2, and local ordinance expectations fit into a defensible basic project.
Decision-focused guidance: baseline data, reuse applications, and verifiable controls.
Executive summary
Before the basic project, close what approval will actually ask
Regulatory text doesn’t replace a shared data baseline or documented comparison across relevant routes.
- ·Define greywater quality and variability with explicit assumptions.
- ·Bound reuse uses with operational criteria and requirement → parameter traceability.
- ·Document critical controls and verification points from design onward.
- ·Compare alternatives in parallel when more than one route is plausible.
Playbook
Seven decisions before locking design
1. Incoming greywater quality
Close stream origins, expected variability, and minimum data to bound assumptions.
Why it matters
- Less rework when new data arrives.
- Comparable baseline across routes.
Typical risks
- Without characterization, treatment is oversized or fragile.
2. Prioritized reuse uses
Pick uses compatible with operational logistics and sanitary constraints.
Why it matters
- Avoids vaguely defined reuse points.
- Supports an operational plan.
Typical risks
- Vague uses force treatment changes later.
3. Applicable regulatory frame
Align RD 1085/2024 with local requirements (e.g. ordinance) and reference standards.
Why it matters
- Even translation into project parameters.
- Fewer scattered interpretations.
Typical risks
- Mixing texts without traceability breaks review consistency.
4. Treatment trains
Define viable options with identical inputs and identical quality objectives.
Why it matters
- Defensible comparison.
- Documented rejections.
Typical risks
- Vendor-only picks without a baseline erode internal confidence.
Patterns that usually fail internal review
Generic templates, copy-pasted parameters without site validation, and single-vendor routes without a shared baseline tend to collapse once engineering or audit questions arrive.
5. Operational reliability
Estimate operational workload, spares, and routine checks during design.
Why it matters
- Avoids paper-perfect systems that are hard to run.
- Reduces OPEX surprises.
Typical risks
- Ignoring operations leads to intermittent compliance gaps.
6. Instrumentation & records
List minimum measurement points and evidence retention for internal audit.
Why it matters
- Real traceability.
- Faster incident response.
Typical risks
- Without logs, reviews become opinions.
7. Hand-off to basic project
Package assumptions, comparison, and recommendation for internal sign-off.
Why it matters
- Fewer late iterations.
- Better readiness for procurement.
Typical risks
- Ambiguous outputs block procurement and construction.
FAQ
Common questions
When multiple routes are on the table, compare before you commit.
Start with Evaluation Inicial
A comparative baseline for your operation.
No site visit required. Same input data, same evaluation framework across all relevant technologies and manufacturers — whether you already have proposals or haven't asked for any yet.