Form ADV Schedule D private fund data

What Schedule D is—and what it is not

Schedule D is the part of Form ADV where an investment adviser reports additional information about private funds it advises or identifies in its regulatory filing. It can contain the fund name, organizational details, investment and ownership context, current gross asset value, investor counts, minimum investment amounts, and service providers. The exact questions and available values depend on the form version and the adviser’s answers.

This is disclosure data, not a continuously marked portfolio. A reported gross asset value is tied to the adviser’s reporting context and period. It should not be presented as a live net asset value, a performance result, or proof that all assets of a complex sit in one named fund. AUMSearch keeps that distinction visible in the record and links the value back to its filing.

Why private-fund researchers use it

A public adviser profile can tell you that a firm exists; Schedule D helps explain the private-market relationships behind that profile. A distribution or business-development team can identify advisers associated with a strategy or fund type. A diligence team can map the fund’s disclosed administrator, auditor, custodian, or prime broker before requesting additional materials. A data team can compare disclosed scale and investor context across dated filings while preserving the source-specific definitions.

The dataset is especially useful when the research question starts with an adviser but ends with a vehicle, provider, or relationship graph. It can surface a fund name for a follow-up search, show that a relationship changed between amendments, or provide a precise citation for a value that would otherwise be copied from a secondary profile.

• Map an adviser’s disclosed private-fund roster and identify master/feeder relationships.
• Compare reported asset bands, minimum investments, or investor counts by filing period.
• Find operational providers shared across funds, advisers, or strategies.
• Create a review queue when an amended filing changes a relationship or key value.

How to use the records in a research workflow

Start with a stable adviser identifier such as the CRD or SEC file number, then narrow to the relevant Form ADV filing and reporting period. From there, inspect each private-fund record rather than collapsing the adviser’s entire list into one total. Use the fund name, structure flags, and provider names as the next search keys, and open the official source document before relying on a value in a memo or model.

For comparisons, line up like with like: the same fund or vehicle, the same field definition, and comparable filing periods. When an amendment appears, retain the earlier record and mark the later value as a new as-filed observation. AUMSearch’s normalized columns are designed to make filtering and joins easier, while the native answer and source link remain available for review.

• Search the adviser by name or identifier and open its filing history.
• Filter to Schedule D private-fund rows and confirm the reporting period.
• Compare disclosed fields across periods without overwriting prior observations.
• Follow the accession and source URL to verify the filing before publication.

History, amendments, and reporting dates

Form ADV is a filing lifecycle, not a single annual snapshot. An adviser may amend its filing when information changes, and an amended filing can restate or add Schedule D information. The filing date and any stated reporting period answer different questions: one says when the submission reached the public system; the other describes the period or point-in-time context of a reported value. Both dates should travel with the row.

AUMSearch treats the history as a sequence of source-dated observations. That supports questions such as when a fund first appeared in the disclosed roster, when a provider name changed, or whether a reported value was later amended. It does not silently fill gaps between filings or imply that a value remained unchanged when the adviser did not report it.

Relationships to the rest of the catalog

Schedule D becomes more useful when it is joined to the adviser identity, not treated as a standalone table. The adviser CRD, SEC file number, and CIK connect to the broader Form ADV record. A named fund can be compared with Form D offering records when the names and identifiers support that link, while disclosed provider names can lead to securities, fund, or filing research. An adviser’s representatives and public documents add people and narrative context around the same firm.

Joins should remain evidence-based. Similar names are a discovery hint, not proof of identity. AUMSearch can expose the candidate relationship and its source, then let a researcher confirm the legal entity, filing, and date before treating the connection as established.

Limitations to keep in every analysis

Private-fund reporting is self-reported and shaped by the form instructions. A missing field can mean that the question did not apply, the adviser did not provide a public value, the value was not available in the normalized record, or the source version used a different representation. Missing should remain missing; it should not be estimated from marketing materials or another fund in the complex.

Names, structure labels, provider relationships, and asset figures can change. A Schedule D record also does not establish performance, liquidity, investor suitability, or the current status of a private fund. Use the original filing and the adviser’s other public disclosures for context, and label any analysis with the source date and the definitions used.

How AUMSearch makes Schedule D usable

AUMSearch exposes Schedule D as a connected, source-linked dataset. Each row carries a normalized adviser and fund identity, the reported fields that were available, the filing and reporting dates, and a direct route back to the official document. Researchers can begin in the web platform, use the same field names in an API request, connect the records to an MCP workflow, or schedule a recurring data feed for change monitoring.

The goal is a defensible path from a question to the exact public record that supports the answer. The normalized layer makes the relationship searchable; the as-filed values, source metadata, and limitations keep the result honest.