Investment Policy Statement
The formal documentation of investment objectives and constraints — containing return targets, risk tolerance, time horizon, liquidity needs, tax considerations, and the asset class restrictions that govern how each portfolio should be managed.
Why This Object Matters for AI
AI cannot construct compliant portfolios or validate trades against guidelines without machine-readable IPS data; without it, compliance checking requires manual comparison of proposed trades against PDF policy documents.
Investment Management & Portfolio Operations Capacity Profile
Typical CMC levels for investment management & portfolio operations in Financial Services organizations.
CMC Dimension Scenarios
What each CMC level looks like specifically for Investment Policy Statement. Baseline level is highlighted.
Investment policy statements exist as verbal agreements between the portfolio manager and the client. The PM remembers that the Henderson family 'doesn't want tobacco stocks' and 'prefers about 60/40 equity/fixed income.' When a new PM takes over the account, these constraints transfer through a hallway conversation. There is no written IPS document for most accounts.
None — AI cannot perform portfolio compliance checking, constraint-aware rebalancing, or suitability analysis because no machine-readable Investment Policy Statement exists to validate against.
Create any written record of investment constraints — even a scanned letter or typed document listing return objectives, risk tolerance, and restrictions per client.
Investment policy statements exist as Word documents or scanned PDFs in client folders. Each IPS follows a different format depending on which PM drafted it and when. The Henderson IPS is five pages of narrative prose describing risk tolerance as 'moderate-to-aggressive' with no quantitative definition. Compliance reviews IPS documents manually by reading the narrative and comparing it to portfolio holdings.
AI could potentially read OCR'd text from IPS documents, but cannot reliably extract specific constraints, tolerance bands, or restriction rules from free-form narrative prose.
Standardize the Investment Policy Statement format with consistent fields — return target, risk tolerance metric, time horizon, liquidity requirement, tax status, ESG restrictions, concentration limits — across all client accounts.
Each Investment Policy Statement is documented using a standardized template with consistent sections: return objective (percentage target), risk tolerance (standard deviation band), time horizon (years), liquidity needs (percentage of portfolio), tax considerations (qualified/taxable), ESG exclusions (sector list), and concentration limits (per-security and per-sector caps). PMs complete the IPS template in SharePoint, but constraint values remain embedded in the document rather than as discrete fields.
AI can search and retrieve Investment Policy Statements by client or PM, but cannot programmatically extract individual constraint values or perform automated compliance checking against portfolio holdings.
Migrate from document-based IPS records to a constraint management system where each return target, risk limit, restriction rule, and concentration cap is stored as a discrete machine-readable field.
Investment policy statements are stored in a compliance system with discrete fields for each constraint: return target (8% annualized), risk tolerance (max 12% annualized vol), time horizon (7 years), liquidity reserve (5% cash minimum), ESG exclusions (GICS codes), concentration limits (5% per-security, 25% per-sector). The system enforces required fields and validates constraint consistency before the IPS can be approved.
AI can query IPS constraints by client, validate portfolio positions against machine-readable limits, automatically flag concentration breaches, and run pre-trade compliance checks against ESG exclusion lists.
Add formal entity relationships linking the Investment Policy Statement to portfolio accounts, benchmark definitions, compliance rule engines, and client risk questionnaire responses — creating a queryable constraint graph.
Investment policy statements are schema-driven constraint entities with explicit relationships to portfolio accounts, compliance rule engines, risk models, and client suitability profiles. Each IPS encodes constraints as machine-executable rules — not narrative descriptions. An AI agent can ask 'which IPS constraints would be violated if I added a 3% position in an emerging market high-yield bond to this portfolio?' and get a complete pre-trade compliance assessment.
AI can perform fully automated pre-trade and post-trade compliance validation, generate constraint-aware rebalancing proposals, and produce suitability documentation without human interpretation of IPS language.
Implement dynamic IPS generation — constraint sets that auto-update based on client risk questionnaire changes, regulatory requirement shifts, and portfolio performance relative to stated objectives.
The Investment Policy Statement is a living constraint engine that generates its parameters from client risk profiling, regulatory requirements, market regime analysis, and portfolio performance feedback. When a client's risk questionnaire is updated, constraints adjust. When a regulatory change affects concentration rules, IPS limits recalibrate. The IPS is a real-time expression of the intersection of client preferences, fiduciary obligations, and market conditions.
Fully autonomous IPS-driven portfolio management is possible. AI can construct, validate, and execute portfolios within dynamically generated Investment Policy Statement constraints without human constraint interpretation.
Ceiling of the CMC framework for this dimension.
Capabilities That Depend on Investment Policy Statement
Other Objects in Investment Management & Portfolio Operations
Related business objects in the same function area.
Investment Portfolio
EntityThe managed container of investment positions for each client or fund — containing holdings, asset allocation, benchmark assignment, investment policy constraints, performance history, and the rebalancing thresholds that trigger portfolio adjustments.
Security Master
EntityThe reference database of all investable securities — containing identifiers (CUSIP, ISIN, SEDOL), instrument type, issuer, pricing data, corporate action history, and the classification hierarchies that enable portfolio analytics and compliance checking.
Trade Order
EntityThe instruction record for each investment trade — containing security, side (buy/sell), quantity, order type, price limits, execution instructions, compliance checks passed, and the lifecycle status from initiation through fill and allocation.
Research Signal
EntityThe quantitative or qualitative investment signal derived from research — containing signal type (fundamental, technical, sentiment), signal strength, affected securities, expiration, and the backtest performance that establishes signal validity.
Performance Attribution
EntityThe decomposition of portfolio returns into contributing factors — containing allocation effect, selection effect, currency effect, and the factor exposures that explain why performance differed from benchmark.
Tax Lot Record
EntityThe cost basis tracking record for each security purchase — containing acquisition date, purchase price, adjusted cost basis, holding period, and the unrealized gain/loss that drives tax-loss harvesting and lot selection decisions.
Manager Due Diligence Record
EntityThe evaluation record for each external investment manager considered or hired — containing investment process assessment, operational due diligence findings, performance track record, fee analysis, and the ongoing monitoring results that determine retention.
Rebalancing Rule
RuleThe codified logic that determines when and how portfolios are rebalanced — including drift thresholds, rebalancing frequency, tax-aware constraints, minimum trade sizes, and the priority rules when multiple rebalancing needs compete for limited trading capacity.
Investment Guideline Compliance Check
ProcessThe automated workflow that validates trades and positions against investment policy constraints — including pre-trade compliance checks, post-trade verification, exception handling, and the override approval process for intentional breaches.
What Can Your Organization Deploy?
Enter your context profile or request an assessment to see which capabilities your infrastructure supports.