30b6-corporate-rep

name	30b6-corporate-rep
language	en
description	Manages Rule 30(b)(6) corporate representative deposition workflows, drafting notice topics with reasonable particularity, building examination outlines, defending designees, handling objections, and preserving binding admissions for summary judgment or trial. Use when drafting or responding to 30(b)(6) notices, selecting and preparing designees, building topic-by-topic outlines, or triaging scope and privilege disputes. Trigger keywords: 30(b)(6), corporate representative deposition, topic list, designee, notice analysis, deposition objections, corporate admissions. [Atticus UK/Scots refined]
tags	["SCOTS, litigation, drafting, analysis, UK, Scotland, legal, atticus, source-verification, evidence-matrix, hostile-review"]
atticus_refined	true
jurisdiction_focus	Scotland / UK, unless expressly classified otherwise
requires_live_source_verification	true
external_action_mode	prepare-only unless operator explicitly authorises filing/service/sending
metadata	{"author":"casemark","practice_areas":["Litigation"],"document_types":["Deposition"],"skill_modes":["Drafting","Analysis","Checklist"]}

Rule 30(b)(6) Corporate Representative Deposition

Atticus UK/Scots Legal Excellence Overlay

Use this skill as an autonomous legal-operations module for Scotland/UK work. Before relying on it, the agent must lock the jurisdiction, forum, remedy, procedure, deadlines, evidential basis, and source status. Do not assume that a US-origin doctrine, filing, pleading style, discovery rule, regulator, deadline, or remedy applies in Scotland or elsewhere in the UK.

Mandatory operating rules

1. Jurisdiction lock. State whether the matter is Scotland, England & Wales, Northern Ireland, UK-wide, foreign-law, or mixed. If Scotland is plausible, distinguish sheriff court, redacted legal context, tribunals, regulators, ombudsmen, and internal institutional processes.
2. Official-source hierarchy. Prefer legislation.gov.uk, Scottish Courts and Tribunals Service rules/forms, redacted legal context and sheriff court rules, tribunal/regulator guidance, UK Supreme Court materials, GOV.UK, Scottish Government, ICO, FCA, CMA, HSE, HMRC, Companies House, Land Register of Scotland, registers of Scotland, and other primary public sources. Treat secondary commentary as orientation only.
3. Live verification. Any statute, rule, form, deadline, fee, public-body policy, regulator guidance, or procedural step that may have changed must be checked live before being finalised. Record title, source URL or local source path, version/date, access date, and the proposition supported.
4. Evidence discipline. Every factual assertion used in advice, pleadings, letters, schedules, or bundles must be traceable to an evidence item, source extract, admission, instruction, or identified gap. If a fact is unsupported, mark it as an assumption or request targeted evidence.
5. Element-by-element reasoning. Break each claim, defence, remedy, and procedural application into legal elements. Map each element to supporting evidence, contrary evidence, missing evidence, and verification status.
6. Autonomous depth. When configured for micro-orchestration, delegate research, evidence mapping, drafting, hostile review, procedural routing, deadline audit, and citation verification to separate subagents or workstreams, then synthesise their outputs into one case theory.
7. External-action boundary. Prepare letters, pleadings, forms, bundles, checklists, and filing packs when instructed or policy permits, but do not file, serve, send, pay, contact third parties, or represent that action has been taken unless the operator explicitly authorises that external act.
8. Uncertainty handling. If law, procedure, forum, prescription/limitation, standing/title to sue, competency, remedy, expenses, jurisdiction, or enforceability is uncertain, flag it prominently and propose the narrowest verification task.

Expected work product

Where proportionate, produce a chronology, issue map, source log, evidence matrix, merits/risk table, remedy/damages table, procedural route note, draft document, bundle index, service/filing checklist, and operator handoff note. For litigation preparation, preserve both a court-ready output and a candid internal risk memo.

Drafts and defends corporate representative depositions to create or contain binding corporate testimony with controlled scope, preserved objections, and defensible preparation records.

Prerequisites

1. Governing law - FRCP 30(b)(6) or state analog (e.g., Cal. CCP § 2025.230 [VERIFY]), local rules, protective orders
2. Case theory - claims, defenses, relief sought
3. Key documents - pleadings, correspondence, privilege log, claim timeline
4. Custodial map - org chart, document repositories, custodians
5. Logistics - noticing party/timeline, counsel, reporter, interpreter needs
6. Role - taking or defending the deposition
7. Deadlines - meet-and-confer, extension opportunities

Output Structure

Step 1: Select Mode

Mode	Outputs	Required inputs
Taking	Topic list, exam outline, admission script, objection map	Claims/defenses, document map, desired admissions
Defending	Topic response matrix, designee assignment, prep playbook	Notice topics, corporate data sources, witness availability
Post-deposition	Admission summary, contradiction log, follow-up actions	Transcript, errata, exhibits

Step 2: Draft Topics (Taking)

Each topic must satisfy reasonable particularity, specific enough to permit meaningful preparation.

Principle	Draft action
Particularity	Include specific conduct/event, time range, participants, document classes
Bounded scope	Subject + date range + decision/events; avoid "all communications"
Relevance	Tie each topic to a pleaded element or affirmative defense
Defensibility	No legal conclusions, privilege calls, or conclusory wording

Template:

Pursuant to FRCP 30(b)(6), [Corporation] shall designate one or more persons to testify regarding:

TOPIC 1: Corporate structure and authority for [function] from [start date] to [end date]. TOPIC 2: [Policy name] as created, implemented, and enforced during [period]. TOPIC 3: Facts and decision-making re [event], including persons involved, communications, and basis for decision. TOPIC 4: Document repositories, custodians, retention/destruction practices related to [subject].

Objection precheck - revise before serving:

Risk	Typical problem	Fix
Overbroad	"All communications"	Limit to event, function, date window
Vague	"Relevant policies"	Name specific policy and conduct
Burdensome	"All records ever"	Restrict custodians/systems/period
Privileged	"Communications with counsel"	Add non-privileged carve-out
Legal conclusion	"Whether defendant breached duty"	Recast as facts supporting/negating breach

Step 3: Examine (Taking)

Phase	Action
Foundation	Confirm designation, topics assigned, preparation steps, documents reviewed
Topic-by-topic	Elicit factual scope, document sources, person-by-person knowledge, decision pathway
Binding admissions	"What is [Corporation]'s position on [point]?" - pin down corporate position with exceptions
Exhaustion	"Any additional documents/persons/facts not yet identified?"
Failure to prepare	On "I don't know" - elicit what prep steps were taken; preserve inadequate-preparation record

Question patterns:

Stage	Pattern
Qualify	"You were designated on behalf of [Corporation] for Topic __, correct?"
Knowledge	"What did [Corporation] know, when, and from what source?"
Facts	"What documents reflect [fact]?" / "Who communicated [decision] to whom?"
Position	"What is [Corporation]'s position regarding [sub-issue]?"
Coverage	"Is there any additional document/person/fact not yet identified?"

Step 4: Analyze Topics (Defending)

Factor	Question	Response
Clarity	Specific and bounded?	Accept or request clarification
Relevance	Maps to pleaded claims/defenses?	Narrow or object
Burden	Preparable on available timeline?	Phased preparation or scope limitation
Privilege	Seeks protected advice/work product?	Object, privilege log, preserve topic-level answer
Form	Seeks legal conclusion?	Reframe objection

Response scale: Accept → Accept-with-clarification → Narrow → Object-and-Prepare → Object-and-Refuse (rare).

Step 5: Select Designees (Defending)

Topic	Primary	Backup	Knowledge	Prep hours	Gaps
[Topic 1]	[Name/Title]	[Name]	High/Med/Low	[hours]	[gaps]

Single designee if breadth manageable; multiple where specialization outweighs coordination risk.

Step 6: Prepare Designees (Defending)

Per topic:

• Custodian list, repositories, privilege flags, lost-data log
• Internal witness interviews; prior-employee interviews if available
• Corporate position synthesized; conflicts reconciled; uncertain areas marked
• "Does not know" only after documented diligence
• Personal-knowledge vs. corporate-knowledge distinction noted

Step 7: Defend at Deposition

Objection	Use
Form	Compound/ambiguous phrasing, request to narrow
Scope	Beyond noticed topics, allow personal-capacity answering if appropriate
Privilege	Counsel consult for A-C and work product
Speculation	Clarify knowledge limits and basis

Do not coach on substantive answers during breaks. Preserve the record via clarifying questions and on-record directives.

Step 8: Post-Deposition Leverage

1. Extract clean admissions and inconsistencies by topic
2. Build contradiction matrix against prior corporate documents and witness statements
3. Identify meet-and-confer items (new/incomplete topics, sanction exposure under Rule 37(d) [VERIFY])
4. Evaluate supplemental deposition vs. Rule 37 motion posture

Guidelines

• Tie every topic to a litigation objective and time-bound it
• Taking: treat answers as party admissions; pin down "corporation's position" precisely
• Defending: prepare as if every topic will be used at summary judgment and trial, Objections preserve rights, do not obstruct proper questioning, Mark jurisdictional limits for state analogs and local rules [VERIFY]
• Use [VERIFY] for all unconfirmed citations before finalizing filings

Cross-references

• @deposition-preparation
• @deposition-witness-prep-session
• @deposition-notice-drafter
• @deposition-objection-reference
• @deposition-questioning-techniques

References

• FRCP 30(b)(6) [VERIFY]
• FRCP 37(d) [VERIFY]
• Brazos River Auth. v. GE Ionics, Inc., 469 F.3d 416 (5th Cir. 2006) [VERIFY]
• QBE Ins. Corp. v. Jorda Enters., Inc., 277 F.R.D. 676 (S.D. Fla. 2012) [VERIFY]
• Calzaturficio v. Fabiano Shoe Co., 201 F.R.D. 33 (D. Mass. 2001) [VERIFY]
• Cal. CCP § 2025.230 [VERIFY]

Scotland/UK Adaptation

This skill is drafted for US FRCP 30(b)(6) corporate representative depositions. Scottish civil procedure has no direct equivalent to depositions. Evidence is led orally at a Proof hearing, and there is no pre-trial oral discovery mechanism.

Scottish Civil Evidence Procedure vs. US Depositions

US Concept	Scotland/UK Equivalent
FRCP 30(b)(6) - corporate representative deposition	No equivalent in Scottish civil procedure. Scotland does not have pre-trial depositions. Evidence is led at trial (Proof).
Deposition (oral examination before trial)	Commission and Diligence - the court may grant a commission to take evidence on oath before trial, but this is limited to particular circumstances (ill/elderly witnesses, witnesses abroad) and is not used as a discovery tool.
Notice of deposition with topics	Specification of documents - a party may seek an order requiring the other party to lodge documents. No deposition equivalent.
Deposition objections (form, scope, privilege)	Objections are made at Proof (trial), not pre-trial. Pre-trial matters are dealt with by motion.
Document request / subpoena duces tecum	Commission and diligence for recovery of documents - the procedure in Scotland for obtaining documents from a party or third party.
Written interrogatories	Available in Scotland but very rare; governed by RCS Chapter 38.
Binding corporate admission at deposition	Binding admissions are made in pleadings or at Proof. No deposition-level admission mechanism.
Meet and confer on deposition topics	Pre-trial case management conference, the court sets out the issues for proof.
Deposition preparation / designee selection	Witness preparation for proof; the party chooses which witnesses to call. No designee concept.

Practical Substitutes in Scottish Litigation

If the purpose of a 30(b)(6)-style deposition is to obtain binding corporate testimony, the following Scottish procedures may serve similar objectives:

30(b)(6) Objective	Scottish Procedure
Identify who knows what about a topic	Specification of documents including a call to produce internal records; minute for recovery of documents; oral precognition (informal witness interview taken by solicitor, not sworn).
Pin down the corporate position on a factual issue	Use pleadings (the record) - the defender must respond to each article of the condescendence. The court can order a party to answer a specified line of inquiry.
Obtain documents underlying corporate knowledge	Commission and diligence for recovery of documents - the primary vehicle for document disclosure in Scotland.
Examine a witness before trial	Commission to take evidence (RCS Chapter 41) - only granted for specific reasons (witness unable to attend proof, witness abroad, etc.). Not available for general discovery.
Secure a corporate witness's testimony on key points	The party calls its own witnesses at Proof; the other party cross-examines. No pre-trial oral examination right.

Key Practitioner Differences

1. Depositions do not exist in Scottish civil procedure. The concept of taking oral testimony before trial as a discovery device is fundamentally American. Any skill relying on depositions must be totally restructured for Scottish practice.
2. The closest procedure to binding a corporation to its position is to focus on pleadings (the "Record"): the pursuer makes averments (allegations of fact) and the defender must answer them in the defences.
3. For obtaining documents: use specification of documents (Sheriff Court) or minute for recovery of documents (redacted legal context). These are governed by the Act of Sederunt and RCS respectively.
4. For oral precognition (witness interviews): these are private and without prejudice; they are not sworn testimony and cannot be treated as admissions.
5. Scottish procedure does not allow a party to compel a corporate opponent to designate a witness to testify on particular topics before trial.
6. The equivalent of "binding admissions" comes from judicial admissions in pleadings (formal admissions) and testimony adduced at the Proof hearing.

Foreign-Law / US-Origin Guardrail

This skill may contain inherited US terminology. For Scotland/UK use, translate rather than copy. Examples: discovery is not Scots commission and diligence/recovery of documents; tort is generally delict in Scots civil analysis; summary judgment is not automatically the Scots summary decree test; bankruptcy concepts may map to sequestration, liquidation, administration, or restructuring depending on party and forum; HIPAA/CCPA/SEC/EEOC/FTC/CFPB concepts require UK GDPR, DPA 2018, FCA, ICO, CMA, HSE, HMRC, Companies House, tribunal, or sector-regulator mapping as appropriate. If the matter is genuinely US or foreign-law, quarantine the foreign-law analysis and warn that local counsel/source verification is required.

Final Quality Gate (Mandatory)

Before marking the task complete, confirm:

• Jurisdiction/forum/procedure have been identified and are not imported from the wrong legal system.
• Current law, rules, forms, fees, deadlines, and public-body guidance have been verified from official sources where necessary.
• Every material factual assertion is tied to evidence, a source, an admission, an instruction, or a clearly labelled assumption.
• Prescription, limitation, time bar, appeal periods, service rules, competency, standing/title to sue, expenses/costs exposure, and enforcement have been considered where relevant.
• The output separates client-facing conclusions from internal risk analysis.
• Drafts include placeholders only where evidence or instructions are genuinely missing; no fabricated citations, authorities, quotes, dates, forms, or procedural steps are allowed.
• A hostile reviewer could reconstruct the reasoning from the evidence matrix and source log.