Resources / Transcript PII redaction / Examples and brief
Free examples and editable requirements brief

Decide what to remove.
Show what should remain.

Explore three redaction policies in English, Hindi–English and Spanish. Then use the blank brief and worked example to define your own audio-to-transcript requirement.

No email gate. No recording upload. All examples are fictional.

An example you can inspect

Choose a language and a policy.

These versions illustrate removal choices. The same customer complaint is retained while the rules change what your team receives.

One conversation. Three different briefs.
Choose the removal rules

The rule for this example

Replace the customer name and location. Keep the complaint, commercial terms and quoted language.

Fictional teaching example. Outputs are prepared illustrations, not live model results or an accuracy benchmark. Speaker labels are part of the example.

Redacted transcriptEnglish / Personal identifiers
Customer

I am [PERSON] from [LOCATION]. The delivery is late. Can you update me?

Agent

For project Cedar, we agreed an 18 percent discount.

Customer

I said ‘damn delay’ and the other person said ‘you are useless’. Please keep my delivery complaint.

Delivery issue, project terms and quoted language remain in this policy.

Hear the fictional source and read its script

Synthetic narration of a fictional script, including mild profanity and quoted abuse. This is source audio, not redacted audio. It is not a recording of real people.

Customer

I am Mira from Jaipur. The delivery is late. Can you update me?

Agent

For project Cedar, we agreed an 18 percent discount.

Customer

I said ‘damn delay’ and the other person said ‘you are useless’. Please keep my delivery complaint.

Define the exception as well as the rule.

REMOVE

Be specific about the target

“Remove customer names” and “remove every name” have different scopes. Specify whether agents, brands or project names should stay.

KEEP

Protect useful meaning

A complaint is not automatically abuse. State whether the issue, impact and requested next step should survive a sensitive passage being removed.

CHECK

Use a representative sample

Review missed information, excess masking, language switches and unclear speech. Record corrections and the acceptance decision.

A useful starting point

Bring a brief.
Keep your recordings private.

Use the editable requirements brief to decide what goes, what stays and how your team will judge the result. No email required to download.

  • Languages, recording volume and output layout
  • Removal rules, exceptions and replacement labels
  • Sample checks, review ownership and data handling
Use the brief in three steps

Make the requirement concrete.

  1. Describe the recordings, languages, volume and intended use.
  2. Write paired examples of what to remove and what to preserve, using fictional text.
  3. Agree output conventions, sample checks, responsibilities and handling requirements.

The worked brief is an example, not a contract or a legal compliance assessment. It does not demonstrate detection accuracy. Your policy and representative sample determine what must be evaluated.

Need the workflow handled for you? Explore custom transcript redaction with AutoQC.

What needs to disappear?
What needs to remain useful?

Bring the languages, volume, rules and output your team needs. We will discuss a representative sample and the scope.

Discuss your redaction requirements