An injury matter may involve an incident report, insurance claim, medical-record request, authorization, demand, court filing, discovery paper, and other documents. Each can have a different recipient, delivery rule, deadline, and legal effect. A single “filed” column hides those differences and can create false confidence when a document was sent but not received, received but not accepted, or accepted by the wrong entity.

A submission log should identify the exact document version, sender, intended recipient, legal entity, claim or case number, delivery method, date and time, confirmation, response, and next action without treating “sent,” “received,” “filed,” and “served” as interchangeable statuses.

Define the submission type before recording status

  • Notice or incident report to a business, employer, property manager, agency, or other recipient
  • Insurance claim report, supporting document, authorization, response, demand, or appeal sent to a carrier or administrator
  • Medical, billing, employment, public-record, or other information request sent to a custodian
  • Complaint, motion, pleading, notice, discovery paper, exhibit, or other litigation document
  • Internal working draft, attorney-client communication, and produced document kept outside a public or recipient-facing submission set

Freeze the exact version that was sent

  • Document title, version number, date, author, page count, attachment list, file name, format, and hash when available
  • Signed and unsigned versions, corrected version, redacted version, native file, PDF, exhibit, and cover message identified separately
  • Recipient name, legal entity, department, address, email, portal, fax, court, or agency selected from a reliable current source
  • Confidential, medical, financial, or identifying information reviewed for secure transmission and appropriate scope

Record transmission evidence

  • Sender, account or device, delivery method, date, time, timezone, recipient, and subject or portal category
  • Email header, portal confirmation, fax confirmation, certified-mail record, tracking result, hand-delivery receipt, electronic filing receipt, or other source
  • Failed delivery, bounce, rejected upload, size limit, wrong recipient, missing attachment, duplicate, withdrawal, or corrected resubmission logged as a separate event
  • Automated message preserved without assuming that it proves human review or acceptance

Keep informal claim activity separate from a lawsuit

North Carolina Rule of Civil Procedure 3 addresses commencement of a civil action. Reporting an event to an insurer, receiving a claim number, sending records, or negotiating does not by itself show that a civil action has been commenced.

North Carolina Rule of Civil Procedure 5 addresses service and filing of specified pleadings and other papers after a case is underway and includes certificate-of-service requirements. Rule 4 and other procedures can govern different documents. The correct filing and service method depends on the paper, recipient, court, case posture, and current rules.

Track filing, service, and court acceptance separately

  • Submitted to court, accepted, file-stamped, rejected, returned for correction, docketed, and later amended treated as different statuses
  • Court file number, county, division, case caption, filing code, lead document, attachments, filing fee, waiver, and receipt as shown in the source
  • Service recipient, address of record, method, date, certificate, automated electronic-service record, and any acceptance or return
  • Deadline calculation and procedural choice sent for qualified legal review rather than inferred from an automated receipt

The North Carolina Judicial Branch’s eCourts page links current statewide court systems and filing resources. System availability, eligible users, case types, filing codes, and procedures can change. Preserve the current instruction used, submission receipt, and court response rather than relying on an old screenshot or article.

Connect each response to the submission it addresses

  • Acknowledgment, claim number, request for information, reservation, denial, partial response, acceptance, objection, or no response located
  • Responder, legal entity, date, delivery method, subject, claim or case number, document version addressed, and next stated action
  • Response deadline, appointment, requested attachment, correction, or follow-up linked to a responsible person and source
  • A response that addresses only one attachment or issue not applied to the entire submission package

The related guide to reading an insurance claim acknowledgment after a North Carolina injury explains what that particular response may contain. The submission log should link the acknowledgment to the precise report or document set that produced it and keep unanswered items visible.

Preserve authenticity and corrections

North Carolina Rule of Evidence 901 addresses authentication and includes examples involving witness knowledge, distinctive characteristics, telephone conversations, public records, and a process or system. Whether a receipt, email, portal export, tracking record, or court notice is usable for a particular purpose depends on its source, context, completeness, and foundation.

  • Keep original messages, headers, attachments, receipts, envelopes, labels, and native exports
  • Record corrections and resubmissions as later events instead of overwriting the failed or earlier version
  • Use a read-only submission set and a separate working tracker
  • Do not treat an internal spreadsheet entry as proof when the supporting transmission record is missing

A North Carolina personal-injury matter involving disputed submission or receipt may require immediate review of the underlying document, current procedure, recipient, deadline, and transmission evidence. This article provides a tracking method, not filing instructions for a specific matter or a prediction about acceptance, timeliness, legal effect, or recovery.