For an adviser-approved administrative request that goes to a custodian or other provider, close it only when that provider's own status shows it finished. Until then, keep four things in your existing CRM workflow: who owns the follow-through, where the adviser's approval is recorded, which system confirms status, and the confirmation reference. A ticked task, a submitted form or an alert summary shows progress, not proof.
Where approved work can stall
When an adviser approves a client's administrative request, the decision is recorded and fulfillment begins. The agreed work moves from adviser to operations, out to a custodian or other provider, and back again. Each handoff takes someone's attention. One way the trail can stall is an assumption: someone sees a ticked task and believes the request is done.
This checklist covers only that administrative trail for requests that go to a provider. Internal-only tasks with no provider status need a different closeout test. The adviser and the firm's qualified people keep every advice, account, tax and money-movement decision, and they remain responsible for whether the request itself was right. Nothing here tells you what to approve or how to complete a custodial request.
Start with what your tools already do
If your CRM has workflow templates and your custodian has a request-status view, you may be able to build this closeout with tools you already have. Check what your own plans and permissions include.
- CRM workflow templates. In Wealthbox, a workflow template can run as ordered steps or as a checklist finished in any order. It relates to a contact, opportunity or project, and you define the steps (Wealthbox help: creating a workflow template; Product check: 1 November 2026). You can add a step such as “confirmation reference recorded”. That help article does not describe making a step mandatory or attaching evidence to it, so treat the step as a check a person completes.
- Sending tasks to providers. On Wealthbox Premier and Enterprise plans, a workflow's Send-To action can push tasks into integrated platforms, including Schwab Advisor Center, Fidelity Wealthscape and Docupace (Wealthbox help: the Send-To action in workflows; Product check: 1 November 2026). That article describes the outbound send. Ask your administrator what your plan and integrations do after a task is sent.
- Custodian status views. Schwab Advisor Services' public What's New page on Status & Alerts describes status features in its advisor platform. These include tracking submitted requests, Action Needed handling (including not-in-good-order items), Action Required handling, request history and adjustable columns. Its October 2026 section describes AI summaries and suggested actions on items that need attention (Schwab Advisor Services: What's New, Status & Alerts; Product check: 1 November 2026).
In this checklist, the provider's own status is the record of whether a request finished. That is our process rule, not a vendor guarantee. We treat an AI summary as a pointer that can help someone spot an item sooner, not as evidence of completion. If you use a different CRM or custodian, check its current documentation for equivalent features before assuming you have a gap.
Four states worth keeping separate
These are our labels. Your provider's status names may differ.
| State | What it means | What it is not |
|---|---|---|
| Approved | The adviser's decision is recorded where your firm keeps it. | Not yet sent anywhere. |
| Submitted | Operations sent the request to the provider. | Not accepted or complete. |
| Needs action | The provider flagged a problem or asked for more information. | Not something to close or quietly retry without the owner. |
| Confirmed complete | The provider's status shows it finished, and the reference is recorded. | Not a CRM checkmark on its own. |
A closeout record you can copy
These fields are our editorial suggestion for a CRM task or workflow step. They are not presented as fields any vendor provides.
| Field | What to record |
|---|---|
| Request reference | Your internal ID or a pointer to the CRM task |
| Approval reference | A reference or link to where the adviser's approval is recorded (for example, a meeting note or task ID) and its date. Point to it rather than copying it in. |
| Operations owner | One named person |
| Status source | Which custodian or system confirms the status |
| Submitted on | Date sent |
| Current source status | The status as the provider shows it, with the date you checked |
| Exception and next human step | What was flagged, who will act, and by when |
| Confirmation reference | The provider's completion reference or status entry |
| Closed by and date | The person who checked the source |
Before you mark it closed
- A person has checked that the provider's own status shows complete.
- The confirmation reference is in the record, not just a checkmark.
- Any needs-action item was resolved by its owner, and the resolution is noted.
- The record points to the approval rather than restating it.
- If anything differs from what was approved, the item goes back to the adviser instead of being closed.
Solo adviser or staffed office
If you are an owner-adviser who also runs operations, the gap to guard against is memory. You approved and submitted the request, and you assume you would remember if something went wrong. One option is a checklist template with a confirmation step you complete yourself, plus a look at the custodian's needs-action view on a schedule you set and keep.
With an operations or client-service lead, the gap to guard against is the handoff. Name one owner per request and agree who watches provider status and how often. Make “closed” mean the owner checked the source, not that the adviser stopped hearing about the request.
Synthetic example, not a customer result
A fictional two-person practice records an adviser-approved administrative request that goes to its custodian. The operations lead attaches the firm's checklist template to the client contact and adds a reference to the meeting note where the approval was recorded. Two days after submission, the custodian's status view flags the item as needing action and asks for more information. The lead records the exception and takes ownership of the next step. If the request would need to change, the lead checks with the adviser first, and the workflow stays open meanwhile. Once the provider's status shows the request complete, the lead records the confirmation reference and the date checked, then closes the workflow. No real client, account, request type or outcome is described here.
When to look beyond native tools
Consider extra tooling only if a specific gap stays visible after a few weeks of using the native steps. One example is staff re-keying status from several providers into the CRM by hand. Before calling that a gap, ask your administrator what your current plan and integrations already do, including any Send-To setup. Even then, the gap is a reason to examine the problem with your firm's approved tools and authorized owners. It is not proof that a new product is needed. Never copy real client, household or account records into an unapproved tool to test an idea.
A next step
Pick one provider-facing request type that comes up regularly in your practice. In your existing workflow template, add a “confirmation reference recorded” step just before the final step, and use it for the next few requests. If a specific gap remains afterwards, you are welcome to talk the process through with Abundance Applied. That conversation needs only a description of the steps, never client or account documents.
Sources
Product documentation checked 1 November 2026. Features depend on the current plan, permissions and setup.