Fitwel v2.1 and v3 resources and project scoring
Domain 3: Fitwel v2.1 and v3 resources and project scoring
This domain tests scoring mechanics and resource use: selecting the correct version, reading the scorecard, calculating points, and preparing documentation that survives review. The exam expects version discipline, not memorized point totals for every strategy.
Core rules
- Use the registered version's scorecard and reference guide. v2.1 and v3 have different strategy sets, point values, evidence expectations, and possibly different thresholds; the reference guide explains applicability and verification.
- The scorecard is the scoring authority. Each strategy has a point value, applicability rules, and required documentation. Required strategies/prerequisites must be satisfied before star thresholds are meaningful.
- In v2.1 scorecards, common thresholds are 90 points for 1 star, 105 for 2 stars, and 125 for 3 stars out of 144. v3 uses its own scoring structure; confirm thresholds in the v3 materials rather than assuming v2.1 values carry over.
- Track points by strategy, not by category alone. Keep a point ledger with strategy ID, claimed points, owner, evidence type, and review status. Documentation can include plans, photos, policies, purchase records, maintenance logs, and surveys.
- Applicability matters: a strategy that fits a new-construction project may not fit an existing leased space. If a strategy is not applicable, follow the scorecard's rules rather than silently claiming or deleting it.
Worked example
An existing office registered under v2.1 has 82 confirmed points and targets 1 star at 90. The team identifies: daylight/views strategy for 3 points, bike parking for 2, healthy vending for 2, and stair prompts for 1. The ledger shows 90 points, so the threshold is met only after required strategies are confirmed. If the vending policy is only a draft, that strategy stays unclaimed until signed and implemented.
Traps
- Using v3 guidance for a v2.1 project, or vice versa.
- Counting points before checking required strategies and applicability.
- Assuming every strategy applies to every project type or lease boundary.
- Submitting design intent as operational evidence.
- Forgetting to update the point ledger after a strategy is rejected.