Creating a project

Select New Project on the dashboard to open the creation wizard. It walks through four steps — project details, files and languages, translation setup, and assignment — and ends with a cost review before the project starts. Your progress is saved as a draft: if you close the wizard, the project card on the dashboard shows Continue and reopens it where you left off.

At the top of the wizard you choose the Project type: Standard (the document projects described here) or Continuous — an always-on project fed by your app or website; see Continuous localization. The type is fixed once the draft exists.

Step 1: Project Info

Two fields:

Project name — must be unique among your projects; the wizard checks availability as you leave the field.
Project deadline — typed as DD/MM/YYYY or picked from the calendar. A deadline without a time defaults to 17:00.

Select Upload Files to continue. This creates the draft.

Step 2: Upload Files

Add one or more source documents — click the upload box or drag files onto it. DOCX, PDF, XLSX, PPTX, ODT, TXT, XLIFF and more are supported. Each file can be removed again with its delete button.

For every file:

Source language — type the name or ISO code, or select Detect to identify it automatically.
Add target language — add as many targets as you need; each appears as a removable chip. A target that equals the source is flagged as a likely mistake but allowed (some documents mix languages).

Nothing is translated at this point — choosing target languages only records what you want. Translation starts when you activate the project, or earlier if you run machine translation during setup.

Step 3: Translation setup

How the project is machine-translated: the MT engine, the translation memories and glossaries per language pair, TM-reuse rules, the workflow, and an optional up-front MT run you can review before anything starts. Every setting has a sensible default, so you can pass straight through — the details are on the Translation setup page.

Select Create. The draft becomes a pending project and the final step appears.

Step 4: Assign translators

Decide who does the work — per file, target language, and workflow stage. You can also select Skip Assignment and do this later from the hub’s Team tab.

For each file you set the Workflow (defaulting to the project’s), the Stage being staffed, and a Stage deadline. The translator list shows candidates whose languages match the file’s pair, with their experience level, languages, a match percentage, and a View profile link.

Yourself — your own entry is marked (You); selecting it and choosing Assign Selected assigns you directly, with no offer.
Organization members — assigned as internal offers that are auto-accepted.
External freelancers — Assign Selected opens the offer form, where you set the rate (per word, character, or page), how long the offer stays valid, and an optional note. See Offers & assignment.
Auto-send offers — instead of picking by hand, let the platform offer each seat to the best-ranked candidates (you choose how many offers per seat); the first to accept wins. Preview offers shows exactly what would be sent before you commit.

Cost review and activation

Select Review & Confirm to open the cost review:

AI Translation Tokens — the estimated machine-translation usage per file and target, set against your plan’s allowance, with any estimated overage cost.
Translator Costs — the confirmed offers, per stage and target.
A Summary of both, plus an optional TM analysis and quote.

Select Confirm & Activate to start the project. Machine translation fills each target in the background; a file becomes editable in the hub once it has finished processing.