Proxy Voting Responsibilities

“Proxy voting responsibilities” under the SEC’s investment adviser rules become real the moment you either (a) accept voting authority in an advisory agreement or (b) actually vote proxies for client accounts. The regulatory expectation is not that you always vote a certain way, but that your firm has policies and procedures reasonably designed to ensure proxy votes are cast in the best interests of clients, with conflicts identified and handled. (17 CFR § 275.206(4)-6)

Operationally, this requirement breaks into five deliverables you can build, test, and evidence: (1) a written proxy voting policy that maps to how your firm votes and supervises votes; (2) a conflicts-of-interest method that works in practice (not just a disclosure paragraph); (3) client-facing disclosure about your proxy voting policies; (4) a process to provide proxy voting records to clients on request; and (5) books and records that let you reconstruct what happened for any vote. (17 CFR § 275.206(4)-6)

This page translates the rule into an implementable control set: roles, workflows, decision criteria, exception paths, and an evidence list you can hand to internal audit or an SEC exam team.

Regulatory text

Rule requirement (excerpt): “Investment advisers that exercise voting authority over client proxies must adopt policies and procedures reasonably designed to ensure that proxies are voted in the best interest of clients.” (17 CFR § 275.206(4)-6)

Operator interpretation: If you vote proxies (directly or through a third party), you must have written, followed procedures that (1) govern how you decide and submit votes, (2) address conflicts of interest in proxy voting, (3) are disclosed to clients, (4) allow clients to obtain proxy voting records upon request, and (5) are backed by complete vote and policy records. (17 CFR § 275.206(4)-6)

Plain-English interpretation (what the SEC expects you to be able to show)

You should be able to answer, with documents and system records:

• Authority: Which clients gave you proxy voting authority, and what instructions or restrictions apply to each. (17 CFR § 275.206(4)-6)
• Decisioning: How your firm decides votes (internal research, a proxy advisor, issuer engagement, custom client policies) and how that approach aligns to “best interest of clients.” (17 CFR § 275.206(4)-6)
• Conflicts: How you identify conflicts (issuer relationships, client relationships, business ties, personal interests) and what you do when one exists (escalation, disclosure, recusal, client-directed voting, or other documented mitigation). (17 CFR § 275.206(4)-6)
• Proof: The vote was cast as intended, exceptions were approved, and records are retained and retrievable. (17 CFR § 275.206(4)-6)
• Client access: You can provide your proxy voting policies and proxy voting records to clients on request. (17 CFR § 275.206(4)-6)

Who it applies to (entity and operational context)

This requirement applies to investment advisers that exercise voting authority over client proxies, including advisers that:

• Vote proxies in-house through a custodian or voting platform. (17 CFR § 275.206(4)-6)
• Delegate voting to a third party (for example, a proxy voting service provider) while retaining responsibility for oversight and conflicts handling. (17 CFR § 275.206(4)-6)
• Use model portfolios, SMAs, or pooled vehicles where the adviser controls voting for underlying holdings, to the extent the adviser has proxy voting authority. (17 CFR § 275.206(4)-6)

It also applies in a “negative” way: if you do not have proxy voting authority, you still need contracts and disclosures to match reality and avoid accidentally taking on responsibility your operations cannot support. (17 CFR § 275.206(4)-6)

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

1) Map proxy voting authority and client-specific instructions

Create and maintain a proxy authority inventory that ties:

• Client / account (or mandate)
• Source of authority (agreement language; standing letters)
• Any voting guidelines, restrictions, or “client directs votes” arrangements
• Where voting occurs (custodian platform; third-party proxy voter; internal ops)

Control objective: No votes cast without authority; no client restrictions missed. (17 CFR § 275.206(4)-6)

2) Adopt written proxy voting policies and procedures that match your real workflow

Your policy should be short enough to be used and detailed enough to supervise. Include:

• Scope: which accounts and products the policy covers, and exclusions (with rationale). (17 CFR § 275.206(4)-6)
• Roles: who owns the policy (typically Compliance), who decides votes (PMs/investment committee), who executes submissions (ops), who supervises exceptions. (17 CFR § 275.206(4)-6)
• Decision sources: internal voting guidelines and/or third-party proxy advisor recommendations, and when overrides are permitted. (17 CFR § 275.206(4)-6)
• Timeline management: how ballots are received, tracked, and voted before deadlines. (17 CFR § 275.206(4)-6)
• Exceptions: how you document and approve overrides, late ballots, share-blocking constraints, or missing meeting materials. (17 CFR § 275.206(4)-6)
• Client requests: how you provide policy copies and voting records upon request. (17 CFR § 275.206(4)-6)

3) Build a conflicts-of-interest workflow specific to proxy voting

Proxy voting conflicts are often situational. Your procedure should define:

• Conflict triggers (examples you should tailor): the issuer is also a client; the issuer is a significant distribution partner; your personnel have outside roles or personal holdings that create bias; your firm seeks business from the issuer. (17 CFR § 275.206(4)-6)
• Conflict check timing: at minimum, at ballot intake and before vote submission for relevant issuers. (17 CFR § 275.206(4)-6)
• Mitigation options: pre-approved voting policy applied consistently; referral to an independent third party for recommendation; escalation to a conflicts committee; client-directed voting in high-risk cases; documented recusal of conflicted personnel. (17 CFR § 275.206(4)-6)
• Documentation requirements: what gets recorded, where, and who signs off. (17 CFR § 275.206(4)-6)

4) If you use a third party (proxy advisor or voting agent), implement oversight controls

Delegation does not eliminate responsibility. Put in place:

• Due diligence of the third party’s methodology, data sources, and operational resilience as it affects accurate, timely voting. (17 CFR § 275.206(4)-6)
• A written service scope (who provides recommendations, who actually submits votes, how recalls/re-votes work). (17 CFR § 275.206(4)-6)
• A process for reviewing a sample of votes, overrides, and conflict cases to confirm the service behaves as your policy requires. (17 CFR § 275.206(4)-6)

Tools like Daydream can help you operationalize this by centralizing third-party due diligence artifacts, linking them to the proxy voting control owner, and keeping the evidence package exam-ready without relying on inbox archaeology.

5) Client disclosure and client requests process

Your client communications should clearly state:

• Whether you have voting authority.
• That you maintain proxy voting policies and procedures and will provide them on request.
• That you will provide information about how you voted proxies upon request. (17 CFR § 275.206(4)-6)

Operationalize requests with a defined intake channel (email alias or portal), ownership (Compliance/Client Service), and a standard response package.

6) Recordkeeping: retain a complete, retrievable audit trail of proxy voting activity

Set a record retention checklist for each ballot:

• Ballot details, meeting information, and issuer identifiers.
• How the vote was cast on each proposal and the date/time submitted.
• Any analysis or recommendation relied on (internal memo, third-party recommendation, research notes).
• Exceptions and overrides with approvals and rationale.
• Conflicts checks and mitigations, if applicable.
• Copies of the proxy voting policies and procedures in effect at the time. (17 CFR § 275.206(4)-6)

Required evidence and artifacts to retain (exam-ready list)

Keep these artifacts organized by period and retrievable by issuer, client, and meeting date:

• Current and historical proxy voting policy and procedures (version-controlled). (17 CFR § 275.206(4)-6)
• Client proxy authority matrix and any client-specific voting guidelines. (17 CFR § 275.206(4)-6)
• Vote logs showing proposals, votes cast, timestamps, and submission confirmation. (17 CFR § 275.206(4)-6)
• Proxy advisor/third-party contracts, due diligence, and oversight reviews (if used). (17 CFR § 275.206(4)-6)
• Conflicts register entries tied to proxy votes, including mitigation approvals. (17 CFR § 275.206(4)-6)
• Client disclosure language and request-response tickets for “provide policy” and “how we voted” requests. (17 CFR § 275.206(4)-6)
• Supervisory reviews, exception reports, and any remediation actions. (17 CFR § 275.206(4)-6)

Common exam/audit questions and hangups (what reviewers probe)

Expect to be asked:

• Show me the written proxy voting policy and the last time it was reviewed and approved. (17 CFR § 275.206(4)-6)
• For a sample issuer meeting, produce the ballot, the decision basis, the conflict check, and proof of submission. (17 CFR § 275.206(4)-6)
• Where do client-specific restrictions live, and how do they flow into the voting platform? (17 CFR § 275.206(4)-6)
• How do you supervise a third party that recommends or submits votes? (17 CFR § 275.206(4)-6)
• How do you respond to a client request for proxy voting records, and how do you ensure completeness? (17 CFR § 275.206(4)-6)

Common hangup: teams can describe the process but cannot reconstruct it for a specific vote because evidence is spread across email, a proxy platform, and an advisor research portal.

Frequent implementation mistakes and how to avoid them

• Mistake: Policy describes “best interest” but never defines decision criteria.
  Fix: Document what inputs drive voting (guidelines, proxy advisor, investment thesis) and what triggers overrides. (17 CFR § 275.206(4)-6)

• Mistake: Conflicts language is generic and never used.
  Fix: Add concrete conflict triggers and a required pre-vote check step, then test it on a sample of issuer meetings. (17 CFR § 275.206(4)-6)

• Mistake: Delegating voting to a third party with no oversight.
  Fix: Set an oversight cadence that reviews vote samples, exception reports, and how conflicts are handled. Retain the review workpapers. (17 CFR § 275.206(4)-6)

• Mistake: Client restrictions are stored in PDFs and not operationalized.
  Fix: Maintain a structured client instruction register and reconcile it to how votes are submitted. (17 CFR § 275.206(4)-6)

• Mistake: Inability to fulfill “how you voted” requests quickly and completely.
  Fix: Standardize a report format and test the request workflow using a mock client request. (17 CFR § 275.206(4)-6)

Enforcement context and risk implications

No public enforcement cases were provided in the source catalog for this page. Treat the risk as primarily fiduciary and exam-driven: weak proxy voting controls can lead to findings that your policies are not “reasonably designed,” that conflicts were not managed, or that client disclosures and records are incomplete. (17 CFR § 275.206(4)-6)

Practical 30/60/90-day execution plan

First 30 days (stabilize and inventory)

• Confirm where proxy voting authority exists across products and client agreements; document any exceptions. (17 CFR § 275.206(4)-6)
• Pull current-state workflows: ballot receipt, decisioning, submission, and record retention. (17 CFR § 275.206(4)-6)
• Identify third parties involved in voting or recommendations and gather contracts and SOC/operational materials already on hand. (17 CFR § 275.206(4)-6)
• Draft or refresh proxy voting policy text to match actual operations; assign owners for vote decisions, ops execution, and compliance oversight. (17 CFR § 275.206(4)-6)

Next 60 days (implement controls and evidence)

• Implement conflict triggers and an escalation path; train PMs and ops on when to escalate. (17 CFR § 275.206(4)-6)
• Configure vote logging and an exception/override register with required fields (rationale, approver, date). (17 CFR § 275.206(4)-6)
• Publish client disclosure language and build a repeatable response package for policy/vote-record requests. (17 CFR § 275.206(4)-6)
• Stand up third-party oversight checks if you use a proxy advisor or voting agent; document reviews in a consistent template. (17 CFR § 275.206(4)-6)

Next 90 days (test, supervise, and remediate)

• Run a sample-based QA review of recent votes for completeness: authority, restriction compliance, conflict checks, evidence, and timely submission. (17 CFR § 275.206(4)-6)
• Correct gaps (missing records, unclear approvals, inconsistent overrides) and update procedures. (17 CFR § 275.206(4)-6)
• Add proxy voting to your annual compliance review calendar and supervisory reporting. (17 CFR § 275.206(4)-6)
• Consider centralizing the evidence pack (policy versions, vote logs, third-party oversight, conflicts approvals) in a system like Daydream so exams do not turn into a manual hunt across platforms.

Frequently Asked Questions

If we follow a proxy advisor’s recommendations, are we compliant?

You can use a third party, but you still need written policies, conflict handling, client disclosure, and records. You also need oversight that shows the third party’s recommendations and execution align with your policy and client best interests. (17 CFR § 275.206(4)-6)

Do we need to vote every proxy for every client account?

The rule focuses on policies and procedures designed to vote in clients’ best interests where you exercise authority. Your policies should define when you vote, when you may abstain, and how you document the rationale and any client-specific instructions. (17 CFR § 275.206(4)-6)

What counts as a “conflict” in proxy voting?

A conflict is any relationship or incentive that could bias the vote away from the client’s best interest. Your procedures should name the conflict triggers relevant to your business and require escalation and documented mitigation when triggered. (17 CFR § 275.206(4)-6)

What do we have to provide a client who asks how we voted?

You need a process to make proxy voting records available upon request, and your recordkeeping must support accurate reporting. Many firms satisfy this by generating a vote report by client/period/issuer from the voting platform plus supporting documentation for exceptions. (17 CFR § 275.206(4)-6)

How do we handle client-specific voting guidelines?

Treat client guidelines as binding instructions: store them in a structured register, map them to the account, and ensure they are implemented in the voting workflow. Test them by sampling votes for restricted accounts and confirming votes matched the guideline. (17 CFR § 275.206(4)-6)

What evidence is most persuasive in an exam?

Examiners typically want end-to-end traceability for sampled meetings: authority, ballot receipt, decision basis, conflicts check, submission confirmation, and a complete vote log. If you used a third party, add oversight records and any override approvals. (17 CFR § 275.206(4)-6)