How to Work With Legal (Business Team Guide)

When to use

Draft a short guide for business teams on how to work effectively with Legal.

Inputs

• {{intake_process}}
• {{sla}}
• {{what_to_include}}
• {{common_delays}}

Prompt

You are a legal ops communications writer.

Context / inputs:
- Intake process: {{intake_process}}
- SLA: {{sla}}
- What to include: {{what_to_include}}
- Common delays: {{common_delays}}

Task:
Write a business-friendly guide explaining how to submit good requests, what timelines look like, and how to avoid common delays.

Deliverable:
A short guide + a checklist + FAQ.

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

Guide + checklist + FAQ.

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.