Ontario E-Filing Programs - How they Work and What they Do and Do Not Do

Douglas Coo J.

[1] E-Filing may well be one of the major developments in court systems over the next decade.

[2] The Ontariosystem has no application to the practice of criminal law. Use of e-filing is not obligatory. Over the short term you will not attain great volume unless use of the system is mandatory, or unless the system just involves a routine e-mail or a fax.

[3] A bilingual E-Filing program has been in operation for some years in Toronto, a very large city in terms of geographical area and population. One has commenced outside Torontowith a new electronic program at three sites, Hamiltona middle size city, the Small Claims Courtin Toronto, and Cochrane, a small city with a major bilingual population. It will expand slowly, as it becomes sure that the new program works without major flaw.

[4] It is uncertain, but likely, that the E-Filing project will continue, whatever may happen, and may very well already have happened, to the Ontario Integrated Justice Project, which has been experiencing financial, business, political and technical difficulties, with special regard to a non-functioning case management program. The Project may well be at an end, in its present form, but it has in no way been adversely affected by the E-Filing Project.

[5] The Toronto Superior Court system has worked well with an existing local case management program, SUSTAIN. It was and is presently dependent for its smooth continuation on updating to take into account new versions of Word and WordPerfect. There have had to be several versions of the E-Filing program to accommodate law offices using various versions of word processors. This was, and is, a costly and time-consuming process, which has been avoided in the new program, which is not dependent on any version of a word processor, but does depend on time-consuming form creation.

[6] There are plans to accommodate the self-represented litigant, an ever-increasing segment of the litigating public, but this is not yet possible.

[7] A series of e-filing forms have been developed that produce in the rendering an exact copy of the regulatory version of the form in text and formatted appearance, so that anything printed looks exactly like 'the original'.

[8] What is filled out as a document to be e-filed is an electronic form that may be completed online or offline. These forms have been and are the subject of time-consuming and expensive technical work. There are sub-committees working on a continuing basis on civil and family law forms.

[9] There is a partial alternative, that is to attach text in PDF format to the e-filed form. PDF was originally considered to enhance security, although that attribute of the system may presently lack real strength, whatever advantages may remain with the format.

[10] The system is based on legal XML tagging, so that when the new electronic case management program is in place, all the information in the e-filed document will be deposited in the correct place within the folder or file of the case. It will be instantly accessible, capable of comparative analysis for managerial purposes and printable from within the program. All documents in a case will be electronically stored and readable online.

[11] The basic way the system works is that the filer or court clerk uses a Web Browser to communicate with the E-File system through the Internet and the government network. The E-File system is actually a set of servers, including a Web Server (which responds to user requests by collecting and formatting information so that the user's Web Browser can understand it and display it as a web page), and a Database Server (which stores all the information so the Web Server has ready access to it). When a filer uploads a filing through his browser, it is stored on the Database Server at that time. When a court clerk signs on to the system, the Web Server communicates with the Database Server and shows the court clerk what the filer has stored there. So unlike e-mail, where a message is passed from one computer to another over the internet, the E-File system has all users communicating with the same computer(s) to access data.

[12] The user can only gain access to the very limited and required part of the GoNet through an SSL security utility. Internal government connection is through the PKI security system that is at the heart of the Ontario government network. There is encryption of communication of information within the system. There is a firewall in place that permits travel through it only of 'expected' sorts of information.

[13] The user requires a Web Browser (only Internet Explorer is supported, although Netscape will work, with a few formatting anomalies).

[14] The user also requires an Adobe FormFlow program that comprises two main components: the form end-user components and the Filler. The end-user components enable the integration of FormFlow electronic forms into a wide variety of environments, such as the Web in our case, Microsoft Outlook and Microsoft Office applications. The Filler is a standalone application that presents FormFlow forms to the user. Its simple user interface allows the end user to save, retrieve, mail and print the document.

[15] The user requires a JetForms Filler program so that he or she can create and enter required data, on or off-line, in forms to be deposited at the Website. (The JetForms product was bought by Accelio, which was acquired by Adobe in April 2002.) Information can be found about the Adobe programs at http://www.accelio.com/products/products_capture_formflow.cfm

[16] Finally, the user requires the free Acrobat Reader.

[17] A good deal of work has been going on in dialogue with private legal forms providers, with a view to exploring the capacity and interest of such firms and technical and computer organizations in the development of all-encompassing systems. They would enable sophisticated law firms to make use of integrated systems, more easily, quickly and smoothly to prepare, check, record, archive and deposit information through the court E-File system. Some progress has been made in this area, but the complexity of the presently-used forms and the macros used by law firms in creation of documents and the storage and use of electronic information has made this task a difficult one. The lack of user-friendliness and the complexity of filling out forms must continue to be addressed, if the system is to attract lawyers. This must be accomplished before any consideration could be given to making e-filing obligatory.

[18] The E-File program requires a broadband transmission facility.

[19] It must be capable of being run with what are sometimes very sophisticated law office computer systems and must not require additional expensive programs to be installed on lawyers' computers.

[20] Work has been going forward to upgrade the system to allow many law firm employees to use the system without separate security password requirements.

[21] A PAD payment system may still be introduced into the next version of the program. It has been in development for some time.

[22] An E-Filing system requires training for:

  • lawyers, so that they can understand it,
  • law clerks and secretaries who will use it,
  • court office employees, including present 'counter', back office, and technical staff,
  • judges, so that they may understand the fundamentals of what it will do and what it will not do. It need not touch judges' daily lives, except for what will be the new method for taking a look at a file or a document in it; and even in that context the old world of paper as a copy of the 'real' document will probably remain for the indeterminate future.

[23] It must have a set of protocols and liability rules and provisions to deal with when the 'electronic court' is open for filing.

[24] It must have a development team which understands what filing is all about.

[25] The OntarioE-Filing Project has:

  • a Chair,
  • an Executive Committee composed of a very small group of judges, lawyers and administrative persons,
  • a Working Group, which oversees problems and their solution and the development of new program versions. The Group is composed of judges, a cross-section of lawyers representing various active bar groups, court staff, administrative personnel, technical persons with various kinds of expertise and Ontario Integrated Justice Project representatives.

[26] The Ontariosystem has created users' committees at each site where the system operates, composed of lawyers and their administrative assistants, court staff, technical personnel and judicial representation. It is only by close cooperation within these groups, and between representatives of the groups, that developmental progress can be made.

[27] Notes follow as to the forms process and structure, to give some idea of the present complexity of the process. They represent nothing more than a general overview.


Forms Process Outline

Definition

[28] The term "form" or "forms" refer to the data entry template used by filers to construct court documents.

E-File Forms Project Structure

[29] E-file forms is a sub-project of the Integrated Justice Project's (IJP) Courts Project

[30] It consists of:

  • an IJP Forms Development Team
  • an IJP Forms Testing Team
  • three stakeholder committees focused around specific law practice areas
    • Civil
    • Small Claims
    • Family Law
  • a technical group Application Architecture (AAR)
  • the forms developer Relizon and CDIT

[31] There are several processes involved in developing electronic forms:

[32] In conjunction with the sub-committees:

  1. establish and confirm a list of identified forms which are to be developed and organized by area of law
  2. prioritization of the confirmed list of forms. IJP has prioritized its forms by:
    • pending - (forms confirmed for initial development and prioritized by volume of use, completion of a court process, business change impact and development complexity)
    • pending - infrequent / low priority
    • pending - to be determined - (rarely used or forms not always filed with the court and requiring determination whether or not they are to be developed)
    • out of scope - forms that will not be developed as part of the E-File Forms Project

[33] The typical process is:

  1. The Forms Development Team (FDT) will prepare:
    • a PDF version of the form containing the XML (data entry field) tagged fields. Each field is identified by a tag number assigned to it by AAR from their links database and the IJP data model.
    • A mock-up of the data entry form is prepared by the developer to show how it will look to the filer.
    • A "draft" Forms Definition Report (FDR) is prepared which provides the initial specifications of the form (e.g. tag number, type of field [text, alpha], number of characters in the field, validation requirements and messages, business rules etc.)
  2. An initial vetting of these three documents is performed amongst members of the FDT following which the FDR is reviewed with AAR to ensure compliance with the IJP data model and field definitions.
  3. A second vetting is performed amongst members of the FDT in preparation for meeting with the sub-committee.
  4. The tagged PDF, mock input form and FDR are distributed to the sub-committee members to allow them to prepare for the meeting.
  5. The sub-committee meets and reviews the specification of the form considering:
    • how well the functionality appears to fit the actual work environment of the filers
    • compliance of the form to court rules, legislation, regulations and policy guidelines
    • how well the form will work within the court processes
    • identification of additional issues to be addressed
  6. Following the sub-committee meeting, notes of the meeting are drafted confirming discussions and agreements.
  7. A post-committee review is performed amongst members of the FDT where substantial changes are required to confirm the approach to be taken.
  8. The tagged PDF, mock input form and FDR are updated as required and reviewed with AAR. This takes place in the form of a vetting where the FDT will confirm that AAR has mapped the data fields to the correct components in the IJ data model.
  9. The tagged PDF and mock input form are sent to the French Language Services (FLS) Branch of the Ministry of the Attorney General for translation of new text and confirmation of existing French text.
  10. On receipt of the translations from FLS, the tagged PDF, mock input form, FDR and French versions of the tagged PDF and mock input form are sent to CDIT to develop the form as specified.
  11. On receipt CDIT develops the form obtaining necessary clarifications from the FDT.
  12. Once development is complete CDIT forwards the form to AAR who "promotes" to the test environment (loads it on the server).
  13. The Forms Test Team (FTT) in conjunction with the FDT prepares English and French "Test Scripts" using real examples of forms that are filed in the courts.
  14. The FTT conducts detailed functional, business and transactional flow testing, document results, which includes data entry, rendering of the regulated version of the form and proofreading for content identifying any defects that must be corrected. This cycle is repeated until all defects have been fixed/resolved.
  15. The French or Bilingual versions of the form are proofread and signed-off by FLS.
  16. Once the defects have been fixed (this requires additional testing) the form is ready to be moved into the production environment (computer server) for access and use by filers.
  17. Depending on the complexity of the form the entire process can take from approximately 4-6 weeks to 3 months.