We have been using the "Last updated" date to reflect changes in the policy statement or procedures and then trying to use the "History" section to list what the change was. For example- This policy was updated in 2013 to reflect changes in procedures.
Jenny Jennifer U. Kincaid Chief of Staff/Director of Policy Administration Office of the Executive Vice President for University Academic Affairs Indiana University Bryan Hall 207 Bloomington, IN 47405 (812)856-1291 [email protected]<mailto:[email protected]> From: [email protected] [mailto:[email protected]] On Behalf Of Hornsby, Eunice Sent: Wednesday, April 16, 2014 8:35 AM To: [email protected] Subject: [acupa-l] Editing or Revising policies versus procedures Hello all. For those of you who have a combined document - policy and procedure - do you allow separate update dates (edit, revision) for each of those sections (policy/procedure), or when a document is updated, do you change both dates? In the past, we've had folks update both dates, and I'm leaning towards going the other way. So I figured I'd ask to see if there is a "usual" practice out there. -Eunice Eunice Hornsby, Ph.D. Policy and Training Director The Ohio State University Office of University Compliance and Integrity 1543 N. High St., Columbus, OH 43201-2190 614-292-8728 Office [email protected]<mailto:[email protected]> compliance.osu.edu<http://compliance.osu.edu> osu.edu/policies/<http://www.osu.edu/policies/> [button] 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
<<inline: image001.png>>
