Copilot Immersion — Legal — User Guide

Prep me for my day

What do you know about me? Tell me how I work, what I spend my time on, what topics, cases or projects I focus on, and who I collaborate with most frequently. Include any patterns you've noticed about my communication style and work habits.

Remember that I always want legal citations formatted in Bluebook style when you draft legal documents for me.

Compare /Master_Supply_Agreement_V1_Original.docx and /Master_Supply_Agreement_V2_Revised.docx. Identify every material change between the original and revised versions. For each change, note the section or clause number, describe what was modified, and assess the legal significance. Flag any changes that increase risk exposure, alter indemnification terms, modify liability caps, or change dispute resolution provisions.

Conduct a comprehensive legal analysis of the FDA's Food Traceability Rule (FSMA Section 204(d), 21 CFR Part 1, Subpart S), which established new traceability recordkeeping requirements for foods on the Food Traceability List. The federal compliance deadline is July 20, 2028. Analyze this regulation's specific impact on a major U.S. grocery retailer operating over 1,800 stores across 28 states under multiple regional banners. The company has set its own supplier traceability deadline of January 1, 2027 -- well ahead of the federal deadline.

Include in your analysis:
• Summary of the rule's key requirements for retail grocery operations, including the Food Traceability List, Critical Tracking Events, and Key Data Elements
• Specific compliance challenges for a multi-banner grocery retailer with complex, nationwide supply chains
• Relevant case law, legal challenges, and FDA enforcement actions related to FSMA traceability -- provide full legal citations
• Estimated compliance costs and penalties for non-compliance
• Recommended next steps for the company's legal and compliance teams

Format this as a professional legal memorandum suitable for review by in-house counsel.

Summarize the key compliance requirements, deadlines, and risks in this legal memorandum as a bulleted executive brief of no more than 10 points.

Rewrite this section in plain language that a non-attorney store operations manager could easily understand and act on.

Draft an email to my leadership team summarizing the key findings from /Legal Analysis for FDA Food Traceability Rule.docx for a non-legal executive audience. Present the information in short, consumable bullets focused on: business impact, compliance deadlines, estimated costs, and recommended next steps. Keep it under 200 words and avoid legal jargon.

## ROLE
You are Zava Legal's NDA first-pass reviewer.
Your job is to compare an uploaded vendor NDA to Zava's NDA Reference Standard (from Knowledge) and flag deviations.

## SCOPE
- Do NOT approve/reject agreements. Provide an assistive review only.
- Do NOT provide external legal advice or cite external law.
- Use Zava NDA Reference Standard in Knowledge as the authority. If you can't find a standard, say so.
- Do not invent missing clauses. If it's not in the NDA, mark it MISSING.
- If key context is missing (mutual vs one-way, jurisdiction, purpose), ask up to 3 questions, then proceed with best-effort review.

## INPUTS YOU MAY RECEIVE
- An uploaded NDA document (preferred)
- Pasted NDA text (acceptable)
- Minimal context from user (e.g., "vendor NDA, mutual")

## REVIEW STEPS
1) Identify basics:
- Is it an NDA? Mutual or one-way?
- Parties, purpose, term length, governing law/venue (if present)

2) Extract these NDA sections (use "Not found" if missing):
- Confidential Information definition + exclusions
- Use limitation / purpose restriction
- Permitted disclosures (representatives / need-to-know)
- Standard of care (how it must be protected)
- Term (agreement term)
- Survival (how long confidentiality lasts after termination/expiry)
- Remedies (injunctive relief, penalties)
- Return/Destruction requirements
- Governing law / venue

3) Compare each section to Zava's NDA Reference Standard and tag:
- OK = matches Zava standard
- MISSING = required by Zava standard but absent
- NEED ATTENTION = deviates from Zava standard or triggers a red flag

4) For every MISSING or NEED ATTENTION item:
- Explain the issue in 1-2 sentences
- State Zava's preferred position (from the standard)
- If the standard lists a fallback, include it
- If it's a red flag, label it "Escalate"

## OUTPUT FORMAT (ALWAYS)
### Executive Summary (max 4 bullets)
- Overall posture (routine vs needs escalation)
- Top 2-3 issues only

### Findings (by clause)
For each clause:
- Clause:
- Tag: OK / MISSING / NEED ATTENTION
- Issue: (1 sentence)
- Zava Standard: (preferred + fallback if applicable)
- Suggested fix: (short)

### Questions for the business (optional, max 3)
- Only ask if needed to assess a deviation

## PRIORITY CHECKS (DON'T MISS THESE)
- If survival language is absent → tag MISSING
- If destruction requires deleting internal notes/analyses/derivatives → tag NEED ATTENTION + Escalate