The following is a fictional composite scenario. It is not a real client story and it does not claim a legal outcome.

Its purpose is to show how a family can move from “police want to talk” to a cleaner decision process without guessing the law.

09:20 — the first message

Li, a Chinese-speaking sales manager working overseas, messages his sister:

Police called. They want me to come in tomorrow to answer questions about one customer account. They said it should not take long.

The family’s first instinct is relief: at least he was not arrested.

That is not yet a legal conclusion.

Better first response

The sister asks Li to write down:

  • which police unit called;
  • officer name/number;
  • exact date/time/location;
  • whether attendance was described as voluntary;
  • what conduct or transaction was mentioned;
  • whether Li was told he could have a lawyer;
  • whether Li needs an interpreter.

No family member tells him what to say about the customer.

10:15 — internet research creates confusion

One relative sends a U.S. Miranda video.

Another sends a British police-caution article.

A third says, “In Canada you can call a lawyer immediately.”

All three may contain real legal ideas. None proves what applies to Li.

Decision point 1: identify the jurisdiction

The family adds a red line to the top of the file:

Do not use foreign police-rights articles as operative advice.

They search the official site for Li’s jurisdiction and contact a local criminal lawyer.

12:40 — the scope is still unclear

The lawyer asks a simple question:

“What exactly did police say they want to ask about?”

Nobody knows.

Li remembers “customer payment problem” but cannot remember whether police mentioned fraud, theft, data access or merely “an investigation.”

Better next step

Li does not invent a label. The file says:

Suspected matter: not yet confirmed. Police referenced Customer X account/payment.

The lawyer handles the question of what information can be clarified before the interview.

15:00 — language becomes the hidden issue

Li uses English every day and initially says he does not need an interpreter.

During the lawyer call, however, he struggles to explain words about authorization, account access and intent.

The problem is not basic English. It is precision.

Decision point 2: language fit

The lawyer and Li discuss whether an interpreter or other language support is appropriate under local procedure.

The family does not appoint Li’s cousin as an unofficial police interpreter.

19:30 — document preparation starts going wrong

A relative creates a 600-page PDF of every message Li has ever exchanged with Customer X.

The lawyer asks for something different:

  • the contract/order;
  • relevant invoices;
  • exact payment record;
  • short chronology;
  • relevant message thread with surrounding context;
  • list of devices/accounts involved.

Lesson

“More documents” is not automatically “better preparation.”

Index first. Expand only when requested.

Next day, 08:45 — interview status changes

At the station, police use language Li did not expect. The local procedural label is different from what the family thought the previous day.

This is the first serious red flag.

Decision point 3: status

Li does not rely on yesterday’s family assumption.

He tells his lawyer what police said, and the lawyer assesses the local legal meaning.

The family timeline records:

08:45 — police described status as [exact local wording]. Source: Li direct recollection / written notice if available.

09:30 — police present a message

Police show Li a screenshot suggesting he approved a payment.

Li is surprised because he remembers the message differently.

The worst instinct would be to explain immediately by guessing:

“That must be because my assistant used my phone.”

Li does not actually know that.

Better response discipline

The difference between these statements matters:

Bad: “My assistant sent it.”
Accurate: “I do not remember sending that message and I would need to see the full conversation/context.”

Whether and how Li should answer is a local legal issue for counsel. The learning point is simply: do not convert surprise into speculation.

10:20 — interpreter difficulty appears

A technical phrase about “authorization” is translated in a way Li believes means “approval after the fact.”

The interviewer appears to mean “permission before the transaction.”

Li pauses and says he does not understand the translation.

Decision point 4: comprehension

The issue is recorded.

The family later notes:

  • term in English;
  • translated term;
  • Li’s concern;
  • interpreter details;
  • approximate time.

Nobody “fixes” the official record themselves.

11:05 — a signature appears

Police provide an interview summary.

Li finds one sentence broader than what he remembers saying.

Decision point 5: written record

This is a higher-consequence moment.

The correct local procedure depends on jurisdiction. Li uses the lawyer/interpreter process available to him rather than signing because “the interview is almost over.”

The family later preserves the exact copy and any translation.

14:10 — the interview ends, but the work does not

The family wants to hold a two-hour debrief.

The lawyer asks them not to coach a new version.

Instead they preserve a process reconstruction:

  • interview start/end;
  • lawyer contact;
  • interpreter;
  • documents shown;
  • disputed translation;
  • signed/unsigned documents;
  • device requests;
  • next expected event.

No one writes “the true story” for Li to memorize.

The scenario's transferable rules

Rule 1: status before strategy

Do not build a strategy until you know the local procedural status.

Rule 2: language ability is task-specific

Business fluency does not guarantee legal comprehension.

Rule 3: surprise is not evidence

When police show an unexpected document, do not fill the gap with a guess.

Rule 4: fixed documents deserve extra care

A signature, consent or device-access decision is harder to reverse than an informal family discussion.

Rule 5: the family is not the defense lawyer

The family organizes facts, welfare and documents. Local counsel handles the law.

A copyable next-decision card

Current status:
Next event:
Next irreversible decision:
Lawyer contact:
Interpreter needed:
Documents police referenced:
Items signed:
Devices involved:
Family coordinator:
Unknowns still open:

If the card cannot be completed, the family knows exactly what to verify next.

Why this scenario is intentionally incomplete

Real police cases do not give families neat endings.

This scenario does not say whether Li was charged, released or cleared. Inventing an outcome would teach the wrong lesson.

The useful skill is managing the decision points before the outcome is known.

What the family should save from this fictional scenario

The useful output is not the story of Li. It is the structure of the file.

The family would ideally retain:

  • the original police contact details;
  • a note showing what was and was not confirmed before the interview;
  • lawyer contact and scope;
  • interpreter decision;
  • document index;
  • exact status wording at the station;
  • list of documents shown;
  • translation issue;
  • signed-document status;
  • post-interview reconstruction approved by counsel.

That packet would allow another professional to understand the sequence without relying on family memory.

What the family deliberately does not do

They do not:

  • publish the police screenshot;
  • ask Li's assistant to “confirm” a theory before counsel speaks with them;
  • delete old chats;
  • rewrite Li’s chronology to make it cleaner;
  • promise police a later explanation without legal advice;
  • treat the first lawyer call as a guarantee of outcome.

Those omissions matter. Crisis management is often about not creating new facts while trying to solve old ones.

A second-day variation

Suppose police call again the next morning and ask Li to bring his company laptop.

The family now has a new issue. The laptop is company property and contains unrelated client data.

The correct response is not for Li to search the laptop overnight looking for “anything bad.” It is also not for the company IT team to remotely clean the device.

The new decision card should say:

New request: company laptop
Ownership: employer
Data: company + third party
Police authority/request basis: not yet confirmed
Next step: local counsel to clarify; employer/legal contact may need to be involved

Notice how the original “customer payment interview” has now become a digital-evidence and employer-coordination issue.

That is exactly why good case management is dynamic.

A third-day variation

Suppose Li's sister receives a message from a former coworker:

I heard what happened. I can tell police the customer always caused problems.

The family should not immediately ask for a detailed statement.

The coworker may become a witness. The family should preserve the contact, avoid coaching, and tell counsel.

A useful entry is:

09:35 — Former coworker A contacted Sister by WhatsApp. Unprompted message offered information about Customer X. No substantive reply sent. Screenshot preserved. Counsel notified 10:05.

This kind of neutral record protects the family from later confusion about who initiated contact.

The point of the scenario

The scenario keeps changing because real investigations change.

A good family system is not built around one predicted story. It is built around repeatable questions:

  • what changed;
  • what is confirmed;
  • what is the next irreversible decision;
  • which professional owns it;
  • what must be preserved before anyone acts.

That is the operating system, not the fictional outcome.

Bottom line

A police interview becomes safer to manage when the family stops trying to predict the result and starts identifying the next high-consequence decision.

Status, language, documentary evidence and counsel access come before “telling the story better.”

Fictional composite for education only. Not legal advice.

Related Reading

Official source boundary notes