Date:

07/09/2008

PRACTICE NOTE SC Gen 7
Supreme Court – Use of technology


Commencement
1. This Practice Note was issued on 9 July 2008 and commenced on 1 August 2008.

Application
2. This Practice Note applies to new and existing proceedings in the court, except as otherwise stated.

Definitions
3. In this Practice Note:

SCR means the Supreme Court Rules 1970

UCPR means the Uniform Civil Procedure Rules 2005

Database means a collection of electronic data that is organised so that its contents can easily be accessed, managed and updated

Electronic Data means information that has been translated into an electronic form that is more convenient to move or process

ESI means electronically stored information and includes emails, webpages, word processing files, images, sound recordings, videos and databases stored in any device

Field means a column of data within a database. Each record (row) can be made up of a number of pieces of information and, therefore, consists of a number of fields. These fields may be displayed as a box to enter or display data (in a form or report)

IMAGE means a picture or photograph that has been created or copied and stored in electronic format.

Medium means a mechanism through which a message is communicated

Virus means a computer program designed to replicate itself, usually having some unexpected and undesirable result for its targets. Viruses can be transmitted by downloading programs from infected sites (including internet sites) or they may be present on a storage device received from an infected system

XML means extensible mark up language used to facilitate the transfer of documents between computer systems

Introduction

4. The purpose of this Practice Note is to set out a protocol for the use of technology in courtrooms and jury deliberation rooms and, in relation to civil litigation, to:

• encourage the use of information technology as a means of improving the efficiency of litigation in general;
• emphasise the court’s power to require the use of technology in particular cases or circumstances in order to provide such efficiencies;
• offer guidelines on the matters parties should to take into account in deciding how to make use of technology; and
• offer examples and suggested standards to assist parties in agreeing upon the extent and manner in which they will use technology to exchange information.

Use of technology in courtrooms and jury deliberation rooms

5. Parties should give the Court as much notice as possible if they require technology in the courtroom or jury deliberation room during a hearing. Equipment and services may be required, such as hardware, software and additional infrastructure and a third party service provider may need to be engaged. Technology may include:
• Real time transcript;
• Video-conferencing; and
• Computers at the bar table.

6. The trial or presiding judge must give approval before technology may be installed or used in courtrooms or jury deliberation rooms. Where such a judge has not yet been allocated, parties should obtain approval from the relevant List Judge. Nothing in this practice note is intended to preclude practitioners from using their own laptop computers at the bar table during hearings.

7. A judge who approves the use of technology will ask the registry to make all arrangements. In most circumstances the Court will install its own equipment and the parties will be asked to meet all associated costs.

8. A document Technology in the courtroom - Protocols and Procedures for Video and Audio Link is available on the Court’s website, along with the relevant forms.

Encouraging the use of technology in civil litigation

9. All parties are required at all stages of their litigation to consider the prospect of using technology for the purposes of information exchange and at trial itself. In preparing a case for trial the parties are specifically encouraged to:
• exchange electronic versions of documents such as pleadings and statements;
• consider the use of electronic data at trial in accordance with the Court’s requirements.
• Serve documents electronically

Electronic exchange of discovery lists and documents

10.Where parties have discoverable ESI, efficiency dictates that any discovery and production of such information be given electronically to avoid the need to convert it to a paper format. In such cases the Court, as a general rule, will require the parties to:

• create electronic lists of their discoverable ESI material
• give inspection by production of databases containing copies of discoverable ESI created in accordance with an agreed protocol. Host and attachment documents must not be separated in this process and
• change original file names to document identification numbers.



11. Where the parties have more than 500 documents that are not ESI, as a general rule the Court will expect the parties to consider the use of technology to discover and inspect such documents along with any ESI. Decisions about the appropriate use of technology will be better informed if the parties have identified early in the proceedings the scope of discovery and the categories of documents likely to be discovered.


12. Practitioners must advise their opponents at an early stage of the proceedings of potentially discoverable electronically stored information and meet to agree upon matters including:

• the format of the electronic database for the electronic discovery, noting that metadata, mark-up or other “hidden” data will be automatically discovered if native format is used. Because of potential costs, the Court would ordinarily expect it should only be discovered where the relevance outweighs the cost
• the protocol to be used for the electronic discovery including electronically stored information
• the type and extent of the electronically stored information that is to be discovered
• how legacy or deleted data is to be dealt with. The existence of ESI that is not reasonably or readily accessible should be disclosed between the parties, but the Court would ordinarily expect that it would not need to be retrieved unless necessary for the conduct of the proceedings
• whether electronically stored information is to be discovered on an agreed without prejudice basis
• without the need to go through the information in detail to categorise it into privileged and non-privileged information and
• without prejudice to an entitlement to subsequently claim privilege over any information that has been discovered and is claimed to be privileged under s 118 and/or s119 of the Evidence Act 1995 and/or at common law.
• Such ESI could be produced separately on a CD-ROM or DVD and appropriately marked to enable the Court to determine any privilege issue.

13. In many cases where there is a substantial amount of ESI the parties should consider producing the material in its searchable native format, rather than by production of document images.

14. If a party chooses to produce document images rather than originals of ESI, the costs of providing access to hardware, software or other resources to enable inspection of original electronic material should be agreed by the parties.

Agreement by written protocol

15. In any case where there is to be discovery given by production of databases containing discoverable ESI the parties should:
• endeavour to reach agreement early in the proceedings on the protocol to be used and the scope of that protocol; and
• seek either consent orders or directions from the Court, if agreement is not reached, concerning the terms of the protocol.
  16. The court will expect the protocol to deal with the following matters:
• the format of the electronic database for the electronic discovery;
• the protocols and data formats to be used for the electronic discovery;
• the type and extent of the ESI that is to be discovered; and
• whether ESI is to be discovered on an agreed without prejudice basis;
• without the need to go through the information in detail to categorise it into privileged and non privileged information; and
• without prejudice to an entitlement subsequently to maintain a claim for privilege over any information that has been discovered and is claimed to be privileged under S118 and/or S119 of the Evidence Act 1995 and/or at common law.
• whether documents will be produced in native or image format
• for cost reasons, forensic examination of hard drives is only appropriate when the Court makes specific orders
• Any other terms and conditions of electronic discovery

Verification of electronic lists

17. Each party shall consider how lists of documents should be verified where data about those documents is to be exchanged electronically.

Orders to dispense with verifications by affidavit

18. Presently existing rules of Court presuppose that a hard copy list of documents will be verified by affidavit. Where a party believes that it is appropriate to dispense with verification of a hard copy list, that party should ask the Court for an appropriate direction.

Verification by reference to method of service

19. As an alternative to verification of a hard copy list, the parties may wish to consider asking for a direction that the verifying affidavit identify the documents by reference to the medium by which the data was served and the date of service. For example, the affidavit may refer, in a hypothetical case, to: the documents described in the database contained on the compact disks served on the defendant under cover of letters date 21 January, 24 January and 29 March 2003.

Providing electronic lists of documents to the Court

20. The parties should consider whether data relating to their discoverable documents should be provided to the Court electronically in addition to any hard copy list.

Directions

21. The Court retains the power to direct parties to use information technology in appropriate cases. Parties shall comply with any directions issued by the Court in relation to the use of technology and shall comply with any requirements published by the Court in relation to issues concerning the use of technology, such as document formats.

22. It should be noted that whilst this practice note is generally advisory in nature the Court may mandate the use of the technology standards it describes in cases where the parties fail to agree on exchange and presentation mechanisms within a reasonable time frame.

Electronic exchange of Court documents
23. Where a party serves a pleading, affidavit, statement, list of documents or interrogatory on another party, the recipient may ask the first party to also provide a copy of it in an electronic format.

24. The Court expects parties to accede to reasonable requests for copies of court documents in an electronic format. Before copies are provided the parties shall make all reasonable efforts to agree upon:
• the word processing or other format in which electronic versions will be provided;
• the methods by which electronic versions will be exchanged; and
• any other terms and conditions of electronic exchange.

25. Attention is directed to UCPR 3.8, which provides for electronic service of documents in proceedings. The consent can be given inter alia by including an electronic address for service in a notice of appearance.

Document formats
26. Where appropriate the parties may wish to agree upon the preparation of a document in a structured format, such as HTML or XML, so that hypertext links can be made where appropriate. For example, if a document refers to a document ID, a hypertext link can be made to the relevant document image.

Content of Court documents
27. A court document provided by a party in electronic format shall contain only the same text as the paper copy. Where a court document contains an annexure, however, the text of the annexure will be expected to be contained within the electronic copy.

Risk of computer viruses
28. Generally it will not be regarded as unreasonable for a party to provide documents in electronic format subject to a condition that it is the responsibility of the recipient to test it for viruses.

Providing electronic copies to the Court
29. The Court may direct a party to provide the Court with copies of court documents in an electronic format.

Technology checklist
30. In developing a protocol on electronic exchange the parties should consider the matters described in the annexed Technology Check List. The checklist is a guide only and parties are free to agree on appropriate changes to it. However, if the parties are unable to agree on a protocol then the default options indicated in the checklist will apply as a minimum standard.

Recommended fields
31. The fields and associated guidelines described in Annexure 2 are those that ought be used for the purpose of electronic exchange and which may be mandated by the Court in a given case, in the absence of agreement to the contrary by the parties.

Use of technology during a hearing
32. Where parties have used databases or databases and associated documents or images to facilitate discovery and inspection, the parties should consider and make submissions about how best to use technology at the hearing. For example, the parties’ discovery databases might form the basis of an index to the agreed bundle, or for the creation of a database of documents admitted into evidence and rulings on the admissibility of documents. Early involvement of the court in this process will assist in many cases.




J J Spigelman AC
Chief Justice of New South Wales
9 July 2008

Related Information
See also:
Technology in the courtroom - Protocols and Procedures for Video and Audio Link
Video-Link call application form
Video/audio-link call order form
Video-link set-up form

Amendment History
This Practice Note was issued on 9 July 2008 and commenced on 1 August 2008. It replaces Practice Note SC Gen 7 issued on 1 September 2006.
The Practice Note issued on 1 September 2006 replaced the Note issued on 17 August 2005.
The Practice Note issued on 17 August 2005 replaced Former Practice Note No. 127.




Annexure 1

Technology checklist


** = default or minimum standard

Preparation stage	Type of document	Options
Pre-Trial	Exchange of Court Documents and Witness Statements	Hard copy only Electronic Copy only Hard copy and electronic copy**
	Electronic Document Format	Delimited ASCII text file** Word processing format _____ Excel spreadsheet XML Other __________
	Document Exchange Via	DX Courier Australia Post Floppy Disk** Electronic mail CD Rom Internet
Discovery	Exchange of Document Lists	Hard copy only Electronic Copy only Hard copy and electronic copy**
	Electronic Document List Format	Delimited ASCII text file** Word processing format _____ Excel spreadsheet XML Other __________
	Document Exchange Via	DX Courier Australia Post Floppy Disk** Electronic mail CD Rom Internet
	Example Database Formats	MS Access Lotus Notes Filemaker Pro MS SQL Sybase Excel Spreadsheet** Oracle Other

	Document Inspection Format	Hard copy only Electronic/image of hard copy Hard copy and electronic/image copy** Non-paper record for example, video/audio tape, database, microfiche, etc Other Medium _____________
	Electronic Image Formats	TIFF – Multi TIFF – Single** PDF GIF Other
	Special Considerations	Redacting (masking) Confidentiality Other
Trial	Exchange of Agreed Bundle/Court Book Indexes	Hard copy only Electronic/image of hard copy Hard copy and electronic/image** copy Other Medium _____________
	Electronic Document Index Format	Delimited ASCII text file** Word processing format Excel spreadsheet Other
	Document Exchange Via	DX Courier Australia Post Floppy Disk** Electronic mail CD Rom Internet/Intranet
Generally	Image Resolution	Images may be scanned in at around 200 dpi. Any greater file size may be unworkable.
	Filename Structure	Images may be named identically to the relevant Document ID or according to the agreed folder structure. If images are named in accordance with the naming convention of the full document ID then the dots within the Document ID may be omitted (other than the dot preceding the file extension).
	Special Considerations	Consideration should be given to: whether there are any special requirements, such as redacting (masking) the implications of using technology in respect of information that may be subject to confidentiality orders or undertakings.

Recommended fields and default fields**

Among the Recommended Fields, the following are the default fields (those which the parties will be expected to use as a minimum standard unless otherwise agreed or ordered): Document ID Date Document type Author/ Author organisation Addressee/ Addressee organisation Title





Annexure 2

Recommended fields



Field	Data type and length	Notes
Document ID (Default field 1)	Text and Numbers (if appropriate) Length - depending on field structure	Each document should be uniquely identified. The field may be broken into different components such as First Page and Last Page providing the parties agree. The field or fields might comprise a four-part number in form AAA.NNN.NNN.NNNN where "AAA" represents alphabetic shorthand for the party name. The other three sets of numbers could be used to suit the convenience of the parties. It may be useful if the first set is used to refer to an archive box number, the second to the number of the folder within the box, and the third to the page number. Rules for the numbering hierarchy can be agreed prior to discovery and the above is to be used as a guide not the definitive form. The parties should consider whether each page should be individually numbered or agree on some other satisfactory arrangement. If agreement is not reached then the parties should seek the Court’s direction. If the parties agree not to number each page, consideration should be given to an additional field recording the number of pages in each document. Attachments to documents can be separately listed and numbered. Attachments can be numbered sequentially following the host document. For example, a host document may be numbered XXX.001.001.0001 and its attachments would be numbered as XXX.001.001.0002, XXX.001.001.0003 and XXX.001.001.0004. If imaging is to be used the parties can agree to any additional information about document identification. It is recommended that the document ID match the image file name i.e. where the document id is AAA.NNN.NNN.NNNN then the image file name should be AAA.NNN.NNN.NNNN.tiff
Attachments	Text & Number, Length -depending on the number of attachments	Contains first and last pages of each document physically attached to a discovered document. Does not include documents that are only referred to in a discovered document. Each attachment should be listed separately, with its own discovery number and details. Multiple entries to be separated by commas.
Host Document Number	Text and Number, Length depending on the document ID structure	Contains First Page and - if agreed - Last Page of the host document to which an attachment is attached. Should never be multiple entries in this field, as each attachment should only ever have one host document.
Document Group	Text, 3	HWA Host with attachment HNA Host no attachment ATT Attachment This field may be required if parties agree to swap image files.
Date (Default field 2)	Date, 11	Date can be inserted as: DD/MMM/YYYY for example 05/Sep/1996 DD = Day MMM = Month YYYY = Year Undated documents: = Documents with no discernible date should be coded to a standard agreed between the parties which the parties will recognise as "undated." For example, the date field may be left blank. (Where this option is selected the parties may choose to enter the word "undated" in an additional text field.) Alternatively, an agreed date format such as 01/Jan/1801 should be used. It is important to note that databases that use a Date Type format may not accept text such as 'Undated' or dates that include '00' in the field. If there is no way of ascertaining the date of the document*: Documents with only the month and year (e.g. August 1997) can be coded with the first day of the month, the month and the year (e.g. 01/Aug/1997) and a 'Yes' an entry should be made in the next field - "Estimated Date" field. Documents with the day and month but no year are considered undated. For example, a document dated 04/Apr will should be coded as "undated." as the year cannot be identified. Documents with just the year (e.g. 1997) should be coded with the first day of January (e.g. 01/Jan/1997) and a 'Yes' entry should be made in the 'Estimated Date' field. *If there is no way of ascertaining the date of the document, then the parties may agree upon what naming convention to use, for example, "Undated", or 00/00/0000, however, it should be noted that some database formats may not recognise these codes.
Document type (Default field 3)	Text, 254	This field is completed using commonly received document types e.g. letter, memo, deed. Parties should endeavour to create a list of agreed document types prior to discovery. If the document has been faxed, this field should include "facsimile". If a group of documents is being discovered as a bundle, this field should be completed as "Bundle of document type".
Privilege	Text, 6	This identifies whether a claim of privilege is made over the document. The permissible entries in this field are "YES", "NO" and "PART". If this field is completed with "YES" or "PART", the basis of privilege field must also be completed.
Basis of Privilege	Text, 50 (or combination of text and numbers)	Identifies basis of privilege claim. Parties should agree how they will identify privilege claims. One possibility is to set out here the basis of the claim that the document is privileged eg, the section or sections of the Evidence Act.
Status	Text, 10	"Copy" or 'Original' or "Fax". "Fax" should be used for a document that is either the original facsimile document (i.e. the document sent by the sender) or an original facsimile copy produced by the recipient's facsimile machine.
Author (Default field 4)	Text, 254 or as appropriate	Person or persons who wrote the document. To be completed using information on the face of the document. Last name First initial only eg. "Smith B". If more than one author enter as "Brown J; Jones J, ..." etc. If more than one addressee for one company, enter as "Brown J; Jones J;..." etc. Other ways of addressing multiple values can be agreed between the parties.
Author Organisation (Default field 4)	Text, 254 or as appropriate	Organisation from which the document emanated. To be completed from information on the face of the document. Multiple entries to be separated by commas. Parties should agree on standard spellings or abbreviations for organisations. Other ways of addressing multiple values can be agreed between the parties.
Addressee (Default field 5)	Text, 254 or as appropriate	Person or persons to whom the document is addressed. Includes persons to whom copies are circulated. To be completed from information on the face of the document. Last name First initial only eg. "Smith B". Multiple entries to be separated by commas. Other ways of addressing multiple values can be agreed between the parties.
Addressee Organisation (Default field 5)	Text, 254 or as appropriate	Organisation receiving the document. To be completed from information on the face of the document. Multiple entries to be separated by commas. Parties should agree on standard spellings or abbreviations for organisations. Other ways of addressing multiple values can be agreed between the parties.
Parties	Text, 254 or as appropriate	Identifies parties to an agreement or other legal document (not correspondence). Multiple entries to be comma delimited.
Title (Default field 6)	Text, 254 or as appropriate	Title of a document such as “Report on Technology”.
Source	Text, 20 or as appropriate	Parties may find this field useful to identify documents that have been obtained from someone other than the party giving discovery, e.g. documents obtained on subpoena or through some other compulsory process of obtaining access to documents. This field would identify the party from whom such documents were obtained.
Non-paper record	Text, 3	This field should be used to identify information recorded using media other than paper, where the relevant information has not been printed out and discovered in hard copy form, e.g. video and audio tapes, floppy disks and magnetic computer tapes. Permissible entries are "YES" and "NO".