Creating & Maintaining University Policies

Print Friendly

University Policy Number 1101

Categorized:

Responsible Office:

Policy Procedure:

Related Law & Policy:


I. SCOPE

This policy governs the development, issuance and maintenance of all University-wide administrative policies at George Mason University. The policies and procedures set forth herein apply to all George Mason University faculty, staff, students and all academic and administrative units tasked with the creation and maintenance of University policies..

II. POLICY STATEMENT

Because of their application to University-wide operations, and to individual employment contracts, University policies will be created and maintained through a centralized management process and will be publicly accessible through the University’s website. To ensure relevance and accuracy, University policies will be reviewed on a routine basis, and will be revised when necessary. Related forms and procedures, unless expressly stated otherwise within the relevant University policy, will be developed and maintained by the local office or unit that is charged with administration.

University policies typically will require approval by both the Senior Vice President and Provost. Certain policies may also require adoption by the Board of Visitors, at the discretion of senior University leadership in consultation with University Counsel, or at the direction of the Board.

The policies and procedures set forth herein do not apply to local protocols, which are developed by and applicable to discrete academic and administrative units. The development and approval of academic policies are governed by a separate policy. Where, in the opinion of the Office of the Provost, certain academic policies relate to subject matter of unique University-wide application or significance, they may be created and maintained according to the same procedures that govern University policies.

III. DEFINITIONS

University Policy: Administrative policy established to promote the effective and efficient operation of the University, and to guide the management of University affairs. University policies typically address operational expectations across all administrative and academic units of the University, and/or compliance with applicable laws and regulations.

Local protocols: A set of process rules that direct the operations of discrete academic and administrative units. Local protocols may not conflict with University policies, but may be more restrictive. Local protocols are created and administered by the discrete unit where authority for the subject matter resides.

Procedure: A prescribed set of specific actions that must be taken to comply with established University policies, and to guarantee the orderly implementation of those policies. Procedures shall be written in a step-by-step format that is easy to understand.

Responsible Office: The Responsible Office is charged with ownership of a specific policy, and serves as the point of contact for members of the University community. The Responsible Office authors the policy, and any future revisions, according to relevant procedures. The Responsible Office also reviews the policy as required and ensures accuracy of content.

Stakeholder: A University office, department or unit with a notable interest in the subject matter or outcome related to a proposed policy.

IV. COMPLIANCE

Members of the University community will follow the published procedures governing the Development, Review and Revision of University Policies.  The procedures will be maintained by the University Policy Manager.

V. FORMS

University Policy Template

 

VI. DATES

A. EFFECTIVE DATE

This policy will become effective upon the date of approval by the Senior Vice President and Provost.

B. DATE OF MOST RECENT REVIEW

N/A

VII. TIMETABLE FOR REVIEW

This policy shall be reviewed annually by the University Policy Manager.

VIII. SIGNATURES

Approved:

 

__/S_____________________
Maurice W. Scherrens
Senior Vice President

 

_/S_______________________
Peter N. Stearns
Provost

Date approved: August 8, 2012