The WELL Building Standard, a certification mark of the International WELL Building Institute, relies on documentary evidence as well as measured performance. Documentation explains what the project designed, installed, adopted or operates, identifies who was responsible and shows how the submitted claim can be checked. The project team assembles that material, the project administrator coordinates its quality and submission, and the WELL Reviewer considers it alongside any applicable performance-testing results. This page concerns the evidential record rather than the content of individual requirements, so it does not reproduce feature wording, tables or criterion lists from the scheme's copyright materials.
Documentation is not simply a collection of files showing that activity occurred. Its purpose is to demonstrate a clear connection between the project's selected route and the delivered outcome. A useful document identifies the relevant project, describes or depicts the implemented measure, comes from an appropriate source and allows the reviewer to locate the evidence without relying on unsupported explanation.
The evidence may concern design, construction, policy or operation. A drawing can show where a design decision appears. A specification or product record can support what was selected or installed. A signed assurance can identify professional responsibility. A policy, procedure or operating schedule can show that an organisational commitment exists in a controlled form. A dated record or photograph can support implementation at a particular location. These are categories of evidence, not a public reproduction of the scheme's requirements.
The testing and review roles and the treatment of unsuccessful results are addressed on the neighbouring pages.
Design evidence commonly includes controlled drawings, schedules, calculations, specifications and technical narratives. Its value depends on whether it represents the relevant project stage and whether the submitted portion can be connected to the claimed implementation. An early design drawing may explain intent but may not prove that the final work followed that intent. The project should therefore distinguish design evidence from completion evidence.
Construction and procurement evidence can include approved submittals, installation records, commissioning material, product information, photographs and completion documents. Such records help bridge the gap between what was specified and what was delivered. The reviewer needs a coherent evidential path rather than a large archive of unrelated project files.
Operational evidence can include policies, plans, procedures, schedules, training material and retained management records. These documents should represent arrangements that have been adopted for the project, not generic templates that were never placed into use. Scheme guidance explains that documentation review considers design strategies, policies and protocols, while performance verification considers measured operation where applicable.
No single discipline necessarily prepares the entire submission. The project administrator usually coordinates evidence from people whose responsibilities match the subject of each document. Architects and engineers may prepare design records. Contractors and suppliers may provide installation or product evidence. Client representatives may approve policies. Facilities teams may prepare operational procedures and schedules. Qualified professionals may provide assurances within their areas of responsibility.
The scheme owner advises that documentation is likely to be generated by team members with different expertise and that the project administrator coordinates their contributions. The administrator remains responsible for the quality-control check before submission, even where another professional authored the underlying document.
This allocation should be established early. Asking the person closest to the work to prepare the evidence improves technical accuracy, while central coordination improves consistency and completeness. The administrator should not rewrite specialist evidence beyond its technical basis, and specialists should not assume that uploading a file without context completes the project's submission responsibility.
A reviewer should be able to identify what part of a document supports the claimed feature without searching through an entire manual, drawing set or report. Clear file names, revision information, project references and annotations help establish that connection. Scheme guidance specifically emphasises annotations that show where the relevant evidence can be validated.
Traceability also means showing that the document belongs to the project and reflects the relevant stage. A policy should identify its owner and status. A drawing should carry a recognisable title and revision. A photograph should be associated with a location and purpose. An assurance should be completed by the appropriate responsible person. These controls make the evidence reviewable without turning the submission into a narrative that asks the reviewer to accept unverified statements.
Volume is not a substitute for clarity. Uploading a complete corporate handbook or an extensive technical package can make review harder where only a small portion is relevant. A focused, annotated submission is generally more intelligible than an unstructured mass of files. The project team should preserve the underlying records while presenting the material needed for the formal review in a controlled form.
Documentation and measured results answer related but different questions. Documents can demonstrate that a design, policy, procedure or installation exists. Performance testing can demonstrate the condition recorded at the project under the applicable protocol. Where both forms of verification apply, the reviewer considers them together rather than treating either as a substitute for the other.
A project can therefore have a strong documentary record but an unresolved measured result, or passing measurement data but incomplete supporting documentation. The feature status depends on the complete evidential route assigned by the scheme. The reviewer may mark the matter as pending where one side of that route remains incomplete.
Coordination between the project administrator and testing agent is important because performance-testing files must be associated with the correct project locations and features. Scheme guidance allows the agent different account-access levels, which can change who uploads, tags and formally submits the testing package. Whatever arrangement is used, the project remains responsible for ensuring that the documentary and measured records form one coherent submission.
The reviewer begins with the submitted material, not with assumptions about what probably happened on site. The review considers whether documents and testing results are satisfactory for the relevant features. The reviewer can identify missing evidence, unclear annotations, inconsistencies or information that does not demonstrate the claimed outcome.
Review comments are part of the evidential process rather than an indication that the project has failed as a whole. The project team can respond by clarifying the existing material, correcting a document or providing additional evidence within the applicable review route. The response should address the reviewer's point directly rather than adding unrelated files.
The final determination remains based on the evidence accepted through the scheme's review process. A document's approval within another contractual or regulatory process does not automatically establish that it satisfies the scheme's verification method. Conversely, a document prepared specifically for certification still needs to be accurate, project-specific and supported by the responsible parties.
UAE projects often pass through several organisations before occupation: developer, design consultant, project manager, main contractor, specialist contractor, tenant team and facilities operator. Each transition can separate the evidence from the person who understands it. A documentation plan should therefore identify authorship, review, approval, location and handover responsibility while those parties remain engaged.
Language and format also require control. Project records may originate from multinational teams or from systems designed for contractual administration rather than certification review. The submitted evidence needs to remain clear to the reviewer and should include accurate translation or explanation where necessary. Scheme guidance advises teams to provide translations in a form that allows the reviewer to understand the submitted material.
The best evidence strategy is integrated with ordinary project information management. Certification records should not exist as an unexplained parallel archive assembled after completion. When the scorecard, design responsibility matrix, submittal process and facilities handover are connected, the project can demonstrate what was delivered without recreating its history during review.
An independent resource. WELL is a certification mark of the International WELL Building Institute pbc. No affiliation, endorsement or accreditation.
No. Strength comes from relevance, traceability and clarity. A smaller set of controlled and annotated documents can be more persuasive than a large archive in which the reviewer cannot locate the supporting information. Scheme guidance emphasises identifying the relevant portion of submitted material.
The project administrator coordinates the quality-control check, although the underlying evidence may be prepared by designers, contractors, client representatives, facilities personnel and other responsible professionals. The administrator should confirm completeness and consistency without replacing the technical responsibility of each author.
A template may provide a starting structure, but the submitted document should represent an arrangement adopted for the project. Generic wording that has not been approved, assigned or implemented is unlikely to demonstrate an operating commitment merely because it contains suitable language.
Not where the applicable verification route requires both. Measured results demonstrate recorded performance, while documents establish other aspects of design, implementation or operation. The reviewer considers the complete evidence set and may leave a feature pending where one element is missing.
The review process allows the team to address comments and resubmit material through the applicable review round. The response should be focused on the identified gap and should preserve clear revision and traceability information.
This site is an independent information resource. It is not affiliated with, endorsed by, accredited by or authorised by the International WELL Building Institute pbc, which owns the WELL certification mark, and it is not a certification body, an assessor, a performance testing provider or a scheme partner. Nothing on this page can certify, assess or award anything under the scheme, and nothing here is a substitute for the scheme's own published documentation. Requirements are summarised factually rather than reproduced; where a numeric threshold is stated it is drawn from documentation the scheme's owner publishes openly, and the specific figure is cited rather than the table it sits in. Certification under the scheme is voluntary and is not required by any authority in the United Arab Emirates.