> For the complete documentation index, see [llms.txt](https://docs.cottfile.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cottfile.com/reference/document-requirements.md). # Document Requirements This page covers file format rules, size limits, document types, and special document handling in Cott E-Filing. *** ## File Format All uploaded documents must be in **PDF format**. The system validates the MIME type on upload and rejects non-PDF files. {% hint style="warning" %} Word documents (.docx), images (.jpg, .png), and scanned TIFFs must be converted to PDF before uploading. Most word processors and scanners have a "Save as PDF" or "Export to PDF" option. {% endhint %} *** ## Size Limits | Limit | Maximum | | ------------ | ------- | | **Per file** | 500 MB | If a single document exceeds 500 MB, reduce its size before uploading. Common approaches: * Re-scan at a lower resolution (150-200 DPI is sufficient for most court documents) * Use a PDF compression tool to reduce file size * Split large documents into multiple parts *** ## Document Types Each document you upload must be assigned a **document type** that matches the kind of filing you are making. The available document types depend on the case type you selected in the first step of the wizard. Common document types include: * Petition / Complaint * Answer / Response * Motion * Memorandum * Order (proposed) * Exhibit * Affidavit / Declaration * Subpoena * Notice * Judgment * Stipulation {% hint style="info" %} Court administrators configure which document types are available for each case type. If you do not see the document type you need, contact the court. {% endhint %} *** ## Lead Document Every filing must have exactly **one lead document**. The lead document is the primary document in your filing -- the one that drives the docket entry. For example: * In a new case filing, the lead document is typically the **Petition** or **Complaint** * In a motion filing, the lead document is the **Motion** itself * Supporting exhibits, memoranda, and affidavits are non-lead documents Mark your lead document using the **Lead** toggle in the document upload step. The lead document appears first in the clerk's review and is used to generate the primary docket entry. {% hint style="info" %} **📹 GIF:** In the document upload step of the filing wizard -- uploading two PDF files, setting the document type for each, toggling the Lead switch on the primary document, and entering document titles. {% endhint %} *** ## Page Count The system automatically detects and records the page count for each uploaded PDF. Page counts are used for: * **Per-page fee calculation** -- Some fee schedules charge by the page * **Clerk review** -- Clerks can see how many pages each document contains * **Docket entries** -- Page counts are recorded in the CMS You do not need to manually enter page counts. The system reads them from the PDF. *** ## Sealed Documents If a document contains sensitive information that should not be publicly accessible, mark it as **Sealed** during upload. Sealed documents: * Are stored with restricted access * Are flagged in the clerk's review interface * Are recorded in the CMS with a sealed indicator * Are not included in public docket searches {% hint style="warning" %} Marking a document as sealed does not automatically grant a sealing order. The court must approve the sealing. Check your court's local rules for sealing requirements. {% endhint %} *** ## Redacted Documents If a document contains personally identifiable information (PII) that must be removed before it becomes part of the public record, mark it as **Redacted** during upload and upload the redacted version. Clerks also have redaction tools available during review: * **PII detection** -- The system can scan a PDF for common PII patterns (Social Security numbers, dates of birth, phone numbers, email addresses) * **Manual redaction** -- Clerks can draw redaction rectangles over sensitive areas in the document viewer Redacted versions are stored separately from the original, and the redacted path is tracked in the filing record. {% hint style="info" %} **📹 GIF:** Marking a document as Sealed and Redacted during upload -- toggling the Sealed checkbox and the Redacted checkbox on a document in the upload panel, with the flag badges appearing on the document card. {% endhint %} *** ## Summary Checklist Before submitting your filing, verify: * [ ] All documents are in **PDF format** * [ ] No single file exceeds **500 MB** * [ ] Each document has the correct **document type** assigned * [ ] Exactly **one document** is marked as the **lead document** * [ ] Sensitive documents are marked as **sealed** or **redacted** as appropriate * [ ] Page counts look correct (the system detects these automatically) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.cottfile.com/reference/document-requirements.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.