Search Tips

Administrative Order 12 - PUBLIC TRUST AND CONFIDENCE IMPLEMENTATION COMMITTEE

Effective Date: 4/1/2006

Obsolete Date: 5/1/2006

This Order establishes a Public Trust and Confidence Implementation Committee and is in effect until further Order of the Court.

A. Membership - Staffing

1. The Chief Justice, in consultation with the members of the Supreme Court, appoints up to 14 members of the bench, bar and public to serve as permanent members on the Committee. At the request of the Committee, temporary members may be appointed to assist the Committee in specialized areas of need.

2. Permanent members shall be appointed for three year terms. Of the permanent members initially appointed and as determined by lot at the first meeting, one-third of the members will be appointed for one year, one-third for two years, and one-third for three years. Each permanent member is eligible for reappointment and serves until the member's successor is appointed. A permanent member may not serve more than three consecutive terms. A former permanent member who served three consecutive terms is eligilbe for reappoitnment after a six-year break in service. Temporary members will have no term.

3. The Committee is chaired by a member appointed by the Chief Justice.

4. The Committee is staffed by the State Court Administrator's office, unless other arrangements are made by the Committee.

B. Expenses

Expenses incurred by members are reimbursed by the Supreme Court.

C. Mission

1. Oversee the development of a detailed course of action to implement recommendations in the March 2000 Report of the Committee on Public Trust and Confidence.

2. Monitor the progress of the Judicial Branch toward enhancing the public's trust and confidence in the courts.

3. Recommend action beyond that set forth in the Report where necessary to achieve the goals identified in this section.

D. Report

The Committee shall submit a progress report to the Supreme Court by October first and April first of each year, beginning October 1, 2000.

E. Effective Date

This Order is effective May 1, 2000, and remains in effect until further Order of this Court.

Dated March 1, 2006.

Source: Adopted April 26, 2000, effective May 1, 2000; amended effective April 1, 2006 (Supreme Court No. 20060059). 

Effective Date Obsolete Date
05/01/2006 View
04/01/2006 05/01/2006 View
05/01/2000 04/01/2006 View

 


Runtime Error

Server Error in '/' Application.

Runtime Error

Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".


<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="Off"/>
    </system.web>
</configuration>

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.


<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
    </system.web>
</configuration>