Missing accident dates and negative case reserves should stop the run, not get buried in a footnote.

Before any development factor is trusted, the claims file has to answer basic questions. Accident date present. Case reserve non-negative. Paid not above policy limit without a documented recovery.

numdog logs those exceptions with a status: blocking, review, or reconciled. Blocking items keep the triangle from pretending the data is clean.

A short dated list beats a long narrative

Each exception needs enough detail to reopen the claim. Count of claims, the field that failed, and what was done.

When Schedule P Part 1 ties later, the reconciled exceptions stay in the file as proof of what was checked.

Exceptions that usually block assignment:

• Accident date absent
• Negative case reserve
• Paid above stated policy limit
• Coverage mismatch on the segment
• Duplicate claim keys across systems
• Recovery posted to the wrong period

Review status is for items the actuary can accept with disclosure. Blocking means fix the data first.

That discipline is ASOP 23 in practice, not a slide about data quality.

If the exception is not dated, it did not happen for the review.

The triangle is only as honest as the exception log that precedes it.

‍