One Client, Twelve Entities: A Tax Engagement Letter Runbook

Start every renewal cycle by pulling the prior year's engagement letter for each entity, not a blank template. Compare what the letter says against what the firm actually billed for that entity last year. A letter that scoped compliance only, next to an invoice that includes nexus analysis and estimated payment planning, is the exact gap that matters: work performed outside the signed scope, with no letter covering it if a position gets challenged.

This comparison takes longer the first season a firm does it properly, since most practices have some backlog of scope drift built up across several prior years. Once it's done once and the letters are brought current, each following season is mostly confirming that nothing new has drifted, which is a much smaller task.

Not every entity in a twelve-entity group needs the same letter. Some are dormant holding companies with minimal activity; others triggered new state filing obligations this year, or added a service the firm didn't provide last time. Sorting entities into a short list, no change, minor scope addition, new nexus or service line, before drafting anything determines how much customization each letter actually needs, rather than treating all twelve as one batch that gets the same boilerplate.

This is where PandaDoc earns its place for a firm at this volume. A base engagement letter template, with entity name, scope, and fee as merge fields, can generate and send all twelve letters from one client record in a single pass, with a shared dashboard showing which have come back signed and which are still outstanding. For a firm managing dozens of multi-entity clients through busy season, that batch view is what keeps a single unsigned letter for one subsidiary from getting lost among the eleven that came back the same week.

Once the batch comes back, the harder check is whether any signed letter's stated scope still doesn't match what the firm is actually planning to bill. This is where Ironclad's repository search helps a firm running many multi-entity clients at once: pulling every signed letter across a client group and checking scope language against the engagement plan in one pass, rather than opening each PDF individually, catches a mismatch before the invoice goes out rather than after a client questions it.

When a mismatch turns up, the fix is a scope amendment to the engagement letter, not a quiet adjustment to the invoice. An invoice that bills for planning work under a letter that only scoped compliance is billing outside the engagement, which is the exact exposure a signed letter exists to prevent. A short addendum, generated the same way as the original letter, closes that gap properly and takes a fraction of the time a full new letter would.

It's worth sending that addendum before the invoice goes out, not alongside it. A client who receives a scope amendment and an invoice for the newly scoped work in the same email is more likely to read the amendment as a formality; a client asked to sign the amendment first, separately, is actually confirming they understand what changed and why.

The goal isn't twelve perfectly worded letters; it's twelve letters that actually describe what the firm is doing for each entity, kept current as scope shifts through the year rather than reset once annually. Firms issuing a high volume of engagement letters each season, batch, track, and reconcile against billed work, tend to catch scope drift before it becomes a dispute. New client relationships in this kind of advisory work typically take a real stretch of the sales cycle to close, on the order of three months¹, so the volume that actually needs this runbook each season is usually renewals and expansions, not entirely new clients, which is exactly the group where scope creep is most likely to have gone unnoticed.

Run each renewal season in this order:

1. Pull last year's engagement letter for each entity and compare its scope with what the firm actually billed that entity.
2. Sort entities into no change, minor scope addition, or new nexus or service line before drafting anything.
3. Generate the letters in one batch from a merge-field template and watch the dashboard for any that are still outstanding.
4. Check each signed letter's scope against the engagement plan, searching across the whole client group in one pass if you can.
5. Fix any mismatch with a scope addendum to the letter, not a quiet adjustment to the invoice.