What Are Call Detail Records and What Do They Show in Court?
Published on August 4, 2026
Contact Mark CV DownloadReading call detail records without overreading them
Call detail records often become important when a case turns on communication timing, contact patterns, or network activity.
The records can help reconstruct events even when the phone itself is missing, but they do not show content or exact location.
That distinction matters in litigation because a carrier log can show that a device connected to a network, while leaving open who held the phone, what was said, and whether a background connection reflected active use.
Why call detail records matter in litigation
When someone says “phone records” in a case, people often assume the records show what was said on a call or the precise location of a person.
In many matters, the phone itself is missing, locked, damaged, or not collected, so parties turn to carrier records because they can exist even without the device.
Those records can feel objective, but they also invite over-reading.
A call detail record shows device and network activity, not the words spoken or the text someone read.
Cell tower information can suggest a general area, but it is not the same as GPS.
Data-session entries often appear when the phone checks in with the network in the background, so a record does not necessarily mean a person tapped the screen.
A gap in records can reflect a carrier’s retention limits or the fact that a requested record type was not created.
What a call detail record contains
A call detail record, often called a CDR, is a set of carrier-generated logs about communications that touched the carrier’s network.
It covers metadata about calls, text messages, and some data connections.
Typical fields include the calling number and receiving number, the date and time, call duration, connection status, and the type of event, such as voice or SMS.
Some CDRs also include the cell tower and sector identifiers tied to a connected call or session, which can matter when location becomes an issue.
Many carriers also log call attempts, including calls that rang but did not connect.
CDRs do not include the content of a voice call, and they usually do not include the content of text messages.
App-based messages or other over-data messaging may not appear as SMS content in carrier records, even if the phone used data at about the same time.
Some records also include device identifiers such as IMEI or MEID, which can help distinguish the physical phone from the subscriber line when devices or SIMs change.
Those mechanics define what the data can and cannot support as evidence in court.
How carriers create CDRs
Each time a phone connects to the carrier network, the network can log an event.
A timestamp reflects when the network recorded the start, end, or presence of that event, depending on the carrier and field.
A tower or sector identifier reflects which part of the carrier’s equipment handled the connection, not a coordinate on a map.
When a call moves while staying connected, some records include handoff information reflecting a change from one tower or sector to another during the same call.
Tower density shapes how specific any location inference can be, as towers sit closer together in many urban areas and farther apart in many rural areas.
Phones may connect to a tower other than the closest tower.
Terrain, building materials, network load, and carrier routing choices can all affect which tower handles a connection.
Data records typically show that a connection occurred, not what was happening on the screen at the time.
Carrier field definitions, switch logs, and cell-site lists are therefore part of the technical review, not background paperwork.
What CDRs can show in court
In court, CDRs often support timelines.
They can corroborate or contradict testimony about whether a call attempt occurred, when it started, and how long it lasted.
They can also show contact patterns over time, which may matter when a dispute turns on communication frequency or gaps in contact.
When tower and sector fields are available, they can support an inference that a device connected within a general area at a given time, which sometimes matters in alibi or presence disputes.
In distracted driving cases, CDRs can show that a call or outgoing text occurred near a crash time, or that no carrier-logged events appear in a given window.
CDRs also have limits that shape admissibility and weight.
A CDR does not identify who held the phone.
It does not show whether a voice call was hands-free or handheld.
Incoming texts do not show whether the recipient read them.
Data transmissions often occur in the background, meaning not every data event reflects active use.
Tower-based location is approximate, and the absence of some record types, such as timing advance or round-trip time data, does not establish that the phone was off.
Those limits define what CDR evidence can and cannot establish in litigation.
How CDRs are obtained and preserved
CDRs are commonly obtained through a subpoena in civil litigation, and in some settings through an account holder request if the carrier allows it.
Timing is a factor because carriers delete records on schedules that vary by carrier and record type.
Preservation requests sent early, once relevant numbers and dates are identified, reduce the risk of records being purged before they can be obtained.
Requests for records are strongest when they specify the types needed, such as voice, SMS metadata, data sessions, call attempts, tower and sector information, and device identifiers, along with clear date and time ranges.
A phone bill and a CDR are not the same document.
Bills may round call durations and leave out non-billable attempts, while CDRs may track events in seconds and include a broader range of attempts.
For court use, a printed copy may face admissibility objections unless it can be shown to have come from the carrier in the ordinary course of business.
A custodian certification, affidavit, or comparable business-record documentation typically supplies that context.
Maintaining a record of how the records were received, including envelopes, transmittal letters, and file metadata for electronic deliveries, supports chain-of-custody review.
When tower or data fields play a central role, a qualified analyst can explain what the codes mean and what they do not show by themselves.
In criminal matters, the legal process used to obtain location-related records may also be reviewed separately from the engineering analysis.
A clean, authenticated record set defines what the CDRs can support and where room for dispute remains.
Frequently Asked Questions
The carrier produced a large spreadsheet. What makes it technically readable?
The technical step is to preserve the original production, work from a copy, and normalize the records before drawing conclusions.
That usually means identifying the carrier’s time-zone convention, separating voice, SMS, and data-session event types, matching tower or sector identifiers to the supplied cell-site list, and building a timeline that can be checked against known case events.
Can data-session logs conflict with testimony without showing active phone use?
Yes.
A data session can be created by background activity such as push notifications, email sync, app updates, location services, or device maintenance traffic.
The technical review should separate user-initiated activity from automated network activity before treating a data event as evidence that the person was interacting with the phone.
What production details help an expert evaluate whether CDRs are complete?
The review usually looks for the request language, carrier transmittal materials, field definitions, file names, production dates, date ranges, and any custodian or business-record documentation supplied with the files.
Those details help distinguish an authenticated carrier production from a partial export that may need additional context.
What changes when the phone may have used dual SIM or eSIM service?
A number-only request may miss activity if the same handset used more than one subscriber line.
The review should look for device identifiers such as IMEI, MEID, ICCID, or IMSI fields when they are available, then compare whether the handset, SIM profile, and subscriber number stayed consistent during the relevant time window.
When should uncertainty be shown in a CDR timeline or map?
Uncertainty should be visible when the opinion depends on tower coverage, sector direction, timing conversions, missing record types, or carrier-specific field definitions.
Showing those limits helps keep the analysis tied to the records instead of presenting a tower connection as a precise device location.
