What You Get
What You Get
Fund Analyst Intelligence is designed to produce standard, repeatable artefacts.
The artefacts are built for allocator workflows and governance.
They prioritise evidence, comparability, and operational clarity.
This page lists the main outputs.
It also explains how they are used in real production cycles.
Core artefacts
1. Living fund profile
A canonical fund record that remains current across cycles.
It consolidates validated facts, operational terms, and monitoring status.
Includes
- identifiers and reference fields
- strategy and mandate summary
- key people and organisational context
- fees, liquidity terms, and operational constraints
- last validation date and cycle status
- links to sources and prior snapshots
Used for
- internal reference and client answers
- fast onboarding of new team members
- avoiding “latest file” ambiguity
2. Monthly validation memo
A standard monthly deliverable for each fund.
It records what was checked, what changed, and what requires action.
Includes
- cycle scope and input sources
- validation summary and quality signals
- material changes since last cycle
- exception list with classifications
- open questions and follow-ups
- reviewer decision and approval stamp
Used for
- monthly internal monitoring
- client-ready updates in private banking
- evidence-backed committee discussions
3. Exceptions queue
A prioritised list of issues that require attention.
It is ranked by materiality and operational impact.
Examples
- inconsistent liquidity statements across sources
- fee changes or new share class terms
- team changes or key person departures
- updated risk limits or exposure shifts
- missing or outdated evidence for key fields
Used for
- focusing analyst time on signal
- coordinating follow-ups with managers
- reducing full-document rereads
4. Change log and snapshot history
A structured “what changed” record across time.
It enables trend analysis and reproducibility.
Includes
- delta comparisons between snapshots
- timestamps and cycle identifiers
- links to evidence for each change
- reviewer actions and notes
Used for
- quarterly IC packs and annual reviews
- audit and internal control evidence
- explaining decisions after the fact
5. Evidence pack
A structured bundle of sources and citations.
It connects extracted claims to artefacts and versions.
Includes
- source inventory (documents, links, versions, dates)
- claim-to-evidence mapping
- excerpts or page references where applicable
- provenance metadata and retention signals
Used for
- defensible decision-making
- fast response to client or internal questions
- reducing repetitive evidence searches
Quarterly and portfolio-level outputs
6. Quarterly IC pack section
A quarterly view that is consistent across funds.
It is assembled from validated monthly cycles.
Includes
- stable narrative structure
- changes and themes across the quarter
- unresolved exceptions and follow-up status
- trend indicators and recurring issues
Used for
- investment committee documentation
- risk and governance reporting
- portfolio monitoring at scale
7. Portfolio dashboard views
Cross-fund monitoring for allocator teams.
It supports prioritisation and oversight.
Includes
- exception counts by category and severity
- funds with recent material changes
- recurring issues by manager or strategy
- cycle completion and review status
Used for
- weekly operational steering
- escalation management
- capacity planning and coverage expansion
Output characteristics
Evidence-first
Key statements link to sources.
Outputs are designed to survive scrutiny.
Comparable across funds
Templates enforce consistent structure.
This enables true portfolio-level oversight.
Reviewable and auditable
Approval states are explicit.
Decision trails are preserved.
Designed for production
Artefacts are generated on schedule.
Failures are visible and actionable.
What you can expect in a pilot
In a pilot, you typically receive:
- initial baseline profiles for a selected fund set
- one full monthly cycle with memos and evidence packs
- an exceptions queue tuned to your materiality policy
- a short portfolio summary for steering
The pilot objective is to prove two things.
The cycle is reliable.
The outputs are useful.