DDQ automation for asset managers coordinates the intake, evidence retrieval, drafting, subject review, approval and release of investor due diligence answers across firms, legal entities, funds, strategies and share classes. It reduces repetitive work while preserving the exact scope, date, source and authority behind performance, organization, operations, risk, compliance, sustainability, technology and security claims.
Investor DDQs repeat themes but rarely ask the same question in the same scope. An answer valid for the management company may not describe a fund; a firm-wide policy may not establish the control used by one strategy; assets, personnel and performance change by cutoff date. Teams copy a prior response, then circulate spreadsheets through many experts. The answer can sound consistent while mixing entities, dates and definitions or losing the evidence that reviewers need.
Automate coordination and evidence assembly, not fiduciary or compliance judgment. Model facts at the level at which they are true: firm, entity, product, strategy, vehicle and period. Treat quantitative data, policies, incidents and forward commitments as controlled classes with distinct owners. Draft from current approved evidence, expose conflicts and require accountable review. The investor’s workbook is a delivery format, not the source of institutional truth.
Scope
Asset-manager knowledge is multidimensional by design
An asset manager does not have one reusable profile. The management company, affiliated advisers, funds, strategies, vehicles and service-provider arrangements can differ. A DDQ may ask for the firm’s ownership, the strategy team, the vehicle’s administrator and the fund’s current assets in adjacent rows. Store each fact at its true level and make inheritance explicit. A firm policy may apply broadly, while a committee, limit or process belongs only to one product.
Time is another dimension. Performance, assets, personnel, systems, incidents and provider arrangements need an as-of date or valid period. Preserve definition with the value: committed capital is not net asset value, and firm assets are not strategy assets. For derived metrics, retain calculation rule and input sources. The answer should state an appropriate cutoff and remain internally consistent even when the investor workbook repeats the number in several places.
- Model firm, entity, product, strategy and vehicle separately.
- Make inheritance and exceptions explicit.
- Attach date, unit, currency and definition to every number.
- Preserve calculation lineage for derived values.
- Reconcile repeated facts across the full request.
Evidence
Route facts through the function that can actually establish them
Client teams coordinate the response but should not become the authority for every claim. Investment leadership owns strategy and process descriptions; operations establishes workflows and providers; finance controls certain assets and financial values; risk, compliance, legal, sustainability, technology and security own their respective evidence and approvals. Define the exact kinds of answer each role may approve. A fluent historical answer is not a substitute for a current source or authorized decision.
Use change-based review carefully. Stable approved language can pass when its source, scope and validity remain unchanged. A changed source, new investor formulation, absolute wording, incident question, exception or commitment triggers deeper review. Show experts the proposed answer beside evidence and prior approved state, highlighting the difference. This is faster than circulating a blank workbook and safer than asking one central writer to infer the current institutional position.
| Class | Typical authority | Critical context |
|---|---|---|
| Organization | Management and HR | Entity, role and effective date |
| Investment | Investment leadership | Strategy, product and decision process |
| Quantitative | Finance, risk or performance | Definition, period, currency and source |
| Control | Operations, risk or compliance | Policy versus operating evidence |
| Technology | Technology and security | System scope, control boundary and disclosure |
Release
Control the workbook and preserve what the investor actually received
Investor templates are often complex operational artefacts. Protect formulas and required structure, detect merged cells and hidden sheets, observe response limits and preserve requested formats. Reconcile tables with narrative and attachments. Validate that the exported file contains the approved content, not an earlier local copy. When a portal requires manual entry, use a second-person comparison or controlled export and retain evidence of the final state.
Archive the exact response, attachments, source snapshot, approvals and delivery receipt as one release. Later questions and corrections should be classified. A change in investor preference may improve presentation but not institutional knowledge; a factual correction should update the source or governed claim and trigger dependent review. Track which gaps recur across allocators. The strongest content roadmap comes from repeated unanswered evidence needs, not from accumulating every submitted sentence.
- Validate formulas, hidden content and formatting constraints.
- Reconcile narrative, tables and attachments.
- Compare the released artefact with the approved set.
- Archive response, evidence, approvals and receipt together.
- Classify feedback before updating reusable knowledge.
What good looks like
Useful outcomes from DDQ automation for asset managers
- Requests are classified by investor, consultant, product, strategy, entity, period, language and deadline.
- Repetitive questions route to current facts without carrying assumptions from another fund or cutoff date.
- Quantitative values preserve definition, currency, period, source system and approval.
- Policies, controls and operating descriptions link to the responsible function and current evidence.
- Conflicts between a prior response, source system and subject expert surface before release.
- Experts review only material changes, gaps and matters within their authority.
- Approved responses retain provenance when delivered through spreadsheets, portals or documents.
- Post-release corrections improve the controlled knowledge base and future evaluation.
Operating model
How to run the work
- 01
Classify the request and scope
Capture investor, intermediary, entity, fund, strategy, vehicle, share class, reporting date, language, format and deadline. Split compound questions and distinguish new information requests from confirmations of previously supplied material.
- 02
Resolve facts and evidence
Retrieve from controlled sources using hard scope and date filters. Preserve definitions and units for quantitative fields. Link policy versions, governance records and approved descriptions. Represent unknown, conflict and unavailable disclosure explicitly.
- 03
Assemble the investor-specific answer
Compose the response at the requested detail and format while keeping factual claims linked to evidence. Reconcile cross-question consistency, tables and attachments. Keep the investor’s wording and any deal-specific interpretation visible.
- 04
Route material review and approval
Assign investment, operations, risk, compliance, legal, finance, sustainability, technology and security sections by authority. Highlight changed facts and commitments. Apply dual or executive approval where the institution requires it.
- 05
Release, archive and learn
Verify entity, period, totals, attachments, formulas and export integrity. Preserve the exact released set and approval record. Classify later corrections before updating reusable knowledge and add representative failures to the quality set.
Evaluation
Questions that change the decision
- At which firm, entity, product, strategy, vehicle and date level is each claim true?
- Which source is authoritative for organization, assets, performance, risk, operations and controls?
- Which numbers require a fixed definition, calculation method, currency and cutoff?
- Which answers can be reused unchanged and which always need current subject review?
- What information is restricted by investor, agreement, team or internal sensitivity?
- How should policy, implementation evidence and a statement of no known incident remain distinct?
- Which wording creates a new commitment rather than describing current practice?
- What final checks prove consistency across workbook, narrative and attachments?
Failure modes
Where teams lose control
A firm-level fact can be applied to a fund or strategy where it is not accurate.
Assets, headcount, performance and exposure can be mixed across cutoff dates.
Similar terms can use different definitions across investors and source systems.
A policy document can be cited as proof that an operating control occurred in every case.
A prior answer can contain a negotiated disclosure or caveat that is inappropriate for another investor.
Spreadsheet formulas, hidden sheets and character limits can alter an approved response during export.
Restricted investor or portfolio information can enter a broadly searchable repository.
Subject experts can approve wording outside their formal decision authority.
Generated prose can turn a qualified fact into an absolute promise.
Learning from corrections without classification can encode one investor’s preference as general truth.
Measurement
Measure the finished job
Measure the completed workflow, including review effort and exceptions. Output volume on its own is not evidence of a better process.
- questions classified to entity, product, strategy and reporting date
- claims with current authoritative evidence and named owner
- quantitative responses passing definition and period reconciliation
- material conflicts discovered before investor release
- questions requiring substantive expert drafting versus targeted review
- approval turnaround by function and risk class
- unsupported, out-of-scope or over-broad claims found in quality review
- cross-answer inconsistencies and workbook export defects
- on-time releases with complete approval and evidence records
- investor corrections and reopenings traced to source and process
Questions
Common questions
What can be automated in an asset-manager DDQ?
Intake, question classification, evidence retrieval, answer assembly, ownership routing, change highlighting, consistency checks and export can be automated. Current facts, ambiguous disclosures, policy interpretation and commitments still need review by the function with authority.
How do you prevent reuse across the wrong fund or strategy?
Store claims with hard scope metadata for firm, entity, product, strategy, vehicle and period. Apply those filters before semantic retrieval, show the scope to writers and block release when a requested context has no applicable evidence.
Can prior DDQs become an answer library?
They are useful for question patterns and approved wording, but not automatically authoritative. Extract factual claims, connect them to current sources and owners, preserve negotiated caveats and prevent restricted investor content from broad reuse.
How should quantitative DDQ answers be controlled?
Store definition, unit, currency, period, source, calculation method and approver with each value. Reconcile repeated numbers across the request and verify the final export or portal entry against the approved value.
About the author
Malcolm Ferguson
Malcolm writes from the buyer side about procurement, sourcing, due diligence and the evidence suppliers need to pass a serious evaluation.
Ziva
Proposal software for source-grounded RFP, RFI, DDQ and questionnaire response work.
Bid, proposal, presales, security and compliance teams. Start with the workflow, constraints and evidence you already have.
See Ziva→