Build Your Practice Context Document

Every time you start an AI chat cold, you re-explain your services, your client mix, your software, and how you review. That is wasted time and the draft still comes back generic. A Context Document is a single page you paste at the top of every chat so AI shows up already knowing your practice. Build it once with the Practice Context Document tool, then reuse it on every client.

This track serves a mixed firm, and each role needs something different from AI.

• Staff accountants want speed: less manual entry, help drafting client communications, research starting points instead of escalations. Their quiet worry is "will AI replace my job?" The honest answer is no, but the job changes. Staff who learn to work with AI take on harder work sooner.
• Managers want better first drafts and faster research turnaround, plus a systematic way to evaluate AI output rather than blindly accept it. Their question is "how do I trust this enough to sign off?"
• Partners want firm-level capacity and a handle on the liability. Their questions are "what is the exposure?" and "how do I know staff are not putting client data into public tools?"

This is the rule that holds for every module and every tool in this track. Keep client identifiers out: no names, SSNs, EINs, account numbers, or specific taxpayer data. Describe the situation in patterns instead: "an Ohio S-corp, cash basis, construction, calendar year." Putting client tax data into a public AI tool risks IRC 7216 and your clients' trust. Use role labels like "the Client," "Vendor A," and "the Owner."

• Jurisdiction: federal, state (which), local if it applies.
• Entity type: 1040, 1120S, 1120, 1065, 990, 1041.
• Tax year: always. Tax law changes every year.
• Standards: IRC, Treasury Regulations, AICPA, Circular 230.

AI does not know your jurisdiction, entity type, or tax year unless you tell it, and getting any of them wrong changes the answer.

• Claude. Save it as a Project so every chat starts with your context.
• Gemini. Save it as a Gem, or paste it at the top of any conversation.
• NotebookLM. Upload it as a source and reference it in every prompt.

Update it when something real changes, a new service line, a new software, a new client type. Otherwise leave it alone.