Witness mapping. Mapped clearly.

Witnesses do not arrive as isolated statements — they arrive tangled in friendships, workplaces, fears and prior encounters that shape what they notice and what they omit. Case teams interview people in sequence and file statements in folders. Overlaps — shared landlords, the same night bus, a cousin who already spoke — stay invisible until cross-examination invents them. Counsel and investigators brief from memory of who might contaminate whom, which is a brittle way to protect fairness. linkchart turns witness relationship charts into a working board: persons, addresses, events, phones and vehicles linked with knows, works with, present at and related to. Interview planning and disclosure thinking start from a shared picture of social proximity.

Why a real link chart for witness mapping

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 witness relationship chart 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 witness mapping 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.

Legal and investigative teams searching for a witness relationship chart, contamination-risk map or interview-planning network need structured social edges around an event. linkchart.art provides that canvas with labelled links and controlled sharing.

Who this map is for

Prosecutors, investigators, and case builders charting who saw what and how witnesses relate to parties.

The signature move on the canvas: Connect witnesses to events and to each other with bias-aware labels — coworker, relative, rival — so credibility context is structural.

What belongs on the map

Every witness relationship chart gets noisy when the wrong things dominate the board. Prioritise these domain-specific anchors before decorative extras:

• Witnesses and parties
• Events each person can speak to
• Prior relationships and conflicts
• Statement dates and consistency notes

Sample relationship labels

Prefer short, scannable edge text. Useful starters for this domain include: witnessed, related to, employed by, hostile to, recanted regarding, corroborates.

Your first week on this canvas

List every witness against the events they claim to cover. Draw relationship edges to defendants and victims with plain labels. Midweek, mark corroboration pairs and isolation risks — lone witnesses versus clustered ones. Prepare a trial-prep view that shows who must be called for which factual brick. Document why each card earned its place so the witness mapping 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 imply perjury from a shared workplace alone. Avoid putting sensitive witness location detail on broadly shared maps. Never flatten “does not like defendant” into proof of lying. Resist one unsorted cloud of names without event anchors. If an edge cannot be explained in one plain sentence, it is not ready for a briefing view of your witness mapping map.

What success looks like

Success is a courtroom-ready relationship board: coverage of facts, potential bias, and corroboration paths are visible. Examination strategy follows structure instead of a binder’s tab order. When someone new opens the witness mapping canvas, they should grasp the live question, the strongest links, and the next check within minutes. That is the operational definition of a successful witness relationship chart on linkchart.

How to use linkchart for witness mapping

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 witness mapping who want speed without losing structure.

1. Create a map scoped to the incident and its immediate aftermath, not the whole neighbourhood.
2. Add witness and key civilian person cards with role notes (eye-witness, ear-witness, continuity).
3. Link prior relationships separately from same-scene presence so contamination risk stays precise.
4. Attach homes, workplaces and social venues as address cards when they explain contact.
5. Place the offence and gathering events on a timeline with who was present.
6. Share a viewer map with counsel so interview order and special measures discussions use one chart.

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 witness mapping work has consequences.

Entity types that shine for this use case

linkchart supports investigation-ready cards you can reuse across domains. For witness mapping, start with these and expand only when a new type earns its place on the canvas:

Person Address Event Phone Vehicle Company Item

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 witness mapping narratives often depend on. Together they form a vocabulary you can teach a teammate in minutes.

Real-world scenarios

Street robbery with overlapping household witnesses

Four statements sound independent until person and address cards show three witnesses share a landing and a WhatsApp group. Event cards for the robbery and a later corridor conversation sit an hour apart. Phones link two of them to a mutual friend who is not a witness. Interview scheduling changes so the first account is captured before further household talk — fairness improves because the network was visible early. Interview order changes when household and workplace clusters are visible before the first ABE is booked.

Workplace incident with contractor layers

Employees and agency staff describe a loading-bay assault differently. Mapping company cards for employer and agency, person cards for each witness, and vehicle cards for who arrived together reveals two social clusters that barely mix. Event cards for shift handovers explain knowledge gaps. Counsel stops treating contradictions as simple dishonesty and starts testing cluster-based perception. Counsel sees contamination risk as labelled proximity rather than a late surprise in cross-examination. Intimidation pathways can be briefed for protective measures without inventing a conspiracy the evidence does not carry.

Intimidation risk around a trial

A peripheral associate begins appearing near two witnesses' homes. Person, address and vehicle cards chart the approaches as events without assuming the defendant directed them. Phone bridges to a known faction sit as hypotheses. Protective measures briefings finally name the pathway of concern rather than a vague feeling that people are nervous. Intimidation pathways can be briefed for protective measures without inventing a conspiracy the evidence does not carry. Interview order changes when household and workplace clusters are visible before the first ABE is booked.

Across these scenarios the constant is the same: when witness mapping 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

• Distinguish scene co-presence from pre-existing relationships with explicit labels.
• Keep victim–witness dual roles carefully noted when the same person is both.
• Update after each ABE or follow-up interview while overlaps are fresh.
• Use coded titles on shared maps when anonymity orders apply.

Common pitfalls

• Do not imply collusion from mere acquaintance — label what you know.
• Avoid mapping every Facebook friend of every witness.
• Never put addresses of vulnerable witnesses on broadly circulated 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 witness mapping 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: Witness mapping

Related ways to use linkchart

• Criminal investigation link charts — Law enforcement
• Map organized crime networks — Law enforcement
• Build a family tree with linkchart — Personal & genealogy
• Map GTA roleplay networks and factions — Gaming
• Browse all 50 use cases

Ready to build your own witness relationship chart? Open linkchart, place your first cards, and let the network tell the story you have been trying to hold in your head.