Investment adviser representative records and history

What an IAR record represents

An investment adviser representative record describes a person’s public relationship to an investment adviser or other regulated firm, together with registration information maintained by the relevant public system. Depending on the jurisdiction and source, the record may include the individual’s public name, firm association, registration categories, qualification or exam information, and disclosed events. The meaningful unit is the person, firm, jurisdiction, and date together.

The dataset is not intended to infer a person’s complete employment history from a single page. A registration can be jurisdiction-specific, a firm association can change, and a public disclosure can require careful review of the underlying document. AUMSearch keeps those dimensions separate so a researcher can see what was reported and by whom.

Why teams use the people layer

Firm-level data is necessary for market mapping, but it can hide the people and jurisdiction relationships that drive distribution and diligence work. IAR records let a team find representatives connected to a firm, see where a registration is reported, and build a dated movement or qualification history from public records. That is useful for business-development research, recruiting intelligence, supervisory review, and source-backed client diligence.

The records also provide a bridge between an adviser’s formal filings and its public-facing documents. A person-level search can lead to the associated firm’s Form ADV, brochure, Form CRS, disciplinary disclosure, or other official record, allowing the analyst to inspect the whole context instead of relying on a name match alone.

• Build a firm-to-person map for a defined market, state, or registration category.
• Monitor disclosed association changes and identify records that merit review.
• Compare qualification or exam information using the source’s own labels.
• Route a person-level discovery result back to the firm’s official filings and documents.

How to use IAR records responsibly

Begin with the public individual identifier when one is available; otherwise search the name together with the firm and jurisdiction. Confirm that the candidate firm is the intended legal entity before interpreting a relationship. Then review the registration status and dates, examine any disclosed event or document, and follow the firm identifier into structured Form ADV and adviser-document records.

For time-series work, keep each dated observation rather than replacing it with a single ‘current’ row. Separate a registration event from a firm association event, and separate both from a disclosure event. When names collide, the firm, jurisdiction, identifier, and source URL are the evidence needed to resolve the match.

• Search by individual name plus firm or jurisdiction, then confirm the identifier.
• Filter registrations by category and status before comparing people.
• Open the source record for any event, disclosure, or qualification that matters.
• Join to the firm’s Form ADV and Part 2/Form CRS pages for complete context.

History, status, and source timing

Registration data is maintained through regulatory filing and registration processes, so a public page can reflect a date of registration, withdrawal, amendment, or source refresh rather than the moment a person changed jobs. Different jurisdictions can publish different fields and update them on different schedules. A blank date is not evidence that no event occurred; it is a signal to inspect the source and the available record history.

AUMSearch stores source dates and observation dates separately where the underlying record supports both. That enables a defensible answer to ‘when was this reported?’ and a more cautious answer to ‘when did this relationship change?’ The latter should only be stated when the source dates and filing evidence establish it.

Relationships to adviser, filing, and document data

The most useful IAR workflow is a connected one. Individual CRDs and firm CRDs can connect a person to the adviser’s structured Form ADV profile. The firm relationship can then lead to Schedule D private-fund context, Form ADV Part 2 and Form CRS text, and a filing history. Where a disclosure references an official proceeding or document, the source link becomes the handoff for deeper review.

These joins are designed for discovery and verification, not for a blanket conclusion about a person. A shared name is not a shared identity, and a firm association does not establish a person’s role in every product or client relationship. The normalized graph should expose the evidence and the uncertainty together.

Limitations and privacy-aware interpretation

Public IAR records are not a complete personnel database. Availability, field definitions, and update timing can differ by regulator and jurisdiction. A person may have more than one registration or association, and a status label may require the regulator’s own definition. Use the record for public regulatory research, not for sensitive profiling or assumptions about an individual’s private employment, compensation, clients, or performance.

Disclosures also need their original context. An event category alone does not tell a complete story, and absence of a public event is not a certification of conduct. AUMSearch preserves the source record and links to the official page so a user can review the language before taking action.

How AUMSearch makes IAR history useful

AUMSearch makes IAR records searchable by person, firm, jurisdiction, registration, and source date. The same normalized identifiers can be used in the web platform, API, MCP workflows, and recurring feeds. A firm-level record can carry the person links that led to it; a person-level record can carry the filing and document links needed for verification.

This turns a scattered public lookup into a repeatable research path: find the person, confirm the firm and jurisdiction, inspect the dated status or disclosure, and follow the official source. The result remains source-linked and explicit about what the public record can—and cannot—support.