NIGO paperwork is a workflow problem

A transfer form comes back from a custodian because a signature is missing. A beneficiary update is held up over a date mismatch. A client has sent one page of a document, but the rest is still outstanding.

Each item is small. The work around it is not. Someone has to notice the rejection, understand what needs correcting, contact the right person, update the task list, check whether the client responded, and confirm the custodian has accepted the revision. When that chain lives in email, spreadsheets, and an adviser’s memory, cases can stall without anyone realizing it.

For a financial advisory firm, NIGO means “not in good order.” It describes paperwork that a custodian or provider can’t process because information or documentation is missing, inconsistent, or invalid. The exact requirements vary by form and institution, so the correction needs to be checked against the relevant custodian’s instructions.

Automating NIGO tracking doesn’t mean letting software approve client paperwork or decide what a custodian will accept. It means making the status, next action, owner, and deadline visible, then routing the work to a person who can verify it.

That distinction matters. The purpose is to reduce chasing and missed handoffs while keeping human review in the process.

Where manual tracking breaks down

A typical NIGO case can cross several people and systems. An operations associate receives the custodian’s notice. A paraplanner or adviser may need to confirm the intended information. A client needs to supply a correction or sign again. Operations then resubmits the paperwork and waits for a response.

The handoffs create predictable gaps:

The rejection notice remains in a shared inbox, but no task is created.
A spreadsheet says “waiting on client” without showing when the request was sent.
The adviser believes operations has the case, while operations is waiting for the adviser’s approval.
A revised document is uploaded, but nobody confirms that the custodian received it.
A case is marked complete when it has been resubmitted, not when the custodian has confirmed acceptance.

The cost is more than a few extra emails. Staff lose time reconstructing what happened, and the client may have to repeat information or sign documents again. A delayed account transfer can also disrupt the client’s expectations and the adviser’s service plan.

It helps to treat the NIGO item as a case with a defined lifecycle, rather than as a message to remember. A clear record should answer five questions: what was rejected, who owns the next action, what must happen next, when is it due, and what evidence confirms resolution?

That kind of task discipline also supports broader operations. Firms looking at ownership and follow-through across teams can read about tracking team task delegation in financial advisory firms. NIGO is a useful place to start because the case status and next step are usually concrete.

Design the tracking workflow before adding an agent

Before automating anything, agree on a small set of case statuses. Too many statuses make reporting difficult. Too few hide important differences.

A practical starting point might be:

New notice: A rejection or deficiency has arrived and needs review.
Correction defined: A person has confirmed what needs to change.
Waiting on client: The firm has requested information, a signature, or a corrected document.
Internal review: The correction has arrived and needs checking.
Ready to resubmit: The firm has verified the updated paperwork.
With custodian: The corrected paperwork has been submitted and is awaiting a response.
Resolved: The custodian has confirmed acceptance or processing.
Exception: The case needs an adviser, compliance, or operations lead to make a decision.

The statuses should reflect what is actually happening, not what the firm hopes will happen. “With custodian” should mean a submission was made. It should not mean that a document is ready to send. “Resolved” should require evidence, such as a custodian confirmation or an updated account status.

Each case also needs a consistent record. At minimum, capture the client and account reference, form type, custodian, date received, stated deficiency, assigned owner, next action, due date, and latest response. Keep links to the source notice and related documents in approved systems. Avoid copying sensitive client information into tools that aren’t authorized for it.

The correction itself should be explicit. “Fix form” is not a useful assignment. “Confirm the date of the client’s signature against the account records, then route the updated form for review” gives the owner a defined task without making an automated assumption about what the correct date should be.

What an agent does from notice to resolution

An agent can help coordinate this workflow by reading incoming messages, creating a structured case, suggesting a task, and monitoring for replies. The people in the firm still decide whether the notice has been interpreted correctly, whether the document is accurate, and whether the response is ready to send.

A sensible end-to-end process looks like this:

1. Capture the incoming notice

The workflow starts when a notice arrives in an approved shared inbox, document system, or case-management queue. The agent identifies likely NIGO messages and extracts details such as the custodian, account reference, form type, stated deficiency, and response date if one is included.

It should also retain a link to the original notice. The extracted fields are a working summary, not a replacement for the source. If the message is unclear, the agent should mark the case for human review rather than guessing.

2. Create a case and suggest an owner

The agent creates or updates the case record and checks for a matching open item. That duplicate check matters when the same notice has been forwarded or copied to multiple people.

Assignment can follow firm rules. For example, a particular operations team may own transfer forms for certain custodians. A case outside those rules, or one involving a complex client instruction, should be routed to a person who can decide the owner.

The task should include the notice, the extracted deficiency, a proposed next action, and the target date. A person confirms the case details and assignment before any client-facing request is sent.

3. Route the correction to the right person

Once reviewed, the case moves to the appropriate owner. If the client needs to provide a document or sign again, the owner can use an approved template to request it. If an adviser needs to confirm an instruction, the task goes to the adviser with enough context to act.

This is also where firms can set boundaries. The agent can draft a message, but a person approves it. It can flag a missing signature, but it shouldn’t create or alter a signature. It can identify a possible mismatch, but it shouldn’t decide which client detail is authoritative.

4. Track replies and custodian responses

When a client replies or a document arrives, the case can be updated with the event and assigned for review. When operations resubmits paperwork, the submitted date and method should be recorded. If the custodian sends a new response, the workflow should add it to the case rather than create a disconnected thread.

The agent can monitor for changes in status and prompt the owner when a response is overdue. If a second deficiency arrives, it should open a new correction task or update the existing case in a way that preserves the history. The team needs to see what was requested, what came back, and what was sent next.

5. Surface stalled items

A dashboard or daily exception report should show cases with no recorded next action, overdue client requests, custodian responses that have not been reviewed, and submissions waiting beyond the firm’s chosen threshold.

Those thresholds should be based on the firm’s service standards and the custodian’s process, not on a universal assumption. A useful report groups exceptions by owner, age, custodian, and blocker. It should help a manager answer, “Which cases need attention today?” without reading every email thread.

The agent can notify an owner or escalate a case according to clear rules. It should not quietly close a case because no response appeared. If the evidence is missing, the item stays open.

Keep human review where it belongs

Automation is most useful for repeatable coordination. Human judgment remains necessary for interpreting ambiguous notices, confirming client instructions, reviewing corrected paperwork, and deciding when to escalate a case.

A practical control model has three checkpoints:

Notice review: A person verifies the extracted deficiency and confirms the case details.
Correction review: A qualified team member checks the updated information and document before resubmission.
Resolution review: A person confirms the custodian’s response or another reliable record before closing the case.

The firm should also define access controls, retention rules, and approved systems for client documents. Keep an audit trail of status changes, assignments, approvals, and submissions. If a workflow can’t show who approved a correction or what evidence closed the case, it isn’t ready to run unattended.

This approach fits with other administrative work that firms are already organizing. For example, automating account transfer paperwork in your firm can address the paperwork that often sits upstream of a transfer-related NIGO case. And if new prospect records are arriving in inconsistent formats, automating prospect intake for advisory firms can help standardize the information before it reaches operations.

A firm may also connect this process to other administrative workflows. A person still reviews the advice and documentation. The value is in reducing repetitive drafting and helping the team keep a clear record around the work.

Measure whether the workflow is helping

Start with a baseline before changing the process. Useful measures include:

Number of open NIGO cases and their age.
Time from notice received to an assigned owner.
Time spent waiting on the client versus waiting on the custodian.
Number of cases returned for another correction.
Time from resubmission to confirmed resolution.
Staff time spent chasing status or reconstructing case history.

Don’t judge the workflow by how many tasks an agent creates. A system can generate plenty of activity while leaving the underlying case stalled. The better test is whether the team can identify the blocker sooner, assign a clear next action, and confirm when the custodian has accepted the paperwork.

The dollar case depends on the firm’s volume, staffing, and current rework. An audit should test how much of that exposure is connected to this workflow and what portion is realistically addressable.

If staff are also spending time preparing for reviews and writing up notes, they can consider those as separate administrative workflows. The financial advisory AI meeting prep guide covers that adjacent workflow. It’s useful to separate these opportunities rather than assume one automation will solve every source of admin pressure.

Make the first version narrow

A good first release doesn’t need to cover every custodian, document type, or exception. Pick a workflow with enough volume to test and clear rules for assigning ownership. Map the existing steps, including the exceptions staff handle today. Then automate a small part of the process, such as capturing notices and creating reviewed case records.

Before expanding, check that:

The agent links each case to its original notice.
A person verifies extracted details.
Each open case has an owner and next action.
Client messages require approval.
Resubmission and custodian responses are recorded.
A case can’t be closed without evidence.
Managers can find stalled cases without searching inboxes.

From there, add status monitoring and escalation rules. Keep a way to correct the case record when the agent classifies a notice incorrectly. Review exceptions regularly, since they often reveal where the firm’s process needs better rules or a clearer owner.

For an owner or partner, this is an operational decision, not just a software choice. If the process depends on a handful of experienced staff knowing where to look, a new tool won’t fix the underlying ambiguity. Define who owns each step first. Then automate the repeated handoffs that slow the case down.

Start with an Omni Audit

An Omni Audit is an opportunity to discuss the firm’s workflow and consider where cases may stall.

The conversation should include the people who handle notices and follow-ups, not only the owner. They can show which custodian responses require interpretation, which corrections need adviser approval, and what the team currently treats as proof of resolution.

If you want to see how this work fits the wider service, see Omni for financial advisory firms. For a working session on your process, book a 60-min Omni Audit.

Bring a few recent NIGO examples with sensitive details removed, your current tracking method, and the roles involved in each handoff. Those examples can help clarify what should be captured, where human review belongs, and which stalled-case signals may help your team act sooner.

NIGO tracking is a focused place to improve operations because the work has a clear beginning, a sequence of handoffs, and an outcome the firm can verify. Start by making every case visible. Then use automation to keep the next action moving, while your people remain responsible for the decisions that affect the client and the account.

For a closer look at the service and the audit process, see Omni for financial advisory firms. When you’re ready to map the workflow with your team, book your 60-min Omni Audit.

Automate NIGO Paperwork Tracking at Your Firm