Southern Local School District
Administrative Guidelines
 

7540.05 - PROPER USE OF E-MAIL ACCOUNT

Depending on the content of an e-mail message, it may be a public record that needs to be maintained by the District in accordance with the Board of Education’s Records Retention Policy and made available for inspection and/or copying upon request by a member of the public. The following procedures are established so that the District’s e-mail and Internet capabilities are not compromised, and e-mail messages are maintained in accordance with Ohio law.

PUBLIC RECORD CONSIDERATIONS:*

E-mail messages that are kept by the District and that serve to document the organization, functions, policies, decisions, procedures, operations, or other activities of the District are public records, unless they meet one of the statutory exceptions, and must be maintained in accordance with the Board’s Records Retention Policy and made available for inspection and/or copying by the public. The length of retention of an e-mail message is dependent upon its content and the purpose it serves. The content, transactional information, and any attachments associated with an e-mail message are considered a record if they meet the statutory criteria.

For the purposes of this guideline, there are four (4) categories of e-mail retention: non-record messages, transitory messages, intermediate messages, and permanent messages.

 A.Non-Record Materials
  E-mail messages that do not meet the criteria of the Ohio Revised Code definition of a record may be deleted at any time, unless they become part of some official record as a result of special circumstances. These types of messages may include:

  1.Personal Correspondence
   Any e-mail not received or created in the course of District business, may be deleted immediately, since it is not an official record: the "Let’s do lunch" (not a District-business lunch) or "Can I catch a ride home" type of note.

  2.Non-District Publications
   Publications, promotional material from vendors, and similar materials that are "publicly available" to anyone, are not official records unless specifically incorporated into other official records. In the electronic world, this includes listserv messages (other than those you post in your official capacity), unsolicited promotional material ("spam"), files copied or downloaded from Internet sites, etc.

 

These items may be immediately deleted, or maintained in a "Non-Record" mail box and deleted later, just as you might trash the unwanted publication or promotional flyer.

 
 

However, for example, if you justify the purchase of a "Zippo Filing System" by incorporating the reviews you saved (from the "Files R Us Listserv") in your proposal to your supervisor, those listserv messages become official records and must be retained in accordance with the retention schedule for purchasing proposals.

 B.Official Records – Retain As Required
  E-mail messages that meet the definition of a record in the Ohio Revised Code are official records and must be scheduled, retained and disposed of as such. These official records fall into the following categories:

  1.Transient Retention
   Much of the communication via e-mail has a very limited administrative value. For instance, an e-mail message notifying employees of an upcoming meeting would only have value until the meeting has been attended or the employee receiving the message has marked the date and time in his/her calendar.

 

Transitory messages do not set policy, establish guidelines or procedures, certify a transaction or become a receipt. The informal tone of transitory messages might be compared to a communication that might take place during a telephone conversation or conversation in an office hallway. Transient documents include telephone messages, drafts and other limited documents which serve to convey information of temporary importance in lieu of oral communication. Transient documents should be retained in accordance with the Board’s Records Retention Policy [ex. Retention: Until no longer of administrative value, then destroy].

2. Intermediate Retention

E-mail messages that have more significant administrative, legal and/or fiscal value but are not scheduled as transient or permanent should be categorized under other appropriate record series. These may include (but are not limited to):

   a.General Correspondence: Includes internal correspondence (letters, memos); also, correspondence from various individuals, companies, and organizations requesting information pertaining to the District and legal interpretations and other miscellaneous inquiries. This correspondence is informative (it does not attempt to influence Board/District policy).
    Retention: [See Records Retention Policy; ex. one (1) year, then destroy.]

   b.Routine Correspondence: Referral letters, requests for routine information, or publications provided to the District, which are answered by standard form letters.
    Retention: [See Records Retention Policy; ex. six (6) months, then destroy.]

   c.Monthly and Weekly Reports: Document status of on-going projects and issues; advise supervisors of various events and issues.
    Retention: [See Records Retention Policy; ex. one (1) year, then destroy.]

   d.Minutes of Staff Meetings: Minutes and supporting records documenting internal policy decisions.
    Retention: [See Records Retention Policy; ex. two (2) years, then transfer to State Archives for their possible retention or destruction].

  3.Permanent Retention
   E-mail messages that have significant administrative, legal and/or fiscal value and are scheduled as permanent also should be categorized under the appropriate record series. These may include (but are not limited to):

   a.Executive Correspondence: Correspondence from the Superintendent, Treasurer, or other administrator that deals with significant aspects of the administration of their offices/buildings. Correspondence includes information concerning Board/District policies/guidelines, program, fiscal and personnel matters.
    Retention: [See Records Retention Policy; ex. two (2) years, then transfer to State Archives].

   b.Departmental/Building Policies and Procedures: Includes published reports, unpublished substantive reports and policy studies.
    Retention: [See Records Retention Policy; ex. Retain until superseded, obsolete or replaced, then transfer to State Archives for their possible retention or destruction].

 

Not all e-mail messages will fall into these record series. For more suggested retention periods, consult the Board’s Records Retention Policy.

Guidelines and Best Practices for Managing E-Mail

Record Copy E-Mail

E-mail users should be aware that e-mail messages are often widely distributed to a number of various recipients. Determining which individual maintains the record copy of the message, i.e., the original message that must be retained per the retention schedule, is vital to e-mail management. If the holder of the record copy is not identified and aware of his/her responsibility, the District may find that no one retains the message or that everyone retains the message. Neither of these scenarios is appropriate.

For example, Board/District policy/guidelines documents that are transmitted to multiple recipients via an e-mail system need not be maintained by each recipient beyond his/her need for this information if record copy responsibility is established so that the record is maintained by some office, employee or agent for its established retention period. In this example, a logical record copy responsibility rests with the creator or original distributor of the policy/guideline document. Prompt deletion of duplicate copies of e-mail messages from an e-mail system makes the system as a whole much easier to manage and reduces disk space consumed by redundant information.

Generally speaking, the individual who sends an e-mail message should maintain the record copy of the message. However, the varied uses and wide distribution of e-mail may result in many exceptions to this rule that will have to be dealt with internally.

Filing

Non-transitory e-mail messages should be filed in a way that enhances their accessibility and that facilitates records management tasks. The IT staff will advise users on the set up or modifying of e-mail systems to facilitate records management and appropriate filing systems. Procedures and systems configurations may vary according to the building’s/users’ needs and the particular hardware and software in use.

In addition to the IN and OUT boxes that come with your mail account, you usually have the option of creating other "mailboxes" or "folders". After brief periods in your IN-OUT boxes, messages should be transferred to other boxes, based on business and retention requirements.

Employees should be responsible for classifying messages they sent or receive according to content, the District’s folder/directory structure, and established records series.

Distribution Lists

If you send to a "distribution list" (not a listserv, but a specified list of individuals), you must also keep a copy of the members of that list for as long as you are required to keep the message itself. It is of little value to know that the "Security Alert!" notice went to "Building Principals", without knowing whether Arnold S. received the message. Nicknames present a similar problem.

Subject Lines

Fill in the subject line on your e-mail both to help your recipient identify and file messages, and to help you file your OUT box messages that must be retained for some period. Subject lines should be as descriptive as possible.

The following are some examples of poor and good subject lines for the same message:

Poor, confusing subject lines

Better, descriptive subject lines

"helpful info"`

"contact info"

"report"

"quarterly financial report"

"minutes"

"Jan 99 Board minutes"

"important"

"revised admin. procedures"

"today?"

"lunch plans today?"

"news"

"new agency head appointed"

*This Section has been adopted from the Ohio Electronic Records Committee’s publication entitled "Managing Electronic Mail – Guidelines for State of Ohio Executive Agencies".

See http://www.ohiojunction.net/erc/email/emailguidelines.html

Approved 12/27/05