# Draft Markup Of Procedural Order > Ensures a respondent-side procedural order markup analyzes hearing-time adequacy, privilege-log and insurance-disclosure risks, and due process concerns under the applicable curial law. - Skill: `finchipaiorg/draft-markup-of-procedural-order` (Agent Skill) - Install (CLI): `npx skillmds@latest add finchipaiorg/draft-markup-of-procedural-order` - Raw SKILL.md: https://api.skillmd.com/api/skills/finchipaiorg/draft-markup-of-procedural-order/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-markup-of-procedural-order --- # Skill: Procedural Order Markup (Respondent Side) ## 1. Subject-matter triage - Treat the procedural order as a comparison task against prior orders, case-management directions, institutional rules, and the client’s strategy materials. - Identify whether the draft changes hearing logistics, document production, privilege handling, confidentiality, expert evidence, motion practice, or admissibility rules; each category may require a different objection or fallback proposal. - If the draft implicates multiple witnesses, experts, issues, or time blocks, enumerate them before analysis and test the draft against each item rather than using a single representative pass. - Write the markup first, then the cover letter after the redline file is complete and non-empty. ## 2. Failure modes the skill is correcting - Fails to test whether the allotted hearing time is realistically sufficient for examination, cross-examination, redirect, openings, closings, and tribunal questions in light of the record and witness mix. - Accepts a privilege-log waiver concept without checking whether the wording is too broad, whether it unintentionally reaches admissibility or confidentiality, or whether it should be confined to the document-production context. - Misses the need for a carve-out where confidentiality language could conflict with insurance-notification, disclosure, reporting, or similar legal obligations. - Ignores whether a procedural direction departs from prior orders, agreed case-management positions, or institutional rules. - Overstates an admissibility prohibition or costs sanction without considering whether the provision chills legitimate procedure, burdens due process, or exceeds prior directions. - Fails to assess whether a draft procedural rule creates challenge or set-aside risk under the applicable curial-law fairness standard. ## 3. Legal frameworks / domain conventions that apply - Hearing allocation: assess the total hearing schedule against the expected witness count, expert count, issue complexity, and the need for tribunal questions, then propose a workable reallocation if the draft is tight. - Prior-order consistency: procedural directions should be checked against earlier orders and conference records; new wording should be narrowed if it expands prior agreements. - Concurrent experts: if the draft addresses concurrent expert evidence, confirm it matches any prior agreement or prior procedural direction and does not broaden the topic, sequencing, or scope beyond what was previously authorized. - Privilege-log waiver: a waiver-by-omission provision may be useful, but it should be limited to the intended production mechanic and should not be read to waive substantive privilege beyond the logging failure. - Confidentiality and third-party notice: confidentiality provisions should preserve mandatory or policy-based disclosure obligations, including insurance, indemnity, reporting, or other legally required notifications. - Admissibility and late production: absolute exclusions should be checked for necessary carve-outs tied to reasonable diligence, later-discovered documents, or other common arbitration exceptions. - Procedural motions and costs: costs-shifting language for unsuccessful applications should be tested for proportionality and for any deterrent effect on legitimate procedural requests. - Curial-law fairness: any provision that materially restricts presentation of evidence, witness examination, or procedural access should be tested against the applicable seat-based fairness / due-process standard and the governing institutional rules. ## 4. Analytical scaffolds - Compare the draft against each prior order and strategy note provision-by-provision; where there is a conflict, identify whether the new draft should be rejected, narrowed, or accepted with clarification. - For each objection, state the source of the problem, the scope of the risk, and the practical consequence for the client if the clause stands. - Use a uniform severity scale for markup commentary, applied consistently to every issue raised. - Where a point depends on multiple documents or parties, identify the interacting provision or document before drawing the objection. - For hearing-time issues, assess the schedule as a whole and then isolate the pinch points: witness blocks, expert sessions, tribunal questions, and post-hearing submissions. - For privilege-log language, ask whether the clause is merely an administrative waiver mechanism or whether it can be read as a broader waiver of privilege, confidentiality, or objection rights. - For confidentiality language, test whether a narrow exception is needed so the order does not force breach of insurance or reporting obligations. - For admissibility and sanctions language, assess whether the wording is overbroad, punitive, or likely to invite later procedural challenge. - For any fairness-sensitive provision, tie the objection to the governing curial-law principle and the institutional rule or prior order that should control. - Every redline change must be visible in the text itself using a robust textual convention, not styling alone, so the change survives conversion and can be reviewed outside Word markup. - Every markup note should include a short rationale and an authority reference drawn from the source materials or generally recognized arbitration practice. - End the advisory materials with concrete next steps that assign responsibility and timing. ## 5. Vertical / structural / temporal relationships - Check whether the draft procedural order sits above, below, or alongside earlier orders; later directions should not silently displace earlier ones unless the change is explicit. - Check whether the draft is intended to govern the entire remainder of the case or only the next phase; phase-limited language should be preserved where strategy depends on it. - Check whether a rule is triggered by a deadline, hearing milestone, document production step, or expert exchange; objections should be anchored to the relevant procedural moment. - If the draft uses sequencing rules, confirm that the sequence does not make later rights illusory or impossible to exercise in practice. ## 6. Output structure conventions - Deliverable 1: a redlined procedural order using plain-text change markers plus visible annotations for each substantive edit; include a short severity label for each objection or proposed revision. - Deliverable 2: a cover letter to the Tribunal that prioritizes the principal objections, explains the requested revisions, and identifies the governing source for each request. - Keep the redline self-explanatory even if exported without Word formatting; each change should be understandable from the text alone. - Use conventional arbitration drafting shapes for the final document set; do not mirror internal checklist labels or rubric phrasing. - If the record supports multiple alternative fixes, present the narrowest workable revision first and reserve broader objections for unresolved issues. - Before finalizing, confirm that the redline file is complete and substantive, and that the cover letter follows it as a secondary deliverable.