Portfolio Implementation and Ongoing Practice for Investment Adviser Representatives: 26.2

## C4-M01-S01 | Translate the decision into an executable specification Portfolio construction ends with a desired investment arrangement. Implementation starts by determining how the actual accounts can reach that arrangement. A target allocation is not an executable instruction. It does not by itself identify the account, legal owner, permitted security, quantity, available cash, required approval, tax lot, order condition, or completion evidence. The operational professional must connect these details without silently changing the approved decision. This connection is the subject of this course. The examples use fictional securities and stipulated terms; they demonstrate process and arithmetic, not actual product recommendations. Begin with the decision that has already been made. Separate the desired end state from the path to that state. The end state might specify three approved sleeves, a reserve, and a restriction on selling a legacy holding. The path might require an account transfer, collection of missing acquisition records, a partial sale, funding of the reserve, and purchases. A plan that reaches the target weights by violating the restriction is not a successful implementation. A plan that preserves the restriction but fails to fund a known payment is also incomplete. Implementation quality therefore depends on satisfying the full set of constraints, rather than optimizing one visible number. A useful specification identifies six dimensions: ownership, authority, inventory, constraints, dependencies, and acceptance evidence. Ownership answers whose property is involved and in which legal account. Authority identifies who may approve or place the particular action. Inventory describes actual positions, cash, pending activity, and unresolved records. Constraints describe restrictions such as a minimum cash reserve, a stated gain budget, unavailable fractional transfers, or an account-specific prohibition. Dependencies explain which conditions must be established before a later step. Acceptance evidence states how someone will know that the step occurred correctly. These dimensions are a recommended operational framework, not a claim that every regulator mandates one particular form. Consider the fictional Alder household. Two spouses discuss their combined finances, but one taxable account belongs only to Mira and an IRA belongs only to Leon. The approved plan calls for changes in both. A combined household summary is useful for understanding the intended result, yet it cannot replace account-level authority. Instructions for Mira's account must resolve the rights of its owner and authorized persons. Instructions for Leon's IRA must resolve the rights and restrictions of that account. Merely combining the values in a worksheet does not combine ownership, withdrawal rights, beneficiary designations, or tax treatment. The operational specification should retain separate account identifiers even when a consolidated report is prepared. Authority should be resolved at the action level. An adviser may be authorized to trade within a mandate but lack authority to direct a payment to an outside recipient. A person may be able to view an account without authority to instruct transactions. A client may approve a recommended allocation while withholding approval of a particular sale until a tax professional responds. In each situation, a broad statement that the relationship is active fails to answer the next operational question. The relevant question is whether this specific instruction is authorized in this specific account under current documentation and firm procedures. For advisers registered or required to register under Advisers Act section 203, Rule 204-2(a)(3) addresses memoranda of securities orders, received instructions, and modifications or cancellations. Paragraphs (a)(8) through (10) address discretionary accounts, evidence of discretionary authority, and agreements. These federal provisions should not be indiscriminately presented as rules governing every state-only adviser. Their operational lesson is narrower and practical: the instruction and its authority should remain traceable rather than disappearing into a final portfolio total. [C4-M01-CL001] The specification also needs a version. Suppose an initial plan authorized selling 400 shares, but the client later limited the sale to 250. A spreadsheet that retains the old quantity while a separate email contains the new restriction creates two competing instructions. The professional should establish which version governs, preserve the earlier record, and update dependent quantities. Deleting the first instruction destroys history; continuing to use it ignores the change. A versioned record can show the original request, the revised limit, the time of acceptance, and the effect on cash and purchase quantities. Finally, identify what remains an assumption. A quoted transfer value is not a guaranteed arrival value. An expected receipt is not available cash. A target trade date is not an executed order. The implementation specification should label these distinctions explicitly. If a later step depends on an assumption that has not been verified, the plan needs either a hold or a conditional alternative already within the authorized scope. The discipline is to make uncertainty visible before the system converts it into an unintended transaction.