METHODOLOGY / FRESHNESS

Update and freshness policy

How AUMSearch distinguishes source reporting dates, filing dates, retrieval timestamps, processing dates, and content review dates.

EDITORIAL OWNER AUMSEARCH DATA EDITORIAL

LAST REVIEWED

SOURCE STANDARD PRIMARY PUBLIC RECORDS

DIRECT ANSWER

Definition

AUMSearch uses source-specific dates instead of one ambiguous “updated” timestamp. Published data should distinguish the reporting period, filing date, source acceptance time, retrieval time, normalization time, and page review date.

01

Date vocabulary

DatePurpose
Reporting periodWhen the disclosed information applies
Filed dateWhen the filer submitted the record
Accepted timeWhen the source system accepted it
Retrieved timeWhen AUMSearch collected it
Normalized timeWhen AUMSearch processed it
Reviewed dateWhen page explanations and sources were checked

02

Source cadence

Form 13F is a quarterly disclosure with filing lag. Form ADV changes through initial filings, annual updating amendments, and other amendments. Source cadence does not guarantee AUMSearch processing cadence; the public coverage dashboard will publish validated refresh status when the production pipeline is ready.

03

Stale-data behavior

  • Keep the last known source date visible.
  • Warn when an expected refresh is delayed.
  • Do not silently substitute an old value as current.
  • Preserve historical editions of research pages.
  • Update schema last-modified dates only for material changes.

SRC

Primary sources

Definitions and regulatory claims on this page are grounded in the following official public resources.