Client Repapering for RIAs: How to Run It Without Drowning in NIGO

Client repapering is re-executing a client's account and advisory paperwork because the custodian, the adviser entity, or the agreement underneath it changed. It has three common triggers: an acquisition or change of control, a custodian change or conversion, and an advisor joining from another firm. Each trigger produces the same production line: pull the household from the CRM, prefill the forms, check them, get them signed, chase the ones that stall, submit to the custodian, fix what comes back not in good order (NIGO), and record the result. The firms that get through it cleanly treat it as a production line with a control at every stage, not as a pile of envelopes.

The three triggers, and what each one changes

• Acquisition or change of control. The adviser entity on the relationship changes, or its ownership does. Under the Advisers Act a transfer of a controlling block of the adviser's voting securities can be an assignment of the advisory contract, which brings in client consent. Some deals also move accounts to a new master account or custodian. The full sequence is in the RIA acquisition integration checklist.
• Custodian change or conversion. The firm moves its book from one custodian to another, or a custodian retires a platform and converts accounts. The advisory agreement may not change at all, but the account agreements, transfer instructions, standing instructions and often beneficiary designations have to be re-established at the receiving custodian.
• An advisor joining from another firm. Every client who follows the advisor opens new accounts, signs transfer forms and a new advisory agreement, with a short window before the relationship cools. The timeline and pre-move work are in the breakaway advisor transition checklist.

What gets repapered

The exact packet depends on the trigger, the account types and the custodian's requirements, but most repapering projects touch the same eight document types.

The full directory of custodian and regulatory paperwork is at /forms, with the fields and the work behind each.

Positive consent vs negative consent

When repapering is driven by a change in the adviser, the first question is usually about the advisory agreement, not the custodial forms. Section 205(a)(2) of the Advisers Act says an adviser may not enter into an advisory contract that "fails to provide, in substance, that no assignment of such contract shall be made by the investment adviser without the consent of the other party to the contract". Section 202(a)(1) defines assignment to include "any direct or indirect transfer or hypothecation of an investment advisory contract by the assignor or of a controlling block of the assignor's outstanding voting securities" , which is why a sale of the firm, not only a transfer of contracts, can trigger it.

The statute requires consent. It does not describe its form. In practice there are two:

• Positive consent. The client affirmatively signs or clicks to approve. Silence is a no. It is the cleanest evidence, and the heaviest operational load, because every non-responder is a chase and, eventually, a decision about the relationship.
• Negative consent. The client receives written notice of the change and a stated period to object, and a client who does not object is treated as consenting. The operational load is lighter (send, log, track objections), but it only works where the existing agreement and the transaction support it, and some client types and account types may still need an affirmative signature.

Which one applies to which clients is a legal call, not an operations call. Ask your counsel and CCO, and get the answer by client segment before you build the send list, because it decides the size of everything below. Whichever it is, keep the notice, the send date, the delivery evidence and the response for each client: that is the record you will be asked for. Consent to the advisory contract also does not replace custodial paperwork; if the custodian or the adviser on the account changes, the account documents still need to be signed.

The repapering production line

Every repapering project runs the same nine stages. Each has a predictable way of failing, and a control that catches it before it becomes a NIGO or a client call.

Two stages decide most of the outcome. Source data, because every error in the CRM is copied into every form. And QA before send, because each mistake caught there costs a few minutes, and each one caught by the custodian costs a new envelope, a new chase and a client who has now been asked to sign twice.

For ACAT transfers specifically, the clock after submission is set by rule, not by you: FINRA Rule 11870 has the carrying firm validate a transfer instruction within one business day and complete the transfer within three business days of validation. Most of the time in a transfer is spent before submission and in exceptions, which is where operations has leverage.

NIGO: the usual causes and how to catch them first

Most NIGO rejections are not judgment calls. They are mismatches and omissions that a checklist would have caught. The common ones:

1. Missing signatures, initials or dates. Usually a joint owner, trustee, or custodian of a minor's account who was not on the envelope. Control: derive the signer list from the account registration and check every signature tab against it.
2. Names that do not match the account of record. A missing middle initial, a nickname, a suffix dropped. Control: compare the name on the form to the delivering firm's statement, character for character, not to the CRM alone.
3. Addresses that do not match. The client moved and the CRM was updated but the custodian was not, or the reverse. Control: reconcile address of record before prefill, and treat any difference as a question for the client, not a choice for the associate.
4. Wrong or truncated account numbers. Especially on transfer forms copied from a PDF statement. Control: extract the number from the statement itself and check its length and format for that delivering firm.
5. Wrong form version. Custodians update forms, and a saved copy on a shared drive quietly goes stale. Control: one controlled library of current forms, with the version date checked at QA.
6. Missing beneficiary details. No date of birth, percentages that do not total 100, a contingent beneficiary with no relationship listed. Control: validate beneficiary blocks as a set, not field by field.
7. Registration mismatches on transfers. The receiving account is titled differently from the delivering account, or an IRA is mapped to the wrong account type. Control: match registration and account type between the two before the transfer form is built.

Log every NIGO with a reason code. After the first few weeks the distribution tells you which control to tighten, and it gives the CCO a record of what went wrong and how it was fixed.

Capacity math: how big is your repapering project?

Repapering projects are underestimated because people count households and forget that the work multiplies. The estimate is households, times accounts per household, times forms per account, times touches per form. Here is a worked example. Every number in this example is hypothetical, chosen to show the method, not taken from a customer or a survey. Replace each with your own.

At roughly 90 productive hours a week from a three-person team (again hypothetical), that is about 20 weeks, on top of normal account opening, service requests and billing. Two things move the total more than anything else: the NIGO rate, because each rejection restarts several stages, and prep time per document, because it is multiplied by every document in the project. Those are the two numbers worth attacking first.

Where automation fits, and where it does not

Most of the production line is the same facts moving between the same systems: CRM to form, form to envelope, envelope status back to the CRM. That part is repetitive, rule-bound and checkable, which makes it a good fit for automation. The consent decision, the client conversation, exceptions judgment and custodian submission are not.

This is what Caddi does in a repapering project. Caddi fills the custodian forms from the CRM household record, sends them for signature through DocuSign, and logs the envelope status back to Wealthbox, Salesforce or Practifi. When the record is missing a value, Caddi leaves that field empty and flags it rather than guessing, so the gap goes back to a person before the packet goes to a client. The custodian form auto-fill walkthrough shows exactly this on film: a new account application and a transfer form filled from a Wealthbox household, sent through DocuSign, logged back, with one field left empty on purpose.

Someone on your team builds it in Caddi Automate by screen-sharing the process or describing it in chat, and changes it in plain English when a custodian updates a form. AI builds it, verified code runs it, and any model step inside a run is scoped, logged, and reviewable. With Govern, every run is logged, so the record of what was filled, sent and returned for each household is there when the CCO asks. Across customers, 99% of agent runs complete successfully.

What Caddi does not do: it does not connect to custodian platforms or work inside custodian portals. Submission, custodian exceptions and the consent decision stay with your team and your counsel. Caddi takes the prefill, the envelope, the tracking and the CRM write-back off their plate.

If you want to see how much of this work your team is doing today before a project starts, Discover finds the repetitive work in the tools the team already uses. For the wider picture of the back office, see RIA back-office automation workflows, and for how one independent RIA put this into practice, read The Planning Center's story.

A repapering checklist for operations

1. Scope with counsel first. Which clients need positive consent, which can receive negative consent notice, and which accounts need new custodial paperwork.
2. Reconcile the CRM to the custodian before a single form is filled.
3. Lock the form library to the current versions from the receiving custodian.
4. Size the work with households times accounts times forms times touches, and staff for the NIGO rate, not the best case.
5. Prefill from the record, flag the gaps, and QA every packet before it goes out.
6. Write envelope status to the CRM so the open list is a report, not a spreadsheet.
7. Run a fixed chase cadence with advisor escalation.
8. Queue signed packets for submission daily with a named owner.
9. Log every NIGO with a reason code and tighten the control it points to.
10. Close each household only when the CRM matches the custodian, including new account numbers and consent records.

More for RIA operations leaders

• The Wealth Advisory COO's Guide to AI
• What a Director of Operations at an RIA owns
• The RIA operations tech stack, by workflow
• RIA acquisition integration checklist
• Onboarding a breakaway advisor team

Caddi connects to the systems an RIA back office runs on: Salesforce, Wealthbox, Practifi, Orion, Black Diamond, Tamarac, Addepar, DocuSign, Jump, Zocks. See how it runs client onboarding and the operational side of RIA compliance, or the RIA operations overview.