Business Records in North Dakota Criminal Trials
Calling a document a “business record” does not make it admissible. In a North Dakota criminal case, the proponent must prove how the record was created…
Rule 803(6), qualified witnesses, custodial affidavits, Rule 902 notice, electronic records, financial records, medical charts, phone and location logs, receipts, third-party information, hearsay within hearsay, authentication, completeness, summaries, trustworthiness, confrontation, objections, and trial proof
Business Records in North Dakota Criminal Trials
Calling a document a “business record” does not make it admissible. In a North Dakota criminal case, the proponent must prove how the record was created, when it was made, who supplied the information, why the organization kept it, whether making it was a regular practice, and whether a qualified witness or compliant certification supplies the foundation. Authentication, embedded hearsay, completeness, trustworthiness, and the Confrontation Clause remain separate questions.
Rule 803(6) requires proof, not intuition
The business-records exception rests on habits of accurate recordkeeping, not on the paper’s appearance. Organizations rely on routine records to bill customers, track inventory, schedule staff, provide treatment, account for money, and operate systems. That operational dependence may support reliability. A record assembled for a lawsuit, altered for investigators, or populated with information from outsiders has a different reliability profile and requires closer scrutiny.
Rule 803(6) is broad about the kind of activity covered. A “business” can be a company, nonprofit organization, occupation, profession, or other calling. The exception can cover digital data as well as paper. Breadth does not eliminate the five express conditions or the separate rules governing authenticity, relevance, original-record proof, unfair prejudice, privilege, and constitutional confrontation.
1. What exact record is the proponent offering?
Begin with the exhibit actually offered, not the source organization in the abstract. A native database export, a customer-facing statement, an investigator’s spreadsheet, a screenshot, a PDF assembled from selected pages, and a demonstrative chart may derive from the same account but are not the same record. Identify the file, date range, fields, source table, export method, page selection, and any processing after retrieval.
This distinction mattered in Henderson. An insurance exhibit was described as a condensed version of much larger binders, but the detective did not explain how the condensed documents came into existence or authenticate the altered compilation. 2024 ND 42, ¶ 23. A proponent cannot avoid foundation questions by giving a curated packet the same name as the provider’s original records.
2. Was the record made at or near the time?
Rule 803(6)(A) requires contemporaneity. Ask when the event occurred, when the source information entered the system, when the displayed field was calculated, and when the offered report was generated. A report printed yesterday may reproduce entries made years ago; the relevant timing is ordinarily the entry of information, but later calculations, corrections, migrations, or annotations can create new records requiring explanation.
Not every field shares one timestamp. A transaction may have authorization, posting, settlement, reversal, and statement dates. A medical chart may show service time, note-entry time, signature time, and later amendment time. A phone log may record network time while an analyst’s column reflects a later conversion. Treating one date as the creation time for the entire exhibit can hide delay or alteration.
3. Did a person with knowledge supply the information?
The rule requires someone with knowledge at the beginning of the information chain. A cashier may enter a sale personally observed; a machine may automatically record a network event; a nurse may chart a measurement taken during treatment. When the source is a customer, bystander, unidentified caller, or investigating officer, the source may not have a business duty to report accurately. The custodian’s duty to save a statement does not prove the outsider’s statement true.
For automated data, counsel should ask whether a human assertion is involved at all. A device-generated timestamp or sensor value may raise authentication and system-accuracy issues rather than hearsay. Human-entered names, addresses, transaction descriptions, complaint narratives, and reason codes are assertions. An exhibit can combine machine data, employee entries, customer statements, and investigator labels, each needing its own analysis.
4. Was the record kept in a regularly conducted activity?
The organization must keep the record as part of what it regularly does. A one-time memo written after a subpoena, an investigator-requested interpretation, or a reconstruction prepared by counsel is not transformed into a routine record because an employee created it on company letterhead. Identify the ordinary operational purpose, frequency, users, retention practice, and consequences of inaccurate entries.
Records can be routine even if the underlying event is unusual. A hospital may regularly chart rare injuries; a bank may routinely document fraud holds; a carrier may automatically log uncommon network events. The question is whether this kind of record is routinely made and maintained, not whether this particular incident happens often. The distinction should be established through foundation testimony, not assumed.
5. Was making the record a regular practice?
Keeping records and regularly making this kind of record are related but distinct conditions. A company may retain whatever customers send without routinely verifying or organizing it. A police department may save a merchant’s documents in an investigative file, but that does not establish the merchant’s regular practice. Ask who triggers creation, whether every comparable event produces a record, what fields are mandatory, and how exceptions are handled.
Optional free-text notes deserve particular attention. A system may automatically create a transaction row while an employee occasionally adds a narrative. The automatic row may satisfy a regular-practice foundation; the narrative may not. A global statement that “these are our regularly kept records” should not replace testimony about the disputed field, attachment, comment, image, or calculated column.
6. Do the source, method, or circumstances indicate untrustworthiness?
Once the proponent establishes Rule 803(6)(A) through (D), the opponent may show that the source or preparation indicates a lack of trustworthiness. Relevant facts include litigation motive, unusual delay, manual override, selective export, missing audit logs, inconsistent versions, unexplained corrections, poor quality controls, inaccessible source data, unreliable software configuration, or a recorder who had reason to misstate the event.
Trustworthiness is not a general invitation to argue that every adverse record is wrong. The challenge should identify a concrete defect tied to the offered assertion. A missing timezone may undermine a minute-by-minute alibi comparison but not the existence of an account. An unverified customer name may undermine identity but not proof that a transaction occurred. Narrow objections are more credible and more likely to produce tailored relief.
A “qualified witness” need not be the author—but must know the system
Rule 803(6)(D) permits foundation testimony from the custodian or another qualified witness. The witness need not have entered each transaction or work for the entity that originally created every integrated record. The witness must, however, possess enough familiarity to explain how the particular record came into existence in the ordinary course of the relevant activity.
Henderson states the rule directly: “a qualified witness is someone who can explain the record keeping system of the business.” 2024 ND 42, ¶ 19 (quoting Command Center, Inc. v. Renewable Resources, LLC, 2021 ND 59, ¶ 33, 956 N.W.2d 755). The term is broadly construed, but breadth concerns who may qualify; it does not erase what the witness must know.
A detective who subpoenaed records usually can testify about receipt, custody, and investigative use. That does not necessarily establish the provider’s entry procedures, timing, regular practice, system controls, or meaning of proprietary fields. In Henderson, the detective’s receipt of documents and common-sense belief about receipts did not satisfy Rule 803(6)(D). 2024 ND 42, ¶¶ 20–24.
Cross-examination should be exhibit-specific. Ask whether the witness has used the source system; knows who enters data; understands mandatory and optional fields; can distinguish automatic from manual entries; knows how corrections appear; can explain report parameters; knows whether the export is complete; and can identify post-export formatting. “Are these kept in the ordinary course?” is a conclusion. The foundation lies in the underlying facts.
Third-party records integrated into another business’s files
An organization may integrate and rely on records created by another entity. The receiving organization’s witness can sometimes provide the foundation if the records were incorporated, relied upon in ordinary operations, and otherwise satisfy Rule 803(6). But mere possession is not integration. Saving an attachment in a case file, investigative folder, or customer account does not by itself prove reliance or the creator’s regular practice.
Ask what verification occurred before integration, whether the recipient routinely rejects defective records, how the recipient uses them, and whether the proponent offers the creator’s record or a new compilation. If a collection agency imports creditor data or a hospital imports outside laboratory results, the foundation should explain both the transfer and the operational reliance that supposedly supplies reliability.
Knowledge of content is different from knowledge of recordkeeping
A custodian need not know whether the recorded event truly occurred. The custodian must know the procedures that make the record admissible. Conversely, a witness may know the underlying event but know nothing about the database or report. That witness might authenticate content through personal knowledge under Rule 901, yet still fail to establish the business-records exception.
Counsel should avoid merging the roles. One witness may authenticate a store video, another explain the point-of-sale database, a third identify the purchaser, and an analyst explain a summary. The State may use multiple witnesses. The defense can insist that each evidentiary proposition be tied to testimony that actually supports it, instead of allowing one witness’s general familiarity to float across unrelated exhibits.
Rule 902(11) permits certification, but imposes notice and content requirements
N.D.R.Ev. 902(11) makes an original or copy of a domestic regularly conducted record self-authenticating when a custodian or other qualified person certifies, under penalty of perjury, that the record satisfies Rule 803(6)(A) through (C). The proponent must provide written notice, the record, and the certification at least fourteen days before trial or hearing so the opponent has a fair opportunity to challenge them.
A certification is not a magic cover sheet. Confirm that it identifies the record, the organization, and the signer’s qualification; addresses contemporaneous creation by a knowledgeable source; states that the record was kept in the regularly conducted activity; and states that making it was a regular practice. A generic affidavit for “records produced” may be inadequate when the production contains screenshots, analyst-created spreadsheets, correspondence, or documents from other entities.
The fourteen-day notice matters. Record when notice arrived, what files were provided, whether native material was available, whether the certification matched the final exhibit, and whether the State later substituted a different export. A fair opportunity to challenge is difficult when the certificate identifies thousands of files but the trial exhibit appears only after a prosecutor or analyst selects and reformats them.
Certification removes the need for extrinsic authentication testimony only within its scope. It does not establish that every statement inside the record is nonhearsay, prove defendant identity, satisfy Rule 403, cure incompleteness, establish an expert conclusion, or resolve confrontation. Nor does it prevent the opponent from subpoenaing a knowledgeable witness when a genuine dispute remains about the system or record.
Rules 902(13) and 902(14) address electronic authenticity, not every hearsay issue
Rule 902(13) permits certification of a record generated by an electronic process or system that produces an accurate result. Rule 902(14) permits certification of data copied from a device, storage medium, or file using a digital-identification process. Both use Rule 902(11)’s notice structure. They can streamline authenticity proof for system output and forensic copies.
Do not confuse these rules with Rule 803(6). A hash certification may show that a copied file matches its source; it does not prove that a human statement inside the file is true. A system certificate may show that software accurately generated a report; it does not prove the accuracy of user-entered data. The objection should state whether the dispute concerns copying, system operation, authorship, hearsay, interpretation, or completeness.
Business records often contain hearsay within hearsay
N.D.R.Ev. 805 requires every hearsay layer to be admissible. The fact that an employee reliably recorded what a customer said does not make the customer’s assertion reliable under Rule 803(6). The employee may have a business duty to enter the complaint accurately; the customer ordinarily has no business duty to speak accurately.
In Interest of B.B., 2007 ND 115, ¶ 8, the Court rejected the use of Rule 803(6) for outsider statements in a child-protection report. It explained that “each participant in the creation of the record must be acting in the course of regularly conducted business” to supply the exception’s reliability. Id. The author’s duty to record did not cure statements from family members and other reporters.
Apply that reasoning to medical charts, fraud files, insurance notes, delivery records, security reports, and account histories. The employee’s observation may be a business record. A patient’s statement may fit Rule 803(4) if reasonably pertinent to diagnosis or treatment. A defendant’s statement may be an opposing-party statement under Rule 801(d)(2). A bystander accusation may have no exception. Analyze each sentence and field.
A double-hearsay objection should identify the layers. For example: the store’s incident report is one layer; the customer’s accusation quoted in it is a second; the customer’s repetition of another person’s claim is a third. The proponent must identify a rule for each truth-bearing assertion. Redaction can admit operational portions while excluding unsupported narrative.
Account-holder information does not necessarily identify the user
Provider records may establish that an account was opened under a name, billed to an address, or associated with a device. The name may come from an unverified subscriber, purchaser, family member, employer, or reseller. Rule 803(6) can support the provider’s recordkeeping without proving who supplied accurate identity information or who used the account during the charged event.
Identity should be corroborated with payment instruments, recovery from a device, login records, possession, known contacts, distinctive messages, admissions, surveillance, or other evidence. The defense should separate ownership, subscription, possession, access, authorship, and conduct. Those propositions often require different evidence and should not collapse into a single “business record” inference.
Electronic business records require attention to source data and report generation
Modern records are often query results, not static documents. A bank statement, location-history export, call-detail record, ride-share report, point-of-sale log, or access-control report may be generated from multiple tables using parameters chosen after the investigation began. The database may be routine while the selected report is new. Foundation should cover both the underlying entries and the process that produced the exhibit.
Request the data dictionary, field definitions, timezone rules, retention policy, audit history, export instructions, filters, and known limitations. Determine whether blank means “none,” “unknown,” “not collected,” or “not included.” Ask whether timestamps reflect event, processing, upload, or display time. A visually polished spreadsheet can conceal assumptions that matter more than its formatting.
Native data may contain values absent from a PDF, including unique identifiers, uncertainty measures, source flags, edit histories, and deletion markers. Discovery should seek the original production and accompanying documentation, not only the prosecutor’s trial subset. If a provider delivered a compressed archive, preserve its directory structure and metadata. If investigators converted it, identify the software, version, settings, and operator.
Financial records
Bank and payment records can establish authorizations, postings, reversals, merchant descriptors, account relationships, and transfer instructions. They do not automatically prove physical presence, receipt of goods, criminal intent, or the identity of the person who initiated an electronic transaction. Merchant descriptors may be abbreviated or supplied by intermediaries. Pending and settled amounts may differ.
In theft, fraud, exploitation, or money-laundering cases, totals can determine offense grading. Recalculate from source transactions, remove duplicates and reversals, distinguish attempted from completed transfers, and verify the charged date range. Henderson reversed because improperly admitted financial exhibits were central to the statutory value thresholds. 2024 ND 42, ¶¶ 25–28.
Medical and treatment records
Medical charts may contain observations, diagnoses, images, measurements, medication administration, patient statements, family reports, law-enforcement requests, and later legal correspondence. Rule 803(6) may cover routine charting, while patient statements require Rule 803(4) or another basis. Statements identifying an assailant are not automatically pertinent to diagnosis in every case. Context and treatment purpose matter.
Different modules can have different authors and times. An emergency-department triage note, physician note, nursing flowsheet, radiology interpretation, and billing code are not interchangeable. Corrections and addenda should remain visible. If the State offers a summary diagnosis but omits normal findings or alternative explanations, completeness and Rule 403 objections may be as important as hearsay.
Phone, platform, and location records
Telecommunications and platform productions can include subscriber data, call events, IP logs, cell-site fields, messages, location estimates, device identifiers, and provider-generated interpretations. Some fields are automated; others originate with users or third parties. A custodian’s certificate may establish regular maintenance, but an analyst may be needed to explain technical meaning without overstating precision.
Distinguish a record that a device communicated with a system from a conclusion about where a person stood. Location fields can reflect network architecture, account settings, IP assignment, routing, or estimation models. A business-record foundation does not replace expert-reliability analysis when the prosecution uses technical data to make a specialized inference.
Receipts, surveillance, and point-of-sale records
A receipt can show that a system recorded a sale at a location and time, but it may not identify the purchaser. The receipt’s transaction fields, a loyalty-account name, and a cashier’s free-text note may have different sources. Surveillance video may require separate authentication, timestamp analysis, and proof connecting the video to the transaction. One exhibit should not silently authenticate another.
Henderson rejected the idea that common sense alone establishes the business-record foundation for receipts. The Court wrote that although receipts are generally kept in business, Rule 803(6)(D) still requires a custodian, qualified witness, or Rule 902 certification. 2024 ND 42, ¶ 20. That holding is a practical checklist for any merchant exhibit.
Authentication, hearsay, and original-record rules answer different questions
N.D.R.Ev. 901 asks whether evidence is what the proponent claims. Rule 803(6) asks whether specified hearsay is admissible. Rule 1002 governs proof of content, and Rule 1003 addresses duplicates. Passing one rule does not satisfy the others.
Henderson illustrates the separation. The Court found both authentication and business-record defects. 2024 ND 42, ¶¶ 8–24. A detective could identify documents received during an investigation, yet could not establish that a selected, condensed exhibit was the provider’s record or explain how the provider created and kept it. Counsel should make separate objections and request separate rulings.
For electronic records, a printout may qualify as an original if it accurately reflects the stored information under Rule 1001. Accuracy remains the operative question. Ask whether the printout shows all relevant fields, whether it was generated from the production, whether formulas were added, and whether hidden rows or filters existed. A duplicate is admissible unless authenticity or fairness presents a genuine question.
Completeness can change the meaning of a record
N.D.R.Ev. 106 allows an adverse party to require contemporaneous introduction of another part of a writing or recorded statement that fairness requires. With business records, missing preceding transactions, later reversals, explanatory notes, excluded columns, or adjacent messages may materially alter the inference. Completeness is not a license to admit unrelated material, but it prevents distortion.
Identify the smallest additional material necessary to correct the misleading impression. If the State offers a failed payment, the later successful correction may matter. If it offers an account note, the full thread may reveal that the note quotes a customer. If it offers a selected location row, surrounding rows may expose a timezone or accuracy problem.
Rule 1006 summaries must rest on admissible underlying records
N.D.R.Ev. 1006, amended effective March 1, 2026, permits an evidentiary summary, chart, or calculation of voluminous admissible material that cannot conveniently be examined in court. The proponent must make the originals or duplicates available at a reasonable time and place. The underlying material need not itself be admitted, but it must be admissible.
A summary does not cure hearsay or foundation defects. Verify the formula, inclusion criteria, date boundaries, duplicate handling, reversals, missing values, rounding, timezone, and categorizations. Separate an evidentiary Rule 1006 summary from a merely illustrative Rule 107 aid. Jurors should understand whether the chart is evidence, who created it, and which judgments the creator embedded.
The Confrontation Clause focuses on testimonial purpose, not the business-record label
A record may satisfy a hearsay exception and still be inadmissible against an accused if it contains testimonial statements by an absent declarant whom the defendant had no prior opportunity to cross-examine. Crawford v. Washington, 541 U.S. 36, 53–54, 68–69 (2004). The inquiry is practical: who made the statement, under what circumstances, and for what primary purpose?
Routine records created to operate an organization ordinarily differ from records created to establish evidence for prosecution. In Melendez-Diaz v. Massachusetts, 557 U.S. 305, 321–24 (2009), sworn drug-analysis certificates were testimonial. The Court distinguished records “created for the administration of an entity’s affairs” from documents created to prove a fact at trial. Id. at 324.
Bullcoming v. New Mexico, 564 U.S. 647, 652, 661–65 (2011), held that the prosecution could not introduce a certified blood-alcohol report through an analyst who neither performed nor observed the testing. A knowledgeable substitute may explain a laboratory system, but cannot supply confrontation of the analyst whose testimonial assertions the State offers.
Smith v. Arizona, 602 U.S. 779, 789–802 (2024), rejects the idea that an absent analyst’s statements escape confrontation merely because a substitute expert recites them as a basis for an opinion. If the statements support the opinion only when true, they are admitted for their truth. The court must identify the actual declarant and assertion.
The distinction is especially important for laboratory reports, forensic downloads, compliance certificates, and analyst-created interpretations. Instrument output may be nonassertive machine data; a technician’s entries, certifications, conclusions, and deviation statements are human assertions. A routine maintenance log may differ from a case-specific certificate. Analyze each component rather than labeling the entire packet “business records.”
911 and dispatch records may implicate multiple rules
In State v. Burton, 2025 ND 83, ¶¶ 2–34, a records custodian certified a 911 recording, but the Court separately considered authentication, hearsay, and confrontation. The caller’s statements were nontestimonial because their primary purpose addressed an ongoing emergency, and Rule 803(1) supplied a hearsay exception. The certificate did not itself resolve those questions.
That layered analysis should govern dispatch logs and call recordings generally. A system may routinely preserve the audio and metadata. The caller’s assertions require their own hearsay basis. Operator notes may paraphrase rather than quote. Officer statements can raise public-record and confrontation concerns. Authentication of the recording does not establish caller identity without additional direct or circumstantial evidence.
How defense counsel should litigate business records
Demand the actual foundation before trial
Use discovery to obtain the original provider production, subpoenas or warrants, return letters, certifications, native files, data dictionaries, audit logs, extraction reports, and all later spreadsheets or exhibits. Compare hashes, filenames, page counts, date ranges, and row counts. Ask when the prosecutor first identified the trial subset and whether the custodian certified that subset or only the larger production.
For important records, build a provenance table: source system; creator; knowledgeable person; entry time; export time; recipient; transformations; certification; proposed witness; embedded statements; and claimed purpose. This exposes missing links more effectively than a broad “foundation” objection and helps the court fashion a limited ruling.
Object with specificity
State each ground: Rule 901 authenticity; Rule 803(6)(A) knowledge or timing; Rule 803(6)(B) regular activity; Rule 803(6)(C) regular practice; Rule 803(6)(D) custodian, witness, or certification; Rule 803(6)(E) untrustworthiness; Rule 805 embedded hearsay; Rule 1002 content; Rule 106 completeness; Rule 403 prejudice; and confrontation. One ground does not automatically preserve another.
In Henderson, timely, specific objections gave the Court a record for meaningful review. 2024 ND 42, ¶¶ 5–7, 13–17. Object when the exhibit is offered, identify the disputed pages or fields, and explain what foundational fact is missing. If later testimony changes the foundation, renew the objection or request a limiting ruling.
Ask for a hearing when the record is central or technically complex
A pretrial hearing can resolve certification scope, witness qualification, provider methodology, embedded hearsay, and confrontation without forcing the jury to wait. It also permits voir dire of the foundational witness and a clear offer of proof. When grading, identity, or the timeline depends on the record, a developed ruling is worth the time.
Propose practical relief. The court may admit routine transaction fields but redact customer accusations; admit native records but exclude an investigator’s unsupported labels; require a qualified witness; order production of missing source material; allow a completeness excerpt; or exclude a summary while permitting properly founded underlying records. Tailored requests demonstrate that the defense is testing reliability, not resisting documentary proof categorically.
Cross-examine the system, not merely the custodian’s job title
Establish the witness’s actual training, access, and familiarity. Then address source inputs, automatic versus manual fields, timing, corrections, quality assurance, missing data, migrations, report parameters, and post-production edits. Ask whether the witness can reproduce the exhibit from the native source. If not, determine who can.
Use precise concessions. The custodian may be able to say the system recorded a transaction but not who held the card. The analyst may explain a cell sector but not the handset’s exact location. The nurse may authenticate a flowsheet but not an outsider’s narrative. Narrow testimony prevents the evidentiary label from expanding beyond the record’s actual proof.
Connect every record to an element and a disputed inference
Admissibility is only the beginning. Ask what the record proves about act, identity, knowledge, intent, value, timing, venue, or causation. A routine record may be genuine and admissible yet weak on the proposition the State emphasizes. The closing argument should distinguish the provider’s reliable operational facts from the prosecutor’s contested inference.
For example, a bank record may prove a transfer from an account but not who initiated it; a hotel record may prove a reservation but not presence; a medical diagnosis may prove treatment but not legal causation; and a phone record may prove network activity but not message authorship. Keeping those distinctions visible is often the core defense task.
Frequently asked questions about business records in North Dakota criminal cases
Is every receipt automatically a business record?
No. State v. Henderson holds that common sense about receipts does not replace Rule 803(6)(D). The proponent still needs a custodian, qualified witness, or compliant Rule 902 certification.
Can a police officer authenticate records received from a business?
An officer can ordinarily describe receipt and custody. Unless the officer understands the business’s recordkeeping system, that testimony may not establish the Rule 803(6) foundation or the identity and completeness of a provider-generated exhibit.
Must the person who entered the data testify?
Not necessarily. A custodian or other qualified witness may establish the foundation, and Rule 902(11) permits certification. The source still must be a person with knowledge, and every embedded hearsay layer needs a basis.
What makes someone a qualified witness?
The witness needs enough familiarity to explain how the record was created and kept in the ordinary activity. A title alone is insufficient, and the witness need not be the author.
Can records from another company be admitted through the recipient?
Sometimes, when the recipient integrated the records, relied on them in ordinary operations, and can explain the relevant system and reliability. Mere possession in a file is not enough.
Does a Rule 902(11) certificate eliminate all objections?
No. Certification can establish specified authenticity and Rule 803(6) foundation facts. It does not cure embedded hearsay, incompleteness, unfair prejudice, lack of relevance, technical overstatement, or confrontation problems.
How much notice is required for a Rule 902(11) certificate?
North Dakota requires written notice, access to the record, and access to the certification at least fourteen days before trial or hearing so the adverse party has a fair opportunity to challenge them.
Are customer statements inside business records admissible?
Not simply because an employee recorded them. The customer’s assertion needs its own nonhearsay purpose or exception. Rule 805 requires a basis for every hearsay layer.
Are medical records automatically admissible?
No. Routine chart entries may qualify, but patient, family, and law-enforcement statements require separate analysis. Authentication, privilege, relevance, completeness, and confrontation may also matter.
Can a spreadsheet created for trial qualify as a business record?
Usually the new spreadsheet requires proof of its creation and source. It may instead be a Rule 1006 summary or Rule 107 illustrative aid. The underlying admissible records and all calculations must be disclosed and tested.
Does a provider record prove who used an account?
Not by itself. Subscriber, owner, possessor, authorized user, and event-time user can be different people. Attribution ordinarily requires corroborating evidence.
Can the absence of a business entry prove something did not happen?
Rule 803(7) may allow that inference when the business regularly kept records of that kind and the opponent does not show untrustworthiness. The foundation must establish that the event would ordinarily have been recorded.
Can law-enforcement reports be admitted as business records?
The State cannot use the business-record label to evade the criminal-case limits on public records or confrontation. Routine administrative portions, officer observations, witness statements, and forensic conclusions may require different treatment.
Are laboratory certificates business records?
Routine operational records can differ from case-specific certificates created to prove an element at trial. Melendez-Diaz and Bullcoming require confrontation for testimonial forensic certifications.
What if the record was corrected after the event?
The amendment may be admissible, but the foundation should disclose who changed it, when, why, under what procedure, and whether the original value remains available. Concealed correction history can support untrustworthiness or completeness objections.
Can a printout be an original?
Yes, an accurate printout of electronically stored information can qualify as an original under Rule 1001. The proponent still must prove accuracy and satisfy hearsay and authentication rules.
Can the court admit only part of a business record?
Yes. The court may admit properly founded portions, redact unsupported statements, and require additional context under Rule 106 when fairness demands it. Item-specific rulings are often preferable to all-or-nothing treatment.
What should defense counsel request in discovery?
Request the original production, certification, native data, data dictionary, audit history, provider documentation, export parameters, source files, all transformed versions, and the proposed trial exhibit or summary.