Provisions

Individual rule provisions extracted from part rules documents

Data license: Government edicts — not subject to copyright · Data source: nycourts.gov

3 rows where topics = "["compliance-conference", "discovery-scheduling", "matrimonial"]"

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: rule_number, title, topics (array)

doc_type 2

topics 1

  • ["compliance-conference", "discovery-scheduling", "matrimonial"] · 3 ✖

judicial_district 1

  • 1 3

county 1

provision_id ▼ doc_id judge_id rule_number title text source_page topics cross_references judicial_district county court_type doc_type
NY-SC-1JD-CAPITTI-001 Compliance Conference Order Form — IAS Part 9, Matrimonial Division (Hon. Linda M. Capitti) 38 NY-SC-1JD-CAPITTI FORM Compliance Conference Order — Required Contents The Compliance Conference Order for Part 9 covers: (I) Completed Discovery — categories include tax returns, credit card statements, checking/brokerage/savings account statements; (II) Outstanding Discovery — listing overdue items and disclosure due dates by NYSCEF No.; (III) Disputed Discovery — parties submit letter briefs of no longer than two (2) pages and proposed orders resolving the discovery dispute for court resolution at the conference; (IV) Special Master — appointment, subject matter, and cost allocation between plaintiff and defendant; (V) Depositions — deadlines for party and non-party depositions; (VI) End Date for Disclosure — all disclosure completed by a set date; (VII/VIII) Custody Issues — forensic evaluation status and other custody/parenting time issues; (IX) Status Conference — date, whether parties' appearances are excused, and whether conference is held virtually. 1 ["compliance-conference", "discovery-scheduling", "matrimonial"] [] 1 New York supreme court_form
NY-SC-1JD-TINGLING-001 Compliance Conference Order Form — IAS Part 28, Matrimonial Division (Hon. Aija Tingling) 40 NY-SC-1JD-TINGLING FORM Compliance Conference Order — Required Contents The Part 28 Compliance Conference Order covers: (I) Completed Discovery — tax returns, credit card statements, checking/brokerage/savings accounts (NYSCEF nos. and Bates numbers); (II) Outstanding Discovery — listed items with disclosure due dates; (III) Disputed Discovery — parties separately submit letter briefs of no longer than two (2) pages and proposed orders; (IV) Special Master — appointment, subject matter, and cost allocation; (V) Depositions — deadlines for party and non-party depositions; (VI) End Date for Disclosure — date certain for completion of all disclosure; (VII) Custody Issues — forensic evaluation anticipated completion date; (VIII) Other Custody/Parenting Time Issues; (IX) Status Conference — date, whether parties' appearances excused, and whether conference is held virtually. The failure to file this Compliance Conference Order in advance of the conference date may result in adjournment of the conference. 1 ["compliance-conference", "discovery-scheduling", "matrimonial"] [] 1 New York supreme court_form
NY-SC-1JD-WILKOFSKY-P51-007 Part 51 Rules – Matrimonial Division (Hon. Yael T. Wilkofsky) 87 NY-SC-1JD-WILKOFSKY Conferences – Compliance and Status Conferences Compliance and Status Conference Requirements Compliance Conferences (CC) and Status Conferences (StC): TUESDAY MORNINGS. The date for the CC will be set by the Court in the PC Order and will be held approximately 60 days after the PC, absent extenuating circumstances and considering case complexity. At least one (1) day prior to the CC, the parties are to upload a jointly completed proposed Compliance Conference Order to be so-ordered by the Court. The proposed Compliance Conference Order should address any outstanding discovery issues and the failure to do so may be deemed a waiver of same. All discovery shall be completed before the final StC.   ["compliance-conference", "discovery-scheduling", "matrimonial"] [] 1 New York supreme part_rules

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

CREATE TABLE provisions (
    provision_id TEXT PRIMARY KEY,
    doc_id INTEGER REFERENCES documents(doc_id),
    judge_id TEXT REFERENCES judges(judge_id),
    rule_number TEXT,
    title TEXT,
    text TEXT,
    source_page INTEGER,
    topics TEXT,
    cross_references TEXT,
    judicial_district INTEGER,
    county TEXT,
    court_type TEXT DEFAULT 'supreme',
    doc_type TEXT DEFAULT 'part_rules'
);