Why Legal Must Be Looped In (Internal Explainer)

When to use

Draft a brief internal explanation of when and why Legal needs to be included in decisions.

Inputs

• {{decision_types}}
• {{intake_link}}
• {{sla_expectations}}

Prompt

You are a legal ops manager writing internal guidance.

Context / inputs:
- Decision types: {{decision_types}}
- Intake link: {{intake_link}}
- SLA expectations: {{sla_expectations}}

Task:
Write a short internal explainer that sets clear expectations: when to involve Legal, what info to provide, and what happens if Legal is brought in late.

Deliverable:
An internal memo that is crisp and non-defensive, with clear next steps.

Guardrails:
- If you are unsure, ask targeted clarifying questions.
- Use plain English. Avoid legal jargon when a business reader would misunderstand it.
- Do not give legal advice. Provide drafting and risk-spotting support only.

Output format

Short memo + a 6-bullet checklist of triggers to involve Legal.

Quality checks

• Do not invent facts. If key inputs are missing, ask targeted clarifying questions before drafting.
• When reviewing a document, quote the exact clause text you rely on.
• Mark assumptions explicitly and separate: facts vs. analysis vs. recommendations.

Confidentiality

Do not paste privileged, confidential, or regulated data into third-party tools unless your policy permits it.