Delegation requires disclosure. If you need administrative help with estate documentation, banking correspondence, or regulatory filings, someone else must see your information. The question is: how much must they see? Most people default to full disclosure. Send the entire bank statement. Share the complete tax return. Forward the whole email thread. It feels simpler than selective editing.
But full disclosure is not simple. It is a privacy surface that grows with every shared document and persists longer than most people expect. The alternative is redaction-first: systematic minimisation of what gets disclosed, calibrated to what the recipient actually needs for the task at hand.
This is not paranoia. It is operational discipline.
The problem with 'just trust them'
Trust is not a privacy control. Trustworthy people can still expose data through ordinary operational failure: insecure storage, weak authentication, uncontrolled forwarding, or retention beyond need. None of these requires malice. Delegation chains extend: you share a document with your assistant, who shares it with a bookkeeper, whose office stores it in a shared folder. Three people now have access who were not in the original trust assessment. And retention outlasts need: a task that required access for two weeks can leave documents in someone's email archive for years.
What minimisation actually looks like
Redaction-first does not mean 'never share anything.' It means share the minimum necessary for the task. If someone is scheduling a property viewing, they need the address. They do not need the purchase price, the mortgage details, or the ownership structure. If someone is reconciling expenses, they need the transaction descriptions and amounts. They do not need the account numbers, the balance, or unrelated transactions from other accounts. Most documents can be reduced by 60-80% without affecting task completion.
The annotation risk
A subtle problem: annotations and metadata. Most people redact visible content. Fewer redact metadata: document properties, edit history, comment threads, email headers. A redacted PDF may still contain the original unredacted text in its metadata. Effective redaction requires flattening: converting documents to a clean final form without embedded history. For PDFs: print to PDF. For spreadsheets: copy visible cells to a new file. For emails: rewrite the relevant content in a fresh message. Tedious. Also necessary.
Pointer preservation
A specific technique: preserve pointers, redact targets. If a document references 'Account A at Bank B,' the reference can remain. The account number, balance, and transaction history can be redacted. The recipient knows the account exists and what role it plays, without seeing details unnecessary for their task. Pointers let you share the map without sharing the territory.