Lesson 5.3: Discretionary vs Non-Discretionary Mandates

Where This Lesson Fits

Lesson 5.2 introduced the separately managed account structure and established that most SMA platforms operate on a model where the manager has the authority to execute trades without asking the client each time. That operating model depends on a specific legal arrangement — the discretionary mandate — which this lesson examines in depth. Understanding whether a mandate is discretionary or non-discretionary is one of the most consequential distinctions in advisory account operations, affecting how trades are approved, how quickly portfolios can respond to market conditions, and what compliance controls the firm must maintain.

This lesson connects forward to Lesson 5.4 on wrap programs, where discretionary management is typically a core feature of the service, and to Lesson 5.5 on portfolio construction and mandate design, where the decision to offer discretionary or non-discretionary authority shapes how mandates are structured and documented. It also connects to Lesson 5.6 on advisor oversight, where the degree of discretionary authority affects how portfolios are monitored and reviewed. Mandate type is not an isolated feature — it runs through every aspect of managed account design.

At the system level, the distinction between discretionary and non-discretionary mandates reflects a fundamental question about where decision-making authority sits in the advisor-client relationship. This is not merely a procedural difference — it has legal, regulatory, and fiduciary implications that shape how advisors operate, how operations teams process transactions, and how firms document their compliance with client mandates and regulatory requirements.

Lesson Objective

By the end of this lesson, students should be able to define discretionary and non-discretionary mandates and explain how each distributes investment decision-making authority; describe the legal basis for discretionary authority and the documentation required to establish it; compare the operational workflows associated with each mandate type; and identify the compliance requirements and risks that arise from discretionary trading authority in an advisory account context.

Lesson Overview

Every advisory account operates under a mandate that defines how investment decisions are made. The most fundamental dimension of any mandate is the question of authority: who has the right to decide when a security is bought, sold, or held — and does that decision require client approval before it is executed? The answer to this question determines whether the mandate is discretionary or non-discretionary, and it shapes nearly every operational and compliance process built around the account.

In a discretionary mandate, the advisor or investment manager is granted the legal authority to make and execute investment decisions within the account without obtaining prior client approval for each transaction. The client delegates this authority formally — typically through a limited power of attorney included in or attached to the advisory agreement — and the advisor is then free to act within the bounds of the documented investment mandate. This means the advisor can respond to market conditions, implement model changes, or rebalance the portfolio without first calling the client and waiting for authorization. Speed, consistency, and operational efficiency are the primary practical benefits of this arrangement. Most professionally managed portfolio services — including SMA platforms, wrap programs, and institutional separate accounts — operate under discretionary authority because the managed account model fundamentally depends on the manager's ability to act quickly and uniformly across client portfolios.

In a non-discretionary mandate, the advisor may analyze portfolios, make recommendations, and propose trades, but may not execute any transaction without the client's explicit approval. Each time the advisor wishes to buy or sell a security, the recommendation must be communicated to the client, the client must review and authorize it, and only then can the trade be placed. This arrangement preserves maximum client control and is appropriate in situations where the client wishes to remain closely involved in investment decisions, has specific legal or compliance reasons to approve each transaction, or simply prefers to maintain final authority over the portfolio. However, the requirement for client approval before each trade introduces delays, creates execution risk in fast-moving markets, and significantly increases the administrative burden on both the advisor and the client.

In practice, many advisory relationships exist on a spectrum between fully discretionary and fully non-discretionary. A client might grant discretion within defined parameters — for example, allowing the advisor to rebalance freely within the target allocation but requiring approval before changing the strategic allocation itself. Or a client might be discretionary for routine rebalancing but non-discretionary for the selection of new asset classes or managers. Operations teams must understand these nuances because they affect which transactions can be processed automatically and which require a documented client authorization before execution. Misidentifying a mandate type — or processing a discretionary trade in a non-discretionary account — is a compliance violation that can expose the firm to regulatory action and client disputes.

Why This Matters in Wealth & Asset Operations

The distinction between discretionary and non-discretionary mandates has direct and immediate consequences for how operations teams process transactions. In a discretionary account, a trade instruction from the advisor or manager can be routed directly to the custodian for execution — no client authorization step is required, and the workflow is streamlined. In a non-discretionary account, a pre-trade authorization step must be inserted into the workflow: the recommendation must be documented, the client's approval must be recorded, and the trade may only be executed after that approval is confirmed. Operations teams that run a single workflow for all account types — or that do not verify mandate type before processing — risk executing unauthorized trades, which creates compliance violations and potential client harm.

From a compliance perspective, discretionary authority carries heightened oversight requirements. Because the advisor can act without asking the client, regulators expect firms to have controls in place to ensure that discretion is exercised within the bounds of the documented mandate. This includes monitoring for style drift, reviewing that trades are consistent with the IPS, and maintaining audit trails showing that discretionary decisions were made in the client's best interest. These monitoring and recordkeeping functions are operational responsibilities, not purely advisory ones, and teams supporting discretionary accounts must be equipped to fulfill them.

Account documentation is also affected by mandate type in ways that operations must manage. Discretionary accounts require a valid limited power of attorney on file — if this document is missing, expired, or not properly executed, any trade the advisor places is technically unauthorized, regardless of whether the client would have approved it. Operations teams must track the status of LPOA documents across all discretionary accounts, ensure they are renewed or re-executed when required, and flag any accounts where the authority to trade has lapsed or is in question.

Core Concept

Discretionary Mandate — An advisory arrangement in which the client formally grants the advisor or investment manager the legal authority to make and execute investment decisions within the account without obtaining prior approval for each transaction, typically formalized through a limited power of attorney.

Non-Discretionary Mandate — An advisory arrangement in which the advisor may make recommendations but may not execute any transaction without the client's explicit prior approval, preserving the client's final decision-making authority over each investment action.

Limited Power of Attorney (LPOA) — A legal document through which the client grants the advisor specific, bounded authority to act on the client's behalf — typically the authority to place trades — within the scope defined by the advisory agreement and investment policy statement.

These three concepts form the legal and operational architecture of investment authority in advisory accounts. The mandate type defines where authority sits; the LPOA is the legal instrument that transfers it; and the advisory agreement and IPS define the boundaries within which that authority may be exercised. Together they determine what the advisor can do, when they can do it, and what documentation must exist before any action is taken.

What Defines Each Mandate Type

Discretionary and non-discretionary mandates differ across a set of structural dimensions that shape every aspect of how the account is managed and administered.

• Decision-Making Authority — In a discretionary mandate, the advisor holds the authority to decide and act. In a non-discretionary mandate, the client holds final authority and must approve each action before it is taken.
• Legal Authorization Document — Discretionary authority requires a valid limited power of attorney granting the advisor trading authority in the account. Non-discretionary accounts do not require this document because the advisor does not act independently.
• Pre-Trade Client Contact — Discretionary accounts require no pre-trade client contact for routine portfolio management. Non-discretionary accounts require the advisor to present each recommendation to the client and obtain documented approval before execution.
• Execution Speed — Discretionary mandates allow the advisor to act immediately in response to market conditions or model updates. Non-discretionary mandates introduce a delay between recommendation and execution that can be significant in volatile markets.
• Audit Trail Requirements — Both mandate types require documentation, but in different forms. Discretionary accounts require records showing that trades were consistent with the mandate; non-discretionary accounts require records of each client authorization before execution.
• Compliance Monitoring Focus — Compliance oversight of discretionary accounts focuses on whether the advisor exercised authority within the mandate parameters. For non-discretionary accounts, compliance focus is on whether client authorizations were properly documented before trades were executed.
• Client Engagement Level — Discretionary mandates are designed for clients who prefer to delegate day-to-day investment decisions and review results periodically. Non-discretionary mandates are suited for clients who want to remain actively involved in individual investment choices.

These structural differences are not simply policy preferences — they are embedded in the legal and regulatory framework governing advisory relationships. Misapplying the wrong workflow to the wrong mandate type is not a minor procedural error; it is a potential violation of the client's rights and the firm's regulatory obligations.

Layers of Discretionary Authority

Discretionary authority is not binary — it exists on a spectrum and can be scoped in multiple dimensions within a single advisory relationship. The following layers describe how discretion is commonly structured and bounded in practice.

• Full Discretion — The advisor has authority to make all investment decisions within the account, including security selection, trade timing, and position sizing, without client approval. This is the standard operating model for most professionally managed SMA and wrap accounts.
• Bounded Discretion — The advisor has discretion within defined parameters — for example, maintaining the portfolio within a documented allocation range or within an approved security universe — but must seek approval for decisions that fall outside those boundaries.
• Rebalancing-Only Discretion — Some clients grant discretion specifically for rebalancing to the target allocation but require approval for any change to the strategic allocation or investment mandate itself. This is common in accounts where the client wants efficient maintenance but wishes to remain involved in strategy-level decisions.
• Manager-Level Discretion — In multi-manager arrangements, discretion may be granted at the manager level for each strategy while the overall allocation across managers is set by the advisor with client input. This creates a layered authority structure within a single account.
• Time-Bounded Discretion — Some advisory agreements include discretion that must be renewed periodically, requiring the client to reaffirm the authority grant at defined intervals. Operations teams must track renewal dates and ensure that discretionary trading does not continue in accounts where authority has lapsed.
• Custodial-Level Constraints — Even within a fully discretionary mandate, the custodian may impose constraints on certain transaction types — for example, requiring additional authorization for margin transactions or options trading. These custodial-level constraints interact with the advisory mandate and must be understood by operations teams.

The practical implication of this layered structure is that operations teams cannot assume that any account is simply "discretionary" or "non-discretionary" in a uniform way. Each account's mandate documentation must be reviewed to understand the specific scope of authority granted, and workflows must be designed to apply the correct approval logic for each type of transaction in each account.

Discretionary vs. Non-Discretionary in Practice

The operational difference between discretionary and non-discretionary mandates becomes most visible during periods of market volatility or when the advisor wishes to make a significant portfolio change. In a discretionary account, the advisor can respond immediately — selling a position that has breached a risk threshold, rebalancing after a market move, or implementing a tactical shift — without the delay of a client consultation cycle. This responsiveness is not just convenient; it is often the primary reason clients choose professionally managed discretionary accounts over non-discretionary advisory relationships. In a fast-moving market, the difference between acting today and waiting for client approval tomorrow can be material.

In a non-discretionary arrangement, the advisor's role is closer to that of a highly informed consultant than a portfolio manager. The advisor analyzes the portfolio, identifies opportunities or risks, makes a recommendation, and then waits. If the client is traveling, unavailable, or simply slow to respond, the recommended action may not be taken in time to capture the opportunity or avoid the risk. This is not necessarily a failure of the advisory relationship — some clients explicitly prefer this level of control — but it does mean that the non-discretionary model is fundamentally dependent on the client's availability and responsiveness in a way that the discretionary model is not.

From a compliance standpoint, both mandate types carry important obligations, but the nature of the risk differs. In discretionary accounts, the primary risk is that the advisor exercises authority in ways that exceed or deviate from the mandate — for example, trading in prohibited securities, taking on excess risk, or making decisions that benefit the firm rather than the client. In non-discretionary accounts, the primary risk is that trades are executed without proper client authorization, or that the documentation of authorization is incomplete or ambiguous. Both risks require active oversight, but the controls needed to address them are different, and operations teams must understand which risks apply to which accounts in their portfolio.

Operational Workflow

The following workflow illustrates how a trade recommendation moves from decision to execution differently depending on whether the mandate is discretionary or non-discretionary.

1. Portfolio Review and Decision. The advisor or manager reviews the portfolio and identifies a trade opportunity or rebalancing need based on the client's mandate parameters and current market conditions.
2. Mandate Type Verification. Before any action is taken, the operations system or the advisor confirms whether the account is discretionary or non-discretionary. This step prevents the application of the wrong workflow and is a critical compliance checkpoint.
3. Discretionary path — Trade Order Generation. For a discretionary account, the advisor generates a trade order directly, typically within the portfolio management system. No client contact is required at this stage, though the advisor must confirm the trade is within mandate parameters.
4. Non-Discretionary path — Recommendation Documentation. For a non-discretionary account, the advisor documents the recommendation in the client file, including the rationale, the proposed security, the size, and the timing. This documentation is the starting point of the authorization process.
5. Non-Discretionary path — Client Communication and Authorization. The advisor contacts the client, presents the recommendation, and obtains verbal or written approval. The approval and the method by which it was obtained are documented in the account record. No trade is placed until this step is complete.
6. Trade Order Entry and Routing. The authorized trade order is entered into the trading system and routed to the custodian or trading desk for execution. Both paths converge at this step, but only after the authorization requirements appropriate to the mandate type have been satisfied.
7. Execution Confirmation. The custodian confirms trade execution back to the platform. The operations team verifies that the execution matches the order — security, quantity, direction, and timing — and records the confirmation.
8. Post-Trade Compliance Review. For discretionary accounts, a post-trade review confirms that the executed trade was consistent with the mandate. For non-discretionary accounts, the review confirms that a valid client authorization exists in the file. Any discrepancy is escalated immediately.
9. Recordkeeping and Audit Trail. All relevant records — the decision rationale, the authorization (for non-discretionary), the order, the execution, and the post-trade review — are retained in the account file in a form that satisfies regulatory recordkeeping requirements.

This workflow makes clear that mandate type is not a background administrative detail — it determines which steps are required, what documents must exist before execution, and what the compliance review must verify afterward. Operations teams must be able to execute both paths correctly and to identify immediately which path applies to any given account and transaction.

Real-World Example

A wealth management firm manages two client accounts with similar asset levels and the same advisor: one is a discretionary SMA and the other is a non-discretionary advisory account. Both portfolios hold a significant position in a commercial real estate investment trust. News breaks on a Tuesday morning that the REIT has disclosed a material accounting restatement. The advisor concludes that the position should be reduced significantly before the market digests the full implications of the announcement.

In the discretionary account, the advisor places the sell order immediately. By 10:15 AM, the position has been reduced at a price that, while lower than the prior close, is significantly better than where the stock will trade by end of day. In the non-discretionary account, the advisor calls the client to recommend the same action. The client is in back-to-back meetings and does not return the call until 2:30 PM. By the time the trade is authorized and executed, the position has declined an additional 14% from the price at which the discretionary account sold. The same advisor, the same recommendation, the same rationale — but materially different outcomes driven entirely by the mandate type.

This example illustrates the execution risk inherent in non-discretionary mandates and explains why most professionally managed account structures operate under discretionary authority. It also illustrates the importance of clear documentation: in the non-discretionary account, the advisor must record that the recommendation was made in the morning and that execution was delayed pending client authorization — not because the documentation improves the outcome, but because it protects both the client and the firm if the timing of the decision is ever questioned. Operations teams that understand mandate types understand why these documentation requirements exist and can ensure they are fulfilled consistently.

Common Mistakes

Mistake 1: Executing Trades in Non-Discretionary Accounts Without Documented Authorization

The most serious mistake in non-discretionary account management is placing a trade before client authorization has been obtained and documented. Even if the advisor believes the client would approve, and even if the trade is clearly in the client's best interest, executing without authorization is an unauthorized transaction — a regulatory violation that can result in enforcement action, client complaints, and reputational damage. Authorization must be obtained and recorded before the order is entered, not reconstructed after the fact.

Mistake 2: Allowing Discretionary Trading Without a Valid LPOA on File

Discretionary authority is only valid when a properly executed limited power of attorney is on file at the custodian. If the LPOA is missing, expired, or incorrectly executed, every trade placed by the advisor in that account is technically unauthorized, regardless of whether the client approved the advisory relationship and would have approved each trade. Operations teams must track LPOA status for all discretionary accounts and flag any accounts where the document is not current before any orders are processed.

Mistake 3: Misclassifying Mandate Type at Account Setup

If an account is set up in the operations system with the wrong mandate type — discretionary when it should be non-discretionary, or vice versa — the consequences can persist for years before being detected. A discretionary workflow applied to a non-discretionary account bypasses required client authorizations on every trade. A non-discretionary workflow applied to a discretionary account creates unnecessary delays and client contact requirements. Both errors are avoidable through careful review of the advisory agreement at account setup and regular mandate documentation audits.

Mistake 4: Treating Bounded Discretion as Full Discretion

Some advisors operate as though discretionary authority is unlimited once it has been granted, without recognizing that many mandates scope discretion to specific activities or parameter ranges. An advisor with discretion to rebalance within the target allocation does not have discretion to change the strategic allocation — that action requires client consultation regardless of the LPOA. Operations teams must understand the specific scope of discretion documented in each account's mandate and flag transactions that may exceed it before execution.

Mistake 5: Failing to Monitor Discretionary Accounts for Style Drift

Granting discretionary authority to an advisor is not the end of oversight — it is the beginning of a different kind of oversight. Because the advisor acts without client approval, the firm must have monitoring in place to ensure that discretionary decisions remain within the mandate parameters over time. Style drift — where the portfolio gradually diverges from its documented investment approach — is a common risk in discretionary accounts and is not always visible until a formal review reveals significant deviation from the IPS guidelines. Operations and compliance teams must conduct regular post-trade reviews to catch drift before it becomes material.

Practical Exercises

Exercise 1: Mandate Workflow Mapping

For a single hypothetical trade recommendation — a sell order for 10% of the portfolio's equity allocation — map the complete step-by-step workflow for both a discretionary account and a non-discretionary account. Identify every step where the workflows differ, who is responsible at each step, and what documentation must exist at the end of the process. Present your comparison as a parallel-path diagram with annotations explaining the compliance purpose of each step.

Exercise 2: LPOA Audit Scenario

You are an operations associate reviewing the account documentation for a book of 40 discretionary advisory accounts. Define the checklist you would use to verify that each account has valid discretionary trading authority. What documents would you look for? What would constitute a deficiency? What action should be taken for each type of deficiency found — and who should be notified? Write your checklist and the associated response protocol.

Exercise 3: Bounded Discretion Analysis

A client's advisory agreement grants the advisor discretion to rebalance within the target allocation range defined in the IPS, but requires client approval for any change to the strategic allocation or the addition of a new asset class. The advisor proposes four actions: (1) selling equities to bring the allocation back to target after a market rally, (2) adding a 5% allocation to commodities not previously in the IPS, (3) switching from one large-cap equity manager to another within the same sleeve, and (4) increasing the fixed income target from 35% to 45%. For each action, determine whether it falls within the advisor's discretionary authority or requires client approval, and explain your reasoning.

Exercise 4: Post-Trade Review Procedure

Design a post-trade compliance review procedure for a firm that manages both discretionary and non-discretionary accounts. Your procedure should specify what is reviewed for each mandate type, how frequently reviews are conducted, what constitutes a reviewable exception, and what escalation steps apply when a potential violation is identified. Write your procedure in a format that could be used as an internal operations policy document, with clear distinctions between the requirements for each mandate type.

Key Terms

Discretionary Mandate — An advisory arrangement in which the client formally grants the advisor the legal authority to make and execute investment decisions within the account without obtaining prior approval for each transaction.

Non-Discretionary Mandate — An advisory arrangement in which the advisor may make recommendations but may not execute any transaction without the client's explicit prior approval for each action.

Limited Power of Attorney (LPOA) — A legal document through which the client grants the advisor specific, bounded authority to place trades and act on the client's behalf within the scope defined by the advisory agreement.

Execution Risk — The risk that a desired transaction cannot be completed at an advantageous time or price, which is elevated in non-discretionary accounts due to the time required to obtain client authorization before trading.

Style Drift — A gradual deviation of a portfolio's investment characteristics from its documented mandate or strategy, which is a key monitoring concern in discretionary accounts where the advisor acts without routine client oversight of individual decisions.

Bounded Discretion — A form of discretionary authority scoped to specific activities, parameter ranges, or transaction types, requiring client approval for actions that fall outside the defined boundaries.

Post-Trade Review — A compliance process that examines executed trades after the fact to confirm that they were consistent with the account's mandate, properly authorized, and within the advisor's documented scope of authority.

Unauthorized Transaction — A trade executed in an account without the required legal authorization — either a valid LPOA for discretionary accounts or documented client approval for non-discretionary accounts — constituting a regulatory violation regardless of whether the trade was otherwise appropriate.

Knowledge Check

Question 1
What is the primary legal document that authorizes an advisor to place trades in a discretionary account without contacting the client before each transaction?

A. The investment policy statement, which documents the client's objectives and authorizes all trades consistent with those objectives.
B. The limited power of attorney, which grants the advisor specific authority to act on the client's behalf within the scope of the advisory mandate.
C. The custodial agreement, which gives the advisor access to the account and the ability to direct transactions.
D. The Form ADV disclosure, which registers the advisor's authority to trade and satisfies regulatory authorization requirements.

Question 2
A client grants an advisor "bounded discretion" to rebalance within the documented target allocation range. The advisor wants to add a new asset class not currently in the investment policy statement. Which of the following best describes the correct course of action?

A. The advisor may proceed immediately because discretionary authority covers all rebalancing and portfolio management decisions.
B. The advisor must obtain client approval before adding the new asset class, since this action falls outside the scope of the bounded discretion granted.
C. The advisor should document the rationale internally and proceed, then notify the client at the next scheduled review meeting.
D. The advisor must file an updated Form ADV before making any change to the investment policy statement.

Question 3
Which of the following best explains why non-discretionary mandates create execution risk that discretionary mandates do not?

A. Non-discretionary advisors are required to use limit orders rather than market orders, which may not be filled at the desired price.
B. Non-discretionary accounts are subject to additional regulatory review before trades can be executed, adding a mandatory delay.
C. Non-discretionary mandates require client approval before each transaction, and the time required to reach and receive authorization from the client can result in missed opportunities or additional losses in fast-moving markets.
D. Non-discretionary advisors are prohibited from trading during market volatility by the terms of the standard advisory agreement.

Question 4
An operations associate discovers that a discretionary account has been active for six months but has no limited power of attorney on file. What is the most accurate characterization of this situation?

A. The account is compliant because the advisory agreement itself constitutes discretionary authority in most jurisdictions.
B. Every trade placed in the account over the past six months may be considered an unauthorized transaction, creating regulatory and legal exposure for the firm.
C. The account should be converted to non-discretionary status retroactively, and all past trades should be re-authorized by the client.
D. The situation is a minor documentation gap that can be remediated by obtaining an LPOA from the client and filing it with the next quarterly account review.

Question 5
What is style drift, and why is it a particular compliance concern in discretionary accounts?

A. Style drift occurs when an advisor changes their investment philosophy, which is prohibited in discretionary accounts without regulatory approval.
B. Style drift is the gradual divergence of a portfolio from its documented mandate, and it is a heightened concern in discretionary accounts because the advisor acts without client approval, meaning drift may go undetected without active monitoring.
C. Style drift refers to the unauthorized transfer of assets between account types, which is more common in discretionary arrangements because the advisor has broad trading authority.
D. Style drift occurs when a client changes their risk tolerance without updating the IPS, and it is monitored primarily in non-discretionary accounts where the advisor must disclose any deviation from the original mandate.

Lesson Summary

• A discretionary mandate grants the advisor legal authority to make and execute investment decisions without prior client approval for each transaction, formalized through a limited power of attorney, while a non-discretionary mandate requires documented client authorization before any trade is executed.
• The limited power of attorney is the foundational legal document for discretionary accounts and must be valid, current, and on file at the custodian before any discretionary trading activity is permitted — its absence makes all trades in the account technically unauthorized.
• Discretionary mandates enable faster execution and more consistent portfolio management but require active post-trade compliance monitoring to ensure the advisor remains within mandate parameters and does not allow style drift to develop over time.
• Non-discretionary mandates preserve maximum client control and require documented authorization for each transaction, but introduce execution risk and administrative burden that make them unsuitable for most professionally managed account structures.
• Operations teams must correctly identify mandate type for every account and apply the corresponding workflow — including authorization requirements, documentation standards, and post-trade review procedures — to every transaction processed, as misapplication constitutes a compliance violation regardless of the trade's investment merit.

Looking Ahead

With mandate authority now understood, Lesson 5.4 turns to wrap programs and fee bundling — a specific service model that typically combines discretionary management, custodial services, and transaction execution into a single fee arrangement. Wrap programs are one of the most common delivery vehicles for SMA and managed account services and represent a specific commercial and operational structure that builds directly on the advisory account and mandate concepts covered in Lessons 5.1 through 5.3. Understanding how wrap fees are structured, calculated, and billed is essential operational knowledge for anyone working in wealth and asset management.

Study Support

• Templates & Tools

  Use the mandate type comparison chart, LPOA tracking checklist, and post-trade review template to practice applying the correct workflows and documentation standards to discretionary and non-discretionary accounts.

• Glossary Support

  Review key terms including discretionary mandate, non-discretionary mandate, limited power of attorney, execution risk, style drift, bounded discretion, post-trade review, and unauthorized transaction.

• Case Examples

  Study practical scenarios illustrating the operational and compliance consequences of mandate type errors, including unauthorized trade cases, missing LPOA situations, and post-trade review findings in discretionary accounts.

Practical Application

By the end of this lesson, students should be able to define discretionary and non-discretionary mandates and explain how each distributes investment decision-making authority; describe the role of the limited power of attorney in establishing discretionary trading authority and explain what happens operationally when this document is missing or invalid; compare the operational workflows required for each mandate type and identify where they diverge; explain why non-discretionary mandates create execution risk; and describe the post-trade compliance monitoring requirements that apply to discretionary accounts, including the risk of style drift and how it is detected and addressed.

Next Lesson

Understand how wrap programs package advisory, portfolio management, and transaction services into a single bundled fee, how these programs are structured across different platforms, and how fee calculations and billing work operationally.

Lesson Navigation