Hi all, Sorry I'm late to the conversation (and Josh, great points!). We generally do not have emergency policies. However, that said I can think of two over the last five years. One was our policy on pandemic influenza. We could not wait 30-days before saying the policy was in effect. What we did instead was implement the policy, and still invite comments from the University community. At the end of the period, we would have the policy owner consider the comments and determine if the policy (not policy draft) should be updated. But during that time, the policy is fully in effect. We also take steps, such as those outlined by Joshua, to communicate with key constituents such as our faculty governance groups, if the policy is one in which they'd have great interest.
All administrative policies, including those that are considered "emergency", must still be approved by our President's Policy Committee, either at a regular meeting or via email if necessary. No one VP can direct that it be published, because ownership of all administrative policies rests with the President, and the President has delegated this authority/responsibility to a committee of nine (all VPS plus his Chief of Staff.) The other unique thing we've done for policies with unusual timing needs is to publish a approved policy and note a future implementation date. The old policy is still in effect until that date. Our current example is our smoke and tobacco free campus policy<http://www.policy.umn.edu/Policies/Operations/Safety/SMOKETOBACCO.html>. We are moving from a smoke-free indoor act position, to a full ban. The implementation date is 7/1/14. If a user did a search on our site, both would appear. On the "future policy", there is a big, bold indicator on the front page so that it's very obvious to the reader. POLICY STATEMENT [image: InfoIcon] *This policy goes into effect on July 1, 2014. Currently Administrative Policy: Smoke Free Indoor Air <http://www.policy.umn.edu/Policies/Operations/Safety/SMOKING.html> is in effect.* Thanks for the conversation. It highlighted the need for me to put our exception process into the procedures. Have a great weekend! Michele On Fri, Feb 28, 2014 at 7:13 AM, Joshua Adams <[email protected]> wrote: > Ted, > > > > You raise an interesting point. For many reasons, "damage" is not a word I > would use here. But the possible negative reaction to the promulgation of a > "fast track" policy is always measured by this office and policy owners > when developing a policy. However, consider that in the "old world," a > policy would simply be issued by a VP in the form of a memo, and suddenly > everyone who learned of its existence would have to follow it, as if it > were an edict. It is certain that the "new world" answer of having a > centrally issued, codified policy with a standard mode of development and > broad communication, even on this "fast track," is far better than that > "old world" scenario. Of course reactions vary, but the train keeps moving > along, and the vast majority of people are on it. > > > > Related to this, it is through our centralized policy development and > communication process that we manage expectations in the university > community and minimize the bad reactions to policies we issue, whether they > are developed through a long process or via our foreshortened "fast > track." Yes, even tenured faculty members realize that while it is not > always pleasurable to comply with policies, policies are a necessary part > of the administrative arm of our institution, especially in a highly > litigious environment. And we honor faculty members by consulting with > them on policy issues in which they show interest. The bottom line is that > everyone is trying to function in a way that is in the best interest of the > university and protects his or her interests. We are on the same team, and > try very hard not to engender an adversarial atmosphere regarding policy > creation and promulgation. It is a consensus-building effort on every > level. > > > > Best, > > Joshua > > > > > > Joshua Adams > > Director, Cornell University Policy Office and > > DFA Communications > > 35 Thornwood Dr, Suite 200 > > Ithaca, NY 14850 > > > > t: 607.255.8279 > > f: 607.254.1555 > > w: www.policy.cornell.edu > > > > ΓΌ Please consider the environment before printing this e-mail. > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Ayres, Ted > *Sent:* Thursday, February 27, 2014 6:34 PM > > *To:* ACUPA-L > *Subject:* RE:[acupa-l] Emergency Policy Contingency? > > > > Friends: presenting "another side" of the thought process, how much > damage will be done relative to staff/employee relations, particularly > tenured faculty? Even if possible/justifiable under institutional > policy-making procedures. Good luck. > > > > *Ted D. Ayres* > > *Vice President & General Counsel* > > *Wichita State University * > > 316.978.6791, telephone > > 316.978.3046, telefacsimile > > > > "...[He] liked looking out into the universe. > > He liked thinking about it. He used it for perspective. > > He was just a tiny insignificant speck briefly sparked to > > life in the middle of nowhere. So what really mattered? > > Maybe nothing at all." > > Lee Child > > > > > > *From:* [email protected] [ > mailto:[email protected]<[email protected]>] > *On Behalf Of *Joshua Adams > *Sent:* Thursday, February 27, 2014 5:03 PM > *To:* ACUPA-L > *Subject:* RE:[acupa-l] Emergency Policy Contingency? > > > > Lynda, > > > > Here, even our VPs can enact policies on a "fast track," such as those > with special promulgation needs, as quickly as necessary. We call one of > these a "Policy Statement and Interim Procedures," and they are called that > until such a time as they can be brought through the formal approval > process (at which time they become simply "policies"). The reasoning for > not requiring presidential approval is that it is assumed, through the > normal operational chain of command, that a VP asking for such a policy > would naturally have the blessing of his or her superior, namely the > president. > > > > The regulations surrounding these are covered in our Policy 4.1, > Formulation and Issuance of University Policies (although we haven't > changed the terminology in that document--in it, they are still called > "interim policies"). Here is the link: > http://www.dfa.cornell.edu/treasurer/policyoffice/policies/volumes/governance/policies.cfm > > > > If you're interested in why we changed the name from "interim policy" to > "policy statement with interim procedures," it's because the executive > policy group pointed out that when a policy statement comes forth from a VP > and has been properly vetted through normal operational channels and the > chain of command, there's really nothing "interim" about it (although > procedures remain to be worked out). And policy users were reacting to > "interim policies" as if they were not in full effect. > > > > I hope this helps. > > > > Joshua > > > > > > *From:* [email protected] [ > mailto:[email protected]<[email protected]>] > *On Behalf Of *Lloyd, Lynda > > *Sent:* Thursday, February 27, 2014 5:26 PM > *To:* ACUPA-L > > *Subject:* [acupa-l] Emergency Policy Contingency? > > > > Hello, > > > > I have a request from our Chief Administrative Officer/CFO regarding a: > > > > *"policy that would allow the president or cabinet to enact an emergency > implementation of a policy* > > *for fiscal exigency, or other immediate needs"* > > > > Do any of you have such a policy and if so will you share? > > > > Thank you! > > > > Lynda Lloyd, M.Ed., P.H.R. > > Director of Institutional Policy & Professional Development > > NWACC <http://www.nwacc.edu/> > > 479-619-4248 office > > 479-381-8660 wireless > > > > This message is intended solely for the recipient to whom it is addressed. > If you are not the intended recipient, do not disclose, distribute or copy > this email. Please notify the sender immediately and delete this email > from your system. > > > > ATTN: Please be aware that when you respond to an ACUPA-L e-mail, the > reply will be distributed to the ENTIRE e-listing of members. If you do NOT > want to send an e-mail to everyone, please reply directly to the individual > who initiated the query (their e-mail address appears in the "From" line of > their original e-mail). > > If you wish to remove yourself from the ACUPA e-mail list, please go to > this web address and fill out the form. We will remove you from the list > within 24 hours during normal business hours. > > http://www.acupa.org/MembershipForm_Discontinue.html > > ATTN: Please be aware that when you respond to an ACUPA-L e-mail, the > reply will be distributed to the ENTIRE e-listing of members. If you do NOT > want to send an e-mail to everyone, please reply directly to the individual > who initiated the query (their e-mail address appears in the "From" line of > their original e-mail). > > If you wish to remove yourself from the ACUPA e-mail list, please go to > this web address and fill out the form. We will remove you from the list > within 24 hours during normal business hours. > > http://www.acupa.org/MembershipForm_Discontinue.html > > ATTN: Please be aware that when you respond to an ACUPA-L e-mail, the > reply will be distributed to the ENTIRE e-listing of members. If you do NOT > want to send an e-mail to everyone, please reply directly to the individual > who initiated the query (their e-mail address appears in the "From" line of > their original e-mail). > > If you wish to remove yourself from the ACUPA e-mail list, please go to > this web address and fill out the form. We will remove you from the list > within 24 hours during normal business hours. > > http://www.acupa.org/MembershipForm_Discontinue.html > > ATTN: Please be aware that when you respond to an ACUPA-L e-mail, the > reply will be distributed to the ENTIRE e-listing of members. If you do NOT > want to send an e-mail to everyone, please reply directly to the individual > who initiated the query (their e-mail address appears in the "From" line of > their original e-mail). > > If you wish to remove yourself from the ACUPA e-mail list, please go to > this web address and fill out the form. We will remove you from the list > within 24 hours during normal business hours. > > http://www.acupa.org/MembershipForm_Discontinue.html > -- Michele Gross, Director University Policy Program University of Minnesota 356-1 McNamara, 200 Oak street Minneapolis, MN 55454 612-624-8081 http://policy.umn.edu/
