How many claim closures leave a supplemental item unpaid?

Question and scope

Start with one claims unit and ask what the closure supplemental items file can actually prove. Treat the answer as a local reading of retained records, not an industry rate, a coverage opinion, or a reserve estimate. Fix the population and the calendar window first, and print both beside every table. A supervisor with the same claim export should be able to repeat the steps without help.

Treat closure supplemental items as an evidence question, not a liability or damages question. The test is whether a stranger can walk the claim from the source document to the recorded action. Freeze the unit, the population, and the window below before pulling the first file. The last section should say what the review cannot see.

The question is whether a closed closure supplemental items file lets a second examiner locate the source, the reviewer, and the decision date. Use the result to tighten one desk process, never to grade an adjuster or a policyholder. Only the population named below is in scope, and the rest of the claim book stays outside. This is a working method for a claims unit, not a dashboard product.

Population and unit

Draw from claims closed during the observation window. Lock the export date, the systems in scope, and the duplicate rule before outcomes are visible. Keep a claim with a missing document, a conflict, or no available examiner in the denominator unless the plan says otherwise. That choice stops the rate from improving because the awkward claims were set aside.

Define the unit as one claim closed during the observation window, and count it once under a rule written beside the extract. Name the opening event, the closing proof, and the pause condition before selecting any claim. When the inventory changes size during the window, a bare total stops being a measurement. Record every removal with a reason so a colleague can rebuild the list.

Definitions and measures

A claim counts as complete when it supports the share of closures with an unpaid supplemental item with a dated source and a named reviewer. Settle how a reopened claim and a duplicate claim are counted. Print the sample count, the unresolved total, and the oldest open item under each result. Those three figures keep volume, evidence, and delay from masking one another.

Keep a compact field guide that names each field, its permitted values, and the record that proves it. Put blank, unavailable, and confirmed-negative answers in separate columns. The headline figure is the share of closures with an unpaid supplemental item, and it never appears without the denominator and the window. A percentage alone cannot tell a desk what to repair.

Define a finished closure supplemental items file before opening the claim export. List the documents required, the source accepted, and the treatment of a blank field. Report the share of closures with an unpaid supplemental item with the eligible count and the exact window dates. Beside it, show the missing-document count and the age of the oldest open claim.

Evidence standard

Every sampled claim must show the source, the observation time, the field it proves, the reviewer, and the accountable owner. Keep policyholder detail in the claims system and put only a reference in the review note. Accept only evidence the plan can defend, even when a cleaner summary is easy to write. A complete file does not prove the coverage call was right, and the report should say so plainly.

A claim passes only when and sit in the approved system under the same claim number. Where two records conflict, keep both and record which one drove the decision. Mark every estimated figure as an estimate so a later reader cannot mistake it for a verified value. The aim is a trail another person can follow, not a flawless folder.

Sampling and collection

Pull claims from the whole window, including the week when staffing was short and volume was high. A list built only from quiet weeks will make a weak control look stable. Record the observation time and the initials of the person who opened the file. When the eligible list is short, show the raw count and state that the estimate is unstable.

Choose a random or systematic start, then take consecutive claims within each stratum. Stratify by claim type, examiner, and exception so the easiest files cannot dominate. Include one hard case: a missing document, a conflict, an absent examiner, or a deadline that forced a quick call. Log every access failure instead of quietly replacing the claim with another.

Start the extract with the claim export for closure supplemental items, not a set chosen after the result is known. Keep the selection rule, the seed, and the exclusion log with the sample. Add nothing once the result is visible, and drop no hard claim to improve the rate. A repeatable draw lets the unit rerun the review after the workflow changes.

Analysis and reporting

Ask whether the retained file justifies the recorded action, not whether the unit appeared busy. Break the result out by claim type, examiner, and exception so the weak spot becomes visible. Give a range or a raw count when the sample is thin instead of implying precision. End each report with one proposed change and the measure that will reveal whether it worked.

Publish the spread, not only the average, because a median can hide a long tail of untouched claims. Show the open count and the oldest claim by examiner, then point to where delay collects. A finding without an owner or a next step is not ready for the desk meeting. Write the result in ordinary language and keep technical detail in an appendix.

Limits and sources of error

One hard limit is that a closure supplemental items record can be late, partial, or held outside the claims system. The method cannot recover work that left no trace or prove that a policy was applied in a silent file. Print those caveats beside the finding rather than burying them in a footnote. Changes to systems, state rules, vendor mix, or volume can date the result, so list those triggers.

Sampling error, coder disagreement, and records that never reached the system each cap what the number can claim. Publish the overlap agreement and any disputed code rather than declaring the coding clean. One unit and one window produced this number, so it cannot stand in for an industry benchmark. The closing paragraph states what the review still cannot see.

A finished file does not prove the coverage call was right, because this review scores documentation rather than claim quality. The design cannot read intent and cannot describe a claim that left no trace in any system. Put the caveats directly under the finding so a reader cannot lift the number without them. If the rule changes midstream, keep the earlier and later versions and tag each claim.

Review cadence

Make the follow-up sample reuse the guide and the population rule so the comparison means something. If the rule changed, mark each claim with the version that applies and keep both extracts. Rerun the measure after the repair and report whether the gap actually narrowed. A decision someone can reproduce matters more than a precise-looking number.

Put the next review on the calendar and name one owner for the measure and the follow-up. Close with a single process change, its owner, and a recheck date, not a wish list. If the same defect returns, repair the form, the source, or the routing rule before retraining anyone. Reuse the same sampling rule and store the note beside the change record.

Method note

We reviewed the public sources listed below in their original scope and translated recurring operational ideas into review questions. No claim outcome study was conducted.