Documentation, Performance Verification, and Reporting
What the exam tests
This domain covers the evidence chain: what you submit, how it is reviewed, how performance is verified, and how results are reported. The exam rewards project-specific, dated, and traceable evidence.
Core rules
- WELL Online is the documentation platform. Evidence types include annotated drawings, specifications, test reports, policies, photos, and letters of assurance.
- Each claim should name the project, location, product, or feature part, and include a date and author. Generic manufacturer marketing is weak evidence.
- Performance verification follows document review; the assessor may request additional evidence or retesting.
- Reporting should distinguish verified performance from design intent. Recertification requires updated evidence, not a resubmission of old reports.
- Keep a point tracker: preconditions must all be met before optimization points count toward a level.
Worked example
A project submits a smoking policy with no site evidence. The policy states "no smoking on site," but photos show receptacles at the entrance and no signage. The reasoning: a policy is necessary but not sufficient. Add lease language, signage, and enforcement records, and show the designated smoking area is at the required distance.
Traps
Submitting undated or unsigned documents. Using a product letter that does not identify the installed product. Assuming a design submission is final certification. Losing track of which optimizations are claimed and verified.