Distinguish offsets from drift
A constant lead-in offset and gradually increasing drift have different causes and repairs. Inspect several points across a long session. Resampling, edited pauses, inserted ads, or use of a different episode edition can each break alignment. Record what was compared so a later reviewer can distinguish a clock issue from an editorial change.
Keep the repair traceable
Preserve the original annotation file and document any timing transformation. If only one section has changed, a global offset may damage otherwise correct segments. Agree on the tolerated alignment error for the intended task and inspect representative transitions, including reconnects and long silences, before treating the entire session as aligned.
Put the decision in the brief
For finding timestamp drift in long podcast recordings, make the expected treatment visible in the written project brief. Include one acceptable example and one case that needs a decision. Ask the source owner which supporting records exist and mark missing information explicitly. Review the assumptions before applying a rule to an entire archive.
Keep a reviewable handoff
Carry the agreed policy, source identifiers, and unresolved questions into the delivery manifest. A later recipient should be able to connect a finding about timestamp drift to the exact file and version reviewed. Discuss project fit with Fiund before sending source recordings or sensitive contributor information.
Review checklist
- Define the project decision: timestamp drift.
- Identify the exact source files and recording edition.
- Document accepted treatment and unresolved exceptions.
- Agree on review evidence before preparing the full collection.