Articles on: Podcasts & Episodes

Requesting Retranscription and Making Corrections

Sometimes transcripts need fixes. Podscan makes it easy to improve transcript accuracy through retranscription requests and direct corrections.


![Data Fidelity menu showing "Request Retranscription" and "Suggest correction" options

](https://storage.crisp.chat/users/helpdesk/website/5ec8e994fe60b000/image_1yrsoau.png)

When to Request Retranscription


Request a full retranscription when:

  • Many words are incorrect
  • Speaker labels are wrong
  • Timestamps are misaligned
  • Audio quality caused issues


Just click "Request Retranscription" in the Data Fidelity menu. The system will process your request immediately. Due to the asynchronous nature of the ranscription queue, some episodes —particularly ones of relatively small podcasts— might take up to 24 hours.


Retranscribing a podcast will always use the highest possible quality.



![Retranscription status indicator

](https://storage.crisp.chat/users/helpdesk/website/5ec8e994fe60b000/image_18pbm2x.png)

Requesting Reanalysis


Sometimes, the extracted hosts, guests, and summary data might be a bit off — or not present at all. You can request reanalysis from the three-dot dropdown menu. We will immediately queue up another extraction run on our servers, and it'll be done within the hour. If it doesn't go through in 24 days, please reach out to us.


Request Reanalysis




Making Specific Corrections


For small fixes, use the correction tool:


Correction tool



  1. Select the wrong text
  2. Click "Suggest correction"
  3. Type the correct text
  4. Submit your correction



![Correction interface

](https://storage.crisp.chat/users/helpdesk/website/5ec8e994fe60b000/image_1efso3a.png)

Smart Correction Features


Podscan learns from corrections. If you fix a company name once, it might suggest the same fix elsewhere. The system remembers common corrections for:

  • Company names
  • Technical terms
  • People's names
  • Industry jargon


Best Practices


  1. Check context before correcting
  2. Include source links when relevant
  3. Group related corrections
  4. Mark priority fixes


Questions about corrections? Contact Podscan's support team for help.

Updated on: 06/11/2024

Was this article helpful?

Share your feedback

Cancel

Thank you!