Claim chronology builder
Builds a dated chronology from claim notices, correspondence, contracts, invoices, incident records, and evidence logs, preserving source citations and disputed dates. Use for insurance claims, commercial disputes, incident files, demand packages, litigation chronologies, and internal fact reviews.
Published Aug 21, 2026 · Updated Aug 26, 2026
Requirements
Add the applicable policy, contract, or claims-handling procedure. Define the date format and deadline-counting convention. Map claim, document, and payment identifiers. Name the audience for the chronology brief.
Skill document
The full SKILL.md your agent reads and follows.
Claim chronology builder
Purpose
Assemble a source-grounded timeline for one claim so every event, obligation, notice, payment, and response can be traced to a document or record. Keep fact, allegation, and unresolved contradiction distinct.
Scope
Include the claim notice, policy or contract, adjuster correspondence, invoices, payment ledger, incident report, witness statement, and evidence register. Excluded: legal conclusions, liability determinations, settlement negotiation, and contacting witnesses.
Data basis
- Claim file with
claim_id,event_date,received_date,sender,recipient,event_type,amount,document_id, andpage. - Governing policy or contract with notice, deadline, and obligation clauses.
- Correspondence, incident, invoice, payment, and evidence records.
Result
Produce a chronology sheet with one row per event and a brief covering sequence, deadlines, amounts, disputed facts, and evidence gaps.
The sheet is the working record: preserve document identifiers, page references, original amounts, and the status of each event so a reviewer can reconstruct the claim history without relying on narrative shorthand.
Quality criteria
- Every event has an event date or an explicit unknown value.
- Every factual row cites document ID and page, section, or record ID.
- Document date, receipt date, and event date remain separate.
- Contradictory dates and duplicate correspondence are visible.
- Allegations are labelled as allegations, not facts.
Instructions
Order events by event date, then use document date and received date only as tie-breakers. Do not infer an incident date from a filing date. Deduplicate identical correspondence while retaining every source reference. Calculate elapsed days only when both endpoints are known. Preserve original currency and claim amount; do not infer liability from chronology. Put each deadline beside the clause or notice that creates it.
Adapt before use
- Add the applicable policy, contract, or claims-handling procedure.
- Define the date format and deadline-counting convention.
- Map claim, document, and payment identifiers.
- Name the audience for the chronology brief.
Related skills
- Compliance training refresh
Updates compliance training modules against revised policies, identifies changed learner obligations, and creates source-linked lesson text, scenario questions, and an answer key. Use for annual compliance refreshes, policy changes, code-of-conduct training, and controlled learning-content updates.
- Contract obligation register
Extracts dated and recurring duties from signed contracts into an obligation register with parties, triggers, notice windows, service levels, payment terms, evidence, and owners. Use for contract lifecycle management, renewal tracking, vendor obligations, or inherited agreement cleanup.
- Contract playbook review
Reviews a commercial contract against a company playbook, records missing or non-standard clauses with exact citations, and proposes fallback positions. Use for procurement, sales, SaaS, services, and contract redline preparation.
- Contract renewal watchlist
Builds a contract renewal watchlist by calculating expiry and notice dates, checking auto-renewal clauses, reconciling spend and usage, and identifying negotiation priorities. Use for vendor renewals, customer agreements, termination windows, contract calendars, and renewal planning.