managing electronic records in governmental bodies - National ...
managing electronic records in governmental bodies - National ...
managing electronic records in governmental bodies - National ...
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
24<br />
has not been partitioned <strong>in</strong>to <strong>in</strong>dividual work directories. Nam<strong>in</strong>g conventions are<br />
particularly useful <strong>in</strong> ensur<strong>in</strong>g that each document can be recognised as a unique<br />
entity.<br />
6.8 Manage e-mail as <strong>records</strong><br />
E-mail should be managed accord<strong>in</strong>g to the basic pr<strong>in</strong>ciples that apply to <strong>records</strong> <strong>in</strong><br />
any medium. The management and retention of e-mail are subject to the <strong>National</strong><br />
Archives and Records Service of South Africa Act, (Act No 43 of 1996 as amended),<br />
and its regulations. The follow<strong>in</strong>g guidel<strong>in</strong>es are applicable to the management of e-<br />
mail:<br />
Each <strong>governmental</strong> body needs to establish a policy for the captur<strong>in</strong>g <strong>records</strong> of e-<br />
mail communications. Its own unique functions and environment should <strong>in</strong>form this<br />
policy. The policy should be endorsed by senior management and should be<br />
communicated throughout the organisation as part of the overall <strong>records</strong><br />
management policy. See par 6.1<br />
The policies should <strong>in</strong>form e-mail users that official <strong>records</strong> communicated through<br />
e-mail systems must be identified, managed, protected, and reta<strong>in</strong>ed for as long as<br />
is needed for ongo<strong>in</strong>g operations, audits, legal proceed<strong>in</strong>gs, research, or any other<br />
anticipated purpose. A policy should also expla<strong>in</strong> how the <strong>governmental</strong> body would<br />
implement a <strong>records</strong> management programme that <strong>in</strong>cludes e-mail <strong>records</strong>. For<br />
example, the policy should specify where official <strong>records</strong> will be kept, such as <strong>in</strong> a<br />
central repository associated with a departmental network or LAN or <strong>in</strong> decentralised<br />
<strong>electronic</strong> or paper-based fil<strong>in</strong>g systems. Governmental <strong>bodies</strong> should <strong>in</strong>form end<br />
users about policies for security, backup and purg<strong>in</strong>g to protect <strong>records</strong> from<br />
alteration, loss, or <strong>in</strong>appropriate destruction.<br />
Retention periods for <strong>records</strong> communicated through e-mail systems, like other<br />
<strong>records</strong> are derived from the functional needs of the office and any additional legal<br />
and audit needs. Generally, <strong>records</strong> transmitted through e-mail systems will have<br />
the same retention periods as <strong>records</strong> <strong>in</strong> other formats that are related to the same<br />
function or activity.<br />
Strategies for <strong>manag<strong>in</strong>g</strong> and preserv<strong>in</strong>g <strong>electronic</strong> messages as <strong>records</strong> will differ,<br />
depend<strong>in</strong>g on the specific environment with<strong>in</strong> a <strong>governmental</strong> body.<br />
There are two basic options for fil<strong>in</strong>g and <strong>manag<strong>in</strong>g</strong> e-mail <strong>records</strong>:<br />
• pr<strong>in</strong>t messages and file them <strong>in</strong> paper-based fil<strong>in</strong>g systems, or<br />
• transfer e-mail messages to an <strong>electronic</strong> file plan <strong>in</strong> the <strong>electronic</strong> repository.<br />
The method chosen will depend on whether the office has a paper-based fil<strong>in</strong>g<br />
system or an Integrated Document Management System <strong>in</strong> place.<br />
If the office uses the first option, the follow<strong>in</strong>g should be kept <strong>in</strong> m<strong>in</strong>d to prevent<br />
unnecessary duplication of e-mail messages on the paper-based files:<br />
• if an e-mail message is sent and no reply is expected, pr<strong>in</strong>t and file the message;<br />
Manag<strong>in</strong>g <strong>electronic</strong> <strong>records</strong>_Policy Guidel<strong>in</strong>es.doc<br />
First Edition<br />
Version 1.1<br />
April 2003