An injury file may contain a native photograph, an emailed copy, a screenshot of that photograph, a compressed portal version, a printed exhibit, an annotated working image, and a slide using a crop from the same source. Treating all of them as the “original” hides changes and makes later verification difficult. The same problem can affect messages, videos, medical records, reports, spreadsheets, audio, and other electronic files.

A source-control record should identify the claimed original, each duplicate or derivative copy, the custodian and collection path, file or page characteristics, alterations, working summaries, missing material, and the exact source supporting every summary entry.

Classify the item before renaming or converting it

  • Native file obtained from the device, application, account, system, camera, provider, agency, employer, insurer, or other custodian
  • Export created by that system, downloaded portal record, printed system output, certified copy, scan, photograph of a page, screenshot, forwarded attachment, or re-recording
  • Exact duplicate, derivative copy, compressed copy, converted file, excerpt, crop, transcription, translation, redacted copy, annotated copy, compilation, or summary
  • Unknown generation or source kept as unknown until the collection path can be established

Use the evidence-rule terms carefully

North Carolina Rule of Evidence 1001 defines writings, recordings, photographs, originals, and duplicates for Article 10. Among other provisions, it addresses computer-stored data and output shown to reflect the data accurately. The rule’s definition is a legal one; a device owner’s folder named “originals” does not settle the question.

Rule 1002 states the requirement of an original to prove the content of a writing, recording, or photograph except as otherwise provided by the rules or statute. Rule 1003 addresses the admissibility of duplicates and its stated exceptions. These provisions do not mean that every duplicate, screenshot, or printout is automatically authentic, complete, admissible, or persuasive.

Record provenance for each source item

  • Item identifier, description, date created if known, creator, custodian, device or system, account, application and version, and collection date
  • Person who collected it, authority or permission, export or copy steps, transmission method, recipient, storage location, and later transfer
  • Original file name, extension, byte size, page count or duration, resolution, timestamps, hash when available, and related metadata
  • Password, encryption, proprietary format, missing codec, inaccessible account, corrupted file, or incomplete export documented without altering the source

Preserve messages and email in context

  • Complete thread, sender, recipients, copied recipients, subject, dates, time zone, message identifiers, headers when available, attachments, reactions, edits, and deletions
  • Text or messaging export retained in addition to screenshots, with adjacent messages sufficient to understand the exchange
  • Voicemail or audio retained in its native file when available, plus a working transcription labeled as a transcription
  • Forwarded, quoted, printed, copied, or pasted message linked to the source account and complete version

Keep images, video, and audio unaltered at the source level

  • Native media preserved before crop, rotation, brightness change, stabilization, enhancement, speed change, frame extraction, annotation, or format conversion
  • Working edit receives a new identifier and a change log stating the software, setting, operator, date, and purpose
  • Screenshot or exported clip points to the full recording, relevant time range, time-display behavior, and whether frames before or after were omitted
  • No generative fill, object removal, synthetic frame, voice alteration, or other content-changing process applied to a copy presented as a faithful source

Control medical, agency, and business-record versions

  • Request, authorization or legal process, custodian, date range, categories, format, delivery, certification, page count, and missing-item notice
  • Portal view, formal record production, billing production, imaging disc, native image, report, corrected report, addendum, and later supplement kept as separate versions
  • Blank pages, duplicate pages, changed pagination, redactions, Bates numbers, cover letters, and custodian declarations retained
  • Working highlight, bookmark, extraction, OCR text, spreadsheet, or issue note never saved over the supplied record

Build summaries that can be audited

  • Summary title, purpose, preparer, version, date, fields, inclusion rules, exclusions, calculations, and review status
  • Every row links to a source item, page, timestamp, cell, image, or other precise location
  • Direct quotation, paraphrase, calculation, classification, inference, and unknown labeled separately
  • Source correction or later production triggers a dated summary revision without deleting the prior version
  • Underlying records remain available; the summary does not become the only evidence of their contents

Authenticate identity separately from copy status

North Carolina Rule of Evidence 901 addresses evidence sufficient to support a finding that an item is what its proponent claims. Its illustrations include witness knowledge, distinctive characteristics, public records, and a process or system. A file can be an accurate duplicate yet still require evidence identifying the item, source, completeness, and context.

Use an alteration and exception log

  • Item, issue, discovery date, affected version, source consulted, person assigned, response, correction, and resolution
  • Missing original, source device unavailable, incomplete export, unreadable page, corrupt media, wrong account, mismatched hash, or changed metadata documented
  • Lawful redaction, confidentiality protection, court order, privilege review, or access restriction recorded without modifying the preserved source copy
  • Reason a derivative was created and exact limitation on the conclusion it can support

The related version-controlled injury-file index guide explains naming, indexing, status, and revision control across the larger file. This page owns the narrower relationships among originals, duplicates, exports, derivative working copies, and summaries.

Rosensteel Fleishman Car Accident & Injury Lawyers provides general information about North Carolina personal-injury matters involving disputed record versions. Authentication, admissibility, completeness, privilege, and evidentiary weight depend on the item, purpose, applicable law, and complete record.

Sources