Phones are bridges — between people, places and times — and call data only becomes intelligence when those bridges are drawn, not tabulated. CDR spreadsheets hide patterns in rows. Analysts can sort by frequency yet still miss that two sparse numbers only ever meet before the same warehouse events. When exhibits multiply, the story of who brokered whom gets lost in pivot tables that non-analysts cannot read under pressure. linkchart turns phone call link analysis into a visual network: phone cards, persons, addresses, vehicles and events linked by called, co-located with and used near. Briefings show bridges and cut-points instead of raw dumps.
Why a real link chart for phone analysis
Most people start this work with tools that were never designed for networks. Documents narrate. Spreadsheets tabulate. Whiteboards photograph poorly and refuse to scale. A dedicated phone call link analysis approach treats every person, place, asset and event as a node — and every meaningful connection as an edge you can label, question and revise.
That shift matters because decisions in phone analysis are rarely about a single record. They are about patterns: who introduces whom, which address keeps appearing, which phone bridges two clusters, which event changed the shape of the network. linkchart exists so those patterns stay visible while you work, not only in the final slide.
Analysts searching for phone call link analysis, CDR visualisation or communication network charts need more than spreadsheets. linkchart.art helps you attribute numbers, show bridges and brief timelines with structured cards and labelled links.
Who this map is for
Analysts and investigators interpreting call, message, and device relationships within lawful case frameworks.
The signature move on the canvas: Elevate phone numbers and devices as nodes equal to people, because handset reuse and shared lines are often the bridge.
What belongs on the map
Every phone call link analysis gets noisy when the wrong things dominate the board. Prioritise these domain-specific anchors before decorative extras:
- Phone numbers and devices
- Subscribers and frequent contacts
- Cells, towers, or approximate locations where relevant
- Bursts of contact around key events
Sample relationship labels
Prefer short, scannable edge text. Useful starters for this domain include: called, texted, shared device, subscriber is, co-located near, new handset of.
Your first week on this canvas
Load only numbers already in scope for the case question. Link subscribers where known, and leave anonymous lines as phone cards. Highlight contacts that spike around event times. Midweek, mark handset changes and shared-device suspicions. Produce a cluster view for the briefing that shows bridges between otherwise separate people groups. Document why each card earned its place so the phone analysis board does not drift into decoration. Before the week closes, freeze a viewer link for one outsider and capture their first three questions as backlog edges or notes.
What not to do
Do not treat a single call as a conspiracy. Avoid mapping entire phone books beyond lawful scope. Never present tower presence as precise co-presence without caveats. Resist pretty hairballs that hide the two numbers that actually matter. If an edge cannot be explained in one plain sentence, it is not ready for a briefing view of your phone analysis map.
What success looks like
A clear communications map isolates bridge numbers, timing anomalies, and device reuse. Analysts propose next steps from structure — whose handset, which burst, which missing attribution — rather than from raw CDR dumps. When someone new opens the phone analysis canvas, they should grasp the live question, the strongest links, and the next check within minutes. That is the operational definition of a successful phone call link analysis on linkchart.
How to use linkchart for phone analysis
You do not need a special template to begin. Open the linkchart app, create a map, and build outward from the question you must answer. The workflow below is a proven path for people doing phone analysis who want speed without losing structure.
- Create phone cards for numbers of interest with service periods in notes.
- Link attribution to persons carefully — subscriber is not always user.
- Attach significant call/SMS events or bursts rather than every row.
- Connect cell-site or Wi-Fi locations as address cards when available.
- Mark handset changes as item cards tied to the same person hypotheses.
- Produce viewer maps for court or command that highlight the communication spine.
As the map grows, resist the urge to make it decorative. Beauty comes from clarity: consistent card titles, honest labels, and notes that explain uncertainty. A slightly ugly accurate chart beats a pretty misleading one every time — especially when phone analysis work has consequences.
Entity types that shine for this use case
linkchart supports investigation-ready cards you can reuse across domains. For phone analysis, start with these and expand only when a new type earns its place on the canvas:
Phone Person Address Event Vehicle Company
Person and organisation cards carry identity. Addresses anchor geography. Phones and communication profiles expose bridges between clusters. Events give you time. Vehicles and items capture the physical world that phone analysis narratives often depend on. Together they form a vocabulary you can teach a teammate in minutes.
Real-world scenarios
Broker number between two crime groups
Group A and Group B rarely call each other, but both call a quiet third number before meetings. Phone and person cards make that broker unmistakable; event cards show the meetings that follow. When the broker handset changes, an item card keeps continuity of the human hypothesis. Tasking shifts toward the bridge rather than flooding both groups equally. Attribution confidence — subscriber versus handset user — sits on every phone card so charts do not overclaim.
Alibi versus cell-site story
A suspect’s statement places them across the city. Mapping phone events to address cards for cell areas and known CCTV venues shows conflict windows. Vehicle cards for a registered car sit unused that night. The communication map does not convict alone — it frames precise questions for interview and disclosure. Court-ready viewer maps highlight the communication spine rather than dumping entire historic CDRs. Handset-change item cards preserve human continuity when disposable SIMs try to reset the story.
Harassment via rotating SIMs
Victims receive threats from new numbers weekly. Phone cards proliferate, but linking them through a common retail address event, a reused phrase item, and occasional contact with one persistent number reveals a thin controlling line. Protective and investigative steps target that line instead of infinite whack-a-mole on each SIM. Handset-change item cards preserve human continuity when disposable SIMs try to reset the story. Attribution confidence — subscriber versus handset user — sits on every phone card so charts do not overclaim.
Across these scenarios the constant is the same: when phone analysis information stays trapped in siloed files, people argue about memory. When it lives as a labelled network, people argue about evidence — which is exactly where productive work happens.
Field practices that keep maps trustworthy
- Always record attribution confidence: subscriber, handset user, shared phone.
- Visualise bursts around offence times rather than entire historic CDRs.
- Keep exhibit references in notes for evidential hygiene.
- Watch for family phones that explain contact without implying conspiracy.
Common pitfalls
- Do not equate call frequency with leadership.
- Avoid mapping entire contact books without investigative relevance.
- Never display full CDRs with third-party personal data on overshared links.
Compared with slides, whiteboards and generic diagram tools
Slide software is excellent for presenting a finished argument and poor at hosting an evolving network. Whiteboards are wonderful for a one-hour workshop and hostile to long-running phone analysis work. Generic diagrammers can draw boxes and arrows, yet they rarely treat investigative entities as structured records with fields your team actually fills in. linkchart sits in the gap: fast enough for a working session, structured enough for a case file, visual enough for a briefing.
FAQ: Phone analysis
Can we import CDR CSVs automatically?
Treat imports as a separate workflow if you build one; the core value is curated entities and meaningful edges on the canvas.
How do we show one-way versus two-way contact?
Use directional labels such as called or messaged, and note reciprocity in the edge text.
What about encrypted apps?
When lawful evidence shows app identities, create phone/person cards for those handles and link events without inventing content you do not have.
Useful for corporate insider investigations?
Yes — extension numbers, badges and meeting rooms map beside mobile bridges in internal probes.
Related ways to use linkchart
Ready to build your own phone call link analysis? Open linkchart, place your first cards, and let the network tell the story you have been trying to hold in your head.
Ethics, privacy and good judgement
Any powerful mapping tool can be misused. For phone analysis, draw a bright line between legitimate analysis and voyeurism. Collect only what you need. Share only with people who have a role. When working with personal data, follow the laws and policies that apply to your organisation or community. linkchart is a canvas — responsibility for what you place on it remains yours.
Especially when maps include minors, victims, or confidential sources, default to minimisation. Use initials, role titles or delayed identifiers when full names are unnecessary for the analytical task. A precise network with careful labelling beats a sensational wall of private detail.