Skip to main content
Service of Process
Search
Search Legal Tracker Help and Support.

This article applies to:

  • Product: Legal Tracker
  • Audiences: Company

Logs, Reports, and Audit History

All activity with respect to SOP records in Tracker is audited and maintained in the audit history in the system.

View the log of all SOP records

  1. Click
    Reports > Reports list
     from the left navigation.
  2. Select
    Service of Process - Responses Due
    from the
    Matter Info Reports
     section.
  3. Select the criteria for generating the report.
  4. Click the
    Export CSV
     button to export the data to a spreadsheet.
note
The default criterion for this report is to show only those SOP records for which a response is due. To view all SOP records, change the
Response Due Filter
 to
All Service of Process Records
.

View the audit history for an SOP record

1. Open the relevant SOP record.
2. On the SOP profile, scroll to the Service of Process Data section to View Audit History.
The audit history shows all download activity, routing to a matter, error resolutions, as well as changes to certain fields. See the next section below for information about which fields are audited.
Audit fields in an SOP record
Changes to the following fields are displayed in the SOP audit history:
Field Name
Sub-Field Name (if applicable)
SOP Type
N/A
Notice of Appearance Made
N/A
New Response Attachment
N/A
Response Date
N/A
Response Due Date
N/A
Service Received or Delivered
N/A
Adverse Attorney Info
N/A
Date Served
N/A
Case Number
N/A
Filed Date
N/A
Method of Service
N/A
Defendant(s)
N/A
Plaintiff(s)
N/A
Province/Region
N/A
Served On
N/A
Court/Agency Country
N/A
Entity Served
N/A
Entity Name on File
N/A
Authors
N/A
Forum
Court/Agency Country
Forum
Court/Agency State
Forum
Province/Region
Forum
Forum
Forum
Additional Court/Forum Information
Adverse Attorney Info
N/A
Response Due Date
N/A
Response Received Due Date
N/A
Notice of Appearance Made
N/A
Has Response Been Filed
Response Date
Has Response Been Filed
Attachment Type
Has Response Been Filed
File
Has Response Been Filed
URL
Has Response Been Filed
Location
Has Response Been Received
Response Date
Has Response Been Received
Attachment Type
Has Response Been Received
File
Has Response Been Received
URL
Has Response Been Received
Location
Notes/Miscellaneous
N/A
Status
N/A
Review Requested
N/A
Allow File/URL to be Replaced
N/A
Folder
N/A
Access Security
N/A
SOP Person Responsible
N/A

View the audit history of download activity from CSC or CT Corp.

View the Batch History page
The Batch History page shows the entire history of all SOP downloads from CSC or CT Corp., whether there were any errors in the batch, and the number of SOP records included in the batch.
Required role | Only a company system administrator, Default SOP Intake User, SOP Intake User, or SOP Escalation User can view the Batch History page.
  1. Click
    Library
    in the left navigation.
  2. Click
    SOP Intake
    .
  3. On the
    Actions
     menu, click
    View Batch History
    .
Export the Batch History
To export the batch history, on the Batch History page, click
Export CSV
.
This detailed spreadsheet of the batch history will have a row for each download (a batch row) and a row for each SOP record in a batch. Thus, if the Batch ID is listed only once, there were no documents in the batch. If a Batch ID is listed three times, there are two documents in the batch: one of the rows represents the batch itself, and the other two rows are for the two SOP records.
Fields in the Batch History export
Field
Comments
Tracker. Batch ID
This is the unique Batch ID assigned to the download.
Batch Date
This is the date on which the download occurred.
Batch Time
This is the time at which the download occurred. The time is always Pacific Time.
Batch Run By
If the Batch was manually run by a user, the user's name will be shown.
Vendor SOP ID
This is the unique ID used by the SOP Vendor. Use this number if you contact your vendor about a specific SOP record (CSC calls this unique ID the documentID. CT Corp. calls it the LogID).
This field will be filled in only for rows in the export that relate to an SOP record. It will be blank for any batch row. You can use document search to find an SOP record in Tracker.
Vendor SOP Version ID
This field is applicable only to CSC. When an SOP record is readied for download, CSC prepares an XML file and generates a unique ID for that XML file (the CSC field name for this ID is the sequence). Thus, if CSC requeues an SOP record multiple times, the record will always have just one Vendor SOP ID, but each version available for download will have a unique Vendor SOP Version ID.
For CT, the content of this field should be N/A because they do not generate a unique ID for each XML download.
Tracker SOP ID
This is the unique ID assigned to the SOP record in Tracker.
Error/Issue
This field shows the details of any errors. if the row in the export is a batch row, the error is a batch-level error. If the row is an SOP record, the error is a document data error.
Error Level
This field indicates whether the error shown for the row is a batch-level error or a document data issue.
Resolution Status
If there is an error shown for the row, this field will show the resolution status (resolved or unresolved).
Resolution
If there is an error shown for the row, this field will show the resolution status.
Vendor Checksum
This is the number of SOP records that the SOP vendor has received in the last 30 days. For CSC, this is the number of SOP records that have a Date Served within 30 days of the date that the batch was run. For example, if the batch was run anytime on January 15 (Eastern time), the date range for calculating the checksum is December 17 - January 15.
For CT Corp., this is the number of SOP records that have a Date Created within the past 30 days (counting up to midnight of yesterday).
Tracker uses this number as a validation to ensure that all SOP records received by your SOP vendor have been downloaded into Tracker. If the Vendor Checksum does not match the number calculated in Tracker, there will be a batch error because the checksum could not be validated.
Best practice: We recommend that you wait at least 30 days after SOP is set up to enable checksum validation. This will avoid erroneous checksum and retrieval errors. During the 30 days, continue to receive your SOP records from CT Corp or CSC using your original method. After the 30 days, you can enable checksum validation and the calculations will be accurate.
View the Batch Profile page
The Batch Profile page shows the details of each individual batch, including the specific SOP records, and any errors and their resolution. On the Batch History page, click the
Batch ID
 link.