Finishing a project

A project is finished when every target has been through its workflow and the project manager has produced the delivery. This page follows that path from the last confirmed row to the downloadable file. The files themselves — their format, naming, and the XLIFF export — are described in Translated files & XLIFF.

When a target counts as done

Rows carry the state of the work, and a target is done when its rows are. Three rungs matter at the end (see the row states for the full list):

Confirmed — the assignee has confirmed the row at the current stage. Confirm All in the editor’s top bar confirms every remaining row in one go.
Ready for delivery — a project manager has approved the row for export. Marking a row ready records a human review of it.
Locked for delivery — sealed for production delivery. Locked rows are no longer edited.

For project managers the top bar shows one rung of this ladder at a time — Mark Ready, then Lock for Delivery — applying to the whole target; the row menu does the same for a single row.

Sending a row back a stage for rework clears any delivery approval it had; the assignee is notified that work was sent back.

Between stages, Advance Stage hands the target to the next step of the workflow once the current one is complete. Every workflow template ends with a project-manager review stage, so the last advance always lands with a PM. Stage gates can warn about or block on unresolved QA issues, and a PM can force past a block; see Stage advance.

Finalize Project

Finalize Project is the wizard that turns finished targets into a delivery. It opens from three places:

The editor’s top bar, once every target is locked for delivery.
The project card on your projects page — also available earlier, if you need to finalize with unfinished targets.
The project hub.

The wizard has three steps, or two on a project that never had a translator assignment:

Review. A readiness banner sums up the project: Project is ready to finalize when every row is locked or ready for delivery, Most targets ready when a few rows are still in earlier stages, or Translation in progress when some targets have no rows yet. Below it, the deadline, workflow, languages, and each file’s targets with their stage and any unresolved QA errors.

You can proceed with unfinished rows: they deliver their current text — the machine translation, or the source text where a row is empty.
Translator Payments. Every confirmed external assignment on the project, with its payment state. Held payments are released here when you accept the work; see Paying translators. Organization members assigned internally do not appear — there is nothing to pay.
Create. Create translated files rebuilds every document in its original format, then lists them under Available downloads. Rerun it whenever rows change. Export as XLIFF is here too, for external tools. Closing the wizard from this step marks the project complete. Continuous projects never complete — batches keep arriving.

What can hold delivery up

Unpaid assignments. Translated files cannot be created or downloaded, and translation memories cannot be synced, while a confirmed external assignment is still unpaid. The Delivery tab and the Create step say how many remain. When the payments are already held rather than outstanding, the message says so instead, and the outputs unlock once they are released or the project is marked complete. Continuous projects are never held up by payment.
Unresolved QA errors at error or critical severity are flagged in the Review step and can block downloads when the project’s export gates are on. Fix the rows in the editor or dismiss the findings first.
Held payments that need a decision. A payment that has been held for a long time is not a blocker, but the platform will remind you and, if you still do nothing, treat inaction as acceptance — see Paying translators.

After delivery

Downloads and rebuilds stay available on the hub’s Delivery tab for a completed project. A download whose rows were edited after it was created is marked Rows changed since creation.
Sync translation memories writes approved completed rows to the writable TMs attached to the project and reports what was written, deduplicated, in conflict, or skipped.
Re-open for editing only when the project needs more work; downloading never requires it. A re-opened project goes back to the active list.
Organization clients, where the client portal is in use, see the linked project’s progress and downloads there and can record their own acceptance of the delivery; see Organizations.

Deadlines

Standard projects carry a deadline of at most 60 days from creation, and a project with a funded translator payment can extend its deadline only within a fixed window after the charge. Shortening a deadline may be refused once a seat is confirmed. Continuous projects have no project deadline; their batch deals carry their own.