Projects
Where: Projects › Projects
A project is a job you are delivering for a client. It holds the source language, the target languages, the service being performed and the workflow it follows. Tasks sit underneath it - typically one per target language per stage.
The project list. Status badges distinguish incoming Request projects from accepted work sitting at To Do.
Creating a project, step by step
Section titled “Creating a project, step by step”Project creation starts with a question rather than a form: which service is this? Awtomated then loads the form that service needs, so an interpreting assignment asks for a courtroom and a translation job asks for a CAT tool.
- Select Create in the top bar, then Project. The Create New Project dialog opens with a single field.
- Choose the service. Required. The note under the field says it plainly - the form will load based on the service you choose. Submit stays greyed out until you pick one.
- Wait for the form to load. The dialog expands into the full set of fields for that service.
- Fill in the fields that appear - they differ by service; the two tables below show a translation job and a court interpreting job.
- Attach the source files if the service takes them, by dragging them onto the upload area or using Compose.
- Select Submit. The project is created with an
APRID. Use Cancel to back out without creating anything.
Step 1. One field to start. Submit is disabled until a service is chosen.
Step 2. The list comes from Settings › Services - every service you have configured appears here.
Step 3, translation. The form now asks for everything a translation job needs.
| Field | What it is for |
|---|---|
| Project Name | Required. What the job is called in your lists. |
| Source / Target Language | The pair being delivered. |
| Upload Files | Drag and drop, or use Compose. Accepts CSV, XLSX, XLS, PDF, HTML, DOCX, JSON, XLF, XLIFF, TXT and PO. |
| Due Date | When the work is due back. |
| Reviewer | The team member who checks the delivered work. |
| Word Count | Defaults to 0. Fill it from the file analysis once you have run one. |
| CAT Tool | The tool the linguist should work in. |
| Machine Translation | Which MT engine to pre-translate with, if any. |
Step 3, court interpreting. Same dialog, entirely different questions.
| Field | What it is for |
|---|---|
| Hearing Date | When the interpreter must attend. |
| Judge | The presiding judge. |
| Link Court / Courtroom | Which court, and which room within it. |
| Case Number | The court’s own reference for the matter. |
| Hearing Type | The kind of hearing, which affects who is qualified to interpret. |
| LEP Party Role | The role of the limited-English-proficiency party - defendant, witness, and so on. |
What the columns mean
Section titled “What the columns mean”| Column | Meaning |
|---|---|
| Status | Request is work that has arrived but not been accepted. To Do is accepted work not yet started. |
| Source Language | The single language the material is written in. |
| Target Languages | Every language you are delivering into. A +1 badge means more languages than fit the column. |
| Project Workflow | The sequence of stages this project follows, taken from the service. |
Related: Creating a project · The project record · Tasks

