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.
17<br />
While some of the <strong>records</strong> published to websites often exist <strong>in</strong> paper format <strong>in</strong> proper<br />
record keep<strong>in</strong>g systems, it does happen that <strong>records</strong> are be<strong>in</strong>g created <strong>in</strong> the onl<strong>in</strong>e<br />
environment, which are not captured <strong>in</strong> record keep<strong>in</strong>g systems. Governmental<br />
<strong>bodies</strong> are responsible for the creation of authentic, reliable and accurate <strong>records</strong> of<br />
all web-based activities to enable them to be accountable to the public to which the<br />
services are provided.<br />
Governmental <strong>bodies</strong> can be held accountable for the <strong>in</strong>formation they publish on<br />
their websites even long after the website has been updated/changed, as well as for<br />
the transactions conducted via the website. At a given time websites may conta<strong>in</strong><br />
<strong>in</strong>formation on:<br />
- the structure and organisation of the body concerned<br />
- the legislation it adm<strong>in</strong>isters or under which it operates;<br />
- the functions for which it is responsible;<br />
- its current policies, guidel<strong>in</strong>es, advice and publications;<br />
- its current products and services;<br />
- <strong>in</strong>structions for the access and use of those products and services and for the<br />
<strong>in</strong>terpretation of the <strong>in</strong>formation posted to the websites;<br />
- the functionality to transact with the <strong>governmental</strong> body to obta<strong>in</strong> products<br />
and services.<br />
Websites document both the structures and public face of <strong>governmental</strong> <strong>bodies</strong>. It is<br />
necessary for <strong>governmental</strong> <strong>bodies</strong> to document their websites accurately over time<br />
so that they can reliably establish the content their websites carried at any particular<br />
po<strong>in</strong>t of time. If websites are not managed appropriately <strong>governmental</strong> <strong>bodies</strong> could<br />
be required to:<br />
o carry the cost of legal action when be<strong>in</strong>g sued for not be<strong>in</strong>g able to provide<br />
accurate <strong>in</strong>formation on the content of a website at a specific time;<br />
o operational cost when vital <strong>in</strong>formation is lost;<br />
o adm<strong>in</strong>istration costs when <strong>in</strong>formation has to be searched for and replicated;<br />
and<br />
o historical costs when the archival <strong>records</strong> conta<strong>in</strong><strong>in</strong>g the corporate memory<br />
are lost.<br />
It is even more imperative that <strong>records</strong> should be created of all transactions<br />
conducted us<strong>in</strong>g this functionality. In the absence of a record of transactions, there is<br />
no evidence of these transactions ever hav<strong>in</strong>g occurred. This can lead to the<br />
transaction be<strong>in</strong>g deemed by a court of law not to have taken place.<br />
All the <strong>in</strong>formation conta<strong>in</strong>ed <strong>in</strong> paragraphs 4.1.2–4.1.8 is also applicable to<br />
websites.<br />
4.4 Structured systems<br />
The <strong>in</strong>formation conta<strong>in</strong>ed <strong>in</strong> these systems also constitutes public <strong>records</strong> that form<br />
part of the offices’ corporate memory and therefore needs to be managed accord<strong>in</strong>g<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