Collecting and Analyzing Outcomes Data

The basic procedures and systems programs use to collect and analyze outcomes data about their client services can be relatively simple conceptually. Once a program identifies the specific types of data it wants to use (e.g., financial and non-financial benefits provided clients in a case), it must implement systems with the functionalities to:

  1. Enable case handlers to easily enter these data into their program’s case management systems (CMSs) at the time they close a case; and,
  1. Aggregate these data and generate a range of reports in formats that present data in formats that enable the program to effectively analyze and present data for a variety of purposes (e.g., assessing success in accomplishing mission and goals, developing strategies and allocating resources and developing strategies, fundraising).

Procedures and Data Management Systems for Collecting Outcomes Data

Several steps are required for programs to effectively and efficiently collect outcomes data.

  1. Programs must first identify the types of outcomes data they want to use and therefore collect. Read more about this.
  1. Case handlers must identify and record in the case file the results of individual extended services cases when they close the case. For example, the case handlers identify whether the client obtained a civil protection order, avoided eviction, obtained (or retained) SSI benefits and so on.  Since this is considered a case handling “best practice,” many programs require their case handlers to document this information in the case file, even if the program does not use a systematic outcomes data system. Learn more about the types of outcome measures used by many legal services programs.

Programs typically collect these data only for extended service cases (LSC CSR case closing codes F-L), not for limited services cases (LSC CSR case closing codes A and B).  It is relatively easy and inexpensive to capture outcomes data for extended services cases because case handlers, know when they close a case, what the outcome(s) of a particular case is (are) and can record this information on simple forms or enter it into specified fields in the CMS.  In contrast, it is costly to identify the results of limited services cases – for example, follow-up services or similar means are required to obtain this information – and the ultimate outcomes of these cases may be determined by factors unrelated to the program’s representation – e.g., to what extent and in what ways did the client act on the advice provided by the program.

  1. Programs must incorporate these functionalities into their CMSs:
    1. Enable case handlers or other staff to readily input into the CMSs (or similar data bases) the outcomes of extended services cases. See the CMS form that a CLAS case handler completes at case closing to provide financial and non-financial outcomes data for a Consumer case.

BRLS case handlers do not directly enter case outcomes data into the CMS.  Instead, they complete a case closing memorandum which capturesthis information; the information is transferred into the CMS later. See the case closing memorandum form that identifies the outcomes data BRLS case handlers document at case closing.

    1. Capture that data in fields related to other CMS fields, so that the outcomes can be linked to type of case, level of service, and other key fields.
    2. Provide the efficient transfer of these data into the system(s) that will produce outcomes data reports.
“Off-the-Shelf” vs. Program-Specific Systems for Collecting Outcomes Data

Some programs use (or adapt) their vendor-provided case management system to collect and store outcomes data.  The vendors of the different CMSs used by the large majority of LSC grantees (e.g., Legal Server, Kemps CaseWorks, Legal Files, PIKA) have informed LSC that their systems have the necessary functionalities for collecting outcomes data or that these capacities can be incorporated into systems.  Contact the vendor of your program’s CMS for more information.

Other programs develop and implement tailored CMSs to collect and store outcomes data.  Learn more about the system CLAS developed and implemented to meet its particular needs.

Systems for Developing Analytical Reports with Outcomes Data
  1. Once they have the CMSs (or other data base systems) for collecting outcomes data, programs need to develop and implement system(s) with the capacities for aggregating these data and generating the types of outcomes data reports that will meet their particular needs.
  1. Programs do not need sophisticated statistical and qualitative data analysis packages to generate useful and effective outcomes data reports. (Click here and here for information about some those packages.)  Instead, they can use database systems that are already used by many legal services programs.

For example, BRLS uses Excel to generate a variety of outcomes data reports, while CLAS uses Crystal Reports to compile data and generate a variety of reports with outcomes data. Learn more about reports that programs generate to analyze the results of their client services on a variety of dimensions.

008732-high-resolution-dark-blue-denim-jeans-icon-arrows-arrow11-left-psOutcomes Data Reports

Developing an Outcomes Data System 008732-high-resolution-dark-blue-denim-jeans-icon-arrows-arrow11-left-ps