Transcript redaction example This completed fictional brief shows how to scope a custom AutoQC campaign for audio to redacted transcripts. All people, dialogue and campaign details below are fictional. The outputs are illustrative examples, not measured results. 1 Campaign and redaction requirements Intended use languages and workload A fictional customer support team wants transcripts for internal quality review and selected external sharing. The owner is the support quality lead. Requested evaluation languages are English, Hindi-English mixed speech and Spanish; retain the original language and script. The short illustration below is in English. The proposed pilot is 10 audio hours in one batch, with calls of 3 to 10 minutes, two speakers, telephone audio and some background noise. Turnaround is to be agreed after evaluating representative samples. Remove keep and replacement rules The default policy replaces the fictional caller name Mira with [NAME] and Jaipur with [LOCATION]. The external sharing policy also replaces the full sentence about the Project Cedar discount of 18 percent with [CONFIDENTIAL_TERM]. The custom content policy additionally replaces the quoted abuse you are useless with [ABUSE]. Retain speaker labels and the ordinary complaint The delivery is late. Apply the named policy consistently; unlisted content remains unless an agreed rule covers it. Fictional source dialogue Caller: My name is Mira and I live in Jaipur. The delivery is late. Agent: The Project Cedar discount is 18 percent. Caller: The agent said "you are useless". Identifiers only Caller: My name is [NAME] and I live in [LOCATION]. The delivery is late. Agent: The Project Cedar discount is 18 percent. Caller: The agent said "you are useless". External sharing Caller: My name is [NAME] and I live in [LOCATION]. The delivery is late. Agent: [CONFIDENTIAL_TERM]. Caller: The agent said "you are useless". Custom content Caller: My name is [NAME] and I live in [LOCATION]. The delivery is late. Agent: [CONFIDENTIAL_TERM]. Caller: The agent said "[ABUSE]". 2 Delivery handling and acceptance Output speakers and timestamps Request editable DOCX and UTF-8 text with one speaker turn per paragraph. Use Caller, Agent and Unknown where needed. These are turn labels, not verified identities. Request turn-start timestamps only if they can be checked against the audio. Use the same replacement label for repeated mentions; a cross-call identity map is outside this proposed pilot. Source audio and working files For this fictional pilot, the client owner must confirm authority to provide the audio. Transfer method, authorised access roles and source-audio deletion timing must be agreed before transfer. The requested handoff contains redacted transcripts. Redacted audio is not requested. Handling of temporary unredacted working text must be agreed explicitly. Processing storage access and deletion Open scoping items are processing location, permitted subprocessors or services, storage locations, retention duration and deletion evidence. Proposed access is limited to named delivery staff and client reviewers. The client must approve the handling terms before recordings are provided; this example does not assert a configured storage or deletion policy. Reference examples and acceptance ownership The support quality lead will approve a reference set of fictional or safely anonymised examples covering each requested language, mixed speech, noise, repeated identifiers, quoted abuse and ordinary complaints. Each example will include expected removals and expected retained content. Reviewers will count missed removals and unnecessary removals separately and check readable turn order. Pilot thresholds, sample size and correction rules remain to be agreed from that set before acceptance. Ambiguous rules return to the client policy owner for a written decision and a revised example. Contact and next action No client or personal contact is supplied in this fictional example. The next action is to agree the language scope, handling terms, reference set, acceptance thresholds and delivery schedule. A completed requirements brief can be sent to hello@autoqc.in. This example describes proposed requirements. It makes no claim about measured accuracy, universal language coverage or a completed deployment.