Green building certification runs on paperwork, and the platform that holds that paperwork changes from time to time. In December 2014, the U.S. Green Building Council (USGBC) told LEED 2009 project teams they would be moved onto the newer LEED Online system already serving LEED v4, Homes, and Campus projects. LEED Online is the web-based system where teams upload credit documentation, track reviewer comments, and manage the evidence behind a certification. The announcement raised practical questions: would credit data survive the switch, would review dates slip, and would older computers still work? For teams weighing the real cost of certification, the same discipline that goes into preparing an estimate for home repair or new building projects applies to the hours spent assembling credit documentation. This article explains what changed in the migration, what stayed the same, and how any project team can prepare for a platform transition without losing work.
Why USGBC Consolidated Every Rating System Onto One Platform
LEED 2009 projects ran on LEED Online v3, while LEED v4, Homes, and Campus projects used a newer system built to replace it. Maintaining two platforms meant two interfaces, two sets of known issues, and two support queues. USGBC had spent the previous twelve months on the customer experience, from launching LEED Coach to reworking how support requests were handled, and a single platform was a natural next step. From the beginning, the new LEED Online was designed to hold every LEED project, LEED 2009 and newer, plus every certification model USGBC offered.
One Interface for New Construction, Interiors, and Existing Buildings
The January 2015 migration covered three commercial rating systems: BD+C (Building Design and Construction), ID+C (Interior Design and Construction), and EB:O+M (Existing Buildings: Operations and Maintenance). Each has a different documentation rhythm. New construction projects assemble credit submittals across months of design and construction. Interior projects compress the same effort into a shorter fit-out cycle. Existing buildings revisit operations data on a repeating schedule. All three needed the same core features: credit forms, document uploads, reviewer comments, and an audit trail.
Room for Programs That Did Not Exist Yet
USGBC also wanted a platform flexible enough to absorb certification models developed later. Homes projects had used the new system for a full year before the 2009 migration, and their feedback shaped the rollout. For builders responding to market pressure as new homes are getting smaller, the single platform meant one learning curve instead of two. A team that already understood the interface for one project type could apply that knowledge directly to another.
The Migration Timeline and What It Changed
USGBC announced the move on Dec. 22, 2014. From Dec. 28, 2014 to Jan. 5, 2015, both the legacy v3 system and the new LEED Online went down for maintenance. When the systems came back on Jan. 5, 2015, LEED 2009 projects using BD+C, ID+C, and EB:O+M were on the new platform, and newly registered LEED 2009 projects used it from the start.
A Shared Maintenance Window
The outage covered both platforms at once, so no team could submit anything while the cutover ran. Scheduling the window over the holidays reduced the number of teams affected. USGBC held Webex sessions where project administrators could ask questions about the change and posted transition notes for teams that could not attend. By the time of the migration, LEED certification had passed 100,000 projects, so the scale of the cutover was considerable.
Go-Live for the 2009 Rating Systems
On Jan. 5, 2015, BD+C, ID+C, and EB:O+M teams logged into the new platform. USGBC made clear there was no opt-out: every project moved, and new LEED 2009 registrations started there as well. The old information was not going away; the system only changed how teams interacted with it.
Projects Already in Review
Teams midway through review had the most at stake. USGBC confirmed that submission and review timelines would not change and that projects already submitted would receive responses on their scheduled dates. The only difference was where the team logged in to check status.
| Feature | LEED Online v3 (2009) | New LEED Online |
|---|---|---|
| Rating systems served | LEED 2009: BD+C, ID+C, EB:O+M | LEED v4, Homes, Campus, LEED 2009 |
| Browser support | Older Internet Explorer, compatibility mode | Current IE, Safari, Firefox |
| Task assignments | Included | Not carried over |
| Pre-submission review | Limited visibility | Easier team review |
| Data carryover | Source system | Full transfer from v3 |
| Maintenance window | Dec. 28, 2014 to Jan. 5, 2015 | Same window |
What Stayed the Same: Forms, Data, and Review Schedules
The core promise of the migration was continuity. USGBC stated that forms and data would not change and that documentation would be easier for teams to review before submission in the new platform. Nothing about the underlying certification requirements moved; only the software changed.
Documentation Carried Over Without Re-Entry
Teams did not need to rebuild credit files. Material schedules, energy model narratives, photos, and submittals carried into the new interface intact. Online tools across the industry were maturing at the same time; a new online safety tool from NCCCO and NSC aimed to reduce crane incidents by standardizing inspection records, and the LEED platform change followed the same logic. Keep the underlying records, upgrade the interface.
Review Timelines Unchanged
The review queue carried over as well. Projects already in review received responses on their scheduled dates, and new submissions followed the same review windows as before. A typical LEED review cycle moves from preliminary review to final review, with an opportunity to submit clarifications or additional documentation between rounds, and none of those windows changed. What improved was the pre-submission experience: teams could review their own documentation more easily before sending it to reviewers, which catches errors before they cost points.
- Credit forms and uploaded documents carried over without re-entry
- Submission and review timelines were not affected
- Projects already in review kept their scheduled response dates
- No opt-out was offered; every LEED 2009 project moved
Preparing the Project Team for a Platform Transition
A platform change succeeds or fails on preparation. Teams that checked their systems, confirmed logins, and reviewed credit files ahead of the go-live date had a smoother January than those that waited. The transition itself took minutes for most users; the work happened before it.
Browser and System Compatibility
The new platform improved browser compatibility significantly. It supported current versions of Internet Explorer without compatibility mode, plus Safari and Firefox. Older browser versions posed the main risk: a machine running an outdated release could fail to render credit forms correctly. Renovation teams had an extra reason to protect their records; when a hospital expansion adds a polishable overlay to bridge old and new concrete, the material documentation feeds both the warranty file and any LEED material credit. Losing that data in a cutover means re-collecting submittals from suppliers.
Running the System Requirements Check
USGBC placed a “check system requirements” link on the login page, below the log-in button. Clicking it ran a compatibility check and told users what needed adjusting before they opened a credit file. The check takes minutes and is worth running on every machine that touches the project, including laptops used by consultants in the field.
A Five-Step Pre-Migration Checklist
- Run the system requirements check on every computer that opens credit files.
- Confirm each team member has a working login on the new platform.
- Note the status of every credit in progress before the maintenance window.
- Record the scheduled response dates for submissions already in review.
- Save any task assignment lists that will not carry over.
Teams that treated the migration like a small project of its own, with an owner and a checklist, reported the fewest surprises. The same planning protects a project when other software changes, from estimating tools to submittal trackers.
New Review Workflows and Documentation Accuracy
Beyond the move itself, the new platform changed a few workflows that teams noticed immediately.
Task Assignments Did Not Carry Over
The new LEED Online did not include the task assignment feature that teams used in v3, where an administrator could assign documentation tasks to specific team members. Project administrators shifted that coordination to their own tracking tools, such as spreadsheets or project management software, while the platform focused on credit forms and review. Document control discipline, naming files consistently and noting who owns each credit, became the substitute for the built-in assignments.
Clearer Pre-Submission Review
The most useful gain was visibility. Teams could review documentation before submission more thoroughly, and USGBC had spent the previous year improving the customer experience, including the launch of LEED Coach and a reworked support process. The stakes of accurate documentation show up in every version of the rating system: a missing window specification can cost building projects their LEED v4.1 points, so catching omissions before submission matters more than the interface it happens in.
Platform migrations will keep happening as certification programs evolve. The same shift that moved paperwork online has changed how crews get hired, with job matching platforms helping construction companies find skilled workers. For a project team, treating the certification system as a real project workstream, with assigned owners, verified logins, and saved records, keeps the green building process from stalling when the software underneath it changes.