The WELL Building Standard, a certification mark of the International WELL Building Institute, is presented by its owner through four connected stages: assess, implement, verify and monitor. This framing turns certification into a managed project rather than a single inspection near completion. Assessment establishes the project's intended route and registration; implementation converts that route into completed measures and submitted evidence; verification subjects the work to external review and on-site testing; and monitoring addresses continued performance and recertification. The sequence is useful for UAE developers, project managers, facilities teams and consultants because it clarifies when decisions, construction work, evidence preparation and operational responsibility enter the process.
The owner's sequence gives the project a simple organising structure without suggesting that every activity happens in isolation. A scorecard decision made during assessment may shape design instructions during implementation. A documentation issue found during review may require the implementation record to be clarified. A lesson from on-site testing may influence later operational management. The stages are therefore distinct in purpose but connected in practice.
This structure also corrects the idea that certification begins with a tester arriving at a completed building. By the time on-site verification occurs, the project should already have defined its intended scope, registered, implemented the selected measures and assembled the supporting documentation. Verification is a late and important stage, but it depends on decisions taken much earlier.
The measurement methods used during verification and the separation between the testing and review roles are explained on the neighbouring pages.
The assess stage covers creation of the project scorecard and registration. The scorecard gives the team a controlled way to identify the features it intends to pursue and to track the selected route through the project. Registration places the project within the scheme's administration and gives the team access to the project environment used for managing the process. The owner describes assessment as the point at which the team sets goals, customises its checklist and registers the project.
For a developer, the value of this stage lies in early definition. The project needs to know what it is attempting to deliver before design packages, procurement decisions and operational commitments become fixed. A scorecard is not simply a future submission index. It influences who needs to contribute, what evidence will later be required and which decisions must be protected through design development and construction.
For a project manager, assessment should become part of governance rather than a parallel specialist exercise. Responsibility for the selected route needs to be visible in the programme, design responsibilities and information requirements. That does not mean reproducing the scheme manual within project documents. It means ensuring that each chosen commitment has an owner, a delivery path and an evidence path.
The implement stage covers adopting the relevant requirements, carrying them through the project and uploading compliance documentation for review. It is the point at which the scorecard moves from an intended route to a record of what has actually been designed, installed, adopted or operated. The scheme owner describes this stage as using project tools and technical resources, implementing requirements and submitting documents that demonstrate compliance.
Implementation can involve several project functions, depending on the selected scope. Designers may need to show how a decision was incorporated into the design. Contractors may need to preserve product or installation records. The client may need to adopt policies or operational arrangements. Facilities personnel may need to demonstrate that procedures have moved beyond draft form and can be maintained in use. The central point is that evidence follows delivery; it cannot compensate for a measure that was never implemented.
Uploading documents is therefore not a clerical end-stage exercise. The quality of the submission depends on whether records were anticipated and collected as the project progressed. A late search for evidence can expose gaps between what the team believes occurred and what can be demonstrated. Implementation is strongest where the delivery record and the evidence record develop together.
The verify stage is where the scheme tests whether the submitted case and the measured conditions support the intended outcome. The owner's process description places external review and passing on-site tests within this stage. Verification is therefore broader than the site visit alone. It includes consideration of documentation and the formal treatment of performance-testing results before an award can be earned.
This distinction matters because a project can be well documented yet still need to demonstrate measured performance, or it can obtain apparently satisfactory field results while retaining unresolved documentation issues. The scheme owner states that certification involves both documentation review and performance verification. Together, those routes assess whether the project's strategies, policies and protocols are supported by evidence and whether the space performs as required.
Verification also provides an external check on the project team's own conclusion. The team may prepare the building, organise records and support access, but it does not determine for itself that the relevant features have been achieved. That determination follows the scheme's review process. The verify stage should therefore be treated as a controlled evidential milestone, not as a ceremonial inspection after the real work has finished.
The monitor stage begins after the immediate certification outcome and addresses the continuing management of the achievement. The owner links this stage to viewing ongoing submissions, revisiting goals, planning improvements and undertaking recertification. Monitoring recognises that a building is operated over time and that the conditions supporting an award need continuing attention.
For facilities teams, this stage is particularly significant. Design and construction records explain how the project reached verification, but operational control determines whether relevant policies, procedures and building conditions remain in place. Staff changes, maintenance decisions, tenant alterations and revised operating arrangements can all affect the continuity of the original delivery case. Monitoring provides the management context for identifying and addressing such changes.
Recertification should not be viewed as an unrelated future project. Decisions made during assessment and implementation can either make later evidence easier to maintain or create recurring administrative difficulty. Clear ownership, retained records and integrated operational procedures reduce the risk that the project loses track of how its verified position was established.
The four stages have a logical order, but they should not be mistaken for a process in which one stage becomes permanently closed before the next begins. Assessment decisions may need refinement as the design develops. Implementation evidence may receive review comments. Verification may identify a need for corrective work. Monitoring may reveal that an earlier operational assumption requires revision. The framework allows feedback while preserving the purpose of each stage.
This is why the scorecard should remain a live management reference rather than an initial document filed away after registration. Changes to scope, design or operation need to be understood against the intended certification route. A project that loses control of those connections may reach verification with work completed but evidence missing, or with evidence prepared for a route that no longer reflects the delivered building.
The most effective interpretation is therefore sequential accountability. Assessment establishes the intended case, implementation delivers and records it, verification subjects it to external scrutiny, and monitoring carries the achievement forward. Feedback may move between stages, but it does not erase their different functions.
UAE developments often involve separate developer, design, construction, fit-out and facilities organisations. The four-stage framing helps connect those parties by showing when responsibility moves or overlaps. The developer may sponsor assessment, consultants may shape implementation, contractors may create delivery evidence, and facilities teams may inherit monitoring obligations. A project manager needs to ensure that the handovers between those groups preserve the certification case.
The programme should show certification activities alongside design, procurement, completion and operational mobilisation. Verification cannot be scheduled intelligently if the scorecard, documentation review and site readiness are treated as disconnected workstreams. The owner's process makes clear that on-site testing sits after implementation and within a wider external review route.
The four stages also provide a useful reporting language for senior stakeholders. A project can explain whether it is still defining its route, implementing selected measures, resolving review and testing, or maintaining an achieved position. That is more informative than describing the project simply as pursuing certification, because it identifies the current management task without reproducing protected technical requirements.
An independent resource. WELL is a certification mark of the International WELL Building Institute pbc. No affiliation, endorsement or accreditation.
No. Registration forms part of the assess stage and places the project into the scheme's process. Certification depends on later implementation, evidence review and verification. Treating registration as an achievement equivalent to the final award would misstate the owner's four-stage sequence.
No. The verify stage includes external review as well as passing on-site tests. The scheme owner also describes documentation review and performance verification as connected approval processes. The site visit creates important evidence, but that evidence still enters a formal review route.
That approach creates unnecessary risk. The implement stage includes both delivery and uploading evidence, so records should be anticipated as the project progresses. Waiting until completion can reveal that a document was never created, a responsibility was unclear or an installed measure cannot be demonstrated adequately.
No. Monitoring is the continuing management stage that supports maintenance of the achievement and preparation for recertification. Operational ownership, record retention and review of changes should continue between formal milestones rather than being recreated shortly before a future submission.
They have separate purposes but can interact. Review comments may send the team back to clarify implementation evidence, and verification findings may lead to corrective action. The value of the framework lies in clear accountability, not in preventing feedback between stages.
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.