Lesson objective

Design an intake automation that gathers facts and requests only the documents an engagement needs, while a named partner decides acceptance and scope.

Plain-language explanation

Why this matters now

Onboarding is where many firms first try orchestration, because it is repetitive and slow. A prospective client fills in a form, someone checks conflicts and independence, a partner decides whether to take the work, an engagement letter goes out, consents are collected, a portal is opened and a document request list is sent. Each step waits on the last, and much of the waiting is clerical.

An agent can do a lot of that clerical work well. It can read the intake form, look up the prospect in the firm's client list, assemble the facts a partner needs, prepare a draft request list and chase missing items. What it must not do is decide. Acceptance, scope and independence are professional judgments, and this module keeps them with a named partner.

This course's sources do not include the text of the AICPA or PCAOB acceptance and continuance requirements, so this lesson does not cite their paragraphs. Your firm's quality management system sets out its own acceptance and continuance procedures; the orchestration serves those procedures and does not replace them.

Two sources shape how much data an automated intake should gather.

  • Professional standard (AICPA Statement on Standards for Tax Services No. 1, section 1.3, Data Protection; binds AICPA members providing tax services, effective 1 January 2024): under 1.3.4 a member "should make reasonable efforts to safeguard taxpayer data, including data transmitted or stored electronically." The explanation in 1.3.9 says members should limit confidential taxpayer information in their files, for example by requesting only what is needed or asking clients to mask personal or health information they do not need. Under 1.3.1 the section "purposefully does not include bright-line rules".
  • Law / rule (FTC Safeguards Rule, 16 CFR Part 314; binds financial institutions under FTC jurisdiction, which expressly include tax preparation firms and accountants in the business of completing income tax returns): § 314.4(c) requires safeguards including access controls that limit users to the information needed for their duties, and a data and systems inventory. The rule's example is tied to completing income tax returns; an audit-only practice should not assume it is covered without that analysis.

An automated intake that asks every prospect for everything is the opposite of 1.3.9. It fills the firm's systems with data it never needed, all of which must then be protected, inventoried and eventually disposed of.

A question to sit with

If your intake form were answered by a prospect you later declined, how much of their sensitive information would the firm now hold, and why?

What goes wrong

The workflow decides acceptance by default. The agent moves a prospect to "engagement letter sent" when the form is complete and no conflict is found. Nobody decided to accept the client; the absence of a red flag did.

The request list is the whole checklist. The agent sends every item on a generic list to every client: prior returns, bank statements, identity documents, payroll records, health savings account forms. A client who only needs a business return uploads their family's medical statements.

Data arrives before the engagement exists. The portal opens at the first click, and a prospect uploads documents before a partner has accepted the work or any consent has been signed. The firm now holds data for a relationship that may never begin.

Scope drifts from the request list. The request list includes items for services nobody agreed to provide, and the client reasonably assumes they are included.

The chase becomes pressure. Automatic reminders every day to a prospect who has not yet signed anything read as the firm assuming the engagement.

The practical answer

Split the flow at the decision. Everything before the partner's decision is fact-gathering; everything after it is execution. The agent works on both sides, but the decision itself is a named person's act.

Stage Agent may Person decides or acts
Intake Read the form, look up the prospect, list related entities and owners None yet
Fact pack Assemble facts for conflicts, independence and scope, with sources Reviewer checks the pack is complete
Acceptance Nothing Partner accepts, declines or asks for more, recorded by name
Scope Draft the scope section from the partner's notes Partner sets services and exclusions
Engagement letter Place the firm's approved template and the partner's scope Partner or delegate releases it
Consents and notices Route the firm's approved forms (Lesson 2) Client signs; staff check validity
Portal and requests Open the portal and send the tailored request list Senior releases the first request

Tailor the request list to the scope. Build requests from the services the partner accepted, not from a master list. For each item, record the service that needs it. If no accepted service needs an item, it is not requested. Where a document holds data the engagement does not need, the request asks the client to mask it, which is the 1.3.9 approach.

Do not open the portal before acceptance. A prospect can give the facts a partner needs through a short form. Documents wait until the engagement exists. If a prospect sends documents early by email, the agent files them in a restricted holding area and a person decides whether to keep or securely return them.

Record the source of every fact. A fact pack is only useful if the partner can see where each fact came from: the client list, a public registry, the prospect's own answer. An AI summary of a prospect is not proof of anything. Anything the partner relies on is checked against its source.

Put the chase on a leash. Reminders go only after the engagement letter is signed, at a set interval, and stop after a set number, when a person takes over. Before signature, a person decides whether to follow up.

Inventory what intake collects. Each field on the intake form and each item on the request list goes in the firm's data inventory with its purpose and retention. Where the firm is covered by the Safeguards Rule, the inventory and access controls in § 314.4(c) apply to this data like any other customer information.

Remember this

  • The agent gathers facts and executes; the partner decides acceptance and scope, by name.
  • Build request lists from the accepted scope, and ask clients to mask what the work does not need (SSTS 1.3.9).
  • Do not open the portal or collect documents before acceptance.
  • Every fact in the pack shows its source; an AI summary is not proof.
  • Data gathered in intake belongs in the firm's inventory and access controls.

Accounting example

Fenwick Orly CPAs is a fictional firm of 30 people. Its operations manager, Tamsin Achebe, is asked to automate onboarding after the firm lost two prospects to slow responses. The first design from the practice platform vendor opens a portal on the first inquiry, sends a 42-item request list and generates an engagement letter as soon as the conflict search comes back clear. Tamsin maps it against the lesson. She moves acceptance into an explicit step: the agent builds a fact pack from the intake form and the firm's client list, marking where each fact came from, and places it in the queue of the partner who owns that service line. Nothing downstream starts until the partner records a decision. She rebuilds the request list from the scope. For a new client taking only a partnership return and bookkeeping clean-up, the list drops from 42 items to 11, and two of those ask the client to redact account numbers the firm does not need. The portal now opens only after the engagement letter is signed. When a prospect emails three years of personal returns before any decision, the agent files them in a restricted holding folder and alerts the operations manager, who asks the partner whether to keep them. The partner declines the work the next week, and the firm securely returns the files and records their disposal. Reminders now start after signature, go every four business days, and stop after three, when a staff member calls. Tamsin adds every intake field to the data inventory with its purpose.

Responsible-use warning

Do not let a workflow advance a prospect because nothing was flagged. A clear conflict search is a fact, not an acceptance. Every engagement needs a named partner's recorded decision before a letter, a consent form or a portal invitation goes out. Do not send a generic master request list either; each item must be needed by a service the partner accepted, or the firm ends up holding sensitive data it never needed and must still protect.

Human-review requirement

The partner responsible for the service line decides acceptance, scope and independence and records the decision by name. For attest work that is the engagement partner, a licensed CPA; for tax work, the partner who will own the returns and their signing preparer. A senior checks each tailored request list against the accepted scope before the first request goes out. The firm's information security lead confirms that intake data is in the inventory and under access controls.

Practical exercise

Use a fictional firm and a fictional prospect.

  1. Write a short intake form for a fictional prospect seeking a business return and monthly bookkeeping. List each field and why a partner needs it to decide.
  2. Draw the onboarding flow from inquiry to first document request, marking the acceptance step as a named person's act.
  3. For each stage, write what the agent may do and what a person decides or releases.
  4. Take a generic master request list of at least twenty items, real or invented, and cut it down to the items the accepted services need. Record the service each surviving item serves.
  5. Mark any item where the client should mask data the firm does not need, and write the masking instruction.
  6. Decide what happens when a prospect sends documents before acceptance, and who decides whether to keep them.
  7. Write the reminder rule: when reminders start, how often, how many, and who takes over.
  8. List where each intake field will be recorded in the firm's data inventory, with its purpose and retention.
  9. Write one sentence for the firm's onboarding policy stating that a clear conflict search is not an acceptance.
  10. Name the person who will review the flow after its first month and what evidence they will look at.

Knowledge check

  1. Which onboarding decisions stay with a named partner rather than the agent?

    Answer guidance: Acceptance of the client or engagement, the scope of services and exclusions, and independence. The agent gathers facts and executes the steps that follow a recorded decision.

  2. What does SSTS 1.3.9 suggest about the data a firm requests?

    Answer guidance: That members limit confidential taxpayer information in their files, for example by requesting only what is needed or asking clients to mask personal or health information that is not needed.

  3. Why should the portal not open before acceptance?

    Answer guidance: Because the prospect may upload sensitive documents for a relationship that never begins, leaving the firm holding data it must protect, inventory and dispose of with no engagement behind it.

  4. How should each item on a request list be justified?

    Answer guidance: By naming the accepted service that cannot be done without it. Items no accepted service needs are dropped, and data the work does not need is masked by the client.

Sources and further reading