Trade Allocation Fairness

Trade allocation fairness requires you to allocate investment opportunities among eligible client accounts using a documented, consistently applied methodology that avoids preferential treatment and can be evidenced after the fact. Under the antifraud provisions of the Investment Advisers Act, your controls must cover pre-trade allocation, partial fills, exceptions, monitoring, and personal trading conflicts. (15 U.S.C. § 80b-6)

Key takeaways:

• Use a pre-trade allocation method (pro rata, rotation, etc.) tied to objective eligibility criteria, and document exceptions. (15 U.S.C. § 80b-6)
• Control the hard parts: partial fills, cross trades, aggregated orders, and personal trading that can distort fairness. (15 U.S.C. § 80b-6)
• Prove it with timestamped allocations, OMS/blotter evidence, exception logs, and periodic testing that looks for systematic favoring. (15 U.S.C. § 80b-6)

“Trade allocation fairness requirement” usually shows up in exams as a simple question with a difficult subtext: can you prove, account-by-account, that your allocation process is designed to prevent favoritism and actually works in real trading conditions. The requirement is rooted in the Investment Advisers Act’s antifraud provisions, which the SEC uses to scrutinize whether an adviser’s conduct disadvantages some clients for the benefit of others. (15 U.S.C. § 80b-6)

Operationally, fairness breaks down where firms rely on informal trader judgment, handle partial fills inconsistently, or allow “exceptions” that always seem to benefit the same accounts. That includes flagship funds getting better fills, proprietary or affiliated accounts getting priority, or personal trades competing with clients. Your goal is not to defend every outcome; it is to show a repeatable process: eligible accounts are defined, the allocation method is selected in advance, deviations are controlled and approved, and monitoring looks for patterns of systematic preferential treatment. (15 U.S.C. § 80b-6)

This page gives requirement-level implementation guidance you can put into a written supervisory procedure, implement in your OMS/workflow, and defend in an exam.

Regulatory text

Regulatory excerpt (provided): “Investment advisers must allocate trades fairly among client accounts, with written policies and procedures to prevent preferential treatment of any account.” (15 U.S.C. § 80b-6)

Operator interpretation:
You need written, implementable procedures that (1) define which accounts are eligible for a given trade, (2) allocate orders and fills among those accounts using an objective method set before execution, (3) handle partial fills and exceptions in a controlled way, and (4) detect and correct patterns suggesting favoritism. If you cannot evidence those elements from books-and-records outputs (OMS logs, trade blotter, approvals), your “policy” is not operational. (15 U.S.C. § 80b-6)

Plain-English interpretation (what the requirement means)

Trade allocation fairness means similarly situated clients should have a fair chance at the same investment opportunities. If you run multiple accounts with comparable mandates or strategies, you cannot steer better prices, larger fills, or scarce allocations to preferred clients, affiliated accounts, or employees. You also need controls to prevent personal trading from undermining client allocations. (15 U.S.C. § 80b-6)

“Fair” does not require identical outcomes on every trade. It requires a process designed to prevent preferential treatment and a surveillance program that can identify systematic bias (for example, one account repeatedly receiving favorable partial fills). (15 U.S.C. § 80b-6)

Who this applies to (entity + operational context)

In scope entities: investment advisers and adviser personnel making or influencing allocation decisions, including portfolio managers and trading teams. (15 U.S.C. § 80b-6)

Operational contexts where this becomes exam-critical:

• Aggregated (“bunched”) orders across multiple accounts and later allocations to sub-accounts. (15 U.S.C. § 80b-6)
• Partially filled orders where there is discretion in who receives the filled quantity. (15 U.S.C. § 80b-6)
• Scarce capacity / limited allocations (new issues, liquidity-constrained instruments, hard-to-borrow, etc.). The instrument type is less important than the scarcity dynamics. (15 U.S.C. § 80b-6)
• Side-by-side management (e.g., performance-fee accounts alongside other clients, or materially different fee structures that can tempt favoritism). (15 U.S.C. § 80b-6)
• Personal trading and conflicts where employee trades could compete with client trades or influence allocation decisions. (15 U.S.C. § 80b-6)

What you actually need to do (step-by-step)

1) Define “eligible accounts” per strategy and security type

Create a documented eligibility rule set that your trading workflow can apply consistently. For each strategy or model, specify:

• Account inclusion criteria (mandate alignment, restrictions, cash/position limits, guideline constraints).
• Exclusion criteria (client restrictions, lack of capacity, legal/contractual constraints).
• How eligibility is evidenced pre-trade (e.g., model membership list, restrictions check output, cash check).

Control objective: if an account is excluded, you can point to a contemporaneous reason, not a post-hoc explanation. (15 U.S.C. § 80b-6)

2) Choose and document a pre-trade allocation methodology

Pick a primary method and a limited set of permitted alternatives. Common methods include:

• Pro rata by order size / target size for aggregated orders.
• Rotation for scarce allocations (with clear rotation rules).
• Randomized or time-stamped rule only if it is truly systematic and reproducible.

Document:

• When each method is used.
• What inputs drive the allocation.
• Who can authorize a deviation and under what criteria.

Non-negotiable: the method must be determined before execution and applied consistently. (15 U.S.C. § 80b-6)

3) Control partial fills with a deterministic “fill allocation” rule

Partial fills are where fairness breaks in practice. Write a specific rule such as:

• Allocate partial fills pro rata to intended allocations, with rounding rules.
• If pro rata is impractical, use rotation with documented order priority rules.
• Prohibit ad hoc reallocations after price movement unless pre-approved and documented.

Require traders to record the fill allocation at the time of allocation, not later. The record should show the filled quantity, allocation logic, and any rounding. (15 U.S.C. § 80b-6)

4) Build an exception process that is narrow, approved, and reviewable

Define “exception” categories (examples: hard restrictions discovered post-trade, settlement constraints, operational errors). For each exception:

• Required fields in an exception log (trade ID, affected accounts, reason code, approver, timestamp).
• Required pre-approval vs post-approval rules.
• Independent review cadence by Compliance (or another control function) for repeat patterns. (15 U.S.C. § 80b-6)

A practical test: if you can’t summarize exceptions by reason code and impacted account, your exception process is not exam-ready. (15 U.S.C. § 80b-6)

5) Address personal trading conflicts tied to allocation fairness

Your personal trading policy should clearly prohibit conduct that could disadvantage clients or create incentives to favor certain accounts. Operationalize with:

• Pre-clearance rules for access persons where relevant to your program design.
• Restricted lists/watch lists aligned to trading activity.
• Surveillance triggers that look for employee activity around client trades and allocations. (15 U.S.C. § 80b-6)

Keep the focus on allocation impact: can personal trades compete for liquidity, influence timing, or create incentive to direct better fills away from clients. (15 U.S.C. § 80b-6)

6) Implement monitoring that detects “systematic” preferential treatment

Design testing that answers two questions:

1. Process adherence: Did the OMS allocation match the documented methodology, and were exceptions approved?
2. Outcome patterns: Over time, does any account (or account type) receive consistently better outcomes than similarly situated accounts?

Practical monitoring outputs:

• Exception trend reports by account, PM, trader, and reason code.
• Reviews of partial fill allocations for repeated favorable rounding or priority.
• Comparison of allocations for limited-capacity trades across eligible accounts. (15 U.S.C. § 80b-6)

If you need a workflow system to track allocations, exceptions, approvals, and evidence in one place, Daydream can be used as the control hub to route exception approvals, store artifacts, and produce audit-ready reporting without reconstructing decisions manually.

Required evidence and artifacts to retain

Keep artifacts that let you replay the decision from “intent” to “execution”:

Policies and procedures

• Trade allocation and aggregation policy (current + prior versions). (15 U.S.C. § 80b-6)
• Exception handling procedure with reason codes and approval authorities. (15 U.S.C. § 80b-6)
• Personal trading/conflicts policy sections relevant to allocation conflicts. (15 U.S.C. § 80b-6)

Trading and allocation records

• OMS/trade blotter entries showing order creation, aggregation, execution, and allocation details (including timestamps where available). (15 U.S.C. § 80b-6)
• Allocation worksheets or OMS allocation reports showing the algorithm and final assigned quantities. (15 U.S.C. § 80b-6)
• Partial fill allocation records, including rounding logic when used. (15 U.S.C. § 80b-6)

Governance and oversight

• Exception log with approvals and escalation evidence. (15 U.S.C. § 80b-6)
• Periodic surveillance/testing results, investigation notes, and remediation tracking. (15 U.S.C. § 80b-6)
• Training records for traders/PMs on allocation procedures. (15 U.S.C. § 80b-6)

Common exam/audit questions and hangups

Expect questions like:

• “Show me your allocation policy and walk me through a partial-fill day.” (15 U.S.C. § 80b-6)
• “How do you decide eligibility for a trade? Where is that recorded?” (15 U.S.C. § 80b-6)
• “How many allocation exceptions occurred? Which accounts benefited?” (15 U.S.C. § 80b-6)
• “Who can override the default methodology, and how is it approved?” (15 U.S.C. § 80b-6)
• “How do you monitor for systematic favoritism across accounts?” (15 U.S.C. § 80b-6)

Hangups that slow exams:

• Exceptions tracked in email with no structured log.
• Inability to reproduce allocations due to missing timestamps or overwritten OMS notes.
• Surveillance that checks only “policy exists,” not outcomes and patterns. (15 U.S.C. § 80b-6)

Frequent implementation mistakes and how to avoid them

Mistake	Why it fails	Fix
Policy says “allocate fairly” with no method	Un-testable and invites discretion	Define methods, eligibility inputs, and rounding rules. (15 U.S.C. § 80b-6)
Partial fills handled ad hoc	Creates appearance of favoritism	Hard-code a default partial-fill rule and require documented exceptions. (15 U.S.C. § 80b-6)
Exceptions are common and repetitive	“Exception” becomes the real process	Add reason codes, set approval thresholds, and escalate repeat patterns. (15 U.S.C. § 80b-6)
Monitoring looks only at a few sampled trades	Misses systematic bias	Add trend views by account/PM/trader and focus on scarce/partial-fill scenarios. (15 U.S.C. § 80b-6)
Personal trading controls sit separately from allocation	Misses the conflict mechanism	Tie personal trading surveillance to allocation windows and liquidity competition. (15 U.S.C. § 80b-6)

Enforcement context and risk implications

The SEC’s fairness focus is whether any account systematically receives preferential allocations and whether the adviser’s written policies and procedures prevent that outcome in practice. Failures can be framed as fraudulent or deceptive conduct under the Investment Advisers Act’s antifraud provisions, particularly when disclosures, policies, or actual practices diverge. (15 U.S.C. § 80b-6)

Risk is not limited to enforcement. Weak allocation controls create client complaints, reputational damage, and a difficult remediation path because historical allocations are hard to reconstruct without clean data. (15 U.S.C. § 80b-6)

Practical 30/60/90-day execution plan

First 30 days: stabilize and document the real process

• Inventory strategies where you manage multiple accounts with similar mandates; identify where aggregation and partial fills occur. (15 U.S.C. § 80b-6)
• Map current workflow from order creation to allocation; identify who decides exceptions and where decisions are recorded. (15 U.S.C. § 80b-6)
• Draft or revise the allocation policy with: eligibility criteria, standard methods, partial fill rule, exception governance, and personal trading conflict hooks. (15 U.S.C. § 80b-6)
• Stand up an exception log immediately, even if manual, and require approvals for deviations. (15 U.S.C. § 80b-6)

Days 31–60: implement controls in systems and train

• Configure OMS templates or standard allocation worksheets aligned to the documented methods. (15 U.S.C. § 80b-6)
• Implement structured approvals (Compliance or designated supervisors) for exception categories. (15 U.S.C. § 80b-6)
• Train PMs and traders with concrete scenarios: partial fills, rounding, restricted accounts, and post-trade corrections. (15 U.S.C. § 80b-6)
• Start surveillance reporting: exceptions by account and partial-fill reviews. (15 U.S.C. § 80b-6)

Days 61–90: test, tune, and evidence

• Run a targeted lookback on scarce/partial-fill trades; document findings and remediation. (15 U.S.C. § 80b-6)
• Tighten reason codes and approval thresholds based on what you learned from early exception patterns. (15 U.S.C. § 80b-6)
• Create an exam-ready evidence pack: policy, sample allocations with traceability, exception log excerpts, and testing results. (15 U.S.C. § 80b-6)
• If evidence is fragmented, centralize it in a workflow tool such as Daydream so approvals, artifacts, and reporting are consistent and retrievable.

Frequently Asked Questions

Does “fair allocation” mean every account must receive the exact same price or fill?

No. The requirement is about a fair, consistently applied process designed to prevent preferential treatment and to detect systematic bias over time. (15 U.S.C. § 80b-6)

Can we change allocation methods depending on the product (e.g., rotation for scarce trades, pro rata otherwise)?

Yes, if you define when each method applies, document it in procedures, and apply it consistently with controlled exceptions. (15 U.S.C. § 80b-6)

What is the minimum documentation you need for an allocation exception?

Record the trade, impacted accounts, a standardized reason, the approver, and a timestamped record of the decision. Keep enough detail to explain why the exception did not create preferential treatment. (15 U.S.C. § 80b-6)

How should we handle rounding in pro rata partial fills?

Set a rounding rule in advance (for example, deterministic rounding and rotation of residual units) and apply it consistently. Document any deviation through the exception process. (15 U.S.C. § 80b-6)

If an account has tighter restrictions and often can’t participate, is that “unfair”?

Restrictions can legitimately affect eligibility. The control requirement is to document eligibility decisions contemporaneously so exclusions are traceable to client constraints, not preference. (15 U.S.C. § 80b-6)

What do examiners usually want to see first?

A written allocation policy that matches actual practice, plus OMS/blotter evidence and an exception log that demonstrates oversight and pattern monitoring. (15 U.S.C. § 80b-6)