Contract Review Checklist

Review process for vendor, client, and service contracts at an RIA or wealth management firm. Used by operations and compliance to verify legal sufficiency, financial terms, performance obligations, and risk exposure before counter-signature.

6 sections 21 steps Collects data
1

Intake and Classification

  1. Log the contract in the vendor register
    • Add the agreement to the firm's vendor / contract register with counterparty name, effective date, term, renewal type (auto-renew vs. evergreen vs. fixed), and contract owner. The CCO uses this register at annual vendor due diligence and ADV update.

    Collects text Collects date Collects file
  2. Classify the contract type
    • Classification drives the rest of the review. Critical vendor contracts (custodian, portfolio accounting, CRM, archiving) and any agreement that touches client NPI trigger enhanced diligence under Reg S-P and the firm's vendor management policy.

    Collects list
  3. Confirm the parties and signatory authority
    • Verify the legal entity name matches the firm's ADV Part 1 filing — common error is signing as the dba rather than the registered RIA. For the counterparty, confirm the signer has authority (officer, member, or authorized representative) and pull a recent good-standing certificate for entity counterparties.

2

Legal and Regulatory Review

  1. Verify Form ADV and disclosure alignment
    • For client IAAs and solicitor agreements: confirm fee schedule, services, and conflicts described in the contract match Form ADV Part 2A Items 4, 5, and 10. Mismatch is a common SEC exam finding and forces an ADV amendment.

  2. Check producer and adviser licensing requirements
    • Solicitor and subadvisor agreements require the counterparty to be appropriately registered (Series 65/66 IAR or RIA registration in client states). Insurance-linked agreements require state producer licensing. Pull CRD / IARD or NIPR before signing.

  3. Confirm the data privacy and Reg S-P clauses
    • Any vendor with NPI access needs a written information security agreement, breach notification SLA (typically 72 hours), and a return / destruction clause at termination. SEC's amended Reg S-P (effective 2025-2026) requires written incident-response procedures with vendors.

    Collects list
  4. Collect SOC 2 report and information security questionnaire
    • For vendors with NPI access, request the most recent SOC 2 Type II report (not Type I, not older than 12 months) and review the bridge letter covering any gap. File alongside the executed contract for annual vendor due diligence.

    Collects file
3

Financial Terms Review

  1. Reconcile fee schedule against the firm's pricing
    • For client IAAs, confirm AUM tiers, householding rules, and billing frequency match the fee schedule disclosed in ADV Part 2A Item 5. For vendor agreements, validate per-account or per-user pricing against the budgeted run-rate before sign-off.

  2. Review pass-through expenses and out-of-pocket costs
    • Watch for travel, implementation, data feed, and integration fees buried in exhibits. Confirm whether the firm or the client absorbs custodian transaction costs, ACATS fees, and wire fees — ambiguity here drives client-billing disputes.

  3. Confirm payment terms and auto-renewal language
    • Net-30 vs. advance, ACH vs. invoice, and the auto-renewal notice window. Multi-year evergreen agreements with 90-day notice windows are the most common reason firms get locked into vendors past usefulness — flag and add a calendar reminder 120 days before renewal.

    Collects date
4

Performance and Service Levels

  1. Verify scope of services and deliverables
    • Match the statement of work to what operations actually expects — data feeds, reconciliation cadence, reporting deliverables, support hours. Vague scope ("portfolio reporting services") leads to scope-creep arguments at renewal.

  2. Review SLAs and uptime commitments
    • For trading, custody connectivity, and archiving vendors, confirm uptime SLA (99.9% minimum for critical), incident response time, and remedies. Email archiving outages are exam-reportable — the SLA needs teeth, not just credits.

  3. Confirm implementation timeline and milestones
    • Identify dependencies: data conversion from incumbent vendor, custodian feed setup, single sign-on integration. Most portfolio management or CRM migrations slip — bake in milestone-based payment rather than full upfront.

  4. Check non-performance and termination penalties
    • Termination-for-cause should be available without penalty for SLA breach, regulatory issue, or change of control. Termination-for-convenience usually carries a fee — negotiate down for any agreement over 12 months.

5

Risk and Liability Review

  1. Review warranties and representations
    • Confirm the counterparty represents authority to contract, regulatory good standing, no pending enforcement actions, and IP ownership of any deliverables. For data vendors, look for accuracy / fitness representations — most vendors disclaim them, which is a flag for downstream client reporting risk.

  2. Evaluate indemnification and liability caps
    • Mutual indemnification is the floor. For vendors with NPI access, push for a data-breach carve-out from the liability cap (typical caps of 12 months' fees do not cover a real breach). Confirm cyber and E&O insurance coverage amounts in the insurance exhibit.

  3. Review dispute resolution and governing law
    • Confirm governing law and venue are workable — out-of-state arbitration in a vendor-friendly jurisdiction is common boilerplate. For client IAAs, FINRA / state arbitration provisions must be disclosed in ADV Part 2A Item 9 if applicable.

  4. Document overall risk rating and red flags
    • Summarize unresolved issues for CCO review. High-risk findings (uncapped liability, no breach notification, no SOC 2, missing licensure) trigger escalation rather than counter-signature.

    Collects list
6

Approval and Execution

  1. Escalate high-risk findings to the CCO and principal
    • Document the specific concerns, proposed redlines, and counterparty position. CCO and managing principal sign off jointly before re-engaging counsel or counterparty.

  2. Route for principal sign-off and counter-signature
    • Send through DocuSign or the firm's e-signature platform. Confirm the signer is the authorized officer per the firm's authority matrix — bind decisions over the matrix threshold require board or managing-member resolution.

    Collects list Collects paragraph Collects signature
  3. File the executed agreement in NetDocuments
    • Save the fully-executed PDF, all exhibits, SOC 2, and COI in the contract folder. Update the vendor register with the renewal-notice calendar reminder. Books and records under Rule 204-2 require retention for 5 years (first 2 in an easily accessible place).

Use this template

Copy it to your account, customize the steps, and run it with your team in minutes.


Sections 6
Steps 21
Category Financial Services
Price Free to start
Need a different process

Browse hundreds of free templates across every team and industry.

Back to template library

Run Contract Review Checklist with your team

Customize the steps, assign roles, set a schedule, and keep a complete record for every run.