Primary uses
What Clearpath clients are tracking with Collect apps
| Goal | Examples |
|---|---|
| Supplement missing data in a source system | Adjuster follow-up calls; slowly changing dimensions like agency-to-agency grouping over time; department or region names |
| Organize or group data | Grouping policies by renewal cohort or territory; consolidating tax IDs for a group of affiliated agencies |
| Create a standalone data-capture system | Catastrophe (CAT) response intake forms; manually entered data a source system produces only as a hard-to-parse PDF |
| Custom purposes | Financial class groupings not supported by a source system; mapping a source system's loss code to a standard code; consolidating spreadsheets used by a single team; subrogation referral tracking; fraud-referral logs; producer license exception tracking; executive rollup structures; survey questions and responses |
When to use (or not use) Collect
Collect is excellent for:
- Cross references
- Sorting and grouping
- Manually augmenting source data
Collect is not optimized for:
- Data sets requiring frequent maintenance
- Automated business logic
- High-volume, recurring transactional work
Don't use Collect to capture data that belongs in your policy or claims system of record.
API access
Extend Collect's API to your reporting and BI tools through a RESTful web service. Users can update existing data based on what they see in the presentation layer.
See the Clearpath Collect API Reference for details. From anywhere within Collect, click your username, then About, then API Reference.