Building Your Document Collection Process
If you collect the same documents from clients every year — tax returns, onboarding packets, patient intake — you shouldn't be retyping that list each time. Build a template once and reuse it.
Here's how to structure templates that clients actually complete, how to pick the right field types, and how to get better at it over time.
Templates: build once, send forever
A template is just a saved list of items — names, descriptions, and settings. Create it once, then reuse it for every client who needs it.
What makes a good template
The difference between a template that works and one that generates "what is this?" emails: item descriptions. Your clients think in plain language — "the thing my employer sends in January," not "Form W-2." Meet them where they are and you'll get faster, more accurate responses.
Bare minimum:
- Name: "Form W-2"
- Description: (blank)
Much better:
- Name: "Wage statement from your employer (W-2)"
- Description: "Your employer mails this by January 31. Upload one per job. This is not a pay stub."
- Type: Document upload, allow multiple
- Required
Every question you answer in the description is a follow-up email you don't have to write.
Choosing the right field type
Not everything needs a file upload. Picking the right field type makes the request faster for your client and gives you cleaner data.
| Information you need | Recommended field type | Why |
|---|---|---|
| W-2, 1099, bank statement | Document upload | You need the actual document |
| W-2 for a client with multiple jobs | Document upload, allow multiple | One item, multiple files |
| Social Security Number | Text field | Faster than uploading a document; avoids storing an image of their SSN card |
| Filing status | Select field (dropdown) | Finite options — Single, MFJ, MFS, HoH, QSS |
| Mailing address | Text field | Structured data, no document needed |
| "Did you buy a home this year?" | Yes/No field | Triggers follow-up items in your workflow |
| List of dependents (names + DOBs) | Text field | Unless you need birth certificates as proof — then document upload |
| Business formation documents | Document upload, allow multiple | Articles of incorporation, operating agreement, EIN letter |
File upload or form field? Use a document upload when you need the actual source document — for your records, for the IRS, or because the information is too complex to type. Use a form field when you just need a piece of information — it's faster for clients and you get structured data instead of a scanned image you have to squint at. Gray area: if you need the info and a copy of the source document, use a document upload and say what you're looking for in the description.
Template structure
Lead with the easy stuff. When a client can upload their W-2 in the first 30 seconds, they build momentum and keep going. Save the harder items — business formation documents, lists of dependents — for later in the list.
Here's what a solid individual tax template looks like:
Income (lead with this — clients usually know where their W-2 is)
| Item | Type | Required | Multiple | Description |
|---|---|---|---|---|
| Wage statement (W-2) | Document | Yes | Yes | Your employer mails this by January 31. Upload one per job. |
| Freelance/contract income (1099-NEC) | Document | No | Yes | From any company that paid you $600+ as a contractor. |
| Other income (1099-MISC, 1099-K, etc.) | Document | No | Yes | Interest, dividends, payment apps, crypto — any 1099. |
Basic information (quick form fields — builds momentum)
| Item | Type | Required | Multiple | Description |
|---|---|---|---|---|
| Social Security Number | Text | Yes | — | We need this to file your return. |
| Filing status | Select | Yes | — | Single, Married filing jointly, MFS, Head of household. |
| Mailing address | Text | Yes | — | Current address as of December 31. |
Deductions (all optional — not every client itemizes)
| Item | Type | Required | Multiple | Description |
|---|---|---|---|---|
| Mortgage interest (1098) | Document | No | No | Your lender mails this by January 31. |
| Property tax statements | Document | No | Yes | Annual statement from your county assessor. |
| Charitable donations ($250+) | Document | No | Yes | Receipts or acknowledgment letters for donations over $250. |
Life changes (optional — helps you catch things the client might not mention)
| Item | Type | Required | Multiple | Description |
|---|---|---|---|---|
| Did you get married, divorced, or have a child? | Text | No | — | Brief description of any major life changes in the tax year. |
| Did you buy or sell a home? | Yes/No | No | — | We'll follow up for closing documents if yes. |
That's 12 items — comprehensive enough to cover most situations, short enough that clients will actually finish. If you're also handling a business return, split it into two requests rather than cramming everything into one. Shorter lists get completed faster.
Comprehensive or lean? A 20-item template catches everything upfront but can feel overwhelming. A 6-item template gets fast completion but means follow-up requests. Build two variants: a lean "new client" template with just the essentials (income docs, SSN, filing status), and a comprehensive "returning client" template for people who know the drill. First-timers do better with a shorter list — you can always send a follow-up for the rest.
Evolving your templates
Your templates will get better with use. Start with a system template or a basic custom one — you'll refine it quickly:
- Week 1: Send it to 5–10 clients. Note which items generate "what is this?" emails.
- Week 2: Fix the confusing descriptions. Cut items nobody fills in. Add items you keep requesting separately by email.
- Week 3: Clone the template for specific client types — self-employed, rental property owners, your state's specific forms.
After one season, your custom templates will be better than any pre-built option because they reflect how your clients actually respond.
Going faster with AI
Once your templates are built, the repetitive part is sending them — pick a template, fill in the recipient, set a due date, click send. Now do that fifty times.
If your document collection tool supports AI assistants (via MCP or API), you can skip the clicking. Tell the assistant who to send what to and it handles the rest. Status checks, batch sends, file downloads — all through conversation.
This works best for the operations you do dozens of times a season. The dashboard is still better for reviewing uploads and managing settings. For setup details, see AI Assistants.