Skip to main content
idapt
HomeCodeAI ModelsPricing
Sign inStart free
  • Home
  • Pricing
  • AI Models
  • Image models
  • Voice models
  • Video models
  • Rankings
  • New models
  • Model status
  • Multi-Model Chat
  • Voice Mode
  • Voice HUD
  • Web Search
  • Image Generation
  • Video Generation
  • Audio Generation
  • Transcription
  • Drive
  • Credentials
  • Sharing
  • Workspaces
  • Tasks
  • Memory
  • Agents
  • Subagents
  • Automations
  • Skills
  • idapt Code
  • Code Execution
  • Computers
  • Computer Use
  • Computer Assist · Soon
  • Containers
  • Cloud Computers
  • Local AI
  • AI Gateway
  • API & SDK
  • CLI
  • MCP
  • Tunnels
  • All features →
  • LLM cost calculator
  • Token counter
  • Context window checker
  • Can I run it
  • Model picker quiz
  • Savings finder
  • Video cost estimator
  • Text to speech cost
  • Transcription cost
  • API endpoint tester
  • All free tools →
  • Blog
  • Use cases
  • Comparisons
  • Best of
  • Skills
  • Learn
  • Changelog
  • Help center
  • FAQ
  • Privacy
  • Compare all models
  • Support
  • idapt Code
  • Developers
  • Quickstarts
  • API reference
  • API pricing
  • CLI
  • MCP
  • Downloads
  • Desktop
  • Badges and embeds
© idapt[email protected]TermsPrivacy PolicyLegal noticeReport content
X (Twitter)
All skills
Productivity

Build a privilege log

Every withheld document, described enough to defend and not enough to waive.

Fill it in

What is being reviewed.

Rather than deciding them silently.

Your prompt

Build a privilege log from .

Every entry needs enough for the other side to assess the claim and not enough to
waive it. Date, author, recipients, type, and a description of the SUBJECT rather
than the content: "email seeking legal advice regarding the supply agreement", not
what the advice was.

The common failures are both fatal. Too vague and the log is challenged and the
privilege can be lost; too detailed and it is waived by the log itself.

Watch for documents that are only partly privileged, and for anyone copied who
breaks it: a lawyer copied on a business email does not make it privileged, and a
third party copied on legal advice usually destroys it.

Flag the close calls for a human rather than deciding them.
Continue and pick your folderOpens with everything above already filled in.

Why this works

Too vague and the log is challenged and privilege can be lost; too detailed and it is waived by the log itself. This describes the subject rather than the content, and watches for the third party copied on legal advice, which usually destroys the claim.

More productivity skills

  • Document to slides
  • Meeting notes

Use it now in a chat in 1 click

Use Build a privilege log
Turn this into tasks
  • Weekly review
  • Decision brief
  • Build an investor deck