ISI POLICIES

ISI PoliciesISI Policies

This document contains all policies related

to the use of the Envision® sustainable
infrastructure framework, including
policies related to Envision verification, the
Envision Sustainability Professional (ENV
SP) credential, and credential maintenance
program.

Updated May 2024

Released: September 12, 2018

Last Updated: March 1, 2022 [updated
Credential Maintenance Policies]
ISI POLICIES

History of Updates to ISI Policies since Envision v3 release

Date Description of Substantive Changes
September 2018 Fee Updates, Envision Framework Updates and Revisions, Trademarks, Minimum
Program Requirements, Envision v3, Credit Coversheets, Evaluation Criteria,
Credit Applicability,
October 2018 Addition of Credential Exam, inactivation of ENV SP credential, ENV SP renewal
fees,
March 2019 Update of Minimum Program Requirements, Registration Closure & Cancellation,
Roles, Non-Disclosure Agreement, Quality Assurance Checklist, Credits not
pursued and new credits, Verifier Anonymity, Verifier Guidance, and change of
award level
May 2020 Links added to Table of Contents
March 2022 Updated Credential Maintenance Policies;
May 2024 Inserted more direct and specific language, Referenced Credential Maintenance
Guidance Document, Removed Sunset Date, Clarified Registration Cancellation
Due to Inactivity, Expanded description of Roles (including File Owner and
Reviewer), Specified Verification Timelines, Updated Minimum Program
Requirements and quality expectations, Allowed more than two new credits for
second review, Confirmed Pathway A Post Construction Review may address
pending credits, new or revised credits from decisions made during construction,
and any changes to the scope or key design elements, Required attestation and
final as-built documents or similar
ISI POLICIES

Table of Contents

TABLE OF CONTENTS
INTRODUCTION....................................................................................................................... 1
THE ENVISION FRAMEWORK ........................................................................................................... 1

POLICIES ................................................................................................................................... 2

1.0 GENERAL....................................................................................................................... 2
1.1 UPDATES AND REVISIONS ................................................................................................... 2
1.2 TRADEMARK POLICY ............................................................................................................. 3

2.0 CREDENTIALING........................................................................................................... 4
2.1 ENVISION SUSTAINABILITY PROFESSIONAL CREDENTIAL ............................................... 4
2.2 CREDENTIAL MAINTENANCE ............................................................................................... 4

3.0 VERIFICATION AND AWARDS...................................................................................... 7

3.1 MINIMUM PROGRAM REQUIREMENTS AND PREREQUISITES ......................................... 7
3.2 PROJECT ELIGIBILITY ............................................................................................................. 9
3.3 PROJECT REGISTRATION .................................................................................................... 10
3.4 REGISTRATION CLOSURE & CANCELLATION ................................................................... 11
3.5 ROLES ................................................................................................................................... 12
3.6 INQUIRIES & INTERPRETATIONS ....................................................................................... 15
3.7 DOCUMENTATION REQUIREMENTS & CONFIDENTIALITY ............................................. 16
3.8 PROJECT SUBMISSION AND REVIEW................................................................................. 19
3.9 VERIFIER POLICY.................................................................................................................. 24
3.10 ADDITIONAL CREDIT REVIEW & APPEALS ........................................................................ 26
3.11 AWARDS POLICY ................................................................................................................. 28
ISI POLICIES

INTRODUCTION

The Institute for Sustainable Infrastructure (ISI) is a non-profit 501(c)(3) basedheadquartered in

Washington, DCthe District of Columbia, United States of America.

The Institute for Sustainable Infrastructure (ISI) provides infrastructure solutions tothat enhance the
human experience, deliver superior financial performance, and drive continuous environmental
improvement. ISI maintains and administers the Its leading tool, Envision Sustainable Infrastructure
Framework (Envision) which was the result of, results from a collaborative effort between
thecollaboration with the Harvard University Zofnass Program for Sustainable Infrastructure (formerly
at Harvard University),, the American Council of Engineering Companies (ACEC), the American Public
Works Association (APWA),) and the American Society of Civil Engineers (ASCE).

Envision is a framework that provides guidance to decision makers and project teams on how to
identify sustainable and resilient approaches to the planning, design, and delivery of infrastructure
projects.

ISI members include a variety of government agencies, companies, and individuals that useusing
Envision to develop more sustainable infrastructure worldwide. Projects world-wide. Envision
supported by the Envision framework have been completed orinfrastructure projects are currently
in progressunder development across the United States,U.S., Canada, Italy, Israel, and several other
countrieselsewhere.

THE ENVISION FRAMEWORK

There are six components ofthat comprise the Envision framework:

1. Envision Guidance Manual: The written framework.

2. Envision Pre-Assessment Checklist: An early-phase high-level pre-assessment.
3. Envision Online Scoresheet: The detailed online assessment tool and calculator.
4. Envision Sustainability Professional Credential: (ENV SP): Professional training in Envision
use.
5. Envision Verification: Independent third-party project review process.
6. Envision Awards: Recognition for qualifying verified projects.
ISI POLICIES

POLICIES

The latest ISI Policies areis available for download from the ISI website and on an Envision User’s
Individual Dashboard in the Resources section. The policies are updated as needed. . If you
previously downloaded a copy of this document, be sure to check the website often to ensure for
updates as the latest version of this document is being referencedwill always be online.

1.0 GENERAL

1.1 UPDATES AND REVISIONS

1.1.1 Policy Updates and Revisions [Issued 2018-09-12]

ISI reserves the right to update and change the policies articulated in this document.
Updates and changes shall apply immediately upon publicationISI’s publishing of the same.

1.1.2 Fee Updates and Revisions [Issued 2018-09-12, Updated 2019-03-08]

ISI reserves the right to change the fees associated with any of its programs, including, but
not limited to, membership fees, credentialing fees, verification fees, credential
maintenance fees, registration fees, and verification fees.etc. Changes to fees will not be
appliedapply retroactively. If ISI; meaning, if a fee has already been formally committed to a
fee in writing (e.g.,such as an accepted quoteproposal to an owner, published fees for a
training event fee, etc.) or a portion of the fee has already been paid for some aspect of the
Envision program, there will not be an adjustment accountingby ISI for the difference
between the original and the subsequent published fee.

1.1.3 Envision Framework Updates and Revisions [Issued 2018-09-12]

ISI reserves the right to revisemake revisions to the Envision Guidance Manual.
Updates/revisions to the Envision Guidance Manual shall take immediate effect but;
however, such changes will not be applied apply to projects retroactively to projects that
have indicated their intent to verify by registering the ; meaning, if a project. has already
completed the verification process, any changes to the requirements set forth in the
Guidance Manual will not impact those projects.
ISI encourages users of the Envision framework to accessuse the latest version of the
Envision Guidance Manual available from the ISI Dashboardonline as it is always the most
up-to-date version. Any major revisions – e.g., the launch of a new version of the Envision
Guidance Manual, will be communicated to users well in advance.
From time to time, clarifications to the Envision Guidance Manual, are published. These are
known as Credit Amendments, are published. Interpretations. Any published Credit
ISI POLICIES

AmendmentsInterpretations take immediate effect immediately but willare not be applied

retroactively to projects that have already submitted for the first review of verification.

1.2 TRADEMARK POLICY

1.2.1 Trademarks [Issued 2018-09-12]

ISI owns all rights to several proprietary trademarks, logos, and other graphic images,
including, but not limited to, the “Envision” logo, the “Institute for Sustainable
Infrastructure” logo, and the Envision verification trademarks (collectively, the “Marks).”)
and, pursuant to licenses from ISI, in the event a project team receivesyou receive an
Envision award, ISI has the right to grant you the limited right to use the Marks. The Marks
constitute valuable intellectual property held by ISI and their licensors and are protected by
law. UsersYou acknowledge and agree that any unauthorized use of these Marks
constitutes intellectual property infringement.
After ayour project has registered, or while ayour project is under Envision Verificationreview,
ISI may grant you the limited right to use the applicable Marks to indicate that you are
pursuing verification under the project’s pursuit of Envision Verification.
Project teamsprogram. You are prohibited from using the Marks in any manner that
indicates or implies (as determined by ISI in its sole and absolute discretion) that the project
has achieved, or will achieve, an Envision award at any level.
If aIn the event that your project earns an Envision award, then, subject to the terms and
conditions of this document, ISI grants theyou a non- exclusive, non-
sublicensablesublicenseable, non-transferable, revocable (atin the sole discretion of ISI),
royalty-free, limited license to use the applicable Marks and the level of Envision award
achieved, for the purposes of indicating the level of Envision award granted in relation to
the project.
All Marks must be used In connection with all use of the Marks, you agree to use the Marks
in accordance with all applicable laws, rules, and regulations in compliance, and you will
comply at all times with the latest version of any ISI Trademarks Policies. In addition, users
will respectPolicy(ies) as published by ISI and as may be updated from time to time, and
any other reasonable related standards associated with the use of the Marks as provided
by ISI in writing to you.
All rights not expressly granted herein are reserved by ISI and no license is granted
hereunder for the use of the Marks for any purpose beyond the uses set forth in this
section, or to any other intellectual property of ISI. UsersYou acknowledge and affirm ISI’s
ownership of the Marks and the validity and enforceability thereof, and you shall not
engage in or support any action, claim, or challenge that is inconsistent with the foregoing.
All use of the Marks and the goodwill associated therewith shall inure to the sole benefit of
ISI.
You acknowledge that the Marks and the goodwill associated therewith possess special,
unique, and extraordinary characteristics, which make difficult the assessment of monetary
ISI POLICIES

damages that ISI would sustain becauseas a result of your unauthorized use of the Marks.
RecognizingYou recognize that ISI would suffer irreparable injury by such unauthorized
use, and agree that injunctive and other equitable relief is appropriate in the event of a
breach by you of any of the terms of this policy. Such remedy shall not be exclusive of any
other remedies available to ISI, nor shall it be deemed an election of remedies by ISI.

2.0 CREDENTIALING

2.1 ENVISION SUSTAINABILITY PROFESSIONAL CREDENTIAL

2.1.1 Envision Sustainability Professional Credential Requirements and

Prerequisites [Issued 2012, Updated 2022-03-01]

To become an Envision Sustainability Professional (ENV SP), a personan individual must

take ISI’s
official ENV SP training, either online or facilitated by an approved Envision trainer, and
pass an online exam, either online or, in special circumstances, in-person.. An ENV SP must
remain in good standing through the ongoing credential
maintenance. There are no other requirements or minimum qualifications to become an
ENV SP.

2.1.2 Credential Exam [Issued 2018-10-01]

The exam may be attempted up to three (3) times. Once an exam has started, it must be
completed within 72 consecutive hours. The exam is open book and is comprised of
multiple-choice questions. A passing grade is 75% or higher.%.
If a passing grade is not earned after three exam attempts, the ENV SP training must be
retakenre-taken, and all applicable fees to re-take the training and exam areis the
responsibility of the applicant.

2.2 CREDENTIAL MAINTENANCE

2.2.1 Credential Maintenance Guidance Document

ISI has published a Credential Maintenance Guidance Document for ENV SP credential
holders that contains important information for maintaining the Envision Sustainability
Profession (ENV SP) credential. The document can be found on the Individual ISI Dashboard
under Resources, Credentialing Resources.
ISI POLICIES

2.2.12.2.2 Inactivation of ENV SP Credential [Issued 2018-10-01]

The ENV SP credential is valid for one1 year. On the first anniversary afterof earning the
credential, the credential maintenance period begins. If the credential is not maintained
per the required renewal fees and completion of education hours, the credential enters a
grace period of six months before it expires. During these six months,expires. Credential
holders will be listed as “inactive” on the ISI website but, and may no longer use the “ENV
SP” designation. After the six months, if the credential maintenance is not satisfied, the
credential will expire.

2.2.22.2.3 Renewal Fees [Issued 2018-10-01, Updated 2022-03-01]

Envision Sustainability Professionals are responsible for the renewal fee at the beginning of
theirthe reporting period. Payments will be accepted by credit/debit card via the ISI
website. Submitted payments cover renewal of the credential for the coming year. For
example, if a renewal fee is submitted on time, on the first day of the reporting period, on
June 1, 2020, the credential is active until June 1, 2021. During this one1-year period the
ENV SP has access to online credential maintenance courses.

Each paid renewal fee supports the purchase of continuing education courses from ISI’s
website. The renewal fee serves as a subscription to available prescribed and elective
courses found in the ISI All Courses library online. Active and Inactive ENV SPs will not be
charged additional course fees to complete online courses designated as prescribed or
elective. Premium courses and specialty training require additional fees.

Renewal fees cannot be used to offset the purchase of any of the following, including, but
not limited to: membership fees, registration or verification fees,; credential training (online
or in-person),); exams,; credential maintenance renewal fees; premium courses, or
specialty training.

2.2.3 Continuing Education Credit [Issued 2018-10-01, Sunset on 2022-03-01]

—Intentionally blank—

2.2.4 Past Due [Issued 2018-10-01, Updated 2022-03-01]

Credential holders will have a 6-month grace period in which to renew their credential,
which
which starts after the reporting period has ended. While you will be able to earn hours
during this
during this time, your reporting period does not change.

For example, if an ENV SP’s renewal period is June 1, 2020 – June 1, 2021, the credential
holder will be past due on June 2, 2021. The grace period becomes June 2, 2021 –
December 1, 2021. Regardless of when the credential is renewed within the 6-month grace
ISI POLICIES

period, the reporting period remains the same. After renewal, the next reporting period
becomes June 1, 2021 – June 1, 2022; all renewal fees and hours will be due on June 1
regardless of when the last renewal was submitted. If the credential holder doesn’t report
enough hours and successfully renew by the end of the grace period, the credential will be
rendered “expired”.

Example Reporting Period with Grace Period

Reporting Next reporting Next reporting
Reporting Grace period end
period start period start period end
period end date date
date date date
June 1, December 1, June 1,
June 1, 20242021 June 1, 20242021
20232020 20242021 20252022

2.2.5 Self-Reported HoursHour Reviews [Issued 2018-10-01, Updated 2022-03-01]

All self-reported hours are subject to ISI approval. Self-reported hours will display as
“pending” for a maximum of four4 weeks (28 days) while ISI review is occurring.

2.2.6 Failure to Comply [Issued 2018-10-01]

Each Envision Sustainability Professional is responsible for demonstrating full compliance

with credential maintenance guidelines. Unsupported, misstated, or fraudulent reporting
of education hours is cause for action by ISI and may be grounds for disciplinary action, up
to and including revocation of the ENV SP credential.
Failure to fulfill and/or report the required education hours for the credential maintenance
reporting period will result in inactivation of the Envision credential. Failure to submit the
required renewal fee for the credential maintenance reporting period will result in
inactivation of the Envision credential.

2.2.7 Waivers/Extensions [Issued 2018-10-01, Updated 2022-03-01]

If unforeseen circumstances prevent the credential holder from being able to complete
credential maintenance within the one1-year reporting period plus six-month inactive
period, one may request a waiver or extension.

Situations that could be recognized by ISI as warranting a waiver or extension include: long
term unemployment,; military deployment,; or health problems. This list is not exhaustive
nor do these circumstances guarantee a waiver or extension. Written requests must be
received at least 30 days before the end of the reporting period. ISI reviews requests on a
case-by-case basis and only grants waivers or extensions in situations where the ENV SP
was prevented from completing credential maintenance.
ISI POLICIES

2.2.8 Reinstatement [Issued 2018-10-01]

To reinstateregain a credential after expiration, one must apply, register, train, and retest
as a new candidate. Such individuals are responsible for all applicable fees.

2.2.9 Maintenance Renewal Closure [Issued 2018-10-01]

ISI retains the right to close the credential maintenance portal and course library at any
time, for any reason, and without notice. The closure of the portal means that no education
hours may be tracked, and no renewals may be submitted.

3.0 VERIFICATION AND AWARDS

3.1 MINIMUM PROGRAM REQUIREMENTS AND PREREQUISITES

3.1.1 Compliance with Minimum Program Requirements [Issued 2018-09-12, Updated

2019-03-08]

Project teams must demonstrate compliance with the Minimum Program Requirements
that were in place at the time of project verification. registration. Project teams may
voluntarily elect to demonstrate compliance with a revised version of the Minimum
Program Requirements rather than the version of such requirements (if any) that existed at
the time of project registration. Minimum Program Requirements are contained in the
Guide to Envision Verification for Applicants.
The following ISI reviews each project submission prior to sending it to the verifier to ensure
it meets the Minimum Program Requirements must be met by all projects prior to submitting
for verification:
1. The project team must acknowledge. Projects that they have reviewed the Guide to
Envision Verification for Applicants, the ISI Policies, and all relevant Credit
Amendments available on the ISI website.
2. The project team must provide confirmation that the project meets the Envision
prerequisites which are a series of environmental, social, and governance (ESG)
safeguards. Refer to Policy 3.1.3.
3. All required fields about the project must be completed in the Envision Online
Scoresheet. Refer to the Guide to Envision Verification for Applicants.
4. The project boundary and scope must be consistently applied across all credits.
5. Project teams must use the ISI coversheet templates available on the ISI website. A
coversheet narrative must be provided for each criterion and each criterion must
be addressed separately. Refer to Policy 3.7.2.
6. The project team must select a level of achievement, Not Applicable, or zero (if no
level of achievement is being pursued) for all 64 credits in the Envision Online
Scoresheet.
ISI POLICIES

7. A credit submittal (i.e., credit coversheet and supporting documentation) must be

provided for each credit being pursued, including credits being pursued as Not
Applicable. Every credit submittal must be stand-alone. Refer to Policy 3.7.1.
8. Credits pursued as Not Applicable are appropriately justified. Refer to Policy 3.7.5.
9. All evaluation criteria and associated documentation guidance relevant to the
pursued level of achievement must be addressed by the credit submittal for all
credits pursuing a level of achievement. Refer to Policy 3.7.4.
10. All supporting documentation must be in in PDF format. All pertinent sections of
supporting documentation must be highlighted and/or annotated. All coversheet
references to supporting documentation must cite specific and appropriate page
numbers. Refer to Policy 3.7.3.
11. Credit submittals for Innovate or Exceed Credit Requirements credits address one
or more of the identified criteria options.
12. All credits deemed pending must identify and describe pending documentation and
provide supporting documentation to show the criteria will be met during the Post-
Construction Review. Refer to Policy 3.8.11.
13. Project registration fees must be paid, and verification fees are due in full prior to
the return of the First Review to the project team. Refer to Policies 3.3.2 and 3.8.8.
14. The Project Leader and/or Lead ENV SP must conduct a final quality assurance
review of the submission and complete the Verification Submittal Quality Assurance
Checklist. Refer to Policy 3.8.1.

To ensure the project meets the Minimum Program Requirements, ISI will review project
submissions prior to assigning a Verification Team. Project contacts will be notified if the
project doesdo not meetcomply with the above requirements and will be notified by ISI and
required to address any issuesgaps before moving forward with the verification processthe
project is verified.

3.1.2 Minimum Program Requirements Updates and Revisions [Issued 2018-09-12,

Updated 2019-03-08]

The Minimum Program Requirements for any of ISI’s programs may be revised and
updated from time-to-time. Any revisionsMinimum Program Requirements take immediate
effect and, unless otherwise indicated, are not applied retroactively.

3.1.3 ProjectProgram Prerequisites [Issued 2018-09-12, Updated 2019-03-08]

While applicants are not required to pursue specific credits in the Envision framework (i.e.,
there are no credit-based prerequisites for Envision Verification. However,verification),
projects must attest to the followingadhering to a number of environmental, social, and
governance (ESG) safeguards: as contained in the Guide to Envision Verification for
Applicants.
• Documentation provided to ISI for review is accurate and true
ISI POLICIES

• Strict adherence to all applicable international, national, state/provincial/territorial,

and local health and safety laws and regulations
• Strict adherence to all applicable international, national, state/provincial/territorial,
and local environmental laws and regulations
• Strict adherence to all applicable human rights, labor laws, and regulations
• Development is legally permitted
• No illegal resettlement
• No violations involving rights of indigenous peoples
• No bribery, corruption, or anti-competitive behavior has taken place by any of the
owners and firms associated with the project
• No endangered or critically endangered plant or animal species on the were
negatively impacted without all reasonable efforts to mitigate
• No child labor
• No forced or compulsory labor

Project Project teams must demonstrate compliance with the version of the prerequisites
that were in place at the time of project registration. Project teams may voluntarily elect to
demonstrate compliance with a revised version of the prerequisites rather than the version
of such requirements (if any) that existed at the time of project registration.

3.1.4 Program Prerequisites Updates and Revisions [Issued 2018-09-12, Updated 2019-03-
08]

The Project Prerequisites for any of ISI’s programs may be revised and updated from time-
to-time. Any revisionsPrerequisites take immediate effect and, unless otherwise indicated,
are not applied retroactively.

3.2 PROJECT ELIGIBILITY

3.2.1 Project Type [Issued 2018-09-12]

Envision can be applied to is a holistic sustainability framework for all types and sizes of
both public and privatephysical infrastructure. This includes, but is not limited to: airports,
bridges, dams, landfills, levees, parks, power generating stations, pipelines, railways,
streetcars, stormwater management systems, water treatment plants, and other types of
infrastructure. While initially developed for use in the United States and Canada, the
Envision framework can be applied to projects anywhere in the world.components that
make up civil works.
Envision is not intended to evaluate interior, conditioned, buildings with the primary
purpose of human occupation, such as offices, schools, single family homes, or multi-unit
residential buildings. However, buildings may be included within the boundary of an
Envision project if they are associated with the infrastructure being verified. Envision is not
designed to verifyevaluate human-occupied, interior conditioned buildings as stand-alone
projects, but can be used in conjunction with building rating systems. Envision is also not
ISI POLICIES

designed to evaluate non-physical infrastructure such as policies, programs, or master

plans, althoughthough some of the documentation requirements for Envision credits could
be supported through documents related toinclude policies, descriptions of programs, and
information contained in master plans.

3.2.2 Project Phase [Issued 2018-09-12]

Project teams may select from two different verification options: Pathway A: Design + Post-
Construction or Pathway B: Post-Construction. Pathway A projects may not project may be
submitted for Envision Verification before verification at or after 95% design completion
unless special permission has been granted in writing by ISI. Pathway B , meaning all major
design decisions have been made, though project teams may indicate their intention to
pursue verification by registering their project at any earlier point in the project timeline
(e.g., before it reaches 95% design completion).
Projects may not be submitted for Envision verification before 95% construction
completion.design completion has been reached unless special permission been granted in
writing by ISI.
Furthermore, projects may not be submitted for Envision verification once they have been
fully constructed and operational for more than three (3) years unless specialspecially
permission has been granted in writing by ISI.

3.3 PROJECT REGISTRATION

3.3.1 Project Registration [Issued 2018-09-12]

In order to participate in the Envision verification program, a project team must first
register thea project with ISI. Registration is the process whereby project teams create an
Online Envision Online Scoresheet (i.e., the project application which includes the overview
and scorecard, details, team members, and file uploads) on the ISI website,
provideprovides basic information about the project (refer to the Guide to Verification for
Applicants) and remitremits the applicable project registration fee (refer to the fee table in
the Guide to Verification for Applicants). If project teams are unable to access or use the
online platform, alternative arrangements can be made with ISI.

3.3.2 Payment of Registration Fees [Issued 2018-09-12]

The project registration fee is a flat fee due within 30 calendar days from the date of
registration and prior to the project submitting for Envision verification (whichever comes
first). The current fees are listed in the Guide to Verification for ApplicantsAppendix E.
Fees may be remitted to ISI by credit card at the time of registration or by check; however,
ISI reserves the right to not fully process the registration for any project or provide any
services to the project team until payment has been received in full. If payment is not
received within 30 calendar days after a project is registered, such registrations may be
cancelled at the discretion of ISI.
ISI POLICIES

3.3.3 Registration Timeline [Issued 2018-09-12]

Projects can register any time during project development but are required to register at
least two weeks before submitting for submitting for Envision verification. This timeline
ensureshelps to ensure ISI has sufficient time to deliver pre-verification communications
and/or services to the project team., review the project to ensure it meets the Minimum
Program Requirements, and hire a third-party verifier to conduct a review of the project.
Failure to register a project at least two weeks in advance of submission may result in
delays to the verification timeline.

3.4 REGISTRATION CLOSURE & CANCELLATION

3.4.1 Registration Closure [Issued 2019-03-08]

ISI retains the right to close registration for Envision verification at any time, for any reason,
and without notice. Such closure will generally occur when a new version of the Envision
framework is released. The closure of registration means that no new projects may register
under the previousthat version of the Envision framework. The closure of registration is
effective immediately upon the date announced by ISI (12:00 am eastern standard time).

3.4.2 There is noRegistration Closure Sunset Date for anyRegistered Projects

[Issued 2018-09-12, Updated 2019-03-08]

Closure of registration for a version of Envision version. However, ISI will work with project
teamsshall not impact the status of previously registered projects. Projects that are
registered under previous versionsa version that is subject to set reasonable expectations
for completing the project’sclosure will be allowed to proceed through the Envision
verification process. If a project team fails to update ISI for over a year, the project may be
cancelled at ISI’s discretion. until the established sunset date for the version. The sunset
date for any version shall occur no sooner than two (2) years after the close of registration
for that version.
Projects registered to pursue verification under a version of Envision subject to closure
must complete the verification process within two (2) years after the registration closure
date unless special permission (granted only in exceptional cases) has been provided by ISI
in writing. Failure to complete the verification process within this timeframe could result in
the project having to re-register under a new version of Envision. No fees paid to ISI will be
refunded in this event.

3.4.3 Registration Cancellation After Sunset Date [Issued 2018-09-12, Updated 2019-03-08]

After the sunset date has passed, ISI will no longer allow new projects to register under this
framework version nor accepting new verification applications from projects registered
under this version. All project registrations associated with projects for which a verification
application has not been submitted are cancelled.
ISI POLICIES

3.4.43.4.2 Registration Cancellation by Project Teams [Issued 2018-09-12]

Projects that are registered to pursue Envision verification may cancel their registration at
any time prior to submitting for verification; however, registration fees paid or owedowing
to ISI are non-refundable and non-transferrable, unless permitted by . Projects that have
begun the verification process may also elect to discontinue the process at any time;
however, verification fees paid or owing to ISI. are non-refundable and non-transferrable.

3.4.53.4.3 Registration Cancellation Due to Inactivity [Issued 2018-09-12]

After Subsequent to registering a project, a with ISI, project teamteams shall maintain
sufficienta level of activity and communication to demonstrate they intenddesigned to
submit the affect a complete project submission for Envision verification. This
includesProject teams shall remain in periodic contact with ISI with updatesto inform ISI of
progress being made or to update ISI on submission timelines.the date by which the
project will be submitted for verification. ISI reserves the right to cancel any registered
project that remains inactive or unresponsive, as determined solely by ISI.

3.4.63.4.4 Effect of Registration Cancellation [Issued 2018-09-12]

Any projects listed as “registered” on the ISI website will be removed from this listing upon
cancellation.
No refunds of any fees with be provided in the instance that a project registration is
cancelled in accordance with these terms, no refunds of any fees will be provided.
If Envision verification is sought in relation to a project for which registration is cancelled,
the project must be re-registerregistered as a new project under the current Envision
framework. If, at the time of registration cancellation, no applicable framework version is
availableremains open for registration, such projects areproject is ineligible for
Envisionconsideration under the verification program.

3.5 ROLES

3.5.1 Project Team

The project team includes major decision makers involved in the project, as well as those who
act as primary advisors, consultants, contractors, or specialists on behalf of decision makers.
This includes the entity or entities responsible for completing the Envision application.

Key members of the project team include the owner, lead designer(s), and lead construction
contractor(s). Lead designers and lead construction contractors include all entities directly
contracted to the owner to perform the work.
ISI POLICIES

3.5.2 Project Leader

The individual who initially creates the project’s Online Scoresheet is automatically
designated the Project Leader. The Project Leader is responsible for representing the project
team and has the authority to register the project and submit the project for Envision
Verification. They, along with the Lead ENV SP, are the project’s key points of contact and will
be included in all communications from ISI regarding the project.
It is the responsibility of the Project Leader to ensure any information provided by ISI is
conveyed to other project team members. The Project Leader or Lead ENV SP may attest
meeting the minimum program requirements through completing the Verification
Submission Quality Assurance Checklist. They do not need to be an Envision Sustainability
Professional (ENV SP), but they must have an ISI account.
This designation may be changed at any time during the verification process when the
current Project Leader or File Owner’s Admin selects another project team member on the
Envision Online Scoresheet.
If the Project Leader leaves the project before Envision Verification is complete, they or the
File Owner’s Admin must designate a new Project Leader online and notify ISI by email of the
change.

3.5.13.5.3 Lead Envision Sustainability Professional (Lead ENV SP)Envision

Sustainability Professional [Issued 2018-09-12, Updated 2019-03-08]

At least one Envision Sustainability Professional (ENV SP) in good standing (i.e., “(“active”)
must be assigned onassociated with the Envision Online Envision Scoresheet in order for a
project to submitbe submitted for verification. The individual designated as the Lead ENV
SP iswill be responsible for ensuring a high-quality submission in accordance with current
ISI guidance, policies, credit amendments,interpretations etc. This individual has the
authority to register the project., and submit the project for Envision Verification and is
qualified to complete the must sign off on the Verification Submittal Quality Assurance
Checklist. They, along with the Project Leader, are the project’s key point of contact and will
be included in all communications from ISI regarding the project.
The Lead ENV SP may be changed by any team member that has the right to edit the
project. The Lead ENV SP associated with the Envision Online Scoresheet must maintain
their ENV SP credentialremain active for the duration of the project’sproject verification
process.

3.5.4 File Owner and Admin

The File Owner is a field in the Envision Online Scoresheet that connects a project to an
organization within the ISI system. The File Owner is automatically assigned as the
organization of the Project Leader upon the creation of a new project. More than one File
Owner may be added to a project. The involvement of the File Owner will be acknowledged
on ISI’s website.
ISI POLICIES

3.5.2 The AdminProject Leader [Issued 2018-09-12, Updated 2019-03-08]

The individual who initially creates the project will be identified by ISI as the project leader.
The project leader is provided the authority to select members of the project team and to
delegate certain tasks to individual team members. The project leader will receive all
formal communications from ISI regarding the project. It is the responsibility of the project
leader to transmit any information provided by ISI to any or all project team members. The
project leader may be substituted at any time through the Online Scoresheet controls.
He/she does not have to be an Envision Sustainability Professional but must have an
account with ISI to be a project leader.
ISI must be provided with current contact information for any designated File Owners
automatically receive Read-Only access to the project. They also have the authority to change
the project leader. At least one File Owner must be an ISI member organization to receive the
discounted verification fee.

3.5.5 ISI Point of Contact

Registered projects are assigned an ISI Point of Contact who is the main liaison for the project
team. The Project Leader or Lead ENV SP may direct questions related to the verification
process, the use of online tools, specific credits, etc. to their designated ISI Point of Contact.

3.5.6 Verification Team

The Verification Team is responsible for conducting a thorough review of projects

submitted for third-partyduration of time that the project is registered or maintains
Envision verification. The Verification Team includes one or more Verifiers and a Reviewer.
If a project changes hands, the former project leader must notify ISI by email of the
transfer.

3.5.33.5.7 Verifier [Issued 2018-09-12, Updated 2019-03-08]

ISI engagescontracts trained Envision Qualified Companies under contractverifiers in order

to become Verifier Companies and trains qualified employees of the company to become
Verifiers. This ensuresensure practicing professionals are engaged in the independent
peer-review verification process. Verifiers must meet certain qualifications as designated
by ISI and maintain satisfactory performance.. The role of the verifier is to independently
assess and validate the sustainability aspects of infrastructure projects against the Envision
framework. The Verifier role may be composed of one or more Verifiers as designated by
provide a rigorous, transparent, third-party review of the project as submitted by the
Verifier Companyproject team online.
ISI POLICIES

3.5.43.5.8 ISI Reviewer [Issued 2019-03-08]

An ISI-designated Reviewer worksWorking alongside Verifiers to conductcontracted third-

party verifiers, an ISI Reviewer will undertake documentation reviews of infrastructure
projects seeking Envision verification. The ISI Reviewer may beis an internal ISI staff
member or highly skilled Verifier that was selected for the role by ISI. The Reviewer is
responsible for directly liaising with Verifierthird-party verifiers to ensure timely, consistent,
and high-quality project verifications. The ISI Reviewer also ensures the correct application
of ISI guidance and policies on the part of both the verifier and project team.

3.6 INQUIRIES & AMENDMENTSINTERPRETATIONS

3.6.1 Credit or FrameworkRating System Inquiries [Issued 2018-09-12]

Project teams may encounter challenges in applying credit requirements to their projects.
The ISI project manager assigned to registered projects is available to respond to credit or
rating system inquiries. Project teams may obtain clarifications on the interpretation
ofinformation regarding how credit requirements are interpreted by ISI as they pertainit
pertains to their specific project. Once registered, the project’s assigned ISI Point of Contact
is available to respond to inquiries related to credit interpretations, framework features (i.e.,
pending, applicability, baselines, etc.), or verification process.
Unregistered projects may submit inquiries through . However, inquiries from registered
projects will take priority over those not registered.
ISI Responses to inquiries, whether provided in-person, received by email, or verbally,
shallphone from an Envision user, an ISI staff member or the ISI project manager assigned
to a given project are not be deemed final or necessarily considered precedent-setting. ISI
reserves the right to revise or adjust responses to any inquiries and may be interpreted
differently by the Verification Team reserves verifier assigned to the right to make final
decisions regarding project verification reviews.project. ISI aimsdoes its best to
offerprovide a reasonable level of assurance as to ; however, ISI is not able to guarantee
the accuracy of their responses but cannot ensureresults of a review for a specific
outcomes for project team inquiries or guarantee verification review resultscredit.

3.6.2 Credit AmendmentsInterpretations [Issued 2018-09-12]

Inquiries sent to ISI may lead toresult in the publication of formal Credit Amendments
whichInterpretations (CIs). CIs are precedent-setting decisions rulings that are applicable to
all projects seekingpursuing Envision verification. All current Credit Amendments are
accessible from the Resources section of the ISI Dashboard.
Project teams must comply with all relevant Credit Amendments to submit for Envision
Verification. Project applications doCIs may not have to comply with amendments published
after the project was submitted for verification. These amendments do notapply
retroactively affectto projects that have already completedbeen verified using the Envision
ISI POLICIES

Verificationframework, even if they could alter the CI would result in a material change to
the project’s score or Envisionoverall award level.
Current CIs are available on the ISI website. Project teams must familiarize themselves with
any applicable CIs prior to submitting a project for verification.

3.7 DOCUMENTATION REQUIREMENTS & CONFIDENTIALITY

3.7.1 Credit Submittals [Issued 2018-09-12]

A credit submittal consists of a credit coversheet and supporting documentation. A credit

submittal is required for every credit within the Envision framework, being pursued by the
project team, including credits being pursued as Not Applicable. To submit a project for
verification, the project team must upload all credit submittals to the Envision Online
Scoresheet, unless otherwise specified or arranged with ISI. The credit coversheet must be
provided separately from the supporting documentation. All credit coversheets and
supporting documentation must be in PDF format. The Envision verification program is an
online, documentation-based verification program. To complete a project verification,
credit submittals must be provided for every credit in the Envision framework being
pursued by the project team, even credits for which N/A (not applicable) is being sought. A
credit submittal consists of a credit narrative or credit coversheet and supporting
documentation.

3.7.2 Credit Coversheets [Issued 2018-09-12]

ISI has developed a set of credit coversheets for the Envision framework. Project teams
pursuing verification must use ISI’s credit coversheet templates. Coversheets must be
submitted for verification in English unless otherwise specified or arranged with ISI. Credit
Coversheets can be accessed from the Resources section of the ISI Dashboard, from the
Files section of the Envision Online Scoresheet, or requested from the ISI Point of Contact.

3.7.3 Supporting Documentation

Project teams must provide supporting documentation as evidence of all claims made in the
coversheet for all evaluation criteria required for the desired level of achievement. The
project team must clearly highlight and/or annotate within the supporting documentation to
clearly direct the Verifier to relevant information. Detailed references to documentation and
specific page numbers must be cited within each credit coversheet. Where possible, the
project team must submit documentation in English unless otherwise specified or arranged
with ISI.

3.7.33.7.4 Evaluation Criteria and Documentation [Issued 2018-09-12]

For Each credit, in the Envision framework identifies has a series of evaluation criteria,
denoted with letters, and associated documentation guidance,. Evaluation criteria are
ISI POLICIES

denoted with letters and documentation guidance is denoted with numbers. beneath the
evaluation criteria. Project teams must fulfill all required evaluation criteria and address all
associated documentation guidance for the level of achievement being sought. The
numbered items provide ISI’s best guidance as to the type(s) of documents that could best
demonstrate achievement for the evaluation criteria.
Specific documentation guidance varies from credit to credit. Usually, however,
documentation consists of policies, meeting minutes, plans, drawings, specifications,
calculations, maps, and other related media (collectively, “documentation”). Documentation
provided as evidence of compliance for one or more evaluation criteria must be
highlighted, annotated or in some way made easily accessible to the verifier who will be
reviewing the project. Specific references to supporting documentation must be made in
the credit coversheet for each credit. Where possible, documentation should be submitted
in English. If this is not possible, other arrangements can be made with ISI.

3.7.43.7.5 Credit Applicability [Issued 2018-09-12]

Whether or Only whole credits may be deemed “not a credit is applicable is only relevant to
the entire credits. Deeming”. ISI does not allow individual evaluation criteria or specific
documentation guidance ‘Not Applicable’ is not permitted. A credit submittal, including credit
coversheet and supporting documentation, must be provided for all credits pursued as Not
Applicable.

Projects teams must provide an acceptable justification for deeming a credit ‘Not
Applicable’. The following are NOT acceptable reasons:
• The scope of a contract does not address the issue;
• Achieving the credit requirements is deemed within a credit to be too expensive,
difficult, or time-consuming;
• Local laws or regulations prohibit meeting the requirements;
• Those conducting the Envision assessment do not have decision-making
authority; or

Stakeholders have indicated that the issue is not a priority.deemed “not applicable”.

3.7.6 Confidentiality

Other than the project name, location, Envision Award level, and project description, all project
information and documentation provided on the Envision Online Scoresheet will be treated as
confidential. Confidential information shall not be shared with any external parties, outside
of ISI and the Verification Team, unless the project team provides permission for its use. The
Envision Online Scoresheet is only available to the Verification Team after submitting for
verification. Verifiers and Reviewers are under strict contractual requirements to not disclose
or retain project information and documentation.
ISI POLICIES

Project file owners and members of the project teams designated online may continue to
access the Envision Online Scoresheet, including all project information and documentation.
All requests to view the Envision Online Scoresheet must be directed to and processed by the
Project Leader and/or Lead ENV SP. Former members of the project team that are no longer
associated with the project online will not have access.

3.7.53.7.7 Classified Information and Export Controls [Issued 2018-09-12]

ISI does not wish to receive classified information shall not be submitted through the
Envision Online Scoresheet. AllAny information or material uploaded to the ISI website or, in
rare cases sent to ISI via email or file transfer, mustwill be deemed not to be
unclassifiedclassified. Further, by submitting information, project team members represent
that such information, be it submitted in connection with aan Envision verification
application or otherwise, is not controlled for export under the International Traffic in Arms
Regulations, 22 C.F.R. Part 120 et seq., or the Export Administration Regulations, 15 C.F.R.
Part 730 et seq.

3.7.63.7.8 Non-Disclosure Agreements Agreement [Issued 2018-09-12, Updated 2019-03-

08]

ISIISI and/or the contracted third-party verifier will sign a Non-Disclosure Agreement (NDA)
or confidentiality agreement upon request. Given ISI’s policy requiring Verifier and
Reviewer anonymity, ISI’s concurrence with such agreements shall cover all ISI staff and
others involved in the verification process. Such an NDA or confidentiality agreement is
required to be provided to ISI by the project team to ISI. Note that an NDA or confidentiality
agreement being in place for a given project does not negate: Policies 13.11.2 and 3.11.3.
Requesting ISI and/or its verifier(s) to sign an NDA or confidentiality agreement may result
in delays to the verification timeline.

3.7.73.7.9 Transfer of EnvisionRegistration or Online Scoresheet File

Ownership [Issued 2018-09-12, Updated 2019-03-08]

One or more File Owners of a project’s Additional information may be required by ISI to
substantiate the transfer of registration or Envision Online Scoresheet may be designated by
the Project Leader and/or Lead ENV SP. In the case of a dispute, ISI may require additional
information be provided to confirm the appropriateness of any File Owners assigned to a
project. The nature of thisownership. Such information dependsmay vary depending on
the specific project circumstances. specific to the project type and the means by which the
project is transferred. ISI reserves may, in its sole discretion, require the rightsubmission of
such additional information prior to decide what additional stepsgranting any subsequent
owner access to take after any decisions are made regarding appropriateness of File
Owners.project information.
Project teams that submit for verification retain access to their project files and
documentation. ISI will never share project files with anyone no matter the requester or
ISI POLICIES

authorization level. Requests to view any project documentation, including coversheets and
supporting documentation must go through the Project Leader.

3.8 PROJECT SUBMISSION AND REVIEW

3.8.1 Project Submission [Issued 2018-09-12]

Upon submission of a project for verification, ISI will first conduct a review of the
submission to ensure it complies with all Minimum Program Requirements. If one or more
Minimum Program Requirements are not satisfied, ISI will notify the project team and
request that any deficiencies be met before the project is resubmitted for review.

3.8.23.8.1 Quality Assurance [Issued 2018-09-12, Updated 2019-03-08]

Prior to submitting the commencement of a review of a project for reviewby ISI, the project
Leader and/or Lead ENV SPteam must confirm thatacknowledge they have read and accept
the project submission complies with minimum quality expectations, as described inmost up
to date policies, Guide to Verification for Applicants, Credit Interpretations, and other relevant
resources. This is done by submitting a signed copy of the Verification Submittal Quality
Assurance Checklist.
Upon submission, ISI will check to ensure compliance. ISI reserves which is available on the
right to return the submission to the project team. If returned, ISI will notify the project
team and request any deficiencies be addressed before the project can be resubmitted. ISI
website.

3.8.33.8.2 Project Verification [Issued 2018-09-12]

The requirements, schedule, and policies for an Envision verification will vary across the
twoEnvision verification pathways. ISI will strive to meet the timelines stipulated within our
project verification policies as they are set forth in this document. However, if ISI is unable
to meet these projected timelines, no project team shall be entitled to a refund of any
portion of the fees associated with registration, Envision verification services, and/or other
fees that have been remitted to ISI in relation to the Envision verification program.

3.8.43.8.3 Notice of Submission [Issued 2018-09-12]

ISI requests that the Project Leader or Lead ENV SP notify their designated ISI Point of
Contact about their intention to submit for Envision Verification at least two weeks in
advance. This advance notice allows for the assessment of ISI staff and Verification Team
availability.ISI requires two (2) weeks’ notice prior to the project being submitted for
verification. This two week notice period provides sufficient time for ISI to send the project
team a list of potential verification companies, the team to conduct a conflict of interest
check and to notify ISI of any potential conflicts, and for ISI to hire one of the remaining
verifiers from the list. Failure to notify ISI of the submission date at least two weeks in
advance, and failure to notify ISI of any changes to the submission timeline could result in
delays to the overall verification timeline.
ISI POLICIES

3.8.53.8.4 Verification Timelines [Issued 2018-09-12]

After a project has been submitted for Envision Verification, ISI strives to conduct a project
submittal quality assurance review and assign a verification team within seven calendar days
of project submission. Unless otherwise notified by the designated ISI Point of Contact, the
First Review Start Date will be seven calendar days after the date of submission.
ISI endeavors to conduct the complete the verification of a project pursuing verification
review according to the following timelines:

For Pathway A: Design + Post -Construction:

a) First Review: Returned to the project team within 60 calendar days of the First
Review Start Date.
b) Second Review (Optional): Returned to the project team within 30 calendar days of
submission for Second Review.
c) Post-Construction Review: Returned to the project team within 30 calendar days of
submission for Post-Construction Review.
The above schedule within 18 weeks. This timeline does not account forinclude any time
takenneeded by the project team to prepare the project application for First Review,
Second Review, or for re-submission during the design stage (if required), nor does it
account for the time between the final design review and the post-construction review.
ForISI endeavors to complete the review of a project pursuing verification Pathway B: Post-
Construction:
a) First Review: Returned to the project team within 60 calendar days of 12 weeks from
the First Review Start Date.
b) Second Review (Optional): Returned to the project team within 30 calendar daysdate
of submission for Second Review.
The above schedule. This timeline does not account forinclude any time takenneeded by
the project team to prepare the project application for First Review or Second Reviewfor re-
submission.

Should a review stage be delayed due to workload or holiday schedules, the designated ISI
Point of Contact will notify the Project Leader and Lead ENV SP immediately.

3.8.63.8.5 Project Completion [Issued 2018-09-12]

The Upon the completion of a project team may opt, the final score will be considered
“accepted” on the ISI website; however, ISI will provide the project team an opportunity to
acceptappeal one or more credit decisions or re-submit one or more credits for an additional
review (in cases where additional information is made available to potentially support a
higher level of achievement). The results of the First Review or submit for a Second Review.
ISI POLICIES

If accepting the results of the First Review, the Project Leaderappeals and/or Lead ENV SP
should contact the designated ISI Point of Contact for next steps.
If submitting for a Second Review, the project team shall revise and resubmit their
application. For credits being resubmitted, the Second Review will be based on the verifier
comments and overall general comment provided during the first review. New credits
submitted will only receive a single additional credit review.
Upon completion of processes could impact the overall score of the Second Review, the
Project Leader and Lead ENV SP will receive a score which may or may not result in an
Envision project and the project’s award. At this stage, the project team may opt to accept
the score as final, seek an appeal, or request an additional review.
ISI must receive notification of intent to pursue level. If an appeal or credit re-submittal for
additional review has not been made within 30 calendar days of project completion. If no
notice is received, the final credit scores and overall project score shall be considered final
unless ISI offers an extension.
Once an appeal or additional reviewdeemed conclusive, even if a Credit Interpretation is
complete,later released by ISI that would support the results shall be considered final with
no further opportunities to resubmit.
Pathway A: Design + Post-Construction projects require a Post-Construction Review after
95% construction completion to within 3 yearsacceptance of operation. The Post-
Construction Review could impact the project’s score and Envision award level. If it does,
this shall be considered the final score. Final scores cannot be retroactively impacted by
changes to ISI Policies,a denied credit amendments, or updates to the Envision framework
version.
Once a project has been fully completed verification, the verification process verified, it
cannot be repeated with the intent of increasing the finalre-submitted for verification in an
attempt to increase the overall score. This is so, even if new information is discovered that
could have benefitted the project when undergoingit was first submitted for third-party
verification. If aHowever, if an Envision verified project that previously completed
verification undergoes a significant upgrade such that it differs substantially from the
original project that was originally submitted for verification, it may apply for verification as
a separate new project.

3.8.73.8.6 Direct Contact with Verifier [Issued 2018-09-12]

Project teams may not communicate directly, or indirectly, by any means (e.g., phone,
email, in-person, etc.)) with the third-party verifier assigned to their project. If unless
facilitated and supervised by ISI. Project teams that make, or attempt to make, direct
contact with the verifier assigned to their project, this may result in the initiation of a new
verification process with a different verifier and the applicationbeing initiated, and an
assessment of additional fees, up to 100% of the verification fees quoted for the project.
ISI POLICIES

3.8.83.8.7 Verification Fees [Issued 2018-09-12]

Verification fees are determined based on the estimated total cost of the project being
submitted for Envision verification, the verification pathway selected by the project team
(e.g., Pathway A: Design + Post-Construction or, Pathway B: Post-Construction), and the
membership status of the submitting team.
To calculate the total cost of a project includes all the following:, costs associated with land
acquisition; eminent domain/expropriation fees; planning and feasibility studies;
architectural and engineering design; construction, including materials and labor; and
construction financing. Project teams must appropriately account for the total cost. The
total cost can should all be estimated but needs to be updated as the project proceeds
through verificationincluded.
In addition, ISI reservesmay calculate the right to adjust the Envision verification fees based
onat a premium rate if special requests, services, are made or circumstancesthere are
other special characteristics of the project or the submission itself that warrant doing
soneed to be accounted for (e.g., the language of submission, if a fast-tracked review
process is requested, if additional pre-verification creditpreliminary reviews, portfolio
discounts, etc.) are requested).

3.8.93.8.8 Payment of Verification Fees [Issued 2018-09-12]

Project verification fees are due in full prior to the First Reviewinitial project score being
returned to the team (e.g., withinby the verifier. Typically, this is between 45 and 60
calendar days of the First Review Start Date).after the project is submitted for verification.
To avoid any delays to the verification timeline, ISI recommends paying the verification fees
prior to submitting for Envision verification where possible.
Verification fees may be remitted to the Institute for Sustainable InfrastructureISI by check,
ACH, or wire transfer, or major credit card. For wire transfer details, please contact ISI.

3.8.103.8.9 Credits Not Pursued [Issued 2019-03-08]

Should a project team decide not to pursue a given credit(s), the verifier will not review
such credit(s), nor suggest that the team should pursue such credit(s), even if
documentation exists in other credits that suggest a level of achievement could be
attained. If at a later time during the verification process or subsequent to the conclusion
of the verification process the team wishes to have new credits assessed, see policy 3.8.10.

3.8.113.8.10 New Credit Submittals [Issued 2019-03-08; Updated 2020-12-20]

New credits are ones(e.g., credits that were not previously submitted by the project team
for First Review.review) will be allowed during the verification process as outlined below:
For projects pursuing verification Pathway A: Design + Post-Construction:
a) In addition to revisedNew credits, new (e.g., credits that were not previously
submitted by the project team for review) may be submitted for the Second Review
ISI POLICIES

or an Additional Review. Anyreview between the first and second design reviews,
though project teams are to limit the number of new credits submitted will only
receive a single review. to two (2) or otherwise pay the fee for additional credit
reviews.
b) New credits may be submitted for projects pursuing Pathway A in the post-
construction review stage if they are the result of construction-related decisions or
activities that were not known at the time of final design.
For projects pursuing verification Pathway B: Post-Construction:
a) In addition to revisedNew credits, new (e.g., credits that were not previously
submitted by the project team for review) may be submitted for the Second Review
or an Additional Review. Any review between the first and second reviews, though
project teams are to limit the number of new credits submitted will only receive a
single review.

3.8.11 Pending Credits

a) Deeming ato two (2) or otherwise pay the fee for additional credit Pending means
that the credit relies on documentation from the construction phase to
demonstrate that the desired level of achievement is met. Only Pathway A: Design +
Post-Construction projects can deem credits as Pending, and only during the
Design Review (i.e., First and Second Review). reviews.

A credit submittal, including credit coversheet and supporting documentation, must be

provided for all credits deemed Pending. To submit a credit as Pending, the project team
must identify and describe what pending documentation will be provided during the Post-
Construction Review and provide sufficient supporting documentation during the Design
Review to give the verifier confidence that the evaluation criteria and/or targeted level of
achievement could be met during the Post-Construction Review.

3.8.12 Post-Construction Review

BothNew credits (e.g., credits that were not previously submitted by the project team for
review) will not be allowed once the verification process has concluded, as outlined below:
For projects pursuing verification Pathway A: Design + Post-Construction and Pathway B:
Post-Construction projects are required to submit for a Post-Construction Review between 95% :
a) New design-oriented or pending construction completion to within 3 years in
operationcredits (e.g., credits that were not previously submitted by the project
team for review) may not be submitted for review after the conclusion of the
second design review.
For Pathway A: Design + Post-Construction, the Post-Construction Review will be limited to
credits submitted as Pending during the Design Review, new credits resulting from decisions
ISI POLICIES

made during the construction phase, and/or updates due to scope or design changes. These
credit submittals will only receive a single review with the option for Appeal or Additional
Review. If any changes were made to the scope or design, the Project Leader and/or Lead
ENV SP must provide ISI with documentation summarizing the changes and either:
1. Confirm that the changes would not lead to lower levels of achievement than verified
during the Design Review; or
2. Amend credit submittals where changes would lead to different outcomes (e.g.,
levels of achievement) than received during the Design Review.
b) ForNew credits (e.g., credits that were not previously submitted by the project team
for review) may not be submitted for projects pursuing Pathway A in the post-
construction review stage unless they are the result of construction-related
activities that were not known at the time of design. Generally, during a post-
construction review, the verifier will focus on credits marked as “pending” during
the design review stage as the purpose of the post-construction review is to
confirm that commitments made during design were carried out successfully
through construction.
For projects pursuing verification Pathway B: Post-Construction,:
a) New credits (e.g., credits that were not previously submitted by the project team for
review) may not be submitted for review after the conclusion of the review option
will be an iterative First and Second Review with the option for Appeal or Additional
Review.second post-construction review.
Upon submission for Post-Construction Review, regardless of whether Pathway A: Design +
Post-Construction or Pathway B: Post-Construction, the Project Leader and/or Lead ENV SP
is required to attest that the final project submission reflects the final constructed project.

3.9 VERIFIER POLICIESPOLICY

3.9.1 Verifier Selection [Issued 2018-09-12]

Verifiers are assigned at the sole discretion of ISI. All Verifiers must be active ENV SPs, trained
by ISI, with demonstrated expertise in sustainable infrastructure and employed by a Verifier
Company. Verifier Companies must be ISI members (i.e., Envision Qualified Company) and
sign a Professional Services Agreement with ISI. One or more Verifiers working for a Verifier
Company may collaborate in reviewing a project.
The Verifier role is carried by the individual. If a Verifier leaves a Verifier Company to join a
non-Verifier Company, they will have six (6) months to meet the requirements to be a Verifier
Company. If a Verifier Company has no Verifiers, they will have until the next ISI Verifier
Training opportunity to maintain their status.
Upon submitting for Envision Verification, the Project Leader and Lead ENV SP will evaluate a
list of eligible Verifier Companies and identify any conflicts of interest directly related to the
project. Conflicts of interest must relate to the project being verified (i.e., a listed Verifier
ISI POLICIES

Company has worked on the project in any capacity). Conflicts of interest cannot be based
on potential for market competition or assumed intellectual rights.
VerifiersOne (1) to two (2) weeks prior to a project being submitted for verification, ISI will
provide the submitting team with a short list of potential verifiers.
Submitting teams may not select their verifier from the selected Verifier Company will also
evaluate this list; rather, they are to inform ISI of any potential conflicts of interest and are
expected to decline(e.g., a proposed firm worked on the assignment ifproject in any
capacity) that exist. with any of the proposed verifiers.
ISI strives to assignedwill then choose from one of the remaining verifiers. Verifiers to
review the project within seven calendar days of project submissionare selected at the sole
discretion of ISI.

3.9.2 Use of Tools and Guidance Provided by ISI [Issued 2019-03-08]

ISI reserves the right to issue and update new tools and verifier guidance. Verifiers are
expected to ensure consistent, high-quality reviews that adhere to the latest guidance
provided by ISI as issued and updated from time-to-time.

3.9.3 Direct Contact with Project Team [Issued 2019-03-08]

Verifiers may not communicate directly, or indirectly, by any means (e.g., phone, email, in-
person, etc.)) with the project team regarding the project. Ifunless facilitated and
supervised by ISI. Verifiers that make, or attempt to make, direct contact with the project
team, this may result in the initiation of a new verification process with a different verifier
Company. This may also result in the revocation of the Verifier Company’s Professional
Services Agreement. being initiated at the verifier’s expense.

3.9.4 Scoring Disagreements [Issued 2019-03-08]

In instances where the verifier and the ISI Reviewer disagree on a level of achievement for
one or more credits and cannot reach consensus, ISI will intervene to make a decision and
such a decisionISI’s ruling will stand.

3.9.5 Project Confidentiality [Issued 2018-09-12]

ISI holds project information submitted for review to the highest standards of
confidentiality and also requires third-party verifiers and Verifier Companies to treat
project information as confidential. Verifiers are not permitted to discuss or otherwise
disclose project-specific information, including within their Verifier Company. Violation may
result in revocation of the Verifier Company’s Professional Services Agreement.

3.9.6 Verifier Anonymity [Issued 2019-03-08]

The verifier and Verifier Company shall not disclosepublicly advertise his or her role as a
verifier on a specific project in any forum or form whatsoever at any point during or
ISI POLICIES

following a project verification process, whether the project earned an Envision award or
not.
Verifiers may indicate they are Envision verifiers on their CVs/resumes, including the
number of projects verified.; however, specific projects verified may not be identified by
name,. If verifiers wish to include their verification work in CVs/resumes, they may identify
projects only by size, type, orand location at the state/province and country level. Any
further identifying characteristics may not be disclosed.

3.9.7 Suggesting Higher Performance than Submitted [Issued 2019-03-08]

The verifier may assess a higher level of achievement than submitted bywhere the project
team ifdocumentation presented support such. However, as it exposes ISI to risk, where
the credit coversheet and supporting documentation is not sufficient. However, to mitigate
risk to ISIassess a higher level of achievement, the verifier shall not suggest a higher level of
achievement be pursued by the project team if theresubmit credit submittal does not
provide enough evidencedocumentation to deem thesatisfy a higher level of achievement
met.

3.9.8 Assessing Credits not Submitted [Issued 2019-03-08]

To minimize As it exposes ISI to risk to ISI, verifiers may, the verifier shall not assess credits
that the project team has not pursuedsubmitted for verification. This is regardless of any
potential, even if the verifier should feel that the team could reasonably gain points for the
project team to attain levels of achievement on those unpursued creditsa particular credit
not submitted.

3.10 ADDITIONAL REVIEW & APPEAL OF CREDITSCREDIT REVIEW &

APPEALS

3.10.1 Additional Review Additional Credit Reviews for Previously Submitted

Credits Following Verification Completion [Issued 2018-09-12, Updated 2019-03-08]

The Project Leader and/or Lead ENV SP have the option to submit one or more credits for
Additional ReviewUpon completion of verification (e.g., after the Second Review and after
the Post-Construction Review of Pathway A (i.e., Third Review). An Additional Review
allowsthird-party verifier has completed their final review of a project during the design
review phase and/or post-construction review phase), the project team is presented with
the option or to modify a credit submittal or and re-submit newone or more credits (i.e.,
credits that were not previously submitted). If multiple credits will be submitted for the
Additional Review, they must be submitted simultaneously. Project teams may not submit
for both for an additional review and an Appeal.(e.g., if additional documentation is made
available to potentially support a higher level of achievement for one or more credits).
The Additional Review will be conducted by the same Verification Team as previously
assigned within 30 calendar days of submission. Once the Additional Review is complete,
ISI POLICIES

there are no further opportunities to request an Additional Review or Appeal during that
review period (i.e., Design Review or Post-Construction Review).
Unless an exception is provided by ISI, the option to requestThe opportunity to re-submit
credits for an additional review is only available for 30 calendar days. If additional time is
needed, the days after completion of verification. Each additional review may only apply to
a single credit; however, multiple credits may be re-submitted for an additional review
simultaneously.
The decisions are final once an additional review of a credit has been completed; no
further opportunities to re-submit the same credits are available.
New credits (e.g., credits that were not previously submitted by the project team must
submit a request in writing to their ISI Point of Contact listingfor review) will not be allowed
to be submitted once a verification review phase has been concluded (e.g., the end of the
design review phase or the end of the relevant credit(s) and a reasonable timeline for
submission. It is at ISI discretion to accept any rationale for an extension.post-construction
review phase).

3.10.2 Additional Credit Review Fees [Issued 2018-09-12]

The fee associated with an additional credit review is a flat fee, per each credit re-
submitted. Project teams will only incur this fee in the event they elect to re-submit a credit
for an additional review is charged at a flat rate per credit submitted. . Fees maymust be
remitted to ISI by credit card at the time an additional credit review is requested, or by ACH
or check.; however, ISI shall not return the results of initiate the Additional review until
payment ishas been received in full. If payment is not received within sixty (60thirty (30)
days ofafter the Additional Review being complete, the project will revert to its previous
score.submission of a credit for additional review, such additional review shall be
cancelled. Refer to the Guide to Envision Verification for Applicants for fees associated with an
Additional Review.appeals.

3.10.3 Credit Appeals [Issued 2018-09-12, Updated 2019-03-08]

The Project Leader and/or Lead ENV SP have the option to Appeal one or more of the
Verification Team’s credit decisionsUpon verification completion (e.g., after the Second
Review and after the Post-Construction Review of Pathway A (i.e., Third Review).
An Appeal allows third-party verifier has completed their final review of a project and
returned the final scores to the project team to identify), the project team is presented with
the option to formally accept the credit(s) for review but does not allow any modification of
the credit submittal. If multiple determination of ISI, resubmit credits will bepreviously
submitted for Appeal, they must be submitted simultaneously. Project teams may not submit
for both an Additional Review and an Appeal.
The Appeal will be conducted by three Verifiers from different Verifier Companies who, upon
review of the credit submittal and verifier comments, must reach consensus on an
ISI POLICIES

appropriateat a higher level of achievement. Once initiated, the results of the Appeal will be
available within 60 calendar days.
The option, or to Appeal is only available for 30 calendar days. Once the Appeal is
complete, there will be no further opportunities to request an Additional Review or
Appeal during that review period (i.e., Design Review or Post-Construction Review).initiate
an appeal of one or more credit decisions.
Credit The opportunity to appeal credit decisions is only available for 30 days after
verification completion. Each appeal may only apply to a single credit; however, multiple
appeals can be submitted simultaneously.
The decisions of the appeals board are final.

3.10.4 Appeal Fees [Issued 2018-09-12]

The appeal fee for an Appeal is charged at a flat ratefee, per each appeal. Each appeal can
address only one credit submitted. Fees may. Project teams will only incur this fee in the
event they elect to submit an appeal. Fees must be remitted to ISI by credit card at the time
an appeal is requested, or by ACH or check.; however, ISI shall not initiate the Appeal
process whenreview of an appeal until payment has been received in full. If payment is not
received within sixty (60thirty (30) days of the Appeal being submitted,after the project will
revert to its previous score.submission of an appeal, such appeal shall be cancelled. Refer
to the Guide to Envision Verification for Applicants for fees associated with an Appealappeals.

3.11 AWARD POLICIESAWARDS POLICY

3.11.1 Physical Awards [Issued 2018-09-12]

ISI has entered into an exclusive partnership with an awards manufacturer. Projects that
have earned an Envision Award (i.e., a score of at least 20%)% of applicable points in the
Envision framework may purchase physical awards (e.g., plaques and/or trophies) from our
awards manufacturer. The project name as provided in the Envision Online Scoresheeton the
ISI website is the project name that is eligible to be engraved on the award. Modifications
to the project name are generally not possible without express written permission from ISI.
Visit http://envisionawards.org for more information. Physical awards are not included in
the registration or verification fees paid to ISI.

3.11.2 Public Announcements Announcement [Issued 2018-09-12]

All projects that have earned an Envision award are expected to begin the process of publicly
announcing the projectwill be posted on ISI’s website within 30 calendar daysthree months
of the project team’s acceptancefinal score being issued. ISI will develop a project
announcement in collaboration with the project team and any designees identified by the
Project Leader and/or Lead ENV SP. Additional opportunities to publicize the project will also
be discussed.
Unless otherwise arranged by ISI, projects that earn an award are expected to be announced
ISI POLICIES

within 90 calendar days of acceptance. Unless for reasonable cause, as determined by ISI,
ISI reserves, at minimum, the right to post on its website the name, location, Envision award
level, and a brief description of the project based on information provided inby the Envision
Online Scoresheetproject team.

3.11.3 Use and Disclosure of Project Information [Issued 2018-09-12]

Other than the name, location, Envision award level, and brief description of the project
based on information provided inby the Envision Online Scoresheetproject team, ISI will not
disclose any additional information about the project without express written consent from
the project leader and/or Lead ENV SP.
Once the Project Leader and/or Lead ENV SPa project team consents to information about
a project being made public, ISI reserves the right to include such information in articles,
case studies, presentations, webinars, or other public forums.

3.11.4 Award Revocations Revocation [Issued 2018-09-12]

In very rare situations, an Envision award may be revoked. Circumstances under which an
Envision award couldwould be revoked include:
a) The final score of a project pursuing Pathway A: Design + Post-Construction
decreases to below an Envision Award level based on the results of the Post-
Construction review.
a)b) A project pursuing verification Pathway A: Design + Post-Construction fails to
submit for the Post-Construction Reviewaddress credits marked as pending within
three years1 year of the project being constructed and becoming fully operational.
c) A project pursuing verification Pathway A: Design + Post-Construction is not
constructed.
b)d) Project documentation submitted to ISI for Envision Verificationreview is
found to be materially incorrect or misleading.
Should revocation of an Envision award occur, ISI will remove the project from the awards
list on the ISI website. No fees will be refunded.

3.11.5 Change of Award Level [Issued 2019-03-08]

For projects pursuing verification Pathway A: Design + Post-Construction, it is possible for

the Envision award level earned after the Design Reviewiterative design review stage to
increase or decrease based on the results of the post-construction review. In these rare
cases, ISI will update the project’s Envision award level on the awards list on the ISI website,
and any other communications channels under ISI’s control. The project team is also
required to update any public announcements about the project’s Envision award level
within its control and withdraw any public facing symbol of the previously earned Envision
Award (i.e., plaques, trophies, signage, etc)..
ISI POLICIES