A court filing readiness checklist gives a legal team a final control point before submission. It connects the approved document to its authorities, annexures, signatures, technical files, submitter, payment, and acknowledgement. The aim is not to reduce filing to box-ticking. It is to catch operational defects without obscuring counsel's responsibility for substance and procedure.
Requirements vary across courts, case types, filing modes, and current directions. Build the checklist from the official material for the actual forum, then store the version or access date used. A reused template is a starting point, never proof of compliance.
What should be confirmed before drafting begins?
Readiness starts when the task is opened. Record the court and jurisdiction, proceeding or proposed proceeding, document type, filing purpose, authority to act, stated or calculated deadline, responsible counsel, approvers, and filing channel. Link each field to a source where possible.
| Opening question | Evidence to retain |
|---|---|
| What is being filed and in which matter? | Order, instruction, notice, or approved matter record |
| Which forum and filing mode apply? | Current official rule, direction, or portal instruction |
| Who may sign, affirm, approve, and submit? | Authority record and counsel confirmation |
| What is the filing date? | Source event, calculation basis, assumptions, reviewer |
| What documents or fees must accompany it? | Requirement list tied to official source |
| Who owns defect resolution? | Named lawyer and operational contact |
For Indian eFiling, the official eCourts eFiling portal is a primary source for services and published user material within its scope. The Supreme Court of India handbook page provides official practice and procedure resources for the Supreme Court. Counsel should also check the current rules, practice directions, circulars, and registry guidance specific to the forum.
How should dates and authority be verified?
Separate the source event from the calculated filing date. Save the order, notice, service record, portal record, or other material that starts the calculation. Record the rule or direction counsel applied, exclusions or assumptions, calculation, reviewer, and review time. Keep internal drafting milestones in another field.
The Limitation Act, 1963 is official statutory material for limitation questions within its scope. The Code of Civil Procedure, 1908 is official statutory material for civil procedure within its scope. Neither a calendar tool nor this checklist determines how those provisions apply to a particular filing.
Authority controls should identify who instructed the filing, who approved the final position, who may execute or affirm documents, and who is authorised to use the filing account. If an authorisation, vakalatnama, board record, affidavit, or other supporting instrument may be required, route it to counsel for confirmation and preserve the approved version.
What belongs in the substantive review gate?
Substantive approval belongs to qualified counsel. The workflow should make that approval explicit and bind it to a stable document version. A later formatting edit should not silently alter approved language.
Use a versioned review sequence:
- Assign a drafting owner and source set.
- Link propositions, dates, quotations, and references to reviewable sources.
- Complete legal and factual review under counsel's process.
- Resolve comments or record open issues.
- Produce a named approval version.
- Lock or checksum that version before production changes.
- Compare the filing file against the approved text after conversion.
Where a filing uses a dated factual narrative, connect it to an evidence-linked litigation chronology. Confirm that allegations are attributed, quotations match the cited source, and uncertain dates are not presented with false precision.
Counsel approval checklist
- correct proceeding, parties, and document type;
- relief or purpose reviewed by responsible counsel;
- facts, dates, quotations, and authorities checked;
- confidentiality, privilege, redaction, and sealing questions addressed;
- declarations, verifications, affidavits, or certificates confirmed;
- signature and authority requirements confirmed;
- annexure references and defined terms reconciled; and
- final substantive version and approver recorded.
How do you check annexures, exhibits, and citations?
Create an annexure register rather than relying on filenames. For each item, record its label, title, date, source ID, page range, confidentiality treatment, version, and references in the main document. Then test both directions: every text reference points to the right annexure, and every annexure is actually referenced or intentionally included.
| Check | Common defect |
|---|---|
| Label sequence | Missing, duplicate, or inconsistent label |
| Source match | Draft or wrong version attached |
| Internal reference | Paragraph points to another annexure |
| Pagination | Index and PDF page numbers diverge |
| Legibility | Scan, stamp, signature, or text is unreadable |
| Completeness | Page or attachment omitted |
| Redaction | Hidden text or metadata remains |
| Orientation | Rotated or incorrectly sized pages |
Open every final attachment after assembly. Automated checks can find broken sequences or missing files, but visual inspection catches blank pages, clipped seals, unreadable scans, and conversion errors.
What technical checks are needed for electronic filing?
Follow the current portal guidance rather than assuming a universal file specification. Confirm supported format, file size, naming, pagination, bookmarks, searchable text, signatures, and any required forms or structured fields. Validate the actual final files on the intended submission device and account.
Technical readiness checklist:
- final filenames follow current instructions;
- files open without repair warnings;
- page count matches the approved index;
- text and images are legible at normal review size;
- OCR has not replaced or distorted the source image;
- links, bookmarks, and navigation work where required;
- signatures and attestations appear in the intended locations;
- metadata and hidden content have been reviewed;
- redactions are applied safely and visually checked;
- file limits and portal validations are satisfied; and
- a secured filing copy is stored before upload.
Security should remain part of file preparation. Avoid unapproved public converters for confidential records. Use controlled access, documented transfer paths, and an incident escalation route. Teams considering workflow tooling can review Gotham's security approach, then verify the actual deployment and settings against their requirements.
How should the submission itself be controlled?
Plan the operational handoff before the deadline. Confirm the authorised submitter, account access, authentication method, payment route, contact person, and contingency process. Do not share credentials through the matter record. A second person can review the final file list and key portal fields before the authorised submitter confirms submission.
Capture a submission record with:
- final file identifiers or hashes;
- submitter and approving counsel;
- date, time, and time zone;
- portal or physical filing channel;
- entered case and party details;
- fee or transaction reference where applicable;
- generated diary, filing, or acknowledgement reference;
- screenshots or receipts permitted by policy; and
- any error, interruption, or repeated attempt.
Gotham's legal workflows and practice solutions can help a team assess connected document, approval, and task handling. The filing portal or registry remains authoritative for submission status.
Is an upload confirmation the same as an accepted filing?
No universal status should be inferred from a successful upload. Portals and registries may distinguish submission, payment, scrutiny, defect, resubmission, registration, acceptance, or listing. Record the exact label shown and preserve its source. Do not rewrite “submitted” as “filed and accepted” unless the authoritative record supports that statement.
Use a post-submission loop:
- Save the immediate acknowledgement and transaction record.
- Confirm the final files associated with the submission.
- Monitor the official channel for scrutiny or status changes.
- Assign defects to counsel and an operational owner.
- Preserve corrected versions and resubmission references.
- Update the matter calendar only from verified status information.
- Complete service or communication steps as directed by counsel.
The official eCourts Services portal and Supreme Court of India website can support status checks within their scope. Verify the actual matter through the relevant official channel.
How can a team run a final filing huddle?
For a material filing, a short final review can align substance, documents, technology, and ownership. Display the approved version, annexure register, verified deadline, submitter, portal requirements, unresolved exceptions, and post-filing owner. Require explicit answers instead of “it should be fine.”
The huddle ends with one of three states: ready for authorised submission, ready subject to a named correction, or not ready pending counsel decision. Record the state and time. If a file changes, repeat the checks affected by that change.
A court filing readiness checklist is valuable because it makes handoffs observable. It cannot guarantee registry acceptance or legal sufficiency, but it can reveal missing sources, mismatched versions, technical defects, and unclear ownership before submission. Explore Gotham's litigation discovery workflow, browse broader legal workflows, or talk to the team about a source-linked filing process.
