For claims, Groundspeed populates two related fields in the loss detail output to describe the relevant class of insurance business and coverage: line of business and linetype.
Line of business describes the class of insurance business the claim pertains to, and can include umbrella, package, or excess lines.
Linetype describes the underlying coverage type relevant to the claim, and does not include umbrella, package, or excess classifications.
In practice, these fields will always be the same unless the LOB is umbrella, package, or excess. In which case, the linetype will specify the underlying coverage type relevant to the claim.
The Groundspeed pipeline uses capture values, heuristics, and machine learning models to identify the line of business and linetype for a given claim in the following order:
The Groundspeed claim combination logic combines individual claim records that belong to one accident but were split in the source document.
To enable combination the logic performs two steps: identification of claims to merge and combining the data from the claim records.
The Groundspeed claim detail duplication detection logic works to identify individual claim records that are duplicates.
All fields must match in the record to detect a duplicate:
The Groundspeed claim summary duplication detection logic works to identify claim summary records that are duplicates.
The Groundspeed claim occurrence identification logic aims to identify a singular occurrence from which claims originated.
Examples include an auto accident, a hail storm, or an explosion at a factory which resulted in multiple claims.
|Product Type||Support Document Type|
|Setup and Clearance/Submission||
Excel/CSV loss report
Schedule of Hazards
CA WCRIB Emod
CA WCRIB Emod
Note: All versions and variants of each form will be supported. This includes state-specific variants, old form versions, and ACORD forms generated from an agency management system. For example: "Applied 130API," "INS 127," and "137 TX."
|125||Including: "ANI" and "CIS" supplements|
|130||Including: "ANI" supplement|
|137||Including: State-specific variants, ex. "137 FL"|
|139||Including: CISGEM C540 SOV supplement|
|160||Including: "ANI" supplement|
|OFSUPPNAME||Supplemental names of other named insureds|
|APDWCLOC||Applied WC form associated with the ACORD 130|
|OFWCRATE||AMS WC form associated with the ACORD 130|
|Unsupported Document||File extensions or file types that are not machine-readable, OR are not relevant to commercial insurance.
These documents will likely never be on our product roadmap
Signature Block Images
Audio, Video files
Low Image Quality
No data - empty files
Incorrect MIME/Content type
Files with handwriting
Files that do not pass virus scanning checks
Any Personal Lines Submission
|100||unsupported_file_type||The archive file type sent to our intake process was not on the list of supported file types|
|101||failed_virus_scan||The file, or the file container sent failed the virus scan step, and was quarantined|
|102||bad_zip_file||The file extension was a zip, however the file itself could not be opened|
|106||unsupported_document_type||No files within the zip are supported|
This list only covers commercial lines ACORD forms that we consider out-of-scope. All personal lines ACORD forms are out-of-scope at the moment.
Groundspeed uses doctype precedence to determine which document a field is pulled from. If that field is not present in any of the doctypes listed then that field will appear blank on the extract.
Example: “insuredName” in the submissionData section of standard submission extracts.
insuredName has a doctype preference order of slip, email, acord, policyform, brokerspec, exposuredoc, sov, application, and locationschedule.
Scenario: An insured name of “Acme Corp Inc.” is found on a slip doctype and an insured name of “Acme Corp” is found on a brokerspec in the same submission. Because the slip doctype precedes the brokerspec in the doctype precedence rules set for this field, the insured name presented on the extract would be “Acme Corp Inc.”