Regulatory Development Briefing: A Four-Prompt Chain in Claude

What This Builds

A repeatable way to turn a new regulatory development into a half-page internal briefing for your executives. You paste the official text and Claude summarizes it. You check the summary. Claude then applies it to a short profile of your company, and you correct its assumptions. Next Claude drafts the questions the business owner has to answer, and finally it drafts the briefing. You stop after every prompt, so the work stays yours and the conversation stays honest.

The chain never supplies the law. You bring the source text from the official site. Claude only reads what you paste.

Prerequisites

• A Pro plan ($20/month), or the Claude plan your company has approved for confidential and privileged work
• The official text of the development, copied from the agency or legislature's own site
• A short company profile you write yourself (see Part 1)
• Total ongoing cost: the Claude plan above, with nothing else to buy

Data note. Use only the AI tool your company has approved for this work, and check its data settings first: whether chats are used to train models, how long they are kept, and who at your company can see them. A free consumer chatbot plan may use chats for training unless that setting is off. The official source text is public. Your company profile is the sensitive part. Keep it general (industry, rough size, regions, kinds of data) and leave out party names, deal values, nonpublic plans, and any privileged strategy. Whether pasting material into an AI tool affects privilege is unsettled and depends on the facts and the jurisdiction, so follow your company's policy and your state bar's guidance.

The Concept

Think of a junior associate who has never seen your company. You hand over the statute or rule and a one-paragraph description of the business. You ask for a summary and read it against the text. You ask what applies and read the assumptions. Only then do you ask for the briefing. A single big prompt would hide mistakes inside the finished product. Four small prompts with checks between them expose each mistake where it was made.

The chain runs in one Claude conversation, so each prompt can refer to the earlier answers.

Build It Step by Step

Part 1: Prepare your two inputs

Source text. Copy the official text from the agency or legislature's own site into a plain document. Note the URL and the date you copied it. If it is long, split it by part and run the chain on one part at a time.

Company profile. Write four to six lines in your own words. Use this shape:

Industry: [industry]
Size: [rough headcount band]
Where we sell or operate: [regions]
Data we handle: [kinds of data, such as customer contact data, employee records]
Relevant products or activities: [two or three]

Keep it general. No customer names, no deal values.

Part 2: Prompt 1, summarize the source text

Start a new conversation and send:

Below is the official text of a regulatory development. Summarize it section by section. For each section, give the section heading exactly as it appears in the text, then a summary of two or three sentences that uses only what the text says. Quote any defined term, date, threshold or obligation word for word and mark it as a quotation. If a section is unclear, say so and do not guess. Do not add any law, citation, date or threshold that does not appear in the text.

[Paste the source text here]

Checkpoint 1. Read each summary point against the passage it came from. Mark any point you cannot find in the source. Never accept a citation, date, threshold or defined term that the source text does not contain. If Claude added something, reply "Remove the point about [topic]. It is not in the source text." and confirm the corrected summary before going on.

Part 3: Prompt 2, apply it to your company

In the same conversation:

Here is a profile of my company:

[Paste your company profile here]

Using only your summary above, list each point from the development and state whether it plausibly applies to this company. For each point give: the point, a rating of Likely applies, Might apply, or Probably does not apply, the facts from the profile that drove the rating, and every assumption you made that the profile does not confirm. Do not state any legal conclusion as certain.

Checkpoint 2. Read the assumptions column closely. Correct each wrong assumption in a short reply, for example "We do not sell in [region]. Redo the ratings that depended on that." Fix the ratings before step 3. Your knowledge of the business and of the law does the work here.

Part 4: Prompt 3, questions for the business owner

Based on the corrected ratings above, write the questions I should put to the business owner. Group them by team. Each question must be answerable with facts about our operations, such as what data we collect, where we sell, which vendors touch it, or what we already do today. Write in plain language. Do not include any legal conclusion in the questions.

Checkpoint 3. Delete questions that are leading or that ask the business to interpret the law. Send the questions to the business owner yourself, and wait for answers before the last prompt. Paste the answers into the conversation if they change a rating, with names replaced by team or role.

Part 5: Prompt 4, the half-page briefing

Draft a half-page internal briefing for [audience, such as the executive team] on this development. Mark the top as "Privileged and Confidential" in the way my company marks legal advice: [your company's marking]. Include a one-sentence bottom line, what the development says in three or four bullets drawn only from the source text summary, what it means for us based on the corrected ratings and the business owner's answers, the open questions that remain, and the next steps with owners left blank for me to fill in. Do not add any citation, date or threshold that is not in the source text.

Checkpoint 4. Check every sentence of the draft against the source text and the corrected ratings. Fill in owners and dates yourself. Check the privilege marking against your company's practice. Review the draft as you would a junior colleague's work, because you are responsible for it. Decide who may see it before you send it.

Real Example: A Notice on Data Handling

Setup: A new official notice about handling certain customer data, pasted from the agency's site. Profile: "Industry: software. Size: mid-size. Where we sell: [regions]. Data we handle: customer contact data and usage data." Input: Prompt 1 returns five sections with headings and quoted defined terms. At Checkpoint 1 you find one summary line that mentions a date, and the source does not contain it. You have Claude remove it. Output: Prompt 2 marks two points "Likely applies" and one "Might apply", and lists the assumption that the company stores data with a vendor. You correct it: the data stays in your own systems. Two ratings change. Prompt 3 gives questions for IT and for customer success. The business owner replies. Prompt 4 produces a half-page briefing you edit and send. Time saved: The first read-through and drafting. The checks stay with you.

What to Do When It Breaks

• Claude adds a date, citation or threshold → Tell it to remove the point and cite only the pasted text. Never carry such a detail into the briefing. Verify any citation yourself on the official source.
• The summary drifts as the conversation grows → Start a new conversation, paste the source text again and the corrected ratings, and run prompt 4.
• The source text is too long → Run the chain on one part at a time, then combine the briefings yourself.
• Ratings read as legal conclusions → Re-run prompt 2 and ask for "plausibly applies" language only. The conclusion is yours.
• The tool refuses or truncates → Shorten the paste and keep each part to a manageable length.

Variations

• Simpler version: Run prompts 1 and 2 only and write the briefing yourself.
• Extended version: Save the chain in a Claude Project, with your company profile as project knowledge so you do not retype it. Keep the profile general.

What to Do Next

• This week: Run the chain on one development you already know well, so you can judge the accuracy.
• This month: Keep a company profile current and reuse it.
• Advanced: Add a standing list of the business owners to ask for each topic.

Advanced guide for corporate attorney professionals. These techniques use more sophisticated AI features that may require paid subscriptions. AI output is a first draft. You supply the law, check every point, and remain responsible for the work product.