Surface actionable deadlines from archived bills and letters

Why use this

1. An archived letter may contain an issue date, a response deadline and a payment date, all serving different purposes. A reminder generated from the wrong date can create false urgency or miss the action the owner actually needs to consider.

2. A deadline-attention queue could tie each proposed action to the original passage and explain unresolved ambiguity. The owner could prioritize documents for review while keeping notification separate from paying, replying or accepting the letter's claims.

Why an agent / simpler alternative

Useful judgment

Distinguish actionable date language from incidental dates and recognize when a deadline depends on an unknown event.

Simpler alternative

Use manual calendar entries for a small set of clearly dated bills.

Unsuitable when

The task requires deciding legal obligations, confirming a debt or calculating an unsupported statutory deadline.

Proposed inputs

1. Name

   Correspondence excerpt sample

   Owner

   Document owner

   Minimum scope

   Selected text with document IDs, dates and action language

   Quality check

   Preserve unclear scans and original date context.

2. Name

   Attention preferences

   Owner

   Document owner

   Minimum scope

   Relevant categories, reminder lead times and approved destination

   Quality check

   Separate urgent review from automatic execution.

Access and setup — proposed or unknown

Proposed minimum

1. Read-only fictional excerpts and a local attention-ledger proposal.

Compatibility unknowns

1. Unknown: current runtime, archive extraction, scheduler availability and notification behavior.

External actions requiring approval

1. Recurring alert setup, payment, replies and any third-party notice or document sharing.

Expected deliverable and review checks

Proposed artifact

Attention ledger with document pointer, proposed action, date basis and verification status.

Critical checks

1. Each deadline cites the exact passage and identifies any triggering condition.

2. Already resolved items are separated from still-open review candidates.

Missing output evidence

No new workflow run or output inspection is performed for this editorial layer. The linked implementation evidence retains the original source-specific outcome and artifact limits.

Failure signals and proposed responses

1. Signal

   A letter says respond after receipt but the receipt date is unknown.

   Why it matters

   The calculated deadline would rest on an invented fact.

   Proposed response

   Leave the date unresolved and ask the owner to verify the triggering event.

2. Signal

   An old paid bill creates a new payment reminder.

   Why it matters

   The queue may prompt duplicate or unnecessary action.

   Proposed response

   Reconcile the document with supplied resolution evidence before retaining the item.

Effort and cost — unknown

Setup work

1. Define action categories and date-verification fields.

Ongoing review

1. Resolve ambiguous deadlines and close completed items.

Unknowns

1. Unknown: extraction accuracy, notification costs and owner review effort.

First check — proposed, unexecuted

Status

proposed_unexecuted

Synthetic fixture

Three fictional letters include an issue date, a receipt-dependent deadline and a bill already marked paid.

Acceptance checks

1. Keep incidental and actionable dates separate.

2. Flag the unknown trigger and suppress a resolved payment candidate.

Stop conditions

1. Real correspondence, legal interpretation, alerts or payments are required.

Limits

1. The proposed checks and safeguards are editorial recommendations, not evidence of successful execution or permission to act. The linked implementation retains its own observed outcome and approval limits.