The WELL Building Standard, a certification mark of the International WELL Building Institute, divides its requirements into two classes: preconditions and optimisations. Preconditions are mandatory, all applicable preconditions must be achieved, and they score no points; optimisations are elective and contribute points when achieved. That difference changes how each class should be programmed, governed and protected during a project.
A precondition behaves as a gateway. Where it applies, the project cannot compensate for failing it by succeeding elsewhere. Because it carries no points, its importance may be underestimated by teams that focus too early on a target score, yet it is fundamental to eligibility for certification at every award level.
An optimisation behaves differently. It is selected because it suits the project's objectives, scope, control, budget and evidence capability. Its value is expressed through scoring, so the project can compare alternative combinations and decide which elective measures are realistic and worthwhile.
The distinction is therefore not between important and unimportant work. A precondition is important because it must be met. An optimisation may also be important to the client's health or design objectives, but the scheme allows choice about whether it is pursued for points.
The absence of points does not mean that a precondition has no value. It means the scheme treats that requirement as part of the minimum foundation for certification rather than as an optional achievement above the foundation. Points are reserved for elective work that extends the project beyond the applicable baseline.
This structure prevents a project from using scored achievements to purchase its way around a missing mandatory condition. A project may have a strong portfolio of optimisations, but those points do not erase a failed applicable precondition. The mandatory layer and the scored layer must therefore be tracked separately.
For project governance, a precondition should be reported as achieved, at risk, not applicable where the scheme permits that conclusion, or unresolved. It should not be reported as a low-value item merely because its score is zero. A zero-point mandatory item can carry greater programme risk than a high-value elective item.
Preconditions usually need early confirmation because a late failure can undermine the entire certification route. The project team must identify who controls each applicable requirement, what evidence is expected, when the relevant decision becomes fixed and whether completion depends on design, construction, operation or physical verification.
Optimisations can be managed as a planned portfolio. The team may begin with a wider set, assess feasibility and retain a suitable combination as design develops. Some may become impractical because of scope, cost, procurement, landlord control or operational constraints, while alternatives may remain available.
This creates different forms of contingency. A project cannot rely on a spare precondition to replace a failed one, because every applicable precondition is required. It can, however, maintain alternative optimisation routes so that the scoring strategy is not dependent on a single elective measure whose evidence or delivery remains uncertain.
The most consequential preconditions are not necessarily the most technically complex. A requirement can become difficult simply because it depends on a decision made before the certification workstream was fully mobilised. Site planning, base-building interfaces, spatial layouts, system selection, procurement rules and operational responsibility can all become fixed early.
For that reason, the precondition review belongs near the start of briefing and design coordination. The team should identify dependencies before drawings, specifications, leases, appointments or contractor packages remove flexibility. A late compliance review may accurately identify a problem but still arrive too late to solve it efficiently.
Optimisations also benefit from early consideration, but for a different reason. Early review allows the project to select elective measures that align with the design rather than being added as isolated extras. An optimisation that supports an existing client objective can be more robust than one chosen late only to close a points gap.
Every precondition needs a named project owner, even when several parties contribute. Ownership means responsibility for understanding applicability, coordinating delivery, collecting evidence and escalating risk. Without that role, mandatory requirements can sit between consultants, contractors and operators with each party assuming another will close the gap.
Optimisations need equally clear ownership, but their status should remain visible as elective. The project should avoid allowing a desirable optimisation to consume attention while a mandatory issue remains unresolved. A disciplined tracker separates the gateway items from the score-building items and shows the evidence route for each.
Evidence planning should begin before evidence is produced. The relevant party must know whether the requirement is demonstrated through design information, product records, policies, commissioning information, operational records, testing or another accepted pathway. The purpose is not to recreate the scheme manual, but to ensure that the project's ordinary information flow can support the selected route.
Design and operational changes can affect both classes of requirement. A value-engineering proposal, tenant revision, substituted product, altered operating policy or delayed system can change a previously credible compliance route. The certification workstream therefore needs a change-control connection rather than operating as a static checklist.
For preconditions, change control should ask whether the proposal creates a direct eligibility risk. The answer may require immediate technical review because the project cannot trade the issue against points elsewhere. A change that appears minor to cost or programme can still be significant if it removes the only route to a mandatory outcome.
For optimisations, the question is whether the change reduces the expected score or makes the evidence route unreliable. The response may be to protect the original measure, replace it with another elective route or revise the target strategy. Flexibility exists, but it should be managed deliberately rather than discovered during final review.
A practical programme treats preconditions as the protected baseline and optimisations as the controlled selection above it. The two classes should be reviewed together because they can depend on the same design packages, contractors or operational teams, but their status and consequences should remain distinct.
The programme should also recognise that a mandatory requirement may continue into operation. Completion of design or construction does not necessarily finish the obligation if the requirement depends on management practice, ongoing records or conditions in the occupied building. Early involvement from facilities and organisational teams can therefore be essential.
The neighbouring pages explain the ten concepts, the point thresholds and concept cap, and the structural difference between certification and annual ratings; those subjects are not repeated here.
This independent explanation summarises the two-class structure without reproducing the scheme's protected requirement text. Project-specific applicability, evidence and interpretation should be taken from the current material issued by International WELL Building Institute pbc for the relevant project pathway. That check is especially important where scope, tenancy or operational control is divided between several parties.
An independent resource. WELL is a certification mark of the International WELL Building Institute pbc. No affiliation, endorsement or accreditation.
All applicable preconditions are mandatory for certification. A project cannot choose to omit an applicable precondition because it has earned enough points from optimisations. Applicability must be determined through the scheme's current rules rather than assumed from a general summary.
No. Preconditions score no points. Their role is to establish the mandatory foundation that must be achieved before the project can qualify at any certification level.
No. Optimisations are elective and scored. A project selects a suitable combination according to its objectives, scope and ability to deliver and verify the work, while still meeting every applicable precondition.
No. The two classes are not interchangeable. Points gained through elective optimisations do not compensate for failure to achieve an applicable mandatory precondition.
They should be reviewed early because some depend on decisions that become difficult to change after briefing, design, procurement or construction has advanced. Early review allows responsibilities, interfaces and evidence routes to be resolved before the project loses flexibility.
Yes, where requirements depend on operation, maintenance, policy or ongoing records. Early facilities involvement helps ensure that a design-stage compliance route can continue in practice after occupation rather than failing at the transition from project delivery to building management.
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.