When a loss is first reported, it’s recorded with a fixed timestamp in the activity log, serving as the starting point for later entries. Log records are automatically sorted by transaction time, with the newest actions at the top. Earlier entries are kept in older index pages. Each record includes a user ID, office code, and a code for the action taken from a list of options. Documents are filed based on when they were uploaded, not when the event happened, creating separate filing systems from the routing order in the activity log.
The claims system used by the third-party administrator (TPA) has its own activity log. Entries in that log are in order, starting with the initial acknowledgment and moving forward. An updated estimate uploaded by the TPA might show a timestamp of 2:16 PM in their system, but when it’s imported into the carrier’s claim system, it shows up at 2:03 AM the next day because of batch synchronization. The logs show the same event happening at different times due to different system clocks.
Document Storage
Within the carrier’s claim system, the document index organizes files by upload date and type. Photos from a repair network are under Vendor Attachments, while legal letters are under Correspondence. Each file is given a document ID and page count. Opening a document opens it in a viewer panel without changing the sequence in the activity log. The viewer tracks the access in a background audit table that is not visible on the main screen.
In the repair network portal, data about invoices and billing codes is separate from the attached PDFs. The portal’s log includes invoice numbers, unit cost codes, and tax information in a table. When a PDF invoice is sent to the claim system, it loses its billing data and becomes a static image in the document storage. The billing codes remain in the repair network database, only accessible through that portal.
Legal Paperwork
Demand letters are entered through a legal system that is separate from the claim system and the TPA portal. The legal system assigns a case ID that is connected to but different from the claim number. The letter is scanned and stored with a document ID specific to the legal database. During nightly processing, a copy of the letter is sent to the claim system’s storage, with a new document ID and timestamp.
The legal intake activity log tracks service dates, response deadlines, and assigned counsel. The claim system’s activity log only shows the import event and any notes from the adjuster about the letter. Each log grows on its own. Changes to legal case notes don’t change the entries in the claim system’s log.
City and County Interfaces
Permit records for building losses are taken from city websites outside of the claim and TPA systems. An examiner copies permit numbers into a claim note field. The permit document can be saved locally and uploaded into the claim storage. The upload time shows when it was attached, not when the permit was issued.
Sometimes, the TPA platform also has a field called “Permit Verified,” that must be checked manually. The claim system and TPA portal don’t share this status automatically. Each system has its own indicator, and activity logs in both systems record entries for the same city verification.
Appointment Windows
Inspection appointments are scheduled through a scheduling program separate from the claim and legal systems. The scheduling program shows available times for field adjusters and engineers. Once an appointment is set, the scheduling log is updated with the date, time, and assigned staff. An automated email sends confirmation to the involved parties.
The claim system records “Inspection Scheduled” in the activity log after synchronization. The timestamp in the claim log reflects the synchronization time, not when the appointment was made. The scheduling program keeps the original booking timestamp in its own log. If an inspection is rescheduled, the scheduling database records extra entries, while the claim system shows a single “Inspection Updated” entry tied to the latest synchronization.
Paying Bills
Payment processing is done in a financial module that is connected to but separate from the main claim system. Draft payment entries include claim numbers and vendor IDs. The billing module tracks each draft creation and approval in its own log. Once approved, a payment confirmation number is sent to the claim system, showing up as a new activity log entry.
The billing log keeps detailed information such as tax withholdings and bank routing confirmations. This data is not sent to the claim system’s document storage. Instead, the claim system shows only basic details: check number, amount, and issue date. Both systems use the same claim number but have different filing structures.
Different Versions
Revised estimates and updated reports create multiple versions of documents across systems. In the repair network portal, an estimate revision replaces the old data but keeps a version history under a tab called “Revisions.” In the claim system, each revision is imported as a separate document entry. The activity log records “Supplemental Estimate Received” several times, without directly linking to the previous version.
Legal intake tracks changes within draft agreements. Each draft version is stored in the legal database with timestamps for the edits. The claim system only receives the final PDF version, uploaded as a separate document. The history of edits stays within the legal platform.
Escalation Records
When a claim exceeds the authority threshold, it is sent to supervisory approval queues within the claim system. Each routing event adds a new line to the claim’s escalation log. The TPA platform might show a similar status change called “Pending Carrier Approval,” but it doesn’t record the supervisor’s user ID or the exact timestamp from the carrier system.
Modules for watching out for fraud add another activity stream. If the system detects a pattern that might indicate fraud, a flag appears in the claim header. The investigative unit’s notes are kept in a separate module under a tab called “Special Review.” The main activity log has a summary entry noting the referral and clearance, without listing the investigative steps recorded elsewhere.
Archiving the Documents
Closed claims are moved to archival storage after a certain period. The claim system compresses document storage into a read-only format. The TPA platform archives its log under different retention rules. Legal intake has its own archive accessible through case IDs. Each archive keeps its filing order based on the original system design.
The activity log is sorted from newest to oldest. Imported entries from outside systems show their original timestamps in separate logs. Document storage lists attachments by upload time. Billing modules show transaction sequences under different IDs. Archival records show older versions. Previous formats are preserved.
