# Draft Objections To Document Production Request

> Ensures document production objections in a fund-related arbitration address confidentiality concerns with nuance, identify possible open-records exposure for certain institutional investors, and avoid blanket refusals by pairing each objection with a counter-proposal.

- Skill: `finchipaiorg/draft-objections-to-document-production-request` (Agent Skill)
- Install (CLI): `npx skillmds@latest add finchipaiorg/draft-objections-to-document-production-request`
- Raw SKILL.md: https://api.skillmd.com/api/skills/finchipaiorg/draft-objections-to-document-production-request/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: FinchipAIOrg (https://skillmd.com/u/finchipaiorg)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/finchipaiorg/draft-objections-to-document-production-request

---


# Skill: Arbitration Document Production Objections

## 2. Failure modes the skill is correcting

- Treats confidentiality as a stand-alone refusal instead of pairing the objection with a narrower production path, making the response look evasive rather than proportionate
- Overlooks that some institutional investors may be subject to public-records or similar transparency regimes, leaving a secondary disclosure channel unaddressed
- Assumes privilege survives every forwarding chain, without checking whether disclosure to a non-attorney may have waived protection for a particular document
- Mirrors expansive requests for device imaging or all-device collection instead of confining production to targeted, relevant sources under an agreed protocol
- Fails to separate true objections from preservation or custodial topics, causing the response to waive nothing while still conceding too much
- Leaves overlapping or duplicative requests unmerged, which weakens the response and creates inconsistent positions across the schedule

## 3. Legal frameworks / domain conventions that apply

- Use an arbitration-style request-and-response format consistent with an IBA Rules / Redfern Schedule approach: each response should state the objection, the legal basis, and the proposed alternative production
- Anchor confidentiality objections in the governing fund, investor, and disclosure obligations reflected in the source materials; if disclosure is constrained by contract or policy, say so and propose a confidentiality order rather than a flat refusal
- For investor information, distinguish between ordinary third-party confidentiality and situations where institutional investors may themselves be subject to open-records, public-access, or similar statutes; address that downstream risk through a protective order and limited designation protocol
- Treat privilege under the governing privilege doctrine and waiver principles applicable to the forum; if a communication was forwarded outside the attorney-client channel, assess whether waiver may have occurred before withholding it outright
- Apply proportionality and relevance principles to requests for forensic imaging, personal devices, or unfocused collections; targeted collection from identified custodians and sources is the default narrower response
- If the source set reflects a litigation hold or preservation step, state that preservation is being maintained and offer a limited preservation description rather than a broad narrative of internal preservation measures
- Cite the controlling authority for each legal proposition relied on, using the governing rule, statute, treaty article, or recognized arbitration practice identified in the materials or otherwise applicable law

## 4. Analytical scaffolds

- Start with a general objections section that preserves all applicable rights, including privilege, confidentiality, work-product, privacy, and relevance objections, while making clear that no objection is waived by any partial response
- Require a confidentiality order as the condition for producing sensitive investor, investor-account, or internal-fund materials, and specify that redaction, aggregation, or category-based designation may be used where complete withholding is unnecessary
- Where multiple requests overlap, consolidate them and avoid repeating the same objection in inconsistent wording; one reasoned response should govern the related cluster
- For each request, use a three-part response: objection, legal basis, and counter-proposal or production boundary
- For investor-data requests, separate the analysis into: what is requested, what third-party confidentiality applies, whether any institutional investor may face public-access exposure, and what alternative production can be made under protection
- For privilege issues, identify the document or document type, note the privilege basis, and separately flag any forwarding or sharing facts that may create a waiver question
- For non-party materials, address control, possession, and consent; if the responding party lacks authority to produce, say so and offer a path for consent-based or targeted production if feasible
- Keep the tone firm, professional, and cooperative; the draft should read like a serious arbitration response, not an advocacy brief

## 5. Vertical / structural / temporal relationships

- Use a top-level general objections section before any request-by-request responses
- Group duplicative requests by topic, custodian, account type, or document category where that improves clarity and consistency
- Preserve temporal limitations if the requests and source materials define them; if a request is not time-bound, narrow it by relevance and custodians rather than by unsupported date assumptions
- If the document set reflects evolving positions over time, distinguish preservation, search, review, and production obligations so the response does not conflate them
- Where a request reaches both current and historical materials, state whether the objection applies to the full period or only to a particular category of records, then tailor the counter-proposal accordingly

## 6. Output structure conventions

- Draft the response as formal objections and responses suitable for a Redfern Schedule or similar arbitration production table
- Include a general objections section covering privilege reservation, confidentiality obligations, and the need for a confidentiality order before sensitive production
- For each request, state:
  - the request category or number
  - the objection(s)
  - the legal basis with authority cited
  - the proposed alternative production, if any
- Use concise, document-ready prose; do not explain the drafting process
- If a privilege log is warranted by the source materials, include a separate privilege-log style section identifying withheld materials and any waiver-risk note
- When producing the final document, ensure the operative objections and responses are fully written out and ready to be saved as the named `.docx` deliverable