IME study materials
IME study resources

IME: Investment Management Fundamentals and the Investment Policy Statement

IME · Work through your exam, one topic at a time.

All guide sections

Investment Management Fundamentals and the Investment Policy Statement

Core concepts

Every portfolio decision should trace back to a governing document. The Investment Policy Statement (IPS) records objectives (return requirement and risk tolerance), constraints (liquidity, time horizon, tax, legal/regulatory, unique circumstances - often remembered as RRTTLLU), and the governance rules for monitoring and rebalancing. Candidates must distinguish willingness to take risk (a psychological attitude) from ability to take risk (financial capacity). When they conflict, ability usually governs, and the conflict itself must be documented.

Return objectives should be stated as a required return tied to the investor's goal, not a wish list. Risk objectives belong in one of two forms: absolute (a maximum loss or volatility figure) or relative (tracking error against a benchmark).

Traps

  • Confusing the IPS with a marketing or performance document; the IPS is the mandate and the discipline device against behavioral error.
  • Treating a pension's liabilities as a constraint when they are the primary driver of the return objective.
  • Ignoring that constraints can dominate: a high-return objective with an immediate liquidity need is internally inconsistent.
  • Forgetting that the IPS must be reviewed when circumstances change, not only on a calendar.

Worked example

A client needs 6% nominal to fund retirement, holds a 30-year horizon, and has 12 months of expenses in reserve. The reserve satisfies liquidity; the long horizon supports equity-heavy allocation; the return objective is 6% plus inflation if stated in real terms. If the client's stated willingness is low but ability is high, document the gap and consider a goals-based framing rather than abandoning the 6% target.

Rule of thumb: state objectives in measurable terms, then test each constraint against them - any contradiction must be resolved before implementation.