Skip to content

Annotation quality guide

Audio Transcript Consent and Provenance Review: Link Evidence Without Legal Overreach

Build a traceable evidence record for an audio object, its transcript cues, and the collection event while keeping consent questions qualified and unresolved when evidence is missing.

A transcript can be perfectly time-coded and still be linked to the wrong audio, an outdated derivative, or an unsupported collection record. Review artifact identity, cue timing, speaker mapping, source event, and consent-related evidence as separate records. This guide records evidence fields only. It is not a legal conclusion, privacy guarantee, consent adjudicator, transcription engine, or rights clearance.

Updated

On this page

Separate audio identity from consent evidence

The source dates shown in this guide identify documentation checks on 22 October 2026, not original publication dates. Follow each citation for the timing and provenance vocabulary being discussed. Begin with a controlled audio identifier, digest or owner-approved reference, duration, channel description, derivative relationship, and handling boundary. Do not paste raw speech, names, phone numbers, private paths, or customer recordings into a public worksheet.

Consent-related evidence is a record of what was supplied and how it is linked, not a conclusion that a legal requirement was met. Keep source document identifier, collection context, stated scope, version, time, issuing or collecting role, and evidence location separate from an owner or counsel decision. Mark unavailable fields as unknown rather than inferring permission from the existence of a file.

Separate audio identity from consent evidence (table)
Evidence layerSynthetic fieldDo not infer
Audio entitysynthetic-audio-07 and digestWho may use the speech
Transcript entitysynthetic-transcript-07-v2That words match the audio
Collection activityrecorded-event-07That the event was authorized
Consent recordconsent-record-07, scope unknownThat a legal standard is satisfied
Agent or rolesynthetic collection operatorIdentity of a real speaker
Decisionowner review pendingApproval, clearance, or license

Check transcript cues against the media timeline

The World Wide Web Consortium, (opens in a new tab) specification describes cues with start and end timestamps and allows cues to overlap. Record the transcript format, timestamp precision, media duration used for review, and whether cue boundaries were produced by a human, an automated process, or an unknown stage. Overlap is an observation; it is not automatically an error because multiple speakers or displayed tracks may overlap.

Synthetic cue ledger

Check transcript cues against the media timeline code example, Plain text
cue_id | start | end | speaker_id | audio_ref | evidence
cue-01 | 00:00:01.200 | 00:00:03.100 | speaker-a | synthetic-audio-07 | aligned-window
cue-02 | 00:00:02.900 | 00:00:04.000 | speaker-b | synthetic-audio-07 | overlap-review
cue-03 | 00:00:04.000 | 00:00:04.000 | unknown | synthetic-audio-07 | zero-duration-hold
cue-04 | 00:00:05.000 | 00:00:06.250 | speaker-a | synthetic-audio-08 | wrong-audio-link
Check transcript cues against the media timeline (table)
Cue checkEvidenceDisposition
Start before endNormalized cue intervalHold zero or reversed interval
Within reviewed durationMedia duration and cue endpointRecord out-of-range cue
Audio reference matchesAudio id or approved digestHold wrong-derivative link
Speaker mapping statedStable synthetic or owner-approved idKeep speaker unknown
Overlap explainedConcurrent speaker or track noteDo not silently merge cues
Text source retainedTranscript version and activityDo not overwrite prior transcript

A cue ending exactly where the next cue starts may be contiguous. A zero-duration or reversed cue needs a disposition, not a guessed correction. Keep cue text out of broad reports unless the owner has approved the handling boundary; a stable cue id and timing finding often suffices.

Model derivation and collection as an evidence chain

Use PROV-O as a vocabulary for the chain: the audio and transcript are entities; recording and transcription are activities; a collection role, annotator, or system is an agent. Record that a transcript was derived from a specific audio entity and generated by a named activity. This makes missing links visible without claiming that provenance alone proves accuracy or authority.

Model derivation and collection as an evidence chain (table)
PROV-style relationSynthetic recordReview question
usedtranscription activity used synthetic-audio-07Is the input identity stable?
wasGeneratedBytranscript-v2 generated by activity-22Is the producing step known?
wasDerivedFromtranscript-v2 from audio-07Is the derivative relationship supported?
wasAssociatedWithactivity-22 associated with annotator roleIs the role evidence available?
wasAttributedTotranscript attributed to owner roleIs attribution distinct from approval?

Store the event time, tool or workflow version, and evidence locator separately. If a source record is withheld, report that the link is unavailable. Do not put a raw transcript, consent form, speaker name, or customer identifier into a public synthetic fixture.

Keep transcript findings and legal decisions separate

This review can show whether a transcript is linked to an identified audio artifact, whether cues have bounded timing evidence, and whether collection and derivative records are traceable. It cannot establish speaker identity, truth of transcript text, privacy status, permission, legal compliance, ownership, or suitability for a downstream use.

Pair this guide with the data provenance log for artifact history and transcript alignment review for cue and speaker observations. After supported non-health scope, authority to describe the collection, and a controlled evidence packet are established, the qualified appraisal request path may be a next preparation step. It does not inspect recordings, decide consent, create a quote, match a buyer, issue a legal opinion, or grant a license.

Takeaways

  • Keep audio identity, transcript identity, collection activity, consent evidence, and owner decisions as separate records.
  • Use cue ids and timing observations instead of copying raw speech into a public report.
  • Record overlaps and unknown speaker links without forcing a merge or identity.
  • Use provenance relations to expose missing derivation links, not to claim accuracy or authorization.
  • Treat consent-related fields as evidence inputs for the appropriate process, never as a legal conclusion.

Sources

  1. World Wide Web Consortium: WebVTT: The Web Video Text Tracks Format (opens in a new tab)
  2. World Wide Web Consortium: PROV-O: The PROV Ontology (opens in a new tab)

Use the appraisal path after the evidence packet is organized.

It does not inspect recordings, decide consent, create a quote, match a buyer, or grant a license.