All EERE-funded websites, redesigns, and user experience projects must follow Web Governance Team (WGT) and Communication Standards guidance. This includes lab-developed websites that use EERE funding from the EERE technology offices.

Why is the approval needed?

Which types of web projects?

  • New websites or subsites (nested groups) or content types in
  • Web applications, mobile apps, native mobile apps, widgets, scripts, or special features
  • Redesigns of existing websites and applications, including redesigns on
  • New websites, tools or apps that labs or third parties develop to be hosted outside of, including partnership sites, conference sites or competition sites.
  • User-experience projects, such as surveys, quizzes or user-experience studies.

What is the Process?

Step 1: Concept Approval

Before you begin work, meet with the Web Governance Team to guide you through your project.

Email the following to the WGT Facilitator before the concept meeting:

  • Domains and URLs, including marketing URLs or redirects, and justification for .org or .net sites (instead of .gov). All projects must be hosted in's Drupal environment unless DOE Public Affairs gives written approval. Rare exceptions apply for White House initiatives, congressional issues, or partnership efforts. For such sites, WGT is the communication facilitator between Public Affairs and the project team.
  • Technical requirements or features (e.g. public uploads, password-protection, forms, or databases)
  • Any interactive elements (e.g., graphics or maps)
  • Whether your site is an application that may require use of the EERE template
  • Data collection from public or government sources like,, or
  • Personally Identifiable Information (PII); if so, you may need to fill out a Privacy Impact Assessment

Note: For user-centered design projects such as a survey or card sort, complete the user-centered design project information form and send it to the Web Governance Team Facilitator.

Step 2: Project Charter Approval

Write a Charter

  • Create a project charter. Download EERE's Project Charter Template. Submit your project charter to the Web Governance Team. Do this before you begin any work on the project.
    • Note: User-centered design projects do not require a project charter. The WGT may ask you to share your results.

Privacy Impact Assessments

  • If your project involves Personally Identifiable Information, you may need to fill out an E-Authentication Risk Assessment form or Privacy Impact Assessment. If your project requires one, fill it out and submit it to the WGT.

Call into a Web Governance Team Meeting

  • Schedule a meeting with the WGT Facilitator. The WGT will review your charter with you or may provide comments via email. The WGT must approve your charter before you continue.

Step 3: Develop Site Content

In this phase, complete your content so you can determine the final site architecture.

Write content

Follow the EERE Style Guide

  • Use the web writing guidelines to ensure that your content meets the standards for elements such as headers, intro text, subheaders, photo captions, and alt text.

Create the information architecture

Send your final information architecture for review

  • Submit your final information architecture to the Web Template Coordinator for review and approval. You may be asked to make changes before your architecture is approved.

Provide monthly updates via email to the WGT Facilitator

Step 4: Production

Below are the basic steps for developing your website.

Prepare for Production

  • If you're creating a website on and need a new subsite (nested group), request that one of the Site Coordinators create it.

Create the Website

  • Work with your lead contractor to create your website.
  • Provide monthly updates via email to the WGT facilitator.

Step 5: Final Reviews and Going Live

Go through a quality assurance and program review before it goes live.

If Needed, Schedule Security Scans

  • For applications not hosted on the central EERE infrastructure, ensure they undergo a security scan.

Program Review

  • If your office requires internal reviews, schedule them. Make changes based on the feedback.

Get approval to go live from the Web Governance Team

  • Schedule your final meeting with the WGT Facilitator. The WGT must give approval before the site goes live. Provide your final URL.

Step 6: Website Maintenance

During this phase you will keep your content up-to-date, track website statistics, assess user feedback, and plan for future changes. Learn more about maintenance requirements.

Keep the website up-to-date and relevant

  • Make sure you communicate to the WGT how long you need your domain name.
  • Report on your maintenance activities to the Web Governance Team in June and December.