Trust, Risk, and Regulated Communication

Legal Review Request Brief

Give qualified counsel precise claims, intended use, audience, jurisdiction, sources, product facts, deadline, business context, and open questions.

Free editable Markdown · Editors, product marketers, and legal operations teams · Updated July 30, 2026

Download Markdown

Accessible HTML preview

Blank template

The downloaded file contains the same fields in editable Markdown.

Request scope

Request ID and owner: [Enter]
Asset, URL, and version: [Enter]
Channel and publication date: [Enter]
Audience and markets: [Enter]
Relevant jurisdictions: [Counsel to confirm]
Business purpose and action: [Describe]
Deadline and urgency reason: [Enter]
Decision needed: [Approve / Revise / Restrict / Disclose / Other]

Claim or issue card

Duplicate for each issue.

Issue ID and exact wording/location: [Enter]
Proposed net impression: [What may a reader infer?]
Verified factual basis: [References]
Product, plan, and availability scope: [Enter]
Known limitation or conflicting evidence: [Enter]
Commercial or rights relationship: [Enter]
Team assumption: [Enter or None]
Specific question for counsel: [Write]
Priority: [Blocking / Important / Advisory]

Supporting record

Frozen draft and visual context: [Reference]
Claim substantiation: [Reference]
Privacy/data flow: [Reference or Not applicable]
Consent/license/contract: [Reference]
Prior relevant advice: [Controlled reference]
Locale differences: [List]
Other specialist reviews: [Product/security/science/other]
Missing evidence: [List]

Decision and implementation

Counsel response reference: [Controlled location]
Approved wording or condition: [Enter]
Required disclosure/restriction: [Enter]
Assigned edits and owner: [List]
Final version verified: [Enter]
Open question: [Enter or None]
Re-review trigger: [Claim, channel, jurisdiction, product, evidence]
Final approver and date: [Enter]

How to use this template

Freeze the draft and define the exact claim, channel, audience, jurisdiction, and decision needed.
Assemble verified product facts, evidence, permissions, prior decisions, and known limitations.
Write prioritized legal questions and distinguish assumptions from established facts.
Submit through the approved legal process with deadline, owner, and fallback decision.
Apply and verify the response on the controlled final version and record re-review triggers.

Ask a precise review question

Identify the exact asset, version, planned channel, audience, jurisdiction, publication date, and business action. Copy the wording or product behavior that needs review and explain what decision the team requires: approve, revise, disclose, restrict, or identify missing evidence. “Please review this page” forces counsel to reconstruct scope and may hide the highest-risk issue. Separate legal questions from editorial fact-checking, product verification, privacy operations, and brand preference, while noting where they intersect. If several claims raise different issues, label and prioritize them rather than asking one broad question.

Provide the factual record without advocacy

Link to the frozen draft, claim evidence, product specifications, research, contracts, consent records, permissions, prior decisions, and intended visuals. State known limitations, commercial relationships, markets, plans, data flow, and material differences across locales. Distinguish verified facts, team assumptions, and unresolved questions. Do not withhold inconvenient test results or tell counsel only why marketing prefers the claim. A reviewer can give a more useful response when the proposed net impression and factual basis are visible together.

Turn advice into a controlled editorial decision

Record deadline, urgency reason, owner, and what happens if review is incomplete. After counsel responds, preserve the advice under the organization's access and privilege practices; the public content record may only need the resulting approved wording and decision. Translate comments into assigned edits, evidence requests, disclosure placement, audience restrictions, or escalation. Confirm the exact final version and route later material changes back through review. Do not reuse one approval across new jurisdictions, products, media, or claims unless counsel has explicitly scoped it that way.

See the fields in context

Fictional example: compatibility claim

DataSprout and its compatibility test are invented. This example is not legal guidance.

Claim: A fictional page says “works with every spreadsheet.”
Evidence: The team tested two file formats and one application version; it has not tested every spreadsheet.
Question: What narrower wording and disclosure should be used in the two intended fictional markets?
Fallback: Remove the universal claim if review is not complete before launch.
Trigger: Re-review on new formats, markets, media, or comparison wording.

Frequently asked questions

Should counsel receive the entire campaign?

Provide enough full context to understand net impression, plus precise issue labels so review remains efficient.

Can old legal approval be reused?

Only within its recorded scope. Product, wording, evidence, audience, channel, market, or legal changes may require new review.

Should legal comments be copied into a public editorial log?

Follow the organization's confidentiality and privilege practices. Record the approved outcome without exposing protected advice.

What if the deadline arrives before review?

Use the predefined fallback—delay, remove, or narrow the claim—rather than treating silence as approval.