Translate

Turn a protective order into client compliance rules

Converts a confidentiality or protective order into a one-page guide the client team can follow: every tier, exactly who is shut out of each, where files may live, and what the end-of-case deadline actually requires.

About 8 minstarterLitigation, In-house

Your prompt4,892 characters

Still to fill in: Protective order, Client team, Court

RoleYou are a litigator who has had to explain why one chart from a produced document, dropped into a sales deck, became a contempt motion. You translate protective orders into rules a non-lawyer can follow on a Tuesday afternoon, you name the people on the client's own team who are shut out of each tier, and you never tell a client an obligation the order does not impose.What I needA one-page compliance guide to the protective order below for Client team. It governs Case in Court. Tie the handling rules to Where material will actually live.InputsProtective order: Protective order Client team: Client team Case: Case Court: Court Systems in use: Where material will actually liveHow to work this1. Use the order's own tier labels, quoting the paragraph defining each. Build the access table from its qualified-recipient list, then add a column naming who on Client team may not see each tier. That column is what prevents the violation. 2. Where access is conditioned (a signed undertaking, disclosure plus an objection window), state the condition, who performs it, how long it runs. 3. Turn handling provisions into actions in Where material will actually live: which folder, what may be emailed or pasted into chat, whether contractors and offshore staff are covered, what happens on personal devices. End-of-case obligations get a trigger, a day count, a deliverable, and what outside counsel may retain. 4. Consequences at two levels: what the order provides, and what a court in Court can do. Keep my obligations (designation challenges, meet-and-confer, sealing) out of the client rules and list them separately. Close with a "common situations" list: a produced figure in a board deck, forwarding to an insurer, showing a document to a witness, each citing the paragraph that answers it, or saying the order is silent.Close with these four sections, every time, without being askedPut these under "For counsel". Assumptions I made. Every assumption about who qualifies under each tier, whether an undertaking has been signed, who counts as in-house counsel, and what ambiguous handling language means. Mark each [verify] or [safe]. Where this is weakest. The two or three rules most likely to be misread by a non-lawyer or to overstate the order. Name the rule, not "the guide generally." What only you can decide. The calls I left to you, each as options with tradeoffs. At minimum: whether this team gets the strict version of the rules or the version the order literally requires: strict is easy to follow and never draws a motion, but it locks your own client out of material they may use and slows the case, while the literal version preserves their access and depends on people applying judgment under deadline. Also yours: whether to seek AEO clearance for in-house counsel now, which costs a fight early, or work around it and risk needing it at the worst moment. What would make this materially better. The input that would sharpen the next pass: signed undertakings on file, the producing party's designation practice, the client's actual retention settings, or whether any designation is under challenge. Rank by impact.Output formatThe order in one paragraph, then a tier table: Tier as labeled | What it covers | Who may see it | Who on your team may not. Then Before someone gets access, Handling rules, End of the case (trigger, deadline, deliverable), If this is breached, Common situations, and Your custodian: one person who logs every receipt.Never do this- If this guide would fit any protective order in any case, it is too generic. Rebuild it from this order's tiers, this team, and these systems. - No hedging filler. Cut "arguably," "it should be noted," and "use good judgment" as a substitute for a rule. Do not tell the reader to consult an attorney. You are writing for the attorney. - Never invent an obligation, deadline, or penalty the order does not contain. Every rule cites a paragraph, or carries [UNVERIFIED - not in the order as pasted]. - Where the order is silent or ambiguous on a handling question, say you do not know and tell me to raise it in a meet-and-confer. Do not smooth over the gap with fluent prose. - Do not pad. A two-tier order with simple handling rules gets a short guide. Length is not value.Before you answer- Does every rule cite a paragraph of the order, or carry a mark saying the order is silent? - Did I name the specific people excluded from each tier, rather than describing categories? - Do the end-of-case obligations have a trigger, a day count, and a deliverable? - Would this guide be useless to a client under a different order? It should be.

Adds driver's-seat tunes: options instead of answers, questions before work, every citation flagged. Your values come with it.

Pressure-test it

Makes the AI switch hats and attack its own answer.

A client who walks into a contempt motion will have been following this guide word for word. Read it as the lawyer writing that motion. Name the three rules a reasonable non-lawyer could read as permission for something the order does not allow. Then read it a second time as the client's VP of Sales who has a customer meeting tomorrow and wants one chart from a document stamped CONFIDENTIAL: is the answer findable in under thirty seconds? Rewrite the rules that fail either read.

Go deeper

Pushes the work further once the basics are right.

Compliance starts at signature, not at circulation. Produce the two operational documents that ship with this guide: the acknowledgment form each person signs before receiving material, capturing name, role, tier, date, and the undertaking the order requires, and a four-sentence email from the GC transmitting both, naming the custodian and calling out the single rule this team is most likely to break.

Before you run it

What to gather first

The protective order in full, including the exhibit undertaking and any AEO provisions
Every person and role on the client side who will touch produced material, including contractors
Where the client will actually store material: the systems, not the policy
The court and judge, since enforcement and sealing practice vary
Whether any expert or consultant still needs to be disclosed and cleared

Watch for

Protective orders bind by their exact text. A paraphrase that softens an obligation is the document your client will point to when explaining the violation.
AEO tiers routinely exclude in-house counsel and the client entirely. Confirm who qualifies before anything is shared internally, and remember that access is often conditioned on a signed undertaking and an objection window.
End-of-case obligations run from a trigger, not a calendar date, and many require a written certification. Calendar them the day the order is entered.
The model will not know your client's systems, contractors, or offshore staff unless you say so, and those are where most inadvertent disclosures happen.
Designation challenges, sealing, and clawback procedures are counsel's obligations with their own deadlines. Do not let them get buried in a client-facing rule sheet.

What comes back

A one-paragraph plain summary, a tier table using the order's own labels with a column naming who on the team is excluded, conditions that must be satisfied before access, handling rules tied to the client's actual systems, end-of-case obligations with trigger and deadline, consequences, a common-situations list with paragraph cites, and a custodian designation. Counsel-only notes follow separately.

See an example of what you’ll get

The order in one paragraph. The protective order in Orion Systems v. Vertex Industrial creates two tiers. Anything Vertex marks "CONFIDENTIAL" (¶ 2.1) can be used by our team for this lawsuit only. A narrower set marked "HIGHLY CONFIDENTIAL - ATTORNEYS' EYES ONLY" (¶ 2.2) (source code, pricing models, and personnel files) cannot be seen by anyone at Orion, including the GC. Everything expires at the end of the case, and you have 60 days after that to return or destroy it. Tiers and access | Tier (as the order labels it) | What it covers | Who may see it | Who on your team may NOT | |---|---|---|---| | CONFIDENTIAL (¶ 2.1) | Most produced documents, deposition transcripts marked at the time | Outside counsel; the GC and deputy GC; the two named product managers; the damages consultant once cleared | The CFO (not on the ¶ 5.2 list; add her by agreement or she is out); the offshore IT contractor | | HIGHLY CONFIDENTIAL - AEO (¶ 2.2) | Source code, unit-level pricing, personnel files | Outside counsel and cleared experts only | Everyone at Orion, including the GC and both product managers | Before someone gets access. The damages consultant must sign the Exhibit A undertaking and be disclosed to Vertex, which then has 10 business days to object (¶ 7.3). No AEO material goes to her until that window closes without objection. The product managers must each sign Exhibit A; no waiting period applies to CONFIDENTIAL material (¶ 7.1). Handling rules. - Store everything in the single matter folder in Google Workspace with sharing set to named individuals. No "anyone with the link." - Nothing goes in Slack. The order permits electronic storage "in a secure, access-restricted repository" (¶ 8.2); a channel with 40 members is not that. - The two remote product managers may work on personal laptops only if the files stay in the browser and are not downloaded (¶ 8.4 requires no local copies on unmanaged devices). - The offshore IT contractor is not covered by anything in this order. Do not route material through the vendor SFTP. - Use for this lawsuit only. Not for competitive analysis, pricing decisions, or product planning (¶ 4.1). End of the case. Trigger: final judgment or dismissal, including any appeal. Deadline: 60 days after that trigger (¶ 12.1). Deliverable: return or destroy all copies and serve a written certification signed by an officer. Outside counsel may retain one archival set of filings and work product (¶ 12.2). Your team may retain nothing. If this is breached. The order itself requires immediate written notice to Vertex and reasonable efforts to retrieve the material (¶ 11.1). Beyond that, the court can hold Orion or an individual in civil contempt, impose monetary sanctions, and preclude use of evidence. The order does not itself specify a penalty amount. Common situations. - *One chart from a CONFIDENTIAL document in a board deck?* No, unless the deck stays inside the access list and carries the CONFIDENTIAL legend (¶ 8.1). Ask counsel first. - *Forward to the insurer?* The order does not address insurers [UNVERIFIED - not in the order as pasted]. Do not send; counsel will raise it in a meet-and-confer. - *Show a document to a fact witness?* Permitted for a witness who authored or received it, and only during preparation or testimony (¶ 5.4). Your custodian. Designate one person (recommended: deputy GC) to log every receipt of designated material, hold the signed Exhibit A forms, and run the 60-day destruction sweep. For counsel, not the client Assumptions I made. I assumed the CFO is not on the ¶ 5.2 access list because she is not named there [verify - if there is a later stipulation adding her, this table is wrong]. I assumed no Exhibit A undertakings have been signed yet [verify]. I assumed the order's "secure repository" language in ¶ 8.2 excludes group chat [verify - this is my reading, not the order's words]. Where this is weakest. The Slack rule. The order does not name Slack, and I have converted "secure, access-restricted repository" into a flat prohibition. It is the right advice and it is not what the order says. Second: the personal-laptop rule assumes those devices are unmanaged, which I do not actually know. What only you can decide. Whether to give this team the strict version above or the version the order literally permits. Strict is easy to follow and will never draw a motion, but it keeps the CFO out of documents she may need for the damages model and slows your own case. The literal version preserves her access and depends on people making judgment calls under deadline. Also yours: whether to seek AEO clearance for the deputy GC now: a fight that costs you two weeks and some goodwill early, versus needing it during expert discovery when you have no time to lose. What would make this materially better. (1) The signed Exhibit A undertakings on file, which fix the access table. (2) Vertex's designation practice so far: if they are over-designating, the guide should include the challenge path. (3) Confirmation of whether the remote laptops are MDM-managed. (4) Whether any designation is already under challenge.

Why this prompt is built the way it is

## Framework 1. **Use the order's own labels, and make the exclusion list the point.** Translate the tiers it actually creates, quoting the paragraph that defines each. Generic tiers teach the wrong rules. Then say which people on the client's team may not see each tier, by name or role. That sentence is what prevents the violation. 2. **Conditioned access gets its condition.** Experts who must sign an undertaking, in-house counsel who must be disclosed and survive an objection window. Name the step and who takes it. 3. **Handling rules map to real systems; end-of-case obligations get trigger, day count, and deliverable.** Where files may live, what may be emailed, whether contractors and offshore staff are covered, what happens on personal devices. Then return or destroy, certification, what counsel may retain. 4. **Consequences at two levels, counsel's obligations kept separate, and nothing invented.** What the order itself provides, and what the court can do. Challenge procedures, meet-and-confer deadlines, and sealing are counsel's job and do not belong in a client rule sheet. If the order does not address something, that is the answer.