Evidence Index and Hearing Bundle Preparation Guide

Definitions

Field definitions

Controlled vocabulary guidance

Authenticity status

Examples: Not assessed, source located, custodian confirmed, system-generated, derived copy, disputed, counsel review pending, or status accepted for the stated operational purpose.

Governance: This label describes evidence handling and review state. It does not establish authorship, truth, foundation, legal authenticity, or admissibility.

Privilege and restriction status

Examples: No restriction identified, privilege review pending, privileged, work product, confidential, sealed or restricted, redaction required, redacted for delivery, or withheld under instruction.

Governance: Use qualified counsel or the designated legal reviewer for the decision. Keep the source and delivery version linked without broadening access to the source.

Exhibit lifecycle

Examples: Candidate, indexed, proposed, exchanged, marked, objected to, withdrawn, superseded, admitted per the court record, or not used.

Governance: Use only statuses recognized by the proceeding or counsel process. Do not label an item admitted based solely on internal preparation.

OCR and accessibility status

Examples: Not required, source text available, OCR complete, OCR reviewed, OCR exception, tagged and reviewed, accessibility exception, or pending approved remediation.

Governance: Separate machine processing from human review and accessibility testing. Preserve the source image and record languages, tools, versions, and limitations.

Delivery state

Examples: Draft, approved for delivery, sent, uploaded, accepted, received, usable, rejected, incomplete, corrected, superseded, or receipt pending.

Governance: A transmission event is not automatically a receipt or usable delivery. Retain attributable evidence and escalate rejected or inaccessible packages immediately.

Practical workflow

1. Confirm the proceeding and controlling instructions

   Identify the court, tribunal, jurisdiction, case or appeal number, hearing type, hearing date, filing or exchange deadline, required format, permitted delivery channels, page or exhibit rules, accessibility expectations, and any order or practice direction. Record the source and effective version of each instruction. Court-specific rules and counsel instructions control when they differ from this operational guide.

2. Define the bundle purpose and scope

   Write the purpose of the bundle, the hearing issue or agenda it supports, the parties and recipients, the time and subject-matter boundaries, included document classes, excluded populations, working assumptions, and approval owner. Separate candidate evidence, review material, authorities, demonstratives, administrative forms, and confidential work product so that an internal working set is not mistaken for the delivered bundle.

3. Freeze the source inventory

   Create an inventory of pleadings, correspondence, contracts, statements, reports, photographs, recordings, transcripts, orders, exhibits, disclosure, expert material, translations, and prior bundles. Capture source location, custodian, file name, document ID, file type, size, page count, date, version, access state, and known gaps. Record the inventory cut-off and route late additions through change control.

4. Assign stable document and exhibit IDs

   Assign identifiers that remain stable when a file name, folder, page range, or rendered format changes. Keep document ID, source ID, bundle position, and exhibit reference as separate fields. Record the approved exhibit-label convention and any reserved, duplicate, withdrawn, disputed, or not-for-use labels. Do not infer the court record from a filename or an unapproved label.

5. Capture provenance and source custody

   For every included item, record the source system or custodian, original path or reference, collection or receipt event, actor or service, date and time zone, method, source format, original file state, transformations, transfers, and current version. Preserve original or controlled source material and link every rendered, translated, OCR, redacted, or compressed derivative to its predecessor.

6. Resolve versions and duplicates

   Compare duplicate candidates by document ID, content, date, author, source, hash or equivalent marker, visible changes, and legal significance. Identify the canonical version for the intended bundle, retain superseded versions under access control, and record whether a difference is substantive, formatting-only, translation-related, OCR-related, or unresolved. Never silently overwrite a version used in a prior review or delivery.

7. Apply privilege, confidentiality, and redaction review

   Route privilege, work product, sealed, confidential, personal, client-restricted, and third-party material to qualified counsel or the designated legal reviewer. Record the decision, scope, basis, approver, redaction method, redacted version, unredacted source location, and disclosure restriction. Check that hidden layers, comments, metadata, attachments, thumbnails, OCR text, bookmarks, and searchable terms do not disclose content that the visible redaction appears to remove.

8. Manage translations and language variants

   For each translated item, record the original, language pair, translator or service, instructions, date, version, certification or qualification information if required, quality review, terminology decisions, and unresolved differences. Keep the original and translation linked. Counsel must decide whether the proceeding requires a certified translation, a particular format, an interpreter, or disclosure of both language versions.

9. Process OCR and accessibility requirements

   Preserve the source image and add OCR only when it serves search, navigation, extraction, or accessibility needs. Record engine or service, version, processing date, language, confidence or exception state, and human review for high-risk pages. Test text selection, reading order, tags, headings, tables, bookmarks, document language, keyboard operation, contrast, zoom, screen-reader behavior, captions or alternatives for non-text material, and the approved viewer or filing format.

10. Set page numbering and rendering controls

    Confirm whether the court or counsel requires source page numbers, continuous bundle pages, Bates-style identifiers, exhibit labels, section numbering, bookmarks, hyperlinks, or a separate index pagination scheme. Render the exact delivery version, record the rendering tool and settings, reconcile page count, inspect inserted covers and separators, and ensure that every index range and cross-reference points to the delivered pages rather than a working copy.

11. Reconcile references and exhibit relationships

    Check every reference in the index, chronology, pleadings, submissions, witness materials, expert reports, hearing notes, and counsel list against the canonical document and page range. Record cross-references, duplicate references, missing items, withdrawn items, referenced-but-not-included material, and documents that span multiple exhibits. Escalate conflicting labels or page references instead of choosing one silently.

12. Build the index and bundle manifest

    Generate the index from controlled fields, not manual copy and paste. Include document ID, exhibit reference, description, date, author or source where permitted, version, language, page range, confidentiality or redaction status, authenticity status, and notes required by the proceeding. The manifest should list every component, its version, rendered page count, inclusion state, and integrity or delivery marker where used.

13. Run quality checks and legal review gates

    Run automated and human checks for missing IDs, duplicate IDs, duplicate exhibit labels, blank or corrupt files, page-count mismatches, broken links, unresolved placeholders, incorrect ordering, missing translations, OCR failures, accessibility defects, redaction leakage, privilege flags, outdated versions, inconsistent references, and unauthorized content. Obtain named counsel approval for legal treatment and named operations approval for technical completeness.

14. Deliver through the approved channel

    Use only the court-, tribunal-, clerk-, counsel-, or organization-approved delivery method. Record the recipient, sender, channel, encryption or access controls, file or package name, bundle version, manifest, timestamp, time zone, size, integrity marker where used, and any transmission limits. Do not treat a successful upload or sent message as receipt unless the approved process provides attributable acceptance evidence.

15. Capture receipt and confirm usable access

    Obtain and store delivery confirmation, filing receipt, portal acceptance, secure-transfer receipt, or recipient acknowledgment as appropriate. Confirm that the received version opens, renders, searches, follows the approved page scheme, and is accessible to the intended users. Record bounced, rejected, quarantined, incomplete, or inaccessible deliveries as exceptions with immediate escalation.

16. Control changes, corrections, and fallback

    After approval or delivery, prohibit ad hoc replacement. Log each requested change, reason, source, impact, affected IDs and pages, legal reviewer, technical reviewer, approval, new bundle version, superseded version, recipients, and re-delivery or correction evidence. Maintain an approved fallback copy and recovery route, but do not distribute it until the responsible court or counsel process authorizes the action.

Comparison

Limitations and exceptions

• Court-specific rules, tribunal directions, local practice, filing requirements, and qualified counsel instructions control the bundle. This guide cannot determine which materials must be filed, exchanged, marked, translated, certified, admitted, or withheld.
• An authenticity status, hash, provenance record, custodian confirmation, or quality check does not guarantee admissibility, authenticity, completeness, relevance, foundation, or a favorable evidentiary ruling.
• Privilege, work product, confidentiality, sealing, redaction, personal information, client restrictions, and third-party rights require matter-specific legal review. A technical label or automated redaction cannot replace that decision.
• OCR can introduce substitutions, omissions, reading-order errors, and false search results. Preserve the source image, label machine-generated text, and route high-risk or low-confidence material for human review.
• A translation can be incomplete, ambiguous, or materially different from the original even when a translation provider supplied it. Counsel must decide the required standard, certification, use, and resolution of disagreements.
• Accessibility checks depend on the file format, viewer, assistive technology, language, device, and proceeding. Passing a structural or automated check does not prove that every intended user can use the delivered bundle.
• Page counts, exhibit labels, hyperlinks, and indexes can become stale after rendering, redaction, translation, or replacement. Re-render and reconcile the exact delivery version after every material change.
• Delivery evidence shows what happened through the approved channel; it does not prove that a court, counsel, party, or witness reviewed, understood, accepted, or could lawfully use every item.
• This is an organization-designed operational workflow, not legal advice, a chain-of-custody opinion, a records schedule, a translation certification, or a promise about any court outcome.

Primary sources

Methodology

This guide uses an organization-designed evidence-index and bundle-production method. Court-specific rules, tribunal directions, local practice, filing instructions, and qualified counsel instructions control; reconcile any conflict before production. Start with a signed scope and instruction record containing court or tribunal, jurisdiction, case number, parties, hearing purpose, deadline, recipients, format, accessibility, translation, exhibit, and delivery requirements. Maintain a source inventory with stable document IDs, source references, custodians, collection or receipt events, file formats, versions, dates, page counts, language, privilege and redaction state, authenticity status, access restrictions, and known gaps. Keep source, derivative, translated, redacted, OCR, and rendered versions linked and never overwrite a previously approved or delivered artifact. Use a bundle manifest to reconcile component IDs, file versions, page counts, page ranges, exhibit references, indexes, bookmarks, hyperlinks, and delivery markers. Recommended operational measures are bundle metadata completeness = in-scope bundle records with all required identity, source, version, treatment, and page fields / all in-scope bundle records x 100, with records as the unit; provenance coverage = in-scope records with source reference, custodian, collection or receipt event, method, timestamp, and transformation state / all in-scope records x 100, with records as the unit; page reconciliation rate = documents whose rendered page count and indexed page range agree for the approved delivery version / all paginated documents in the delivery set x 100, with documents as the unit; cross-reference accuracy = tested index, exhibit, submission, chronology, and hyperlink references that resolve to the intended document and page / all tested references x 100, with references as the unit; redaction verification coverage = delivered redacted items with visible-content, text-layer, metadata, attachment, thumbnail, and search-leakage checks recorded / all delivered redacted items x 100, with items as the unit; quality exception closure rate = quality exceptions closed or explicitly approved as residual risk before delivery / all quality exceptions identified for the delivery version x 100, with exceptions as the unit; receipt coverage = required recipients or delivery endpoints with attributable receipt or approved acceptance evidence for the exact bundle version / all required recipients or endpoints x 100, with recipients or endpoints as the unit; and change-control completeness = post-baseline changes with reason, impact, approval, new version, supersession, affected-page analysis, and delivery decision / all post-baseline changes x 100, with changes as the unit. Publish numerator, denominator, scope, exclusions, version, reviewer, and date. Do not exclude failed, missing, rejected, disputed, or inaccessible items merely to improve a rate. Example starting bands such as metadata completeness >= 98%, provenance coverage = 100%, page reconciliation = 100%, cross-reference accuracy = 100% for the tested set, redaction verification = 100%, quality exception closure = 100% before release, and receipt coverage = 100% are organization-designed controls, not legal or universal thresholds. A failed quality check is an escalation trigger; it is not a legal conclusion. Re-run the full index, render, accessibility, redaction, page, reference, manifest, and delivery checks after any material source, counsel instruction, privilege, redaction, translation, OCR, rendering, page, exhibit, recipient, or court-direction change. Preserve the approved bundle and an access-controlled fallback with its own version and integrity record, and release the fallback only through the authorized process.

FAQs

Related CaseDocker capabilities

Related guides and resources

• Litigation document chronology guide
• Litigation matter intake checklist
• Legacy litigation data migration guide
• Legal document OCR and search requirements