Skip to content

Handle late-arriving evidence without rewriting a released window

Separate arrival time from window eligibility and version any amended table explicitly.

Guides

Handle late-arriving evidence without rewriting a released window — what should the operator record?

Evidence can arrive after a working table has been released while still describing an event within its declared window. Decide whether the release contract allows amendments, then preserve both receipt timing and source-time eligibility. A late arrival should not silently change a previously signed-off table or be discarded merely because it arrived later.

Practical operations check
Separate arrival time from window eligibility and version any amended table explicitly.
Keep original_receipt_time and eligible_source_time with their actual precision. If the source time is missing, mark window eligibility unresolved rather than assuming that late arrival means the record happened outside the declared reporting period or belongs in a newer one.
State which admitted keys or fields changed and the new revision reference. Retain the original release's historical scope where permitted, without suggesting that the amendment proves the final set now exhausts all source activity within the window or resolves every delayed response.
01 / Guides

Record both time bases

Keep original_receipt_time and eligible_source_time with their actual precision. If the source time is missing, mark window eligibility unresolved rather than assuming that late arrival means the record happened outside the declared reporting period or belongs in a newer one.

02 / Guides

Read the amendment contract

Identify whether the released artifact is fixed membership, amendable or superseded by a later revision. This is a local release decision; it must not invent a Montage guarantee that all evidence for a period has arrived by a certain wall-clock deadline.

03 / Guides

Test eligibility fixtures

Use labeled examples with a source instant inside the window and a receipt after release, plus a date-only ambiguous case. Verify the transformation treats eligibility and lateness as separate states instead of sorting both into one generic out-of-window bucket.

04 / Guides

Prepare an amendment candidate

If authorized by the artifact owner, create a new revision naming the prior release and late receipt. Reconcile qualified keys so repeated late observations do not inflate membership, and preserve current visibility decisions rather than restoring withheld identities during the amendment.

05 / Guides

Publish the actual change

State which admitted keys or fields changed and the new revision reference. Retain the original release's historical scope where permitted, without suggesting that the amendment proves the final set now exhausts all source activity within the window or resolves every delayed response.

Keep the boundaries clear.

  • Separate arrival time from window eligibility and version any amended table explicitly.
  • Operational record: Record both time bases. Context badges do not certify access.

Start with a read-only check: ask your agent to report actual source coverage before collecting records or exporting an audience.

Primary references

Documentation reviewed 2026-11-15. Product capabilities, client availability and plans can change. Third-party marks identify their products, not an affiliation.

Know what social media shows about you.
Start with a question.

Get started
montage