The Engagement Letter That Never Got Signed
An unsigned engagement letter is a liability sitting in your inbox. Here's how to close the gap between sending terms and getting them agreed — before the work starts.
You sent the engagement letter three weeks ago. The work is already underway — you started because the client was in a hurry, and you didn't want to be the bottleneck. Then the BAS gets lodged, the invoice goes out, and someone asks the awkward question: did they ever actually sign?
A quick search of your sent folder confirms the worst. The letter went out. It never came back. You've done the work, raised the fee, and you have no signed agreement covering any of it.
This is one of the quietest risks in an accounting practice. Not a missed deadline you can see coming, not an angry client — just a slow accumulation of work performed under terms nobody formally agreed to. When a dispute finally lands, the unsigned letter is exactly the document you wish you had.
Why the letter goes unsigned
It's rarely deliberate. The letter falls through the cracks for the same handful of reasons, over and over:
- It arrives as an attachment. A PDF in an email is easy to open, glance at, and forget. There's no clear action, no prompt, no consequence for ignoring it.
- Signing is friction. Print it, sign it, scan it, email it back. Every step is a place to give up. Most people don't own a printer any more.
- The work started anyway. Once you've begun, the letter feels like paperwork catching up with reality rather than the thing that authorises the reality. Both sides quietly deprioritise it.
- Nobody's job is to chase it. The person who sent the letter assumes it's handled. The client assumes silence means it's fine. There's no owner and no follow-up.
None of these are the client being difficult. They're design problems. And design problems get fixed with better design, not more willpower.
The letter is the start of the work, not a formality beside it
The most useful shift is to stop treating the engagement letter as admin that runs parallel to the job, and start treating it as the first step of the job itself. Nothing else begins until it's signed.
That sounds strict, and in busy season it's tempting to bend it. But the rule protects you in both directions. It protects the client, who knows exactly what they're paying for and what they're not. And it protects the practice, because every hour you record and every dollar you bill sits on top of an agreement someone actually consented to.
When signing is the gate to the work rather than a box to tick afterwards, the incentive flips. The client has a reason to sign — they want you to start. And you have a clean, dated record of scope and terms before a single timer runs.
Make signing take thirty seconds
The friction is the real enemy. If signing means printing and scanning, a meaningful share of your clients will never do it — not because they object, but because it's annoying. E-signing removes the excuse entirely.
A good engagement-letter flow inside your accounting practice management software looks like this:
- You generate the letter from a template, pre-filled with the client's details and the specific services for this engagement.
- The client receives a link — not an attachment — and signs from their phone in a couple of taps.
- The signed copy is stored against the client record automatically, with a timestamp and an audit trail of who signed and when.
- The work item that depends on it can't be started until the signature is captured.
Done this way, the whole cycle collapses from three weeks of back-and-forth to the same afternoon. There's nothing to print, nothing to scan, and nothing to lose in a sent folder.
Templates keep the terms consistent
Chasing signatures is only half the problem. The other half is what's in the letter to begin with. If every engagement letter is written from scratch, your terms drift — one client's letter caps out-of-scope work, another's doesn't mention it, a third has payment terms nobody remembers agreeing to.
Templating your letters by service type fixes that. A compliance-only client gets the compliance terms. A client on a bundled advisory arrangement gets the bundled scope. You edit the specifics, not the boilerplate, and the clauses that protect you are in every letter because they're baked into the template — not remembered on a good day.
Connect the letter to the client record and the work
An engagement letter isn't useful sitting in a folder on its own. Its value comes from being tied to everything else you know about the client. This is where treating it as part of your broader client accounting system matters more than the signing mechanism itself.
When the signed letter lives against the client record in your accounting client management software, the scope it defines is visible to whoever picks up the work. When someone asks whether a piece of extra work is covered, the answer is one click away rather than a memory test. And when you renew an engagement next year, you start from the last signed version instead of a blank page.
This connection is what separates real practice management from a shoebox of documents. The letter, the client, the recurring jobs, the invoice, the deadlines — they all reference the same record. Sign a letter, and the work it authorises is ready to move.
Finye handles this end to end: generate an engagement letter from a template, send it for e-signing, store the signed copy against the client, and gate the associated work items on it being signed. There's no separate signing tool to reconcile and no attachment to lose. The letter becomes the front of the job rather than an afterthought behind it.
The test to run this week
Pull a list of your active clients. For how many can you produce a signed, in-date engagement letter in under a minute? Not somewhere in an email — actually produce it.
If the honest answer is uncomfortable, you've found the gap. Every unsigned or missing letter is work you're doing on trust alone. The fix isn't more diligence at sending time. It's a system where the letter is the thing that starts the work, signing takes seconds, and the signed copy files itself against the client the moment it comes back.
Get that right and the question did they ever sign? stops being one you have to ask.