A Signed Consent Undercut a Family Trust's Privilege Claim

The situation

The trust ran quietly. It held a small rental property near Kincardine and a modest investment account, and its three co-trustees, Darius, Arman and Radu, split the paperwork the way families do: whoever had time that month dealt with the accountant, filed the return, and answered the odd letter. Darius worked as a court clerk, so he understood forms and deadlines better than most, and Arman, a municipal planner, brought the same instinct for process to the trust's books. Radu handled the day-to-day contact with their long-time accountant. None of them thought of themselves as running anything complicated, and for years the trust had never drawn more attention than a routine annual filing.

The plan, once the trust learned it had been selected for an on-site review, was straightforward. They would let the auditor see the rental ledgers, the bank statements, the investment slips, everything routine. They would keep separate the file of legal correspondence the trust had exchanged with counsel over a property dispute two years earlier, because that correspondence was privileged and had nothing to do with the years under review. Darius drafted a short cover note explaining the carve-out and expected the auditor to accept it the way auditors usually do, since the trust had nothing to hide about the numbers themselves and simply wanted to keep a separate, unrelated legal matter out of the file.

What none of the three fully grasped was that months before the audit was announced, at what felt like a routine intake meeting, Radu had signed a document access consent the auditor's office had sent ahead of the file review. It was framed as confirming dates and a document list. Radu read it quickly, saw nothing alarming, and signed it on the trust's behalf without asking Darius or Arman to look at it first. It seemed, at the time, like exactly the kind of administrative step that came with any government correspondence, no different from confirming a mailing address.

By the time the trust called our office, the on-site visit was three weeks away and Darius was confident the carve-out plan simply needed to be formalized in writing. He wanted us to draft the letter. It was only once we asked to see everything the trust had already sent or signed, every email, every form, every acknowledgment, that the shape of the actual problem became clear, and it was not the problem Darius had called about.

Where it went wrong

The consent Radu had signed listed, in general terms, the categories of documents the auditor expected to review on-site. One category was described broadly enough to sweep in correspondence files connected to the property the trust owned, including files the trust considered privileged. Radu had no way of knowing that at the time; the language was administrative, not legal, and nothing in the covering email flagged it as a decision that mattered. The form did not use the word privilege anywhere, and there was no reason for someone reading it quickly to think a signature there could touch a legal file from an entirely separate matter.

Once a taxpayer consents to a category of documents being made available, withdrawing that consent later is not simply a matter of changing your mind. The auditor is entitled to treat a signed consent as exactly what it says, and an attempt to narrow it after the fact looks, from the other side of the table, like a taxpayer trying to hide something it had already agreed to show. That is not a fair reading of what happened here, but it is the reading the file supported on its face, and the trust had to plan around that reading rather than around what actually happened.

The deeper issue was that privilege over legal advice is not lost just because a document sits in the same filing cabinet as ordinary business records, and it is not lost simply because someone signed an administrative form that never used the word privilege at all. But privilege also has to be actively identified and protected document by document, generally before anything is produced, not after, and a blanket claim over an entire file rather than over specific identified records tends to be treated with real skepticism. The earlier consent had not signed away the trust's right to protect genuinely privileged correspondence, but it had removed the easier path of simply keeping the whole file back, and the trust now had to show which specific documents within the broad category were actually privileged rather than asserting the file was off-limits as a whole. That distinction, between asserting privilege over a category and asserting it over specific identified documents, turned out to matter enormously to how the rest of the file would go.

That is a harder and slower argument to win than the one the trust thought it was making. Darius's instinct, that a clear cover letter on the day of the visit would settle the question, would not have worked. The signed consent was already on file, and the auditor's office was under no obligation to treat a late objection as though the earlier agreement had never happened. The trust's actual position, once we reviewed it, was weaker than any of the three trustees understood, and it stayed that way for the rest of the file. Arman, when we explained it, asked the obvious question: could Radu simply have not signed it. The honest answer was that nothing about the form suggested there was a decision being made at all.

What we did

1. Pulled every document the trust had signed or sent before we were retained, because the consent Radu signed was not mentioned when Darius first called and none of the trustees thought to raise it. We only found it by asking for the full correspondence chain with the auditor's office directly, comparing dates against the trustees' own recollection of events, and it changed the entire strategy once we had it in hand.
2. Assessed what was actually still protectable within the broad category Radu had agreed to, sorting the property correspondence file document by document into what was genuinely legal advice and what was administrative and had never been privileged in the first place. A letter analyzing the trust's options in the property dispute counted; a cover email simply forwarding an invoice to the same lawyer did not, even though both sat in the identical folder, so we were not asserting a claim broader than the facts could support once challenged.
3. Contacted the auditor's office before the on-site date to explain, in writing, that a narrower privilege claim was being made over specific identified documents rather than the whole file, and asked for the review to proceed on that agreed footing so nothing would be contested for the first time in front of the trustees on the day itself, with the auditor learning the trust's position secondhand.
4. Prepared a privilege log listing each withheld document by date, the parties involved, and the general nature of the advice it contained, without disclosing the content itself, which is the accepted way to assert the claim over identified documents without giving away the substance of what is actually being protected from disclosure, and without inviting a fight over documents that were never genuinely at risk.
5. Attended the on-site review alongside the trustees so that any question about the scope of access could be answered in real time by someone who understood both the earlier consent and the current negotiated position, rather than leaving Darius or Arman to interpret an unfamiliar dispute on the spot under time pressure, with the auditor present and the clock running.
6. Negotiated over which documents in the disputed category would be produced and which would be logged as withheld, accepting that some administrative-looking correspondence would have to go forward because it did not meet the threshold for genuine privilege, even though the trust had originally hoped to keep the entire file back from the review altogether and had to accept that some ground, once conceded through the earlier signature, was not coming back.
7. Documented the outcome of the on-site review in writing immediately afterward, recording exactly what had been produced, what had been withheld, and the stated basis for each, so there would be a clear contemporaneous record if the privilege question over any specific document resurfaced later in the audit or in any subsequent dispute over the same file years down the road.
8. Set up a standing internal protocol for the trust going forward, requiring that any document consent, access request, or similar form from a tax authority be reviewed by our office before any trustee signs it, so the trust would never again find itself bound by a form none of the three had read closely enough to understand what it actually gave away.

The outcome

The on-site review went ahead on a narrower footing than the trust originally hoped for. Several documents in the disputed correspondence file were produced because the earlier consent had already brought them within scope and they did not meet the bar for genuine legal-advice privilege. A smaller set, the ones that were clearly communications with counsel about the property dispute, were withheld and logged, and the auditor's office accepted that log without pushing further or demanding to see the underlying content.

The dispute amount at issue in the broader audit sat in the roughly fifty to one hundred and fifty thousand dollar range, and the outcome of the privilege question did not resolve that figure on its own; it affected which records the auditor could rely on in reaching a final position. Losing access to the withheld documents cost the auditor's office some context, which worked in the trust's favour on a few line items later in the audit, but it did not undo the ground already lost through Radu's earlier signature, and the trust never got back the ability to treat the whole correspondence file as untouched.

For the trust, the real result was containment rather than victory. The damage from the signed consent could not be reversed, only limited, and the three trustees left the process with a plainer understanding of what a routine-looking form can actually commit them to. Darius, in particular, said afterward that he wished someone had told him a signature on an intake document could carry that much weight before Radu ever picked up the pen, and the trust now treats every form from the auditor's office, no matter how small, the same way it treats a contract. That change alone, Arman noted, was worth more to the trust going forward than the specific documents it lost this time around.

What you can learn from this