1 00:00:01,000 --> 00:00:03,758 A new claim often arrives with several documents 2 00:00:03,778 --> 00:00:05,038 and missing details. 3 00:00:05,822 --> 00:00:09,158 Foxit IDP helps intake teams organize that information 4 00:00:09,178 --> 00:00:11,682 without retyping every field. 5 00:00:12,422 --> 00:00:15,424 In this example, the packet contains an incident notice 6 00:00:15,444 --> 00:00:17,060 and a repair estimate. 7 00:00:17,822 --> 00:00:20,793 Our extraction schema defines the case, policy, 8 00:00:21,756 --> 00:00:25,460 claimant, asset, incident dates, and estimate details. 9 00:00:26,422 --> 00:00:28,882 The workflow brings the packet into data extraction 10 00:00:29,189 --> 00:00:31,402 and makes the results available for review. 11 00:00:31,422 --> 00:00:35,416 We open the processed packet alongside the original pages. 12 00:00:36,289 --> 00:00:39,704 Foxit IDP has extracted the case number, policy, 13 00:00:40,311 --> 00:00:41,616 and claimant from the notice, 14 00:00:41,956 --> 00:00:44,149 together with the repair estimate details. 15 00:00:44,933 --> 00:00:48,593 The estimate is USD 1,850. 16 00:00:49,378 --> 00:00:51,402 The case reference on the estimate is available 17 00:00:51,422 --> 00:00:53,549 alongside the reference from the notice, 18 00:00:53,889 --> 00:00:55,260 making comparison easier. 19 00:00:56,311 --> 00:00:57,882 You define the fields in the schema. 20 00:00:58,400 --> 00:01:01,038 The system locates the information in the documents. 21 00:01:01,733 --> 00:01:03,558 Now we open another packet 22 00:01:03,578 --> 00:01:05,127 where the loss date is missing. 23 00:01:05,956 --> 00:01:07,638 The loss date appears as unavailable 24 00:01:08,156 --> 00:01:11,171 while the reported date and estimate date remain separate. 25 00:01:11,933 --> 00:01:14,993 The intake team can see which information to request next. 26 00:01:15,800 --> 00:01:18,580 Foxit IDP helps turn incoming claim documents 27 00:01:18,600 --> 00:01:21,927 into a clear, structured starting point for review.