Engagement letter for tax services template (and getting every client to sign it before you start)

Step 1: Write your engagement letter for tax services template

Structure the master document so every variable is a bracketed field, and everything else is fixed text your attorney has reviewed. Check it against AICPA guidance, your state board and your liability insurer before use. This is a starting point, not legal advice.

FIXED (attorney-reviewed, never edited per client):
  - Client responsibilities
  - Records and confidentiality
  - Ending the engagement
  - Signature and acceptance language

VARIABLE (per client, per year):
  [TAX YEAR]            - title and term section
  [CLIENT NAME]         - shortcode or merge field
  [SERVICES PROVIDED]   - scope paragraph (AI-drafted, partner-reviewed)
  [SERVICES EXCLUDED]   - exclusions paragraph (AI-drafted, partner-reviewed)
  [DOCUMENT DEADLINE]   - date for regular-deadline filing
  [FEE OR FEE BASIS]    - from your fee schedule, never AI-generated
  [OUT-OF-SCOPE RATE]   - from your fee schedule

Use the full eight-section letter from the everyday reading as the body. Keep the tax year in two places, so a stale letter is easy to spot.

Step 2: Save the template in TaxDome or Karbon

TaxDome: Templates > Firm templates > Proposals & ELs > Create template. The Terms page holds the engagement letter body and supports shortcodes for the account name and dates. The template's signature requirement setting decides whether one or all signatories must sign. A signature field is added automatically, and the signing date is stamped on completion. Templates can also be created from the Send proposal/EL pipeline automation.

Karbon: Engagements supports reusable proposal and engagement letter templates, bulk sending and digital signing. Confirm the menu path in Karbon's help center for your plan.

Fallback: a Word template with merge fields plus your existing e-signature tool. You lose the built-in status view, so track signatures in a shared sheet.

Step 3: Let AI tailor the scope paragraph

Constrain the model to the variable fields only. Inputs are last year's scope and a de-identified change list. Outputs are two bounded paragraphs plus an exceptions list.

Role: draft only the scope sections of a CPA firm's tax engagement letter.
Constraints:
- Edit only "Services we will provide" and "Services not included".
- Do not add or change legal terms, fees, guarantees or deadlines.
- Do not invent forms, entities, states or amounts. Use [MISSING] for gaps.
- Mark any ambiguous input with [CHECK].

Inputs:
PRIOR_SCOPE: [PASTE]
CHANGES: [e.g. rental property sold mid-year; new nonresident state filing]
EXCLUSIONS: [e.g. notice representation, bookkeeping]

Output format:
SERVICES_PROVIDED: <=80 words
SERVICES_EXCLUDED: <=60 words
EXCEPTIONS: bullet list of [CHECK] and [MISSING] items

No names, SSNs or account numbers go into the prompt. A partner clears every [CHECK] before the text enters the proposal.

Step 4: Send every engagement letter in one batch

TaxDome supports manual, bulk (select accounts, then Send proposal) and pipeline-automated sends. Pre-flight check: proposals can't go to linked contacts without portal login enabled, and clients without email need in-person signing through TaxDome Kiosk. Run the check on your account list before the batch. In Karbon, use the bulk send in Engagements.

Step 5: Get clients to sign engagement letters with two scheduled reminders

Use a fixed schedule with a human escalation, not an open-ended loop. Draft the copy once with AI, then store it as templates.

Generate two reminder emails for an unsigned tax engagement letter.
R1 (day 5): <=70 words, friendly, explains work starts after signing.
R2 (day 12): <=70 words, notes work is started in order of signed letters,
offers help with access.
Placeholders only: [CLIENT FIRST NAME], [SIGNING INSTRUCTIONS], [FIRM NAME].
No legal language, no penalties, no urgency claims.

After R2, the record moves to a named team member's task list.

How the signing flow runs each season

Day 0: bulk send to all returning clients after fees are set. Day 5: R1 to unsigned only. Day 12: R2 to unsigned only. Day 14+: human follow-up; preparation stays blocked until status is Signed.

Example (illustrative): a three-office tax practice on TaxDome

This is a walkthrough, not a real client. The firm split its Word letter into fixed terms and variable fields, then saved it as a TaxDome proposal template with the Terms page holding the body. Scope deltas came from the constrained prompt and were cleared by a partner. A mid-January bulk send went out from the Accounts list, after a portal-login check. R1 and R2 were stored as templates, and anything unsigned after day 12 became a preparer task.

At a glance:

• Problem: late sends and no signature tracking.
• What was built: a field-split template, a scope prompt, a reminder schedule.
• Tools it lives in: TaxDome, Word, an approved AI chat tool.
• What the owner still does: clears scope changes and enforces the work gate.
• Payoff: not measured here.

Mistakes to avoid

• Letting the model touch fixed terms. Restrict it to scope fields, and diff the output against the master.
• Generating fees with AI. Fees come from your schedule only.
• Skipping the portal-login pre-flight. Unsendable proposals fail quietly from the client's side.
• Putting identifiers in prompts. De-identify and use firm-approved tools.
• Unbounded reminder loops. Two automated touches, then a person.

If it still doesn't work

Triage unsigned letters by cause: delivery (spam or wrong address), access (portal login off), or dispute (fee or scope). Delivery and access are fixed by checking the contact record and resending. A dispute is escalated to the partner and taken out of the reminder schedule. Clients who won't e-sign go to in-person signing or paper.

Doing this inside the tools you already use

Deeplathe is a team of developers and solution builders who build custom AI inside the tools a business already uses. For this job, a custom build could read each client's prior-year scope and this year's change notes, draft the scope fields, and queue the proposal in TaxDome or Karbon with exceptions flagged for a partner. A daily list of unsigned letters, each with its reminder drafted, could land with the right preparer. Nothing is sent and no scope changes without your approval, and the fixed terms are never edited. See how a custom build works.

FAQ

What should a tax engagement letter include?

Typically: services provided, exclusions, client responsibilities, deadlines, fees, records and confidentiality, termination and the tax year covered. Treat these as fixed versus variable fields. The fixed language should come from your attorney and be checked against AICPA guidance, your state board and your insurer.

Do I need a new engagement letter every year?

Many firms issue one per tax year, so scope, fees and deadlines are current and signed. Your insurer or attorney may set the policy. Put the tax year in the title and term section, so the active letter is unambiguous in the client record.

How do I get clients to sign engagement letters?

Send early in bulk, make signing a portal click, and run two scheduled reminders followed by a human contact. Gate preparation on signed status. Check portal access before sending, because missing logins block delivery.

Can AI write my engagement letter?

Use AI for the variable fields only, with a constrained prompt and [CHECK]/[MISSING] markers. Keep fixed terms attorney-owned and unedited, and have a partner review every scope change before it goes into the proposal.

Keep these

• Fixed terms are attorney-owned; AI touches variable fields only.
• Bulk-send at season start after a portal-login check.
• Two reminders, then a person.
• Signed status gates the work.

Sources

• TaxDome Help Center: Create and apply proposal templates
• TaxDome Help Center: Send proposals
• TaxDome Help Center: Proposal field reference
• Karbon: Engagements for accounting firms
• IRS Publication 4557: Safeguarding Taxpayer Data

Related reading

• Part of The process that only lives in your head
• Remind clients to send their tax documents
• Estate planning questionnaire template
• How small accounting and bookkeeping firms can use AI
• Ask AI about a contract before you sign it
• Is customer data safe with AI tools?