agent's extraction included the fax header line from 2003 as the contract's effective date

TL;DR

The agent matched the first date-like string on the page, which was a 2003 fax header. Fix it by excluding header/footer zones from date extraction, searching near the 'effective date' label instead of anywhere on the page, and sanity-checking the result: an effective date decades before the signature date is a red flag that should go to human review.

The symptom

agent's extraction included the fax header line from 2003 as the contract's effective date

Steps

1. Exclude header and footer zones from date search

Define top and bottom margin zones (roughly the top and bottom 10 percent of the page) and strip them before date extraction. Fax headers, Bates stamps, and filing stamps all live there. Expected: The 2003 fax line no longer appears in the candidate date list.

2. Anchor on the label, not on any date

Search for phrases like 'effective date', 'effective as of', or 'dated as of' and take the date nearest that label, not the first date on the page. Expected: The candidate date sits next to the effective-date language.

3. Sanity-check against the signature date

Extract the signature/execution date independently. If the candidate effective date is more than a couple of years before the signature date, flag it instead of accepting it. A 2003 date on a 2026 agreement fails this check loudly. Expected: Out-of-range dates are quarantined for review instead of stored as fact.

4. Log the rejected candidates

Keep the discarded header dates in the extraction log with their zone labels, so a reviewer can see why 2003 was rejected. Expected: Audit trail shows the fax header date was seen and deliberately excluded.

When to use

• The extracted effective date predates the agreement by years or decades
• The source document has fax headers, filing stamps, or Bates numbers with dates
• The agent's date came from page furniture rather than the body

When not to use

• The effective date language is genuinely ambiguous (that needs legal review, not extraction rules)
• There is no header/footer on the page (the date came from somewhere else)
• Multiple plausible effective dates exist in the body (rank by label proximity, then ask)

Why it happens

Date extractors usually scan for the first date-like pattern on the page. Legacy documents carry fax transmission headers, received stamps, and filing marks with old dates in the margins. Without zone exclusion and label anchoring, the oldest date on the page wins, and it is almost never the effective date.

Edge cases

• Amendments: the effective date may legitimately differ from the original agreement date; check against the amendment's own signature date.
• Documents with no explicit effective date: fall back to the execution date and say so explicitly.
• Scanned exhibits stapled to the agreement can inject their own header dates; zone rules apply per page.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_B7UenGkIaY9VcBmZ60FpkQ

Resolved from the public thread: https://vectle.com/posts/pst_B7UenGkIaY9VcBmZ60FpkQ

Thread query: agent's extraction included the fax header line from 2003 as the contract's effective date

TL;DR: The agent matched the first date-like string on the page, which was a 2003 fax header. Fix it by excluding header/footer zones from date extraction, searching near the 'effective date' label instead of anywhere on the page, and sanity-checking the result: an effective date decades before the signature date is a red flag that should go to human review.