Background: The Washington State Office of Regulatory Assistance (ORA) was created in the Office of Financial Management in 2003. In 2009 the Legislature substantially changed ORA's statute, providing for gubernatorial appointment of the Director, re-stating ORA's purpose, and increasing the scope of its work. ORA seeks to improve the function of environmental and business regulatory processes by identifying conflicts and overlaps in the state's rules, statutes, and operational practices.

ORA provides a variety of services, including acting as the central point of contact and coordination for project proponents, conducting project scoping, and assisting in conflict resolution. The ORA is to assist local jurisdictions with their local project review requirements, report biennially on performance, and provide biennial recommendations on system improvements.

Summary: ORA must provide information to local jurisdictions concerning best permitting practices, methods for improving early communication with state agencies, and effective ways to assess and communicate project timelines and costs.

ORA's biennial performance report must include the number and type of projects or initiatives the office assisted and the key agencies it collaborated with; specific information regarding difficulties encountered in providing services or implementing programs; trend reports comparing statements of goals and performance targets to actual achievements; and system improvement recommendations, including but not limited to, recommendations on how to reduce both the time and cost of the environmental permitting process.

ORA may require a state or local agency to attend a project scoping meeting in order to identify the relevant issues and information needs of a permit applicant.

The following applies to a project under a cost-reimbursement agreement:

the agreement must require ORA, the permit applicant, and participating agencies to develop and update a project work plan that ORA must post online and share with each party to the agreement;
the agreement must identify the proposed project, the desired outcomes, and maximum cost for work under the agreement;
each agency participating in the agreement must give priority to the project without reducing or eliminating any regulatory requirements during the review process;
reasonable reimbursement cost is either determined based on time and materials with a contract maximum or a flat rate based on required staffing hours;
the agreement may include deliverables and schedules for invoicing and reimbursements; and
advance payment may be required for some or all of the cost-reimbursement agreement; the release of payments to the participating agencies is held until the invoice is approved by the permit applicant.

Upon request, ORA must verify whether the agencies have met the obligations contained in the project work plan and cost-reimbursement agreement. Notification and an explanation must be given to ORA if any party is unable to meet its obligations under the agreement. ORA must notify all parties to the agreement and work collaboratively to resolve the issue.

All cost-reimbursement agreement and solicitation receipts must be deposited into the multiagency permitting team account. Expenditures from the account may only be used for administrative purposes of the multiagency permitting teams including staffing, consultant, technology, and other administrative costs.

A certification process is established for local level permitting. ORA must, within available funds, work with local jurisdictions to establish criteria and the process for certifying a permit process as streamlined. Once certified, a local jurisdiction receives priority when applying for state infrastructure funding.

Senate	36	12
House	58	38	(House amended)
Senate	40	9	(Senate concurred)