Medium impactAdvancedWorkflow

Turn a tax question into a cited research memo you can trust

Take a fact pattern to a Facts, Issues, Law, Analysis, Conclusion memo grounded in retrieved primary authority, with every citation checked.

Instead of a senior spending an afternoon keyword-searching a research database and then drafting a memo from scratch, the firm captures the facts in a structured questionnaire, has a model frame the issues and build a research plan, retrieves primary authorities from a licensed database or official sources, and drafts a memo with a stated confidence level. A separate verification step checks every citation and quotation against the retrieved text and strips or flags anything that doesn't match. The reviewer still owns the conclusion.

Time
Saves hours
About 6 hr down to 2.5 hr per memo
Who does it today
Senior associates, managers, or partners with research database access
Practice area
Research

Illustrative planning estimate, not a measured result. Assumes a single-issue or two-issue federal question (for example, whether a payment is deductible under §162 or capitalized under §263(a), or whether a transaction qualifies under §1031) and a reviewer with subject-matter experience. Traditional time covers fact-gathering, database searching, reading authorities, and drafting. AI time includes the reviewer reading every cited authority the memo relies on, which is non-negotiable. Novel or multi-jurisdictional questions save less.

Traditional vs AI-native

Traditional

  1. 1Facts by phone or email
  2. 2Keyword searches
  3. 3Chase citations
  4. 4Draft from a blank page
  5. 5Imply a confidence level
  6. 6Partner review

AI-native

  1. 1Structured facts, frozen
  2. 2AI frames issues and a plan
  3. 3Primary authority retrieved
  4. 4AI drafts with a stated confidence
  5. 5Code verifies every citation
  6. 6You read the authorities and sign

Where you sit

You own the conclusion. You approve the issues, read every authority the answer depends on, check that it says what the memo claims, and set the final confidence level.

The traditional way

  1. Take the facts in a phone call or email thread, often incomplete and scattered.
  2. Frame the issue mentally and start keyword searches in the firm's research database.
  3. Read explanations, then chase their citations to the Code, regulations, rulings, and cases.
  4. Copy relevant passages into a document and draft the facts, issues, law, analysis, and conclusion.
  5. Decide how strong the position is (substantial authority, reasonable basis, and so on), often without saying so explicitly.
  6. Partner review; citations are rarely re-checked line by line.

Where it hurts

  • Research quality depends heavily on who happened to do it and how much time they had.
  • Facts are gathered too late, so the analysis rests on assumptions nobody wrote down.
  • Confidence levels are implied rather than stated against the §6662/§6694 standards.
  • Memo drafting eats the time that should go to thinking about the answer.

The AI-native way

  1. 1AI

    Structured facts intake

    A questionnaire tailored to the issue area (entity type, dates, amounts, ownership, prior filings, documents) is sent to the client or engagement lead. The model reviews the answers, lists missing or contradictory facts, and drafts follow-up questions. The final fact set is frozen as a numbered list, so the memo's assumptions are written down and can be tested against Circular 230 §10.37(a)(2), which requires reasonable factual and legal assumptions.

    Tools: Form builder or portal questionnaire · Enterprise LLM

  2. 2AI

    Draft issue statements and a research plan

    The model writes each issue as a precise question tied to specific facts ('Whether the $84,000 roof replacement on Building B is a deductible repair under Treas. Reg. §1.162-4 or a capitalizable improvement under Treas. Reg. §1.263(a)-3'), and produces a plan: Code sections, regulation parts, and the likely ruling and case law areas to check. A reviewer approves or edits the issues before research begins.

    Tools: Enterprise LLM

  3. 3Automation

    Retrieve primary authorities

    A retrieval step pulls full text from your licensed research database (through whatever export or integration your license allows) and from official sources: the Code, current Treasury regulations from eCFR, Internal Revenue Bulletins on IRS.gov for rulings, procedures, and notices, and court opinions from the Tax Court and federal courts. Each document is stored with its citation, source URL, and retrieval date, and is split into chunks for search. The model can only cite what's in this retrieved set.

    Tools: Your licensed research database · eCFR · IRS.gov IRB · U.S. Tax Court opinions search · Vector index

  4. 4AI

    Read the authorities and extract holdings

    For each retrieved authority, the model extracts the rule, the key facts, the holding or operative language (as exact quotations with pinpoint location), and how it bears on each issue, including adverse authority. Authorities are tagged by type and weight, following the Treas. Reg. §1.6662-4(d)(3)(iii) list of what counts as authority, so the analysis doesn't lean on secondary sources.

    Tools: Enterprise LLM with long context · Authority extraction schema

  5. 5AI

    Draft the memo with a stated confidence level

    The memo follows a Facts / Issues / Law / Analysis / Conclusion structure. The analysis applies each authority to the frozen facts, addresses contrary authority, and ends with an explicit confidence level tied to recognized standards: 'more likely than not', 'substantial authority' (relevant to §6662 understatement penalties and §6694 preparer penalties for undisclosed positions), or 'reasonable basis' (generally enough only with adequate disclosure, such as Form 8275). It states which facts, if different, would change the conclusion.

    Tools: Enterprise LLM · Firm memo template

  6. 6Automation

    Independent citation and quotation verification

    A separate step, deterministic code backed by a second retrieval pass, parses every citation in the draft and confirms it matches a document in the retrieved set or can be fetched from an official or licensed source. Every quoted passage must appear verbatim (after whitespace normalization) in that source. Unverified citations are removed or highlighted in red with a reason, and the memo can't be marked final while any remain. This step exists because AI-generated citations can look real but be fabricated. In Mata v. Avianca (S.D.N.Y. 2023), the court sanctioned two lawyers and their firm for a filing that cited nonexistent cases generated by ChatGPT.

    Tools: Citation parser (regex for IRC, Treas. Reg., Rev. Rul., Rev. Proc., T.C., F.3d, etc.) · Exact-match text search · Verification report

  7. 7You

    Reviewer owns the conclusion

    A credentialed reviewer reads the verification report, opens every authority the conclusion depends on, checks that the characterization is fair (not just that the quote exists), confirms the facts and assumptions, and adjusts the confidence level if warranted. They sign the memo as the firm's advice. Their edits are saved as examples to improve future prompts.

  8. 8Automation

    File, tag, and reuse

    The final memo, its frozen fact set, the verification report, and the retrieved authority set are stored together in the client file and in a firm knowledge base tagged by issue and Code section. Future research on the same issue starts from prior memos, with a check for later authority since the prior memo's date.

    Tools: DMS / SharePoint · Knowledge base index

What you need

  • A structured facts questionnaire for the issue area
  • Access to primary authority (a licensed database where the license allows, plus eCFR and IRS.gov)
  • A citation checker that runs separately from the drafting step
  • A credentialed reviewer with subject-matter experience

The stack

Facts intake

Portal or form-builder questionnaires by issue area (Microsoft Forms, Typeform, or practice management forms)

Authority sources

Your licensed research database (e.g., Checkpoint, CCH AnswerConnect, Bloomberg Tax) where the license permits, plus eCFR, IRS.gov IRB, and court opinion sites

Retrieval

Vector index plus keyword search over the retrieved authority set (Azure AI Search, Elasticsearch/OpenSearch, pgvector)

Reasoning & drafting

Enterprise LLM with long context (ChatGPT Enterprise, Claude for Work, Azure OpenAI) under no-training terms

Verification

Custom citation parser and exact-match quote checker in Python, run as a separate step from drafting

Knowledge base

Firm DMS or SharePoint with issue and Code-section tagging

Named tools are examples, not endorsements. Check any tool against your own data rules first.

Copy the prompt

Grounded research memo drafting prompt

You are a senior federal tax researcher drafting an internal research memo for review by a CPA or tax attorney. You will receive:
1. FACTS: a numbered list of frozen facts. Treat them as the only facts.
2. ISSUES: the approved issue statements.
3. AUTHORITIES: JSON list of retrieved primary authorities, each with an id, a full citation, the authority type (statute, regulation, revenue ruling, revenue procedure, notice, court opinion), a date, and full text or extracted passages with pinpoint locations.

Draft a memo with these sections: Facts, Issues, Law, Analysis, Conclusion.

Rules for authority and citations:
- Cite only authorities in AUTHORITIES, by their exact citation string, with the authority id in brackets after each citation, for example [A7].
- Quote only text that appears verbatim in AUTHORITIES, and add the pinpoint location. If you paraphrase, don't use quotation marks.
- Never cite an authority from memory. If the analysis needs an authority that isn't provided, write "AUTHORITY NEEDED:" followed by what should be researched.
- Address adverse authority in AUTHORITIES explicitly. Don't omit it.
- Don't rely on secondary sources as authority.

Rules for analysis:
- Apply the law to the numbered facts, referring to facts by number (F3, F7).
- List every assumption you had to make beyond FACTS.
- Don't base any conclusion on the likelihood that the return will or won't be examined.

Conclusion:
- For each issue, state one confidence level: "should", "more likely than not", "substantial authority", "reasonable basis", or "not supportable". Explain in two to three sentences why it clears that standard and not a higher one.
- State which facts, if different, would change the conclusion.

Output JSON:
{ memo_markdown: "", citations: [{ citation, authority_id, quoted_text_or_null, pinpoint }],
  assumptions: [], authority_needed: [], confidence_by_issue: [{ issue, level, reason }] }

Example

Fictional data.

Frozen facts and issue (abridged)

Client: Halloway Properties LLC (partnership), calendar-year taxpayer
F1 Owns a 14-unit residential rental building placed in service in 2011.
F2 In 2025 replaced the entire roof (decking, insulation, and membrane): $84,000.
F3 Roof replaced with comparable materials; no change in building footprint or use.
F4 Building's unadjusted basis: $1.9M; no prior roof replacement.
ISSUE: Is the $84,000 a deductible repair or a capitalizable improvement
  under the tangible property regulations?
AUTHORITIES: 11 retrieved (Code §§162, 263(a); Treas. Reg. §§1.162-4,
  1.263(a)-3; related IRS guidance and cases)

Draft memo and verification report (abridged)

Conclusion: Capitalize as an improvement (restoration). Confidence: should.
  Replacing the entire roof is generally treated as replacing a major
  component of the building structure under Treas. Reg. §1.263(a)-3(k) [A4].
  Alternative repair treatment: not supportable on F2–F3.
  Would change if: only the membrane was replaced, or only a small section of the roof (F2).
Assumptions: roof is part of the building structure unit of property; the
  building doesn't qualify for the small taxpayer safe harbor (F4 basis exceeds the limit).
Verification report: 14 citations · 13 verified · 1 flagged
  FLAGGED: case citation [A9] not found at the cited reporter page. Removed.
  6 quotations · 6 verbatim matches
Status: blocked from final until reviewer clears flagged item

Guardrails

  • Circular 230 §10.37 requires written advice to rest on reasonable factual and legal assumptions, consider all relevant facts, relate the law to the facts, and not take audit likelihood into account. The frozen fact set and explicit assumptions list exist to meet that standard.
  • No citation reaches a client unless the verifier confirms it exists and every quotation is verbatim, and the reviewer has read the authorities the conclusion depends on. Existence doesn't prove the authority says what the memo claims.
  • Stated confidence levels must match the §6662 and §6694 standards as applied by the reviewer. The model's suggested level is a starting point, not a conclusion, and positions below substantial authority need a disclosure discussion.
  • Use research database content only as your license permits. Some licenses restrict bulk export or use with external AI tools, so check before building the retrieval step.
  • Client facts go only to an enterprise AI tier with no training on inputs and minimal retention. Where the facts identify a taxpayer, apply the same IRC §7216 and WISP controls as for return data.

What can go wrong

Fabricated or mis-cited authority (wrong reporter page, a ruling number that doesn't exist).

Model output can only reference ids from the retrieved set, and the independent verifier fetches and matches every citation. Unverified items are removed or block finalization.

A real authority is quoted accurately but mischaracterized, or taken out of context.

Extracted holdings include surrounding context, and the reviewer checklist requires reading every authority relied on for the conclusion.

Stale law: an amended regulation, a superseded revenue procedure, or a reversed case.

Retrieve current regulation text from eCFR with the retrieval date recorded. Use the licensed database's citator or history features where available, and require a 'later authority' check on reused memos.

Garbage-in facts produce a confident but wrong memo.

The intake step lists gaps and contradictions, the memo states assumptions and 'facts that would change the answer', and the engagement lead confirms the frozen facts.

How to prove it worked

Citation verification pass rate on first draft

Share of citations and quotations verified automatically, from the verification report across all memos.

≥ 95% on first draft; 100% before release

Unverified citations reaching a client

Audit a sample of issued memos each quarter and re-check every citation manually.

Zero

Hours per research memo

Time-track 15 comparable memos before and after rollout.

Down 40–60%

Reviewer changes to the conclusion or confidence level

Compare draft and final confidence levels in the saved versions.

Tracked and trending down; never zero review

Where this goes

Research becomes a firm asset instead of a personal skill. Every memo is grounded in retrieved, verified primary authority and stored with its fact set and confidence level, so the firm builds a searchable body of positions that can be re-verified against new authority automatically. Small firms can offer documented, penalty-protection-grade position support that used to require a national tax department.

Demo

Demo video coming soon

Until then, the steps and the example above are the walkthrough.

References

  • Treasury Department Circular No. 230, §10.37 (requirements for written advice)
  • IRC §6662 and Treas. Reg. §1.6662-4(d) (substantial authority standard and types of authority)
  • IRC §6694 and Treas. Reg. §1.6694-2 (preparer penalty for unreasonable positions)
  • IRS Form 8275, Disclosure Statement
  • Mata v. Avianca, Inc., 678 F. Supp. 3d 443 (S.D.N.Y. June 22, 2023) (sanctions for filing AI-fabricated case citations)

Summaries for orientation. Verify against the current standard before relying on any of them.

Want to implement this in your firm?

Bring it to the weekly call. Members work through builds like this one together, with accountants who are already doing it.

Keep browsing