Fix translation readiness and consent problems

Resolve translation readiness problems: a quote estimate that will not generate, missing or unsaved consent, a setup blocker that keeps readiness from clearing, same-voice that stays unavailable, or live translation that has not turned on because provider and legal readiness are not complete.

Purpose

Diagnose and clear the common reasons translation readiness stays blocked — a quote estimate that will not produce, unsaved or missing consent, an unresolved setup blocker, or live translation that has not enabled — so localized work is ready to start once readiness is met.

Who this is for

Admins and creator managers diagnosing why translation readiness stays blocked or a quote estimate will not generate.

Prerequisites

A role that can manage translation readiness, such as owner, admin, or creator manager.
Agreement on the source and target languages for the content.
Speaker consent on hand for any same-voice or localized work.
The name of the project or content showing the blocker.

Steps

Open Translation Readiness for the project or content and read the message explaining what is blocked.
Confirm consent is recorded and that both a source and a target language are set, since a quote estimate needs all three.
Request the quote estimate again and review the units and any setup blockers it reports.
For each setup blocker, follow the readiness step it names, such as provider or legal review, before retrying.
For same-voice work, confirm the speaker's explicit opt-in is saved alongside provider readiness.
Confirm the estimate now shows units with no blockers, and remember live translation only begins once provider and legal readiness are complete.

Expected result

The reason readiness was blocked is resolved: consent and languages are saved, the quote estimate shows units with no outstanding blockers, and you understand that no live translation runs until provider and legal readiness are confirmed.

Verification

The quote estimate produces and shows units once consent and both languages are set.
Each setup blocker either clears or names the exact readiness step still required.
Saved consent and language preferences persist when you return, and no live translation has run prematurely.

If something goes wrong

A quote estimate still will not produce: Confirm consent is saved and that both a source and a target language are set; an estimate needs all three before it can be calculated.
A setup blocker keeps readiness from clearing: Read the blocker; it names the readiness step still required, such as provider or legal review, and readiness clears only once that step is complete.
Same-voice stays unavailable: Confirm the speaker's explicit opt-in is recorded and that provider readiness is in place; same-voice needs both before it can be offered.
The estimate looks fine but live translation has not started: Estimates are preparation only; live translation begins after provider and legal readiness are confirmed and may still need human review of the result.

Permissions

Recording consent, setting languages, and requesting estimates needs an owner, admin, or creator-manager role; clearing live translation also depends on provider and legal readiness, which is reviewed separately.

Support

If readiness stays blocked after these steps, ask your workspace admin to review provider and legal status first. LumenReach support can explain what readiness step remains without making any live translation call or exposing private or credential data.